where programmes actually crack
By delivery, it’s already broken.
When a transformation programme fails, the postmortem almost always focuses on delivery — the timeline slipped, the team lost momentum, stakeholders disengaged somewhere in month three. All of that is usually true. None of it is usually the actual cause. In our experience, the programmes that fail were, in a real sense, already failing before a single week of delivery had happened. The fatal mistakes were made in planning, and delivery simply made them visible.
Why the planning phase is where it actually goes wrong
Planning gets less scrutiny than delivery because it produces fewer visible problems in the moment. A rushed or shallow planning phase doesn’t look like failure — it looks like efficiency, like a team that’s eager to get moving rather than stuck in endless preparation. The costs of weak planning are almost entirely deferred, which is exactly why they’re so easy to underweight when the programme is being set up.
By the time those costs surface — in month two or three of delivery, when the team discovers the scope was wrong, or the sponsor never actually had the authority everyone assumed, or the success metric nobody quite agreed on means different things to different people — it looks like a delivery problem, because that’s where the symptom appeared. The actual cause is usually weeks earlier, in decisions nobody scrutinised at the time because they didn’t yet have visible consequences.
The specific mistakes that doom a programme early
A handful of planning-phase failures show up again and again, and each is avoidable — if it’s caught before delivery starts rather than during it.
The success metric was never made concrete. “Improve operational efficiency” or “modernise the sales process” sound like objectives but function as nothing, because nobody can point to a specific number and say definitively whether the programme succeeded. Without a concrete, agreed metric set at the outset, a programme drifts toward whatever feels like progress at the time — which is a very different thing from actually achieving what it set out to achieve.
The real sponsor was never identified — or the assumed one didn’t have real authority. Every transformation programme needs someone inside the business who can make binding decisions when priorities conflict, resources are contested, or a change meets internal resistance. Programmes frequently launch with an enthusiastic senior stakeholder who turns out, once real friction appears, not to have the authority to actually force a resolution. That gap is invisible on day one and catastrophic by week six.
The scope tried to solve everything adjacent to the actual problem. Ambition during planning is seductive — while the programme is still theoretical, it’s easy to agree that solving three related problems is barely more work than solving one. In practice, scope that broad rarely gets fully delivered; it gets partially delivered across several fronts, none of them completed well enough to count as genuine transformation.
Nobody stress-tested whether the organisation could actually absorb the change. A technically sound plan can still fail if the business doesn’t have the capacity, appetite, or timing to absorb it — a change landing during a period of other major disruption, or requiring buy-in from a team that’s already stretched thin. This is rarely assessed honestly during planning, because raising it can feel like introducing doubt into a programme everyone wants to believe in.
The plan had no defined checkpoints for admitting something needs to change. Programmes built without honest, scheduled moments to ask “is this still the right approach” tend to continue on the original plan long after evidence suggests it should adapt — not because anyone’s being stubborn, but because there was never a structured moment built in for that question to be asked seriously.
Why these mistakes are so hard to catch in the moment
Every one of these failures is easy to see in hindsight and strangely difficult to catch while planning is actually happening. Partly this is optimism — everyone involved wants the programme to succeed, and scrutinising the plan too hard can feel like working against that shared goal. Partly it’s momentum — once a programme has been proposed and generated enthusiasm, questioning its foundational assumptions can feel like it risks losing that energy entirely.
But the discomfort of asking hard questions during planning is trivial compared to the cost of discovering the same gaps three months into delivery, with budget spent, teams committed, and a much harder conversation about whether to continue, pivot, or abandon something that’s already publicly underway.
What good planning actually catches
A properly stress-tested plan names a concrete, measurable success metric before anyone starts. It identifies the actual decision-maker and confirms, honestly, that they hold real authority to resolve conflicts when they arise. It resists the temptation to expand scope to everything adjacent, in favour of a tightly bounded set of changes that can genuinely be completed. And it builds in honest checkpoints — moments where the plan can be revised in light of what’s actually being learned, rather than defended regardless of the evidence.
None of this guarantees success. But it removes the specific, recurring, and entirely avoidable reasons transformation programmes fail — the ones that were never really about delivery execution at all, however much the postmortem ends up focusing there.
If a transformation effort in your business is struggling in delivery, it’s worth checking whether the actual problem was set weeks earlier, in planning. See how our Transformation Programmes model works →
