Most change programmes have a clear owner during delivery. A sponsor is named. A programme team is assembled. Governance structures are established. Accountability is visible, at least to those inside the project. After go-live, something different happens.1
The project closes. The team disperses. Ownership is declared to have been “handled back to the business.” And the value that the change was designed to deliver — the adoption, the productivity, the outcomes, the return on investment — enters a structural vacuum.2 Nobody designed that vacuum. But nobody designed around it either.3
Why value ownership disappears at go-live
The disappearance of value ownership at go-live is not usually the result of negligence. It is the result of how change programmes are structured.
Programmes are built around delivery. Their mandate is to implement. Their success criteria are go-live milestones, budget compliance, and scope completion. Their governance is designed to protect the delivery phase.
Value realisation is a different activity. It requires sustained attention to adoption, behaviour change, and the conditions that allow new ways of working to stabilise and produce results. It has a different timeline, different skills, and different success measures than delivery. When the programme closes, it takes its accountability structures with it. What remains in the business is the requirement to realise value, but often without the ownership, authority, or resources to do so deliberately.
What ‘handed back to the business’ actually means in practice
The phrase “handed back to the business” describes a transfer of responsibility. It does not describe a transfer of capability, authority, or structured accountability.
In practice, the handover typically means that operational leaders inherit the outcomes of a change they were consulted on but did not design, with users who may be partially adopted at best, with no dedicated resource to address the adoption gaps that remain, and with their existing performance targets unchanged.
These leaders are expected to realise value as a by-product of running their operations. Value realisation is not in their mandate. It is not in their targets. It is not in their governance reporting. It is not something they will be measured on. The expected value does not disappear from the business case. It simply has no owner.
How value erodes without ownership
Value does not hold itself. In the months after go-live, adoption that was never fully embedded begins to drift. Workarounds that were tolerated during stabilisation become permanent. Teams that were managing the transition return to the pressures of normal operations and stop tracking adoption fidelity. Managers who were engaged during the programme period disengage once the programme team leaves. Without an owner tracking these patterns and intervening, the gap between delivered capability and realised value widens quietly.4 By the time the benefits review arrives, the shortfall is visible but its causes are difficult to reconstruct.
Value erosion after delivery is rarely dramatic. It is the cumulative result of many small divergences that were never addressed because no one was responsible for addressing them.
The accountability gap at the value horizon
Organisations invest heavily in the delivery horizon and lightly in the value horizon.
The delivery horizon has sponsors, programme managers, steering committees, risk registers, and status reports. It has regular governance attention and clear escalation paths. When something goes wrong, there is someone to contact.
The value horizon — the period after go-live when adoption must embed, behaviours must stabilise, and benefits must materialise — often has none of these things. There is no named owner. There is no dedicated governance. There is no mechanism for early intervention when adoption begins to drift.
This asymmetry is structural. It reflects how programmes are designed, funded, and closed. Changing it requires designing value ownership as deliberately as delivery ownership is designed.
What value ownership actually requires
Value ownership after delivery is not a light administrative function. It requires someone with sufficient authority to intervene when adoption drifts, to address the structural conditions that are allowing drift to occur, and to escalate when value is at risk. It requires a performance framework that tracks adoption fidelity rather than just system usage. It requires ongoing access to the behavioural signals that indicate whether the change is actually holding.
This is not the same as having a named benefits lead in a programme org chart. That role typically exists during delivery and dissolves with the programme. Genuine value ownership sits in the operating model. It is the accountability of a business leader — not a project role — who has the mandate, the authority, and the performance expectations to protect value after delivery.
Why this is a governance question, not a programme question
The absence of value ownership after delivery is not a failure of programme management. It is a failure of governance design.
Governance structures that evaluate change investments at go-live and declare success based on delivery metrics are not designed to protect value. They are designed to protect delivery. The distinction matters.
Organisations that govern change well extend their accountability structures beyond go-live. They ask who is responsible for benefits in the business model, not just the programme model. They define what value ownership looks like in operational terms. They build the value horizon into governance from the beginning, not as an afterthought when post-implementation reviews reveal shortfall.
A structural question before the programme closes
Before any change programme closes, one question should be answered with specificity: Who, by name and role, owns the value this programme was designed to deliver — and what authority, reporting, and governance support do they have to protect it? If the answer is diffuse — “the business”, “operational leadership”, “it will be monitored through normal performance management” — the value is at risk. Not because people are indifferent. Because no one has been designed to hold it.
This is one way of thinking about why change succeeds or fails. Other pieces go deeper into how accountability gaps form after delivery, and what governance structures can do to protect value beyond the delivery horizon.
-
Fama, E. F., & Jensen, M. C. (1983). “Separation of Ownership and Control.” Journal of Law and Economics, 26(2), 301–325. https://doi.org/10.1086/467037. Fama and Jensen demonstrate that separating ownership (the right to claim residual value) from control (the authority to make decisions) produces predictable governance failures. At go-live handover, exactly this separation occurs: the programme team retains the ownership framing (the business case, the benefits projections) while operations inherits the decision rights without the corresponding accountability structure. The expected value has no owner because the governance architecture created ownership on one side of the transition and authority on the other. ↩︎
-
Simons, R. (1995). Levers of Control: How Managers Use Innovative Control Systems to Drive Strategic Renewal. Harvard Business School Press. Simons argues that diagnostic control systems — which monitor critical performance variables against targets — are what make strategic intent operational. When diagnostic governance ends at go-live, the strategic intent embedded in the business case loses its monitoring mechanism. The structural vacuum is not merely the absence of a named owner; it is the absence of the diagnostic infrastructure that would make ownership meaningful. Without monitoring, no owner receives the signal that value is drifting. ↩︎
-
Jensen, M. C., & Meckling, W. H. (1976). “Theory of the Firm: Managerial Behavior, Agency Costs and Ownership Structure.” Journal of Financial Economics, 3(4), 305–360. https://doi.org/10.1016/0304-405X(76)90026-X. The principal-agent framework establishes that value protection requires a specific agent with both the incentive and the authority to act as steward. When ownership of value is transferred to “the business” without designating a specific agent, no individual bears the residual claim on the outcome. Nobody designed the vacuum, and nobody designed around it, because designing around it would require naming an agent and allocating the authority to protect value — which the programme governance structure was not designed to do. ↩︎
-
Kotter, J. P. (1996). Leading Change. Harvard Business School Press. Kotter identifies “not anchoring changes in the corporate culture” as among the most common reasons transformation investments fail to deliver sustained value. Without deliberate ownership structures that embed new ways of working into operating-model accountability — performance targets, management expectations, resource allocation — changes revert to prior patterns as the conditions that supported them during the programme period dissolve. Value does not hold itself; it requires the same deliberate governance at the value horizon that delivery received at the delivery horizon. ↩︎