Benefits realisation: the discipline some projects abandon after go-live

and many do not even start...

There is a familiar moment in enterprise transformation when the mood changes. The programme has gone live, the project team is exhausted, the steering committee wants closure, the supplier is moving people onto the next engagement, and the business is being encouraged to “embed the change” while still trying to run the operation. Everyone agrees that benefits matter, but the machinery that was built to deliver the project is already starting to disappear.

This is the point where value often slips out of the room. Most organisations do not abandon benefits realisation because they are careless or because nobody cares about value. They abandon it because their structures, incentives and governance models are designed around delivery rather than sustained business improvement. They fund the project, manage the project, report the project, celebrate the project and then disband the project just as the value work is beginning in earnest. That is not a technology failure. It is a governance failure, and it is one of the most predictable ways transformation investments lose their commercial impact.

At Arqvera, we would describe this as a value ownership problem. Organisations do not realise value from software, process redesign or new platforms. They realise value from changed behaviour, better decisions, improved operating routines and sustained management attention. The go-live may enable those things, but it does not guarantee them. In many cases, go-live is simply the point at which the organisation discovers whether it has built the conditions for value or merely installed the means of hoping for it.

Project success and value success are not the same thing

One of the reasons benefits realisation gets lost is that organisations confuse project success with business value. The Association for Project Management defines benefits management as the identification, definition, planning, tracking and realisation of benefits, while benefits realisation is the practice of ensuring that benefits are derived from outputs and outcomes. APM also distinguishes project success as the satisfaction of stakeholder needs measured against success criteria agreed at the start of a project.

That distinction sounds technical, but it is hugely important. A project can meet its delivery criteria and still fail to create meaningful value. It can be on time, within budget, broadly within scope and technically sound, while the business case remains unrealised. Users may not adopt the new process. Managers may continue to rely on old reports. Customers may see no improvement. Costs may move from capital expenditure into operational friction. The system works, but the organisation does not work differently enough.

This is where many leadership teams get caught out. They assume that if the project has delivered its outputs, the benefits should follow. Sometimes they do. More often, they require a second and more difficult discipline: helping the business exploit the new capability after the delivery spotlight has moved elsewhere.

Research by Carlos Eduardo Martins Serra and Martin Kunc, published in the International Journal of Project Management, found that benefits realisation management practices are positive predictors of project success and the creation of strategic value for the business. Their work is useful because it reinforces a practical point: benefits are not a by-product of good project administration; they require deliberate management practices that connect project activity to strategic outcomes.

The problem is that most organisations know this in theory and still behave differently in practice.

Why benefits disappear after go-live

The first reason is structural. Most transformations are funded and governed as time-bound projects. A capital budget is approved, a delivery team is assembled, a plan is baselined and progress is managed through a project governance model. The financial and organisational architecture is built to reach a delivery milestone, not to manage value long after the milestone has passed.

Benefits, however, are rarely realised neatly within the project lifecycle. They accrue in the operating environment, often months or years after the platform has gone live or the organisational change has formally completed. Productivity improvements depend on adoption and process discipline. Revenue improvements depend on sales behaviour, customer propositions and management routines. Cost savings depend on decisions that may be politically uncomfortable, such as retiring legacy systems, redesigning roles, changing service models or removing duplicated effort.

The project budget closes before many of these things have matured. The delivery team moves on before the business has fully changed. The steering committee is stood down before the benefit trajectory is properly understood. The result is an accountability gap in which everyone supported the business case, but nobody quite owns the value after the handover.

The second reason is behavioural. Go-live creates psychological closure. It feels like completion because the visible effort has peaked. People have worked hard, weekends may have been consumed, difficult decisions have been pushed through, and the organisation wants relief. In that environment, asking leaders to maintain disciplined benefits tracking can feel like extending the pain.

There is a human truth here that we should not ignore. Transformation fatigue is real. People do not resist benefits tracking because they are anti-value. They resist it because, after months of mobilisation, testing, training, data cleansing and problem solving, the promise of “business as usual” is emotionally attractive. The phrase itself is part of the problem. The whole point of transformation is that business as usual should not quite return.

The third reason is political. Benefits realisation makes promises visible. It tests whether the business case was credible, whether sponsors were realistic, whether adoption has happened, and whether operational leaders have changed how work is done. That can be uncomfortable, particularly when benefits were used to secure investment approval in the first place. Nobody is especially keen to reopen a benefits case that now looks optimistic, particularly when the people who signed it off are still in the building.

This is where candour matters. A benefits plan should not be treated as a trap for leaders. It should be treated as a management instrument that helps the organisation learn, adjust and realise more value over time. Trust is a system, and part of that system is the ability to tell the truth about whether the expected value is actually appearing.

The business owns the benefit

A delivery team can deliver outputs. It cannot, on its own, realise operational value.

This is not always a popular message, because it removes the comfortable fiction that benefits can be delegated to the programme. The project manager may track benefits during delivery, and the transformation office may provide structure, analysis and reporting. The supplier may enable capability. The PMO may maintain the dashboard. But the business sponsor and operational leaders own the value because they own the environment in which the value must be created.

If a new platform is intended to reduce working capital, the benefit owner is not the project manager. It is the finance, supply chain or commercial leader who must change planning, ordering, stock, billing or collection behaviour. If a CRM programme is intended to improve sales conversion, the benefit owner is not the implementation partner. It is the sales leadership team that must change pipeline discipline, coaching, account planning and performance management. If an AI initiative is intended to improve productivity, the benefit owner is not the tool vendor. It is the operational leader who must redesign workflow, decision rights and team routines so the technology has somewhere useful to land.

This is why Arqvera’s Value Compass focuses on value realisation as a leadership and operating discipline, not as a reporting exercise. The work is about keeping benefits connected to owners, behaviours, measures and decisions after the delivery phase has ended. Without that connection, benefits become optimistic accounting entries rather than managed outcomes.

The common traps

The first trap is defining benefits too vaguely. “Improved efficiency”, “better customer experience” and “increased agility” may be directionally true, but they are not benefits in a form that can be managed. A benefit needs a baseline, an owner, a measure, a target, a timeframe and a credible causal link to the change being delivered. Without those elements, the organisation is not managing value; it is describing aspiration.

The second trap is counting activity as value. Training completion is not adoption. System usage is not productivity. A live dashboard is not better decision-making. A deployed workflow is not process improvement. These are indicators that may support benefits, but they are not the benefits themselves. Activity matters only if it changes operational performance.

The third trap is over-claiming value before the business has changed. Many benefits cases assume that capability will be used well simply because it exists. This is particularly risky in AI and digital transformation, where the organisation may have access to powerful tools without the governance, data quality, process clarity or leadership discipline required to convert those tools into results. AI activity is often mistaken for AI progress. The same mistake has been made for years with ERP, CRM, data platforms and automation.

The fourth trap is failing to fund adoption. Organisations often invest heavily in design, build and deployment, then treat adoption as communication, training and goodwill. That is not enough. Adoption requires sustained support, management reinforcement, process ownership, capability building and sometimes a deliberate redesign of incentives. If the old behaviour remains easier, safer or more rewarded than the new behaviour, the old behaviour usually wins.

This is where Arqvera’s Change Studio becomes relevant. Benefits are realised through people changing how they work, decide and lead. Human-centred change is not a soft add-on; it is the bridge between delivery output and operational value.

What good benefits governance looks like

Good benefits governance begins before investment approval and continues beyond go-live. It does not wait until the end of the programme to ask whether value has appeared.

At the business case stage, leaders should define the benefits clearly enough to test them. What is the baseline? What will improve? Who owns the improvement? What behaviour, process or decision must change? What other conditions must be true? What dis-benefits might occur? What will be measured after go-live, and by whom?

During delivery, benefits should be reviewed as part of governance, not as a side document maintained by the PMO. If scope changes, the benefit case should change. If adoption risk increases, the benefit forecast should be challenged. If the operating model changes, ownership should be updated. A project that still reports green while its benefits case is weakening is not green. It is simply reporting on the wrong thing.

After go-live, benefits governance should move into the operating rhythm of the business. That means benefit owners report progress through normal management forums, not through a fading project structure. Finance should help validate the numbers. Operational leaders should explain variance. Sponsors should remove obstacles. The executive team should continue to ask whether the investment is producing the intended change.

This does not need to become heavy governance. In fact, overcomplicated benefits frameworks often collapse under their own administrative weight. The discipline should be proportionate, but it must be real. A small number of meaningful measures, reviewed consistently by accountable owners, is far better than a large benefits register nobody believes.

For higher-risk transformations, Arqvera’s Trust Arq can provide the delivery assurance and governance challenge needed to keep outputs, outcomes and benefits aligned throughout the lifecycle. The point is not to create more bureaucracy. The point is to prevent delivery confidence from becoming disconnected from value confidence.

The role of finance

Finance has an important role in benefits realisation, but it should not become the sole owner of benefits. That is another common mistake. Finance can validate baselines, test assumptions, monitor performance and challenge benefit claims. It can help distinguish between genuine improvement and accounting noise. It can prevent double-counting and ensure that benefits are visible in planning and forecasting.

But finance cannot alone make the business behave differently. If benefits are owned only through financial reporting, the organisation risks measuring value after the point at which management action could have improved it. Operational ownership has to sit with the leaders who control the processes, teams and decisions that create the value in the first place.

The best model is partnership. Finance provides discipline and credibility. Operations provides ownership and action. Transformation provides structure and coordination. Sponsorship provides priority and consequence. When one of those elements is missing, benefits realisation becomes either a spreadsheet exercise or a set of good intentions.

Why this matters now

The pressure to demonstrate value is increasing. Boards are scrutinising transformation spend more closely. Private equity sponsors are demanding operational value creation rather than relying on multiple expansion. AI investment is accelerating, but many organisations are still struggling to show enterprise-wide financial impact. In that environment, the difference between deployment and value is no longer a theoretical concern. It is a commercial one.

PMI has argued that organisations leave strategy to chance when they do not make benefits realisation management a central part of project and programme management. Its 2016 Pulse of the Profession report also found that organisations wasted US$122 million for every US$1 billion invested due to poor project performance, a reminder that weak execution is not an administrative inconvenience; it is a material value drain.

The lesson for leaders is not that every benefit can be perfectly predicted. It cannot. Markets move, organisations learn, assumptions change and some benefits will prove more difficult than expected. The lesson is that value needs active management. A benefit that is not owned, measured, reviewed and acted upon is not a benefit. It is a hope with a number attached.

The readiness perspective

Benefits realisation starts much earlier than most organisations think. It starts when the business case is written, when the sponsor is named, when the operating model impact is understood, when adoption is designed, when measures are agreed, and when leaders decide whether they are prepared to be accountable for value rather than just delivery.

Ready organisations do not wait until go-live to ask how value will be captured. They define the change in operational terms. They identify the owners who must make it real. They build trust in the measures. They fund adoption properly. They keep governance alive after the project team leaves. They are honest enough to adjust when the evidence changes.

Unready organisations do something different. They approve the benefits, deliver the project, close the budget, thank the team and then wonder why the business case has become difficult to evidence. The problem is rarely a lack of effort. It is a lack of value governance.

Benefits realisation is not the final chapter of transformation. It is the reason the transformation exists.

The work does not end at go-live. In many cases, that is where the real work begins.

About Arqvera

Is an AI and technology transformation consultancy and advisory.

We help organisations shape business cases, projects, deliver excellence, and realise change and outcomes that stick. We support organisations before, during, and after projects with an end-to-end service where our domain specialization comes to life.

Before (Inception): We work with you to clearly define the idea, vision, strategy, and business case for change, as well as help select the right partners, and establish governance

During (Execution): We help deliver project and change objectives while keeping implementation under control through structured governance and assurance to realise intended outcomes.

After (Value Realisation): We ensure outcomes deliver measurable value and embed continuous improvement from successes and learnings.

Arqvera is led by industry veterans in the UK and USA with 100+ years of technology delivery intelligence across global consulting, digital transformation, and mission-critical projects and programmes.