Insights

Change Management · The leadership decisions behind transformation

Your Transformation Went Live. Where Are the Benefits?

By Isabella Brusati · 19 November 2026

A team builds the remaining crossing beyond a digital gateway towards a gold tree, illustrating work needed to realise benefits.

A successful go-live makes a capability available. Realising the business case requires a further chain of changes in work, performance and decisions.

Imagine a finance transformation that launches on time. The system is stable and training is complete. Reconciliation becomes quicker, but the team uses the released time to clear overdue exceptions. Expenditure stays the same. The programme reports productivity savings; finance asks why the expected budget reduction has not appeared.

In this hypothetical example, the change may have created useful value. Better control and fewer overdue exceptions are worthwhile outcomes. They are simply different from a reduction in spending.

My argument is that sponsors should make the route from deployment to recognised value explicit. Availability, adoption, operational improvement and financial benefit need separate evidence. Combining them into a single success measure can conceal the decision still required to realise the promised outcome.

Find where the benefit chain breaks

When deployment is treated as completion, the programme can close before anyone owns the remaining operational changes. Managers retain old reports, teams use workarounds and released capacity has no agreed purpose. The business case assumes a benefit that the operating model has not yet enabled.

External evidence supports asking harder questions. In Deloitte and Workplace Intelligence’s 2026 study, 70% of 1,000 executive respondents said their latest transformation had not delivered its intended value. Gartner’s 2025 research similarly reported that only 32% of surveyed business leaders described their latest change as achieving healthy employee adoption. These self-reports cannot diagnose your programme. That requires examining its work and assumptions.

1. Reconstruct one benefit from a completed task

At the next benefits review, select one material promise. Ask its business owner to state the mechanism plainly: “Fewer incomplete orders should reduce rework, allowing the team to handle more demand at the agreed service level.”

Then inspect a small sample of orders. Are people following the intended process? Are fewer orders incomplete? Has rework fallen? Has the team actually handled more demand? The first missing link identifies where investigation should begin.

Agree a baseline and consistent definitions. Compare similar workloads and account for volume, complexity and staffing changes. A lower error rate means little if difficult cases have moved outside the measure.

2. Give the remaining decision to someone who can make it

A benefit owner needs influence over the process and access to the people controlling its dependencies. A project manager can coordinate measurement but may not be able to retire an old report, change a target or release capacity.

Where adoption is incomplete, observe the work before commissioning another campaign. A spreadsheet may persist because a manager still demands it. An approval delay may reflect an extra control that nobody authorised the team to remove. A defective workflow may need repair before wider use is sensible.

Name the relevant decision owner, specify the choice and set a date. Keep that responsibility active after programme closure. “The business owns it” is too broad to settle the next action.

3. Separate released capacity from recognised value

Use a simple illustration. Saving six minutes on a task performed 1,000 times each month releases 100 hours before allowing for any additional support or correction. That calculation describes gross capacity. It does not show that expenditure fell.

Ask what happens to the usable time. More throughput needs demand. Better service needs evidence of the service improvement. A cash saving needs an actual spending change. Agree the treatment with finance before declaring a benefit realised.

Keep cash savings, cost avoidance, capacity and service or risk improvements separate. Do not count the same change twice. Where several initiatives influence the result, record the attribution uncertainty rather than crediting the whole improvement to one intervention.

Check whether the improvement can last

Review the result across several operating cycles. Ask whether the new process still works when exceptional support ends and whether the workload is sustainable. A temporary improvement maintained through repeated overtime may not support the original business case.

Be prepared to revise the benefit assumption. The process may work as designed while demand, costs or priorities have changed. Transparent revision gives leaders a better basis for action than an optimistic forecast repeatedly carried forward.

Bring one benefit back to the work

Ask its owner to show the operational change, evidence of adoption and any outstanding decision. Agree a 30-day action, the evidence it should produce and a finance review date. Keep the owner accountable for explaining what changed.

Go-live should mark the point at which the organisation can begin proving its benefit mechanism in operation.

Sources: Deloitte and Workplace Intelligence (20 October 2026); Gartner newsroom (8 July 2025), linked above. Examples and calculations are hypothetical. The review method is my practice recommendation, not a promise of financial return.

Related reading: AI adoption is a leadership challenge; From resistance to readiness.

← Back to Insights