Why these budgets are structurally optimistic
Transformation business cases are assembled by aggregation: each workstream contributes a benefits estimate, the totals are added, and the sum acquires an authority that none of its parts deserve. The people producing the estimates are the people who want the programme approved, the benefits sit years beyond the tenure of many of the estimators, and the costs of the first phase are shaped to fit under whatever threshold makes approval smooth. None of this requires bad faith. It is what happens when advocacy and analysis are performed by the same team, and it is why the aggregate case should be treated as an opening position rather than a forecast.
The numbers that tend to be missing
Look for the run cost: what the transformed organisation costs to operate after the programme team disbands, including the licences, the upgraded support contracts and the specialist roles that did not exist before. Look for the benefit owners: named line executives whose budgets will be reduced when the savings land, as opposed to a benefits-realisation office that tracks but does not own. Look for the backfill: transformation staffed by seconding your best operators means the base business is funding the programme twice. And look for the dependency chain: how many of the benefit lines silently assume that a different workstream, or a different programme entirely, delivers on time.
Conditions worth attaching to approval
- Fund the programme in tranches released against evidence, not milestones. A milestone can be declared met; a benefit either appears in a budget line or it does not.
- Require every material benefit to be signed by the line executive whose future budget will absorb it, before the money moves.
- Insist the business case shows the do-nothing trajectory honestly, including what deteriorates, so the programme is compared against reality rather than against a strawman.
- Cap the proportion of spend that can go to external partners in each tranche, forcing the capability question into the open early.
- Agree now what evidence would justify stopping at each gate, so a future decision to halt is an act of governance rather than an admission of failure.
Where to apply real pressure before signing
Press hardest on the middle of the plan. The first six months are usually well designed because they were needed for approval, and the end state is a vision nobody can falsify. The middle years are where transformations actually live or die: the legacy systems must keep running alongside the new build, the change fatigue arrives, and the original sponsor may have moved on. They are also typically the thinnest section of the document. Ask what the programme looks like in month twenty if benefits are at sixty per cent of plan, and whether the governance as designed would detect that honestly or would be reporting amber and re-baselining.
The value of eyes that have watched one fail
Executives who have lived through a transformation that missed its case read these documents with a specific kind of scepticism: they go straight to the benefit phasing, the attrition assumptions and the integrator dependency, because that is where their own programme broke. Bringing that experience to bear before approval typically produces one of two results. Either the case is restructured (smaller first commitment, harder gates, named benefit owners) or the approvers proceed with the original shape but with an honest view of the odds. Both outcomes are better than the confident unanimity that internal alignment tends to produce, because internal alignment can hide shared blind spots as easily as it signals readiness.
