The two clock problem…

Most transformation programmes don't fail because the strategy is wrong. They fail because the leader is running on two clocks at once - and trying to pretend they keep the same time.

Almost every senior leader I work with right now is running, simultaneously, two completely different kinds of work.

The first kind is transformation work. Replatform the technology. Adopt AI into the texture of how the business operates. Reshape the business model for what the next decade looks like, rather than what the last one rewarded. Build the bench. Knit the function back together after the last restructure. This work is measured in years. It compounds quietly. It shows up on the P&L eighteen to thirty-six months after the decisions that set it in motion. Most of it is invisible to anyone who is not in the room.

The second kind is quarterly work. The number. The board update. The cost line. The investor narrative. The performance review. The earnings call. The next thing that has to ship by month-end. This work is measured in weeks. It is, on a day-to-day basis, what determines whether you and your team are still in your jobs to see the transformation through.

Both are real. Both have to happen. Both deserve attention.

The trouble starts when leaders try to make them keep the same time.

The instinct is understandable. You have one calendar. One inbox. One head. The energy you bring on Monday morning has to cover all of it.

So you do what leaders trained inside listed companies have been trained to do: you try to convert transformation work into quarterly milestones, and quarterly work into transformation roadmaps. You ask the technology team to show progress on the replatform every ninety days. Y

ou ask the strategy team to plot a quarterly trajectory for the cultural shift. You ask the AI programme to demonstrate measurable impact by the next results call.

It does not hold.

Transformation work that is forced onto the quarterly clock turns into theatre.

The replatform produces a quarterly demo rather than a working platform. The AI programme produces a quarterly headline metric…seat licences activated…rather than the behaviour change that would actually move the curve. The culture work produces a quarterly engagement score that nudges up by half a point and tells you nothing about whether anyone has stopped going around the org chart to get decisions made. The board is reassured. The work is undone.

Quarterly work that is forced onto the transformation clock fares no better.

The decision the business needs this quarter gets routed through a multi-year strategic frame. The hiring decision that needed to be made on Tuesday is still being workshopped for cultural fit on Friday. The product change the desk needed last week is still being held up by a roadmap conversation about what kind of product organisation we are becoming. Speed dies. The company starts to feel slow in ways that show up in retention conversations, exit interviews, and the slow drip of high performers leaving for places where decisions still get made.

Both clocks suffer. The leader, running between them, burns out trying to make a single rhythm out of two.

What I have seen actually work, across twenty-five years in markets, product, fintech and ventures of my own, is the opposite of synchronisation. It is the deliberate, sometimes uncomfortable practice of running the two clocks as separate rhythms - protecting the transformation clock from the quarterly one, ruthlessly.

In practice this means a few specific things.

It means carving out actual time for transformation work that the quarterly cycle is not allowed to interrupt. Not annual offsites. Not the strategy day. Recurring and ruthlessly defended, weekly or monthly time where the question on the table is the long arc, not the short one. Defending the time is the hard part. The quarterly clock will always find a reason to invade the transformation hour. You have to be the leader who refuses to let it.

It means funding transformation work outside the quarterly P&L wherever possible. Treating it as the strategic capex it actually is, not as a line item that has to demonstrate quarterly return. If your AI programme has to justify itself every ninety days against EBITDA impact, it will produce ninety-day theatr, because that is the system you have built.

It means running two reporting rhythms, not one. The quarterly business review is one thing. The transformation review is another. Different cadences, different metrics, different conversations. Forcing them into the same meeting forces them into the same clock, and you are back where you started.

And it means noticing, every week, which clock is winning. Most leaders, in most weeks, are running entirely on the quarterly clock and telling themselves they are doing transformation work.

The honest test is simple: how much of your time, this week, went on work that will show up on the P&L in the next three months? How much went on work that will show up eighteen to thirty-six months from now?

If the answer to the second question is less than twenty per cent, the transformation is being slowly eaten by the urgent. The strategy is still right. The execution is still happening. But the long arc is bending closer to the short one with every week that passes.

The leaders who hit their stretch numbers through reinvention - the ones who do not get caught between a quarterly miss and a transformation that never quite materialised - are not the ones working hardest.

They are the ones working smart, who refuse to let the urgent work consume the important work.

The discipline is unglamorous. It is mostly about saying no.

This is in my experience, the single biggest determinant of whether a leader looks back at this period in three years' time and sees a sucessful transformation…or not…

Be honest, which clock is winning in your business right now?