Every organisation has a resting cadence, and programmes do not change it
Jesper E. Thomsen · 16 October 2026
Organisations run at a speed that is produced, all the time, by how they are put together, and they go back to it once the extra pressure is gone. That speed changes for good when ownership changes, and hardly anywhere else.
Most transformation work starts from the question of how to get the organisation moving. I think the better question is what keeps producing the speed it already has, and whether that can be touched at all.
That is a different question from removing blockers. Blocker language assumes there is a faster organisation underneath, held back by things in the way. If that were true, removing them would work permanently. It does not. Whatever you remove comes back under another name, because the conditions that produced it are still there. The speed you see is the organisation working exactly as it is built. There is no faster version waiting to be released. There is only a different organisation, which would have to be built. Blockers are things standing in the way of the building. Cadence is the ground it stands on.
Two definitions
Cadence is the time from something that calls for a decision to a resource being committed, measured on the decisions that determine whether the organisation adapts. Recognising a problem has its own clock, and so does executing once the decision is taken. The clock that matters is commitment.
Resting cadence is the cadence the organisation goes back to once the extra pressure is off. Every organisation has one. A crisis, a new CEO, a transformation office or a consulting engagement can move the organisation away from it for a while. How far it moves is displacement. How long it takes to come back is the reversion half-life. Neither of those is a change in resting cadence. Only a change in what produces it is.
Efficiency is something else again: output per unit of input inside one process. It gets mistaken for cadence all the time.
What holds the resting cadence in place
Resting cadence is not something an organisation inherits and then carries. It is produced continuously by a set of things that reinforce each other: who has the right to decide and how many layers approve, the meeting and reporting calendar, the budget cycle and how resources get allocated, incentives, who gets promoted and who succeeds whom, what information is available to whom, how much risk and failure is tolerated, who owns the company, and who actually holds power. I call these the generators.
Four things follow from that.
Speeds inside the organisation do not add up. Cadence is set by the slowest element on the path every real decision has to pass through, and that path is normally governance. Cutting a development cycle to one week changes nothing if the board approves every six weeks. That is a gain in efficiency, not in speed. It is also why transformation programmes can report real improvements and still change nothing.
What builds up over time is apparatus. Adding a control costs one incident and one decision. Removing it needs somebody to put their name on the risk that remains, and nobody volunteers. In the meantime, behaviour routes around the controls. The organisation gets formally slower and behaves the same, and the gap widens the older it gets and the more incidents it has been through. The end state is easy to recognise: heavy governance that eats time without governing anything, while the real decisions travel through channels that are on nobody's org chart.
So cadence does not live in the formal apparatus. That is the part you can redesign, and it does not hold. It lives in the informal system, which you cannot reach directly by design.
And the whole set-up reproduces itself through people. Promotion and succession favour those who are comfortable at the current pace, and who read faster colleagues as reckless. Leaders get pulled into the organisation's rhythm at least as much as the other way round.
Why a faster unit inside the company does not spread
A unit running at a different cadence inside the organisation gets rejected rather than absorbed, and the better it performs, the more likely the rejection. Putting it in a separate structure does not solve that. It just makes the rejection cleaner.
I have run both versions. At Maersk, X-Leap in 2010 and the later Simplification programme were both placed outside the line, both delivered, and both were wound down once they came to be seen as running on the side. In both cases the break point was a fast IT organisation up against legacy waterfall IT. The faster body did not lose on performance. It lost on cadence.
When resting cadence does change
The element that binds the organisation's speed is owned by people whose authority comes from it. Changing it means giving up your own authority, and that proposal does not come from inside the system. Cadence can be changed, but not by the people who are usually asked to change it.
Resting cadence changes when ownership of the binding element changes, when the organisation's link to its environment changes, or when slack is destroyed to the point where the environment's clock becomes the binding one. Attention, pressure, programmes and persuasion do not change it.
That puts durable change at ownership events and hardly anywhere else: buyout, IPO, delisting, merger, an activist coming in, a founder leaving, a forced recapitalisation. Near-death belongs to that list rather than being a separate thing. A crisis changes pace because it forces an ownership event and burns the slack that was covering the mismatch, not because it motivates people.
Private equity is the strongest confirming case, and a better one than the celebrated turnarounds because it is repeatable. PE changes the operating cadence of ordinary companies without exceptional leadership, by changing the reporting calendar, the capital calendar, the board, the incentives and the slack at the same time, from outside. It also reaches the informal system, because it changes who holds power and who is still in the building.
The same logic explains why domain hires fail on cadence. A Chief Digital Officer brought in for digital expertise has no authority over anything that produces the organisation's speed. I made this argument when two such roles were being designed, and I still think the outside hires were the wrong answer. Understanding how the organisation works is the qualification that binds. Understanding the domain is not.
What this means for strategy
A strategy that needs a faster cadence than the current one is incomplete until it says how the generators will change. Cadence is a constraint you have to deal with before the strategy, not an execution problem you deal with after. A board reading a plan that assumes a speed the organisation has never sustained should ask which generator changes, who owns that change, and what risk moves to whom.
Fast is not better
Cadence is calibrated to the environment and the risk profile. Pharma and financial organisations are often slow for good reason, because the cost of a mistake shows up over long horizons. Other organisations carry too much risk appetite, and what they need is to slow down. The argument runs both ways and takes no position on which direction is right. It explains why speed is stable. The test of whether anything has changed is simple: does the organisation keep operating differently after the extra pressure is gone.