The board had status. It didn’t have proof.

At a glance

Organization

Large services enterprise, $1.6B revenue, with a board-visible transformation portfolio.

Situation

Seven major programs presenting $120M of aggregate benefit to governance bodies, reported through milestones, risk, budget and RAG status.

Complication

The board could establish whether initiatives were on schedule. It could not establish attribution, duplication, P&L arrival, assumption dependence or sustainability — which is the same as not knowing what should still be funded.

Entry point

Transformation Oversight with Executive Transformation Leadership. PROVE was the most visible stage.

Result

$120M reported → $79M attributable (model output) → $63M Board-committed after the assurance review → $46.6M modeled twelve-month realization in twelve months — 74.0% of committed value.

The board could see schedule. Not attribution.

Governance was not weak. The board received regular reporting, programs were represented at the right level, and the material was prepared competently. Directors could tell, with reasonable confidence, whether the seven programs were progressing on time and within budget.

The aggregate benefit figure of $120M had been built the way such figures usually are: each program contributed its own case, and the transformation office summed them for the governance pack. The total had never been reconciled across programs, because no forum owned that reconciliation.

Directors were therefore in the position of accepting a number they could neither test nor decompose — while carrying personal accountability for the results it implied.

Six questions the reporting could not answer

The gap was specific rather than general. There were six questions the board could not answer with the confidence it could answer schedule questions:

• How much of the benefit is truly attributable to the transformation? As opposed to market movement, pricing decisions or actions taken elsewhere.
• Where are benefits duplicated? Seven programs contributing separately built cases will overlap.
• Which benefits have reached the P&L or the operating result? As distinct from having been declared at closure.
• Which claims depend on assumptions that have not occurred? And what happens to the total if they do not.
• Which results are sustainable? Value that reverses in the following year is not value.
• What should still be funded? Which is the question the other five exist to answer.

Which transformation benefits can leadership actually defend?

The distinction underneath all six is the one this case turns on: delivery assurance is not value assurance. A program can be assured as delivered and remain entirely unassured as to value — and most governance reporting is built to answer the first question.

Why RAG reporting cannot close the gap

A RAG status is an assessment of confidence in delivery, made by the party delivering. It aggregates by taking the worst or the average of its components, which means a portfolio of seven programs can report amber indefinitely while the value question goes unasked.

Internal audit is a different but similarly bounded instrument: it tests whether controls and processes were followed, not whether the benefit was real. A program can pass audit and have contributed nothing traceable to the operating result.

The structural issue is ownership. Benefits are typically owned by programs, and programs close. Once a program closes, the benefit it declared has no owner, no measurement and no forum — which is precisely when most of the realization was supposed to occur.

A decision-grade view of transformation value

The review reconciled the portfolio’s benefit case to what could be attributed and evidenced, then separated what leadership was committing to from what it was hoping for.

Reconciliation across programs, not within them

The seven cases were read against one another rather than in sequence. Overlap only becomes visible that way — two programs claiming the same margin improvement through different mechanisms will each look sound in isolation.

Attribution tested rather than assumed

Each claim was examined for whether the transformation was the cause of the result. Where the value would have arrived regardless, or where the causal link could not be established, it was removed from the transformation’s account rather than from the forecast.

Evidence requirements applied before a claim counted

A benefit was not treated as expected until there was a defined route by which its arrival could later be shown. Claims without such a route were reclassified — not deleted, but no longer carried as commitments.

Commitment separated from aspiration

The attributable case of $79M was the model output. The Board then committed to $63M of it, retaining the $16M difference as upside with no governance weight attached. That step is a governance decision, not a modeled reserve or a probability weighting: there is no equation behind it, and presenting one would be exactly the failure this case exists to correct.

Realization monitored past delivery

Ownership of each committed benefit was assigned beyond program closure, with escalation defined for the point at which realization diverged from commitment.

From reported value to defensible value

The $41M is not a transformation loss. It is value the governance process stopped treating as sufficiently proven or commit-ready — which is the case.

Better capital allocation, not better spreadsheets

A third of the headline portfolio value was reclassified before leadership continued treating it as an expected result. Nothing was written off — the reclassified $41M moved out of the committed case and into upside, where it carried no governance weight and no external expectation. The further $16M between the $79M attributable and the $63M committed sits in the same place, held there by Board decision rather than by calculation.

The committed $63M was then monitored against evidence rather than declaration, with named owners who remained accountable after their program closed.

Funding decisions followed from that view. Two of the seven programs looked materially different once their benefit was read on an attributable basis, and the portfolio was re-weighted accordingly.

The results

Modeled twelve-month realization is $46.6M against the $63M commitment — 74.0%. Measured against the original $120M headline the same figure reads as 38.8%, which is the arithmetic that makes boards distrust transformation reporting in the first place. The $46.6M is a modeled realization outcome derived against the committed case; its proximity to published first-year realization benchmarks is incidental and no benchmark was used to set it.

The commercial outcome is improved capital allocation and governance credibility. A board that knows which $63M it is standing behind can defend it under scrutiny, and can also say what it is not standing behind — which is the harder and more valuable of the two positions.

Why the result held

Benefit ownership and measurement continued past delivery, so completion was never mistaken for realization. That single change accounts for most of the difference between a portfolio that validates at three-quarters of commitment and one that validates at a quarter.

And because the committed number had already survived attribution and evidence testing, putting the twelve-month figure to Finance validation is a confirmation rather than a negotiation.

What this means if you sit on the board

If the reporting answers whether programs are on schedule but not whether the benefit is attributable, the board has delivery assurance and is being asked to treat it as value assurance.

Evidence basis

The research is consistent on both points: realization falls well short of potential, and value continues to leak after implementation has finished. Both findings are cited as context for the pattern, not as the source of this case’s figures.

• McKinsey, Losing from day one: why even successful transformations fall short (December 2021 global survey, n=1,034). Respondents reporting success estimate realizing on average only 67% of the maximum financial benefit their transformations could have achieved, against approximately 37% at all other companies; 55% of value loss occurs during and after implementation.
• PMI, Establish Benefits Ownership and Accountability. States that many benefits are not seen until after delivery, and that ongoing benefits measurement and validation require an accountable owner — benefits ownership therefore has to continue beyond project completion.