To sustain change after a project ends, transfer responsibility to an operational owner, make the new approach part of daily work, and keep checking adoption and business results. Project closure should end temporary delivery arrangements, not the support and accountability needed to keep improvements working.
This Praevion Consulting Inc guide helps Canadian leaders transfer change into everyday operations without losing the intended benefits.
In this article
Why does change fade after project closure?
Change can fade when the people who drove implementation move on before operating teams are ready. Old procedures remain available, new employees miss training, and managers return to previous measures. Without clear ownership, small exceptions can quietly become the normal way of working again.
McKinsey’s 2023 survey found that 56% of respondents reported achieving most or all transformation goals, but only 12% reported sustaining them for more than three years. These are reported survey results, not a universal failure rate or proof of any single cause.
Build sustainment into the change management plan before launch, while resources and leadership attention are still available.
Six practical ways to sustain change
To sustain change, replace temporary project effort with permanent operating routines. The following six actions connect ownership, everyday work, support, and evidence. Apply them in proportion to the change: a revised approval process needs less infrastructure than a business-wide system replacement.
1. Give the process a permanent owner
Name someone accountable for the process after closure and give that person authority to resolve issues. Confirm a deputy, support budget, and escalation route. Prosci’s Sustain Outcomes phase explicitly includes reviewing performance, activating sustainment, and transferring ownership to operational teams.
2. Put the new approach into normal work
Update procedures, job aids, approval rules, and onboarding materials so employees receive one consistent instruction. Retire superseded forms only when it is safe and permitted to do so. Keep necessary records and contingency arrangements; removing an old workflow does not mean deleting its history.
3. Make reinforcement part of management
Ask managers to observe the new process, discuss exceptions, and remove obstacles during existing operational reviews. Recognize the behaviours that support results. If performance targets still reward the old shortcut, change the conflicting expectation instead of asking employees to ignore it.
The Institute for Healthcare Improvement’s 2016 framework places daily frontline management work at the centre of sustaining improvement. Its healthcare context differs from other industries, but clearly assigned management tasks offer a useful design principle.
4. Keep support available after launch
Provide an accessible help route, refresher guidance, and training for new starters and people changing roles. Agree who maintains these resources when project specialists leave. A presentation stored in a shared folder is not enough if nobody can answer the next practical question.
5. Track use and value together
Compare actual process use with the business outcome the change was meant to improve. Maintain the original baseline and consistent definitions. Combine change adoption measures with service, quality, or financial results so a high usage rate does not hide weak performance.
6. Correct drift without freezing improvement
Investigate recurring workarounds before deciding whether to reinforce the standard or redesign it. A workaround may reveal missing access, poor instructions, or a genuine flaw. Sustain change by protecting the intended outcome, not by preserving every implementation decision regardless of what employees learn.
What belongs in a change handover checklist?
A change handover should show that operating teams can maintain the process and respond when it fails. Require evidence of readiness, not just a signature. Unresolved issues may transfer to operations, but only with an accepted owner, resources, and a clear response plan.
| Handover item | Evidence to confirm |
|---|---|
| Ownership | Named owner, deputy, authority, and budget |
| Working instructions | Current procedures and controlled exceptions |
| Capability | Task demonstrations and new-starter training |
| Support | Help route, response arrangements, open-issue owners |
| Performance | Baseline, definitions, reporting source, review dates |
| Escalation | Triggers and authority to intervene |
For a higher-risk process, test the handover: ask the receiving team to handle an exception without project staff directing each step. Record gaps and agree corrective actions before reducing support.
What would this look like in a Canadian SME?
Consider an illustrative Canadian service business that has introduced digital work orders. Technicians use the system during the pilot, but urgent jobs still arrive by phone. The process owner needs a practical route for those exceptions before the project team leaves.
The company could require urgent jobs to be entered by the dispatcher, add a daily check for unrecorded work, and train replacement dispatchers before they work alone. Reviews would compare system use with missed visits and billing delays. These are proposed controls, not reported client results.
How should leaders review whether change is lasting?
Use reviews to decide what needs attention and whether support can safely reduce. Review more frequently while the process is unstable, then move into normal management routines. A calendar milestone alone does not demonstrate that the organization is ready to sustain change independently.
- Early review: Resolve access, training, and support gaps.
- Follow-up review: Check repeated exceptions and process consistency.
- Benefits review: Compare outcomes with the baseline and ongoing costs.
A 30-, 60-, and 90-day schedule can be a starting point, not a universal standard. Adjust for risk, transaction frequency, and seasonality. To sustain change through staff turnover, repeat capability checks when key roles change.
Frequently asked questions about sustaining change
To sustain change, leaders need a clear boundary between temporary project work and continuing operational responsibility. These answers address ownership, duration, and measures. The aim is to maintain useful improvements without keeping every project meeting and reporting requirement permanently in place.
Who owns change after a project closes?
The named operational owner should remain accountable for the process and its results. Managers, support teams, and the executive sponsor retain defined responsibilities, with unresolved decisions escalated through an agreed route rather than left with former project staff.
How long should reinforcement continue?
Continue targeted reinforcement until teams demonstrate stable performance and can handle normal exceptions. Keep relevant training and management checks in everyday operations afterward, especially when staff, systems, customer needs, or the process itself change.
Does high adoption prove that change is successful?
No. Employees can use a new process consistently without achieving the intended benefit. To sustain change effectively, check adoption alongside outcomes, ongoing costs, and unintended effects, then investigate gaps before declaring the business case delivered.
Close the project with ownership in place
Before releasing the project team, confirm who owns results, what evidence they will review, and how problems will be resolved. Contact Praevion Consulting Inc to discuss handover readiness and the operating routines needed to sustain change.
References: Prosci: change management process; IHI: Sustaining Improvement (2016); McKinsey: long-term transformation impact (2023).
Photo credits: Centre for Ageing Better, Ali Mkumbwa, FORTYTWO, Mauricio Gutiérrez on Unsplash.
