Why Good Improvements Fade — and How to Make Them Stick After the Team Goes Home
Almost every team has lived this story. A focused effort solves a stubborn problem, the numbers move in the right direction, everyone celebrates — and six months later the process has drifted right back to where it started. The improvement was real. What was missing was a plan to hold it in place once the people who built it moved on to the next thing. In DMAIC, this is exactly what the Control phase exists for, and it is the phase teams are most likely to short-change, especially when members are stretched thin or working across home offices that never quite became a team room.
Sustainment is not an afterthought you bolt on at the end. It is a design choice you make while the project is still running. The goal of Control is to transfer ownership of the gain from a temporary project team to the people who run the process every day — with the tools, the visibility, and the authority to keep it there.
Why improvements quietly erode
Ownership never transfers. The project team holds all the knowledge, then disperses. Nobody who remains feels responsible for the new way of working, so the old way creeps back the first time things get busy.
The new standard lives in someone's head. Without documented standard work, the improvement depends on the few people who were in the room. When they change roles or leave, the process loses its memory.
Nothing watches the metric. If no one is tracking the key measure after the project closes, drift is invisible until it has become a full relapse. A control chart that nobody reads is the same as no control chart at all.
The fix relied on heroics. If holding the gain depends on extra effort or constant vigilance, it will not survive contact with a normal busy week. Sustainable improvements are built into the workflow, not layered on top of it.
Incentives still reward the old behaviour. When targets, reports, or recognition continue to pull people toward the way things used to work, the process follows the incentive, not the project charter.
Building a Control plan that survives the handoff
Name a process owner before you close the project, and confirm they have the authority and time to act on what the data shows.
Document standard work in plain language, where the people doing the job will actually find it — not in a binder nobody opens.
Keep a small set of leading indicators on a control chart with clear response rules: what happens, and who acts, when a point falls out of range.
Mistake-proof the process where you can, so the right way is the easy way and the old way takes deliberate effort.
Schedule a short check-in at thirty, sixty, and ninety days to confirm the gain is holding before the team's attention fully moves on.
The discipline of Control is unglamorous, which is precisely why it gets skipped. But a half-sustained improvement is often worse than none — it consumes the credibility you will need for the next initiative, and it teaches the organization that improvement is temporary. Treat sustainment as part of the deliverable, plan for the handoff from the first week, and the gain you worked for becomes the new baseline rather than a story about how things used to be better.
If your organization keeps watching hard-won improvements slip away, XNM's strategic advisory can help you build the governance and ownership that make better ways of working stick.