Most organisations treat go-live as the moment risk begins to decline. The system is in production. The project team stands down. Success is declared. Attention moves on. In reality, go-live is often the point at which risk quietly increases, not decreases.1 It is the moment when assumptions meet operating pressure, when temporary workarounds harden into habits,2 and when value is most exposed. The most expensive phase of change rarely announces itself. It unfolds after the organisation believes the hard part is over.
Why go-live feels like an ending
There are understandable reasons organisations treat go-live as a finish line. Delivery teams are exhausted. Leaders are under pressure to show progress. Budgets are spent. Governance cycles demand closure. There is also a psychological release. After months or years of effort, declaring success creates space to breathe.
But this sense of completion is largely administrative. Operational reality is only just beginning to settle. What matters most at this stage is not whether the system works in principle, but whether it works under real conditions, at real pace, with real consequences.
What actually changes after go-live
Before go-live, behaviour is provisional. People are more forgiving of friction. Exceptions are tolerated. Extra effort is justified as temporary. After go-live, the organisation expects stability. That expectation changes behaviour in subtle but important ways:
- tolerance for inefficiency drops
- informal support recedes
- attention shifts to new priorities
- shortcuts become normalised
- early compromises become permanent
This is where value is either secured or quietly lost. The operating model is no longer protected by project scaffolding. It must stand on its own.
Where value erosion really begins
Value erosion rarely comes from outright rejection of the change. It comes from partial adoption that feels reasonable in context.
Teams adapt the new way of working to fit local constraints. Managers make pragmatic allowances. Individuals fall back on what feels safest under pressure.
None of this looks like failure. From a distance, the change appears to be holding. From closer range, it is slowly fragmenting.3 Over time, this shows up as:
- benefits that plateau below expectations
- inconsistent performance across units
- growing support and stabilisation costs
- increasing reliance on informal fixes
- declining confidence in the new way of working
These effects accumulate quietly. By the time they are visible in financial or performance data, the opportunity to intervene cheaply has passed.
Why benefits realisation often collapses here
Most benefits realisation frameworks assume that value follows implementation. In practice, value depends on sustained behaviour under pressure. After go-live, several things often happen at once:
- accountability for benefits becomes unclear
- ownership shifts back to the business without support
- performance management systems lag behind new expectations
- leadership attention moves elsewhere
None of these decisions are unreasonable in isolation. Together, they create a vacuum. Value does not disappear because the change was wrong. It erodes because no one is explicitly protecting it.4
The hidden cost of “good enough”
One of the most damaging assumptions at this stage is that partial adoption is acceptable. In the short term, “good enough” keeps things moving. In the long term, it creates structural drag. Partial adoption leads to:
- duplicated effort
- inconsistent data
- higher error rates
- uneven service quality
- loss of comparability across the organisation
These costs rarely appear as a single line item. They show up as friction, inefficiency, and fatigue. Over time, they reduce the organisation’s capacity to change again.
Why this phase is so often unmanaged
The post-go-live phase sits in an awkward space. It is no longer a project, but it is not yet business-as-usual. Governance structures are often unclear. Reporting becomes thinner. Signals are easier to miss. There is also a strong incentive not to look too closely. Declaring success allows everyone to move on. Acknowledging fragility feels like reopening a chapter leaders are eager to close. As a result, organisations often discover value erosion indirectly, through missed targets, rising costs, or declining confidence in leadership. By then, recovery is far more expensive.
Treating stabilisation as value protection
Organisations that protect value treat post-go-live as a distinct phase, not an afterthought. They recognise that:
- behaviour is still forming
- habits are not yet fixed
- pressure reveals weak assumptions
- early signals matter
They pay attention to where work slows, where exceptions multiply, and where informal fixes become routine. They intervene while the cost of doing so is still manageable.
This is not about extending projects indefinitely. It is about recognising where risk actually sits.
A more realistic definition of success
A successful change is not one that goes live on time. It is one that holds together once attention shifts, pressure rises, and novelty fades. If organisations want to protect the value they invest in change, they need to stop treating go-live as the end of the story and start treating it as the beginning of the most consequential chapter. This is one way of thinking about why change succeeds or fails. Other pieces go deeper into how value erodes in practice, and how leaders can intervene before the cost becomes unavoidable.
-
Weick, K. E., & Sutcliffe, K. M. (2007). Managing the Unexpected: Resilient Performance in an Age of Uncertainty (2nd ed.). Jossey-Bass. Weick and Sutcliffe show that high-reliability organisations maintain heightened vigilance precisely at moments of apparent stability — the period after a major transition is when normalised deviation is most likely to accumulate invisibly. Organisations that relax sensing at go-live are doing the opposite of what the risk profile requires. ↩︎
-
Feldman, M. S., & Pentland, B. T. (2003). “Reconceptualizing Organizational Routines as a Source of Flexibility and Change.” Administrative Science Quarterly, 48(1), 94–118. https://doi.org/10.2307/3556620. Feldman and Pentland demonstrate that actual routines diverge from formal procedures in ways that are invisible in standard reporting — ostensive patterns (what people are supposed to do) and performative enactments (what people actually do) are always in tension. Post-go-live workarounds are not anomalies; they are the beginning of a new actual routine that will harden independently of the intended one. ↩︎
-
Sterman, J. D. (2000). Business Dynamics: Systems Thinking and Modeling for a Complex World. McGraw-Hill. Sterman’s modelling of feedback delays shows that consequences lag significantly behind the decisions and behaviours that produce them — organisations operating in comfort after go-live are not seeing the results of what is currently happening, but the results of earlier decisions. Value erosion that appears later was produced by behaviour that looked acceptable at the time. ↩︎
-
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. Jensen and Meckling’s foundational principal-agent work demonstrates that misalignment between who makes decisions and who bears consequences for outcomes creates agency costs — value degrades when no one is structurally accountable for protecting it. Post-go-live value erosion is an agency problem: accountability for realisation has dissolved with the governance structure that would have enforced it. ↩︎