Could you change gear in time?

The third discipline of Requisite Pace: preserving the ability to become something different

Blog 4 in the Requisite Pace series

Most operating-model work asks a simple question:

Does the current arrangement work?

It is a sensible question. Steady-state coherence matters. If the structure is broken today, it has to be fixed today.

But it is the wrong place to start for the environment most leadership teams are now operating in.

The harder question — the one almost no operating-model work asks — is this:

If conditions shifted, could you become something different in the time the world allowed?

That is the question Lens 3 is built around. It is also where most organisations discover they have spent years optimising themselves into a shape they can no longer change.

Where this sits in the series

The series has worked through three disciplines. Lens 1, choose the clocks: decide which external rhythms should shape you; the measure is Mean Time to Know. Lens 2, design the gears: make the operating model coherent across multiple speeds; the measure is Mean Time to Decide. Lens 3, preserve the ability to shift: keep the capacity to reconfigure when the arrangement itself has to change; the measure is Mean Time to Change.

Sensing, deciding, reconfiguring. Together the three measures form one cycle: how long, end to end, from a signal appearing in the world to the organisation having actually changed in response.

Adequacy is not sufficiency

Lens 3 depends on a distinction most operating-model work misses.

Adequacy is enough to run today. The organisation operates at multiple speeds matched to current conditions. Hierarchy coordinates, buffers absorb friction, governance runs at the right cadences. Most leadership teams that believe they have “enough slack” are measuring against this standard. It is necessary, but it only holds while today’s operating assumptions hold.

Sufficiency is the ability to become something different — before circumstances force you to.

That requires more than spare capacity. It requires protected degrees of freedom: budget that can move, contracts that can flex, people who can be redeployed, architectures that can decouple, and governance that can accelerate without losing control. Sufficiency is not fat. It is optionality made operational — movable capacity deliberately protected from being consumed by today’s model.

Almost every “we have enough slack” claim I have tested with a leadership team has turned out to be an adequacy claim. The sufficiency question had never been asked.

Tactical agility can mask systemic rigidity. The teams most fluent at optimising within the current model are often the most resistant to changing the model itself — so an organisation can look adaptive on every dashboard and still be merely adequate.

The measure: Mean Time to Change

For each critical coupling, Lens 3 introduces a measure: Mean Time to Change.

MTTC is the time from a committed decision to a changed operating reality. Not the time to agree the strategy. Not the time to approve the plan. The time until the organisation is actually different — processes redesigned, contracts unwound, capabilities redeployed, interfaces reconfigured, and the work flowing in a new way.

Consider a bank deciding to launch a new digital proposition. The board does see a number: strategy approval in two weeks, delivery “within the year.” What it does not see is the real one. Rebuilding the procurement arrangements, the technology architecture, the risk models, the incentives and the customer journeys the proposition actually depends on takes eighteen months. The estimate was the number on the slide. Eighteen months was the number that mattered.

The gap is not an accident. MTTC is almost always estimated optimistically — the plan prices the decision, not the reconfiguration — and the actual elapsed time is almost never measured, because by the time the organisation is genuinely different the attention has moved to the next priority and nobody goes back to check. So the error never corrects. The next strategy is approved against the same optimistic instinct, and the gap between the number the board approves and the time the organisation actually takes stays invisible — not because it cannot be seen, but because no one is looking by the time it could be.

Critical couplings are the relationships that must move together if the organisation is to change shape. For example:

• customer promise ↔ fulfilment capability

• pricing ↔ operating economics

• product ↔ platform

• risk appetite ↔ decision rights

Together with the other two measures it closes the cycle:

MTTK + MTTD + MTTC = total time from signal to changed state.

Compare that total to the rate at which your most critical couplings are shifting. If the cycle is longer than the shift, the organisation is structurally unable to adapt in time.

That is the sufficiency test. Stated formally:

Reconfiguration capacity is sufficient if the organisation can reconfigure its top N critical couplings within time T, without breaking the core business.

N and T are context-specific. But forcing those two numbers onto the table changes the conversation. Sufficient is no longer a feeling. It is arithmetic.

Why MTTC stretches: pace debt

MTTC becomes longer than leaders expect for a reason, and the reason has a name: pace debt.

Pace debt is the accumulated cost of running at the wrong speed for too long — the workaround that became permanent, the exception that never expired, the interface nobody redesigned, the shadow process that grew up because the official one could not move at the rate the work required. Each is a small, local accommodation to an unresolved pace mismatch. Individually, many are rational. Collectively, they harden into the structure of the organisation.

It accumulates wherever pace mismatches go unresolved — in governance, in structure, in capability, in technology, and above all in the interfaces between fast and slow. The forms compound: unaddressed technical constraints limit interface redesign; structural debt erodes capability over time; slow governance breeds workaround interfaces that become debt in their own right.

Today’s misdesigned interfaces become tomorrow’s frozen core.

The longer pace debt accumulates, the longer it takes to change anything — which is precisely the point at which Lens 3 becomes urgent, and the point at which it becomes hardest.

The governing tension

There is a real argument against everything above.

If we don’t optimise for today, we die today. We are not in a position to carry optionality for some hypothetical future shift.

The argument is not wrong. It is only half the picture.

Efficiency matters. Lean works. Removing unnecessary cost is part of the job, and unbounded slack is wasteful — the research on organisational slack has long pointed to a non-linear relationship, where too little capacity is paralysing and too much becomes complacent or corrosive.

The point is not to argue against efficiency.

The point is that efficiency without reconfiguration capacity is a slow-motion exit.

The reserves that preserve the ability to shift have to be deliberate, bounded, and protected. If they are described as “spare”, “underutilised”, or “fat”, they will be cut as waste in the next efficiency drive — at exactly the wrong moment, on exactly the wrong logic. The better language is optionality, movable capacity, and protected degrees of freedom. Lock-in needs to be made visible as a pace-constraining liability, not tolerated as the cost of doing business until it becomes the cost of failure.

Two failure archetypes

Optimisation lock-in. The organisation has optimised so thoroughly for today’s conditions that it cannot reconfigure when they change. Every efficiency improvement has removed a degree of freedom. Contracts are tight, structures lean, governance calibrated precisely for current requirements. The result is exquisitely efficient at what the organisation currently does, and unable to become anything else: a gearbox welded into top gear — superbly efficient on the open road, and unable to change gear, slow down, and turn a corner when the road bends.

Adaptive edge / frozen core. Customer-facing teams, engineers, analysts and local leaders see the shift early. The centre cannot evolve fast enough to act on it: core platform decisions, capital allocation, incentive structures and executive governance are all calibrated for the existing model. Sensing is fast; transformation capacity is slow. The adaptive edge is not the problem. The problem is that what the edge learns cannot be translated into core reconfiguration quickly enough.

The human symptoms are recognisable: transformation fatigue, the sense that change initiatives never quite land, the inability to pivot even when everyone agrees the pivot is necessary. These are not motivational problems. They are structural ones.

The diagnostic conversation

Reconfiguration capacity is not a single number. It has to be read across five dimensions — resource, temporal, structural, governance, and sensing and capability — because a constraint in any one of them can stop a change that all the others would allow. A single “agility” score hides exactly the dimension that will defeat you.

From there, a Lens 3 conversation has a particular shape. The questions are simple. The honest answers usually surprise the leadership team.

• For our most critical couplings, how long would it take to materially reconfigure — not to plan to, but to actually have done so?

• Where have we mistaken adequacy for sufficiency?

• Where has our current speed quietly become the only speed we can run at?

• Where is pace debt compounding fastest?

• Where are we optimising for yesterday so tightly that we are consuming the capacity we will need to become something different?

A practical way to start: choose three critical couplings and put numbers against them. How long would the external shift allow? How long would we take to reconfigure? Which locked-in dimension sets the real constraint? What movable capacity must be protected or rebuilt now?

The questions that produce silence are the highest-priority findings.

Closing the cycle

Lens 1 chose the clocks. Lens 2 designed the gears. Lens 3 preserves the capacity to redesign both.

These are not a sequence to be run once. They are a cycle to be returned to. Couplings shift, profiles age, debt accumulates; the arrangement that fits today is, by definition, the one that will need revising next.

That cycle runs in one of two directions.

In the viability cycle, the organisation resists the pull to optimise for yesterday. It couples to the dynamics that will matter tomorrow, keeps clean interfaces between domains that run at different speeds, and protects reconfiguration capacity as a deliberate reserve. Each successful adaptation builds the confidence and capability to do it again. The organisation learns to change gear.

In the fragility cycle, it optimises for current conditions. Slack is cut as waste, contracts tighten, governance is calibrated precisely for today, and every efficiency gain removes a degree of freedom. Pace debt accumulates at the interfaces, invisible until conditions shift — and when they do, the organisation cannot reconfigure fast enough, so the crisis forces the costly, disruptive transformation that designed-in capacity would have made routine.

The difference between the two is not effort. It is whether the cycle is run deliberately.

A final question

If a material shift in your environment landed tomorrow — not a hypothetical one, but the one your strategy team has been quietly worried about — what is your honest estimate of the time required for your operating model to actually be different?

Not the plan. Not the announcement. Different.

If that estimate is longer than the time the shift will allow, you do not only have a strategic problem. You have a Lens 3 problem.

And the work of solving it does not begin when the shift arrives. By then it is too late. It begins now, in the deliberate decision not to spend every degree of freedom optimising for yesterday.

Speed isn’t the issue. Timing is.