Transformation value is lost one decision at a time

Every large transformation begins with a promise. A business case sets out what the organization will gain, by when and at what cost, and a board or a ministry commits the investment on that basis. Then delivery starts, and attention moves to the plan. Months or years later the platforms are live, the milestones have turned green and the closing report is in draft. Somewhere along the way, much of the value that justified the investment has gone missing, and no one can say exactly when it left.

We call this the value gap: the distance between the value an organization approved and the value it actually banks. In our work with ministries and enterprises across the Kingdom, we see it open in strikingly similar ways. It accumulates through a long run of reasonable decisions, each taken by capable people under pressure, and none of them priced in value.

As Vision 2030 programs run at giga-project scale, and boards and ministries press harder on returns, the gap has become a leadership question. Closing it requires something simpler than a new methodology, and harder to sustain: leaders who treat the benefits case as the program’s steering instrument, from the first statement of ambition until the gains are part of how the organization runs.

01Where the value goes

The first leak happens at approval. Business cases are written to win funding, and once funding is won the document has done its job. It is filed, and the program is managed against scope, schedule and budget, the measures a delivery team can control and report. Benefits become a matter for the closing review.

From there, value drains through ordinary choices. A module is deferred to protect a go-live date. An integration is simplified to contain cost. A process redesign is shelved because the business is too stretched to absorb it this year. Each trade looks sensible in the steering committee, and each is logged as a change to scope or timeline. Almost none is logged as a change to the value the program will deliver, because no one in the room answers for that number.

Then comes go-live, which most programs treat as the finish line. The program team disbands, the integrators move on and the operating units inherit a new system with their old habits intact. Much of the value sits exactly here, because it depends on someone stopping something: retiring a legacy platform, closing a manual workaround, releasing a budget line, redeploying a team. Stopping is harder than starting, and it is the work most often left without a sponsor just as it should begin.

02Benefits need owners outside the program

The most consequential decision in a benefits case is who owns each benefit. In too many programs the answer is the program, which in practice means no one. A program director can deliver capability. Only the executive who runs the affected operation can turn it into a lower unit cost, a smaller budget or a shorter wait for beneficiaries.

We ask leaders to assign every material benefit to a named executive in the line, and to write it into that executive’s targets and budget before the program starts. The conversation changes at once. A benefit owner who will carry a reduced budget next year takes a close interest in whether the design will produce the saving. A director general whose service targets depend on a new platform makes sure the front line is ready to use it.

Ownership also forces candor early. When executives must sign for a benefit, inflated estimates shrink, and the case that emerges is smaller and far more credible. A modest number that someone will defend is a better starting point than an ambitious one that no one will.

03Fix the baseline before you build

A benefit cannot be proven if no one agreed where it started. Yet baselines are routinely deferred, on the grounds that the data is imperfect and the team is busy mobilizing. By the time anyone returns to the question, the old process has partly changed, the data has moved, and every claim of improvement becomes a negotiation.

Before design is frozen, agree each benefit’s baseline, definition and source of measurement with the finance function and the benefit owner, and record them in a single register that both sign. Finance’s signature matters for a practical reason: a benefit that finance never accepted will be disputed the moment it is claimed. Where the data is weak, agree a proxy and say so plainly. An approximate baseline that everyone accepts is worth more than a precise one that arrives after the fact. For cost benefits, tie the baseline to the budget lines that will actually change, so that a reported saving can be taken out of next year’s budget. For service benefits, measure the experience of beneficiaries and employees as they live it today, before the new design reshapes it.

04Run value on the same cadence as delivery

Programs are governed by rhythm: steering committees, status reports and risk escalations on a fixed cycle. Value earns attention only when it sits inside that rhythm with equal weight. A benefits review held once a year, or only at stage gates, arrives too late to change a decision.

We recommend a monthly value review, chaired by the executive sponsor and attended by the benefit owners, kept separate from delivery status and fed by it. Each session answers the same short set of questions:

• Which benefits moved against the agreed baseline since the last review, and which stalled.
• Which scope, schedule or design decisions changed the value at stake, and who approved each trade.
• Where adoption is trailing the release plan, since capability that goes unused returns nothing.
• Which benefit owners need a decision from the executive team to stay on course.

One rule does more than any dashboard: no change request is approved without a statement of its effect on the benefits case. Once teams are used to it, the rule costs little time, and it puts every trade-off in front of the people who will live with the result.

05The program ends when the value lands

Most program dashboards report activity: milestones met, budget consumed, users trained. These measures are necessary and insufficient. Boards and ministers should ask to see value realized against value committed, benefit by benefit, drawn from the financial and service data the business already trusts. That report is uncomfortable in the early months, because realized value always trails delivery. The discomfort is useful. It holds leadership attention on the outcome while there is still time to act.

Realized-value reporting also moves the finish line. A transformation is complete when its benefits are embedded in budgets, targets and everyday operations, and that point usually arrives well after the last release. We advise clients to keep a small value function in place, often inside the transformation office, until the benefit owners close the case themselves. The realized gains then become the new baseline, and the organization sets its next ambition from evidence.

Closing the value gap takes executive nerve. Leaders must name owners, commit to baselines, hear unwelcome numbers every month and keep governance in place after the celebrations end. Organizations that hold that line gain more than one successful program. They become institutions that know how to turn an approved ambition into results, and can do it again.