3. Why Transitions Fail Before Implementation Begins
Most failed transitions are blamed on execution:
the plan was sound
the strategy made sense
the people were capable
we’re told that the organisation didn’t follow through
In practice, many transitions fail long before implementation is even relevant. They fail at the point where the situation is framed.
The invisible failure
Transitions create urgency. Something has changed, or is about to. Time feels compressed. Options appear to be closing.
In that environment, there is strong pressure to move.
Plans are drafted quickly. Solutions are proposed. Advisors are engaged. Activity becomes a proxy for progress.
What is often skipped is the harder, quieter work of agreeing on what problem is actually being solved. When the framing is wrong, execution cannot redeem it.
How mis-framing happens
Mis-framing rarely looks like confusion. It usually looks like alignment: people agree on language, timelines, and next steps. Meetings are productive. Outputs are generated.
But beneath that apparent coherence, one or more of the following is true:
different leaders are solving different problems under the same banner
urgency is driving action before consequences are understood
existing plans are being retrofitted to new conditions
difficult trade-offs are being deferred in favour of momentum
At this point, the transition feels active but remains unresolved.
The cost of premature solutions
Solutions introduced before the problem is clearly defined tend to harden quickly: - Resources are allocated. Roles are assigned. Reputations become attached.
Revisiting the framing now feels disruptive rather than responsible.
This is why organisations often persist with approaches that no longer fit. The cost of stopping feels higher than the cost of continuing — even when the mismatch is visible.
Execution becomes increasingly strained, not because people are failing, but because they are executing against the wrong premise.
What effective transitions do differently
Transitions that hold tend to pause earlier, not later. They create space — brief but deliberate — to resolve a small number of foundational questions:
what has actually changed, and what has not?
which risks are real, and which are inherited assumptions?
what decision will shape the next phase more than all others?
what are we choosing not to optimise for?
These questions are uncomfortable because they slow visible progress. But. They are effective because they prevent misdirected effort from accumulating cost.
The role of leadership here
Leadership in transition is often described as decisiveness.
More accurately, it is restraint.
The willingness to delay solutions until the problem is clearly understood.
The discipline to resist activity that creates the illusion of control.
The confidence to say, “We are not ready to act yet — and that is the responsible position.”
This is not hesitation. It is sequencing.
Implementation as a downstream activity
When framing is sound, implementation becomes materially easier: disagreement narrows; trade-offs are explicit; execution aligns without constant reinforcement.
When framing is weak, implementation absorbs the conflict. It becomes the place where unresolved questions surface — too late, and at higher cost.
At that point, execution is blamed for a failure it did not cause.
A final distinction
Transitions do not fail because organisations move too slowly. They fail because they move before they are oriented, before all the key pieces are aligned.
Clarity at the outset is not a luxury. Clarity is what determines whether effort compounds or corrodes.