The business case is the most cited and least examined document in a transformation. It justifies the spend. It anchors the governance pack. It sets the savings targets. And then, somewhere between approval and go-live, it is quietly filed.
By month six, nobody is comparing actual outcomes to the original assumptions. By month twelve, most of the people who wrote it have moved on. By month twenty-four, the case has become a historical artefact — referenced by no one, owned by no one, and answering for nothing.
A business case that survives contact with reality without revision wasn't a business case. It was a sales document.
The Frozen Business Case
Business cases are built at the point of maximum optimism and minimum information. That is structural, not a criticism — at approval stage, the programme is mostly hypothesis. The assumptions are reasonable. The numbers are defensible. The case is fit for its purpose: securing investment.
The mistake is treating that purpose as the whole purpose. Once approved, most cases stop being live documents — which is precisely when they should start. A business case is only useful as a baseline if something later is measured against it. In most programmes, nothing later is.
Why Nobody Revisits It
Revisiting the case creates exposure. The conditions that make organisations rational individually make them dysfunctional collectively.
Sponsors don't want to reopen assumptions that haven't held — doing so retroactively questions the decision to invest. Programme leads don't want to surface savings that aren't tracking — doing so frames their delivery as underperforming. The PMO has moved on to the next phase, and the case lives in nobody's current scope. Finance signed off on the numbers but doesn't own the operational reality behind them.
So silence becomes institutionally rational. It is also organisationally corrosive — because in the absence of revisiting, the case quietly disconnects from the programme, and the programme quietly disconnects from value.
What Gets Measured Instead
The substitution is subtle and rarely challenged. Activity replaces outcome.
- POs raised, suppliers onboarded, contracts migrated. Easy to count. Easy to report green. None are benefits.
- System utilisation rates. A measure of usage, not value. A platform can be heavily used and deliver nothing the business case promised.
- Compliance percentages. Indicator of process discipline, not realised savings.
- Cycle time reductions. Meaningful only if the time saved is doing something more valuable. Usually that question goes unasked.
Each of these was, in the original case, an input assumed to produce benefits. Reported as benefits themselves, they make the programme look healthy while the actual value gap widens. The substitution happens quietly, and is rarely challenged because the people most able to challenge it are the people least incentivised to.
What Good Looks Like
The benefits case is revisited at structured intervals: 90 days post-go-live, six months, twelve months, and annually thereafter. Each revisit tests original assumptions against actual behaviour — adoption rates, category-level savings, exception volumes, cycle realities — and produces a written variance with explanation.
Variances are surfaced, not buried. Where assumptions haven't held, the case is updated and the governance pack reflects the new baseline. Where they have held, that's the evidence that the programme is delivering — far more credible than activity dashboards.
Most importantly, the revisit is owned. A named principal — typically the executive sponsor jointly with finance — is accountable for the case remaining a live document. Without ownership, every other discipline collapses back to silence.
When did you last open the original business case for your most recent S2P transformation? When did the sponsor? If neither answer is within the last six months, the case has stopped doing the work it was written to do.
Was your transformation justified — or was it merely approved?