When the Project Team Walks Away: A Checklist to Keep the Gains
Almost every improvement effort has the same quiet ending. The project closes, the cross-functional team goes back to its day jobs, and within a few months the process drifts back to where it started. The control charts stop being updated, the new standard work gathers dust, and the savings you reported never actually show up in the budget. This is the unglamorous truth of Lean Six Sigma: the hard part is not finding the improvement, it is keeping it after everyone who cared about it has moved on.
The Control phase of DMAIC exists precisely for this reason, but it is the phase teams rush through because the interesting analysis is already done. In 2022, with thin staffing, people changing roles, and supply disruptions forcing constant firefighting, a process with no owner and no monitoring will not survive the first bad week. Below is a checklist you can run this week, before the team formally disbands, while the people who built the change are still in the room.
Before the team disbands: lock these down
Name one accountable owner. Not a committee. One person whose job description, or at least whose manager, now expects them to hold the new process. If you cannot name them by Friday, the improvement has no future.
Update the standard work, and make it the only version. Replace the old work instruction in the system of record. Archive or delete the old one so no one can quietly revert to it. A new method that sits beside the old method is a suggestion, not a standard.
Define the control method and who reacts to it. Decide what gets measured, how often, and what the trigger for action is. A control chart nobody looks at is decoration. Pair every metric with a named person and a documented response.
Build the reaction plan into the daily routine. Write down, in plain language, what to do when the metric goes out of bounds: who to call, what to check first, when to stop the line. Attach it where the work happens, not in a shared drive.
Verify the financial benefit with Finance. Have Finance, not the project team, confirm the savings are real and will land in a budget line. Unvalidated savings are the fastest way to lose credibility for the next project.
In the first weeks after handoff
Hold a short check-in 30 and 60 days out to confirm the control method is actually being used, not just documented.
Watch for workarounds. When people quietly route around the new process, that is data: the standard is missing something, so fix the standard rather than blaming the people.
Train the backup. The owner will take vacation, change roles, or leave. A process that depends on one memory is already failing.
Capture the before-and-after baseline somewhere durable so a future team can tell whether the gain held.
The pattern to avoid is treating sign-off as the finish line. Sign-off is the moment the real test begins. Control is not paperwork; it is the deliberate transfer of a fragile new habit into the muscle memory of an organization that is busy, understaffed, and pulled in ten directions. Spend your last week of the project making the gain boring, automatic, and owned, and it will still be there a year from now.
If you need a steady hand to help embed improvements so they survive turnover and disruption, XNM's strategic advisory can help you build the controls and ownership that make change stick.