Why go-live is a milestone, not an endpoint
Go-live marks the deployment of a change — the point at which new systems, processes, or ways of working become operational. It does not mark the completion of adoption. In most transformations, adoption trajectories continue to develop for weeks or months after go-live, and whether they develop positively or negatively depends significantly on what happens after deployment.
When leadership attention, governance, and reinforcement activities wind down at or shortly after go-live, adoption often stalls, erodes, or reverts. The underlying assumption — that deployment equals adoption — consistently produces gaps between projected and realized benefits.
The adoption curve after go-live
Post-go-live adoption typically follows a recognisable pattern:
Initial compliance: employees follow required steps because they are expected to, not yet because they are fluent or confident.
Proficiency development: with practice and support, employees develop competence and speed in the new ways of working.
Stabilisation: the new behavior becomes the default; effort required for adoption decreases.
Risk of reversion: if reinforcement is withdrawn too early or competing priorities intensify, employees may revert to prior practices, particularly under pressure.
The length and shape of each phase varies by the complexity of the change, the capability of the affected population, the quality of training and support, and the degree of reinforcement provided.
Reinforcement as a design component
Reinforcement refers to the sustained leadership actions, structural adjustments, and accountability mechanisms that embed new behaviors over time. Prosci’s ADKAR model identifies reinforcement as the final stage of individual change, and notes that its absence is a common cause of adoption failure even when earlier stages are completed successfully.
Reinforcement activities typically include:
Visible sponsor behavior: leaders consistently modeling new ways of working in their own decisions and actions.
Manager accountability: direct supervisors tracking and coaching for adoption, not only communicating expectations.
Performance integration: embedding new behaviors in performance expectations, recognition systems, and formal accountability structures.
Continued support availability: sustaining access to job aids, coaching, and expert support beyond the initial go-live period.
Adoption measurement and response: continuing to track adoption signals and intervening where adoption is stalling or eroding.
Pacing and reinforcement duration
How long reinforcement is required varies by environment and by change complexity. Practitioners assess reinforcement duration by examining:
The complexity and novelty of the new behaviors required: more complex behavioral changes typically require longer reinforcement periods.
Organizational expectations about how long commitment is visible before it is considered genuine: in some environments, sustained visibility over a long period is required before employees treat a change as permanent.
The history of change in the organization: where previous changes were introduced and then quietly abandoned, longer reinforcement is required to overcome credibility gaps.
The pace at which the next wave of change is arriving: insufficient stabilisation time between initiatives reduces the depth of reinforcement that can be achieved.
Common pitfalls and errors
Treating go-live as the primary milestone for measuring success, with governance and resources withdrawn shortly after.
Equating hypercare (intensive post-go-live technical support) with adoption support, which are distinct and complementary activities.
Failing to build reinforcement activities and accountabilities into change plans from the outset, adding them reactively when adoption stalls.
Withdrawing leadership visibility too early, before adoption has stabilized into the default behavior.
Underestimating how long the adoption curve takes in complex changes affecting deeply embedded practices.
References
[1] Hiatt, J. M. ADKAR: A Model for Change in Business, Government and our Community. Prosci. (reinforcement as the R in ADKAR).
[2] Prosci: Metrics for Measuring Change Management (adoption and compliance post go-live) — https://www.prosci.com/blog/metrics-for-measuring-change-management
[3] PMI: Benefits Realization Management (sustained adoption as prerequisite for benefits delivery) — https://www.pmi.org/standards/benefits-realization
[4] Kotter: 8-Step Process, Step 8 (anchoring new approaches in the culture) — https://www.kotterinc.com/methodology/8-steps/