October 31, 2026
Why Continuous Improvement Fails After the Handover
Lean gains usually fade after the consultant leaves. The three reasons continuous improvement fails, and a 3-step sustain phase for lean and ops consultancies.
The short answer
Continuous improvement usually fails after the handover, not during the project. The pilot area hits target, the consultant leaves, and nobody keeps the routines running. That gives your clients three problems: the gains fade, leaders move on, and improvement never becomes daily work. The fix is a sustain phase. Sell it to clients you’ve already helped, run it by hand with a monthly review and a quarterly gemba walk, then coach their coordinator to run it and step back.
Why does continuous improvement fail?
Most lean and CI work is set up to deliver a result by the end of the engagement. Far less of it is set up to hold that result a year later. The Lean Enterprise Institute calls sustaining the hardest part. In Why is it so hard to sustain lean gains?, Michael Ballé notes that 5S is easy to start and very hard to keep going.
The best data point is old but clear. Holweg, Staats and Upton tracked 204 lean projects at a European bank (Harvard Business Review, 2018). 79% showed gains. Of those, 73% were still above average a year later, and 44% after two years. That means only about a third of all projects still held their gains after two years. It was a bank, not a factory, but most consultants will recognise the curve.
For a lean or ops consultancy, that shows up as three problems for your clients.
Problem 1: the gains fade
The pilot area hits target and you hand over. Then the huddles thin out, the boards go stale and the area drifts back.
The fix (Prove it): a monthly review with their coordinator and a quarterly gemba walk, so drift gets caught early, not at the next crisis.
Problem 2: leaders move on
A new priority arrives or the sponsor changes roles. Nobody is watching the measures, and the backsliding starts quietly.
The fix (Prove it): a simple results sheet the sponsor actually looks at, and can take to the board. If leaders can see the measures in five minutes, they keep asking about them.
Problem 3: it never becomes daily work
In Forrester’s research for SafetyCulture (2026, vendor-commissioned), only 39% of frontline supervisors said improvement is actually part of their daily work (source). It still depends on you or a couple of champions.
The fix (Grow it): coach their coordinator to run it, then step back once the measures hold. A sustain phase with no exit just creates a new dependence.
How do you sustain 5S and kaizen results?
The tools are the same ones you already use. What changes is who runs them and how often:
- A fixed rhythm after the event. Kaizen follow-up in the first 30, 60 and 90 days decides whether a kaizen event sticks. Book the reviews before you leave.
- Leader standard work. Short daily or weekly checks by the area leader, not the consultant.
- Visible measures. One page, a handful of numbers, owned by the sponsor.
- A named coordinator. One person inside the client who owns the routines, with you coaching them.
- A step-back point. Agree up front what “holding” looks like, so you both know when you can step back.
How do you sustain change in an organisation after the consultant leaves?
Plan the sustain phase as part of the engagement, not as an afterthought. Price it, scope it and give it a start date before the main project ends. The Kaizen Institute describes sustaining as taking 6 to 12 months to embed, which is longer than most engagements run. A light monthly rhythm through that window is usually enough to keep the gains.
The 3-step fix for lean and ops consultancies
- Sell it. Offer a sustain phase to past clients and to clients near handover. They’ve already seen the gains and don’t want to lose them. Sell it before you build anything.
- Prove it by hand. Run the monthly review, the quarterly gemba walk and the results sheet yourself for one or two clients.
- Grow it. Coach their coordinator to run it, step back once the measures hold, and keep a light monthly retainer for support.
They keep the gains. You keep the work.
Frequently asked questions
Why do lean transformations fail?
Rarely because the tools are wrong. Usually the routines stop after the consultant leaves, the sponsor’s attention moves on, and improvement never becomes part of daily work.
What is a sustain phase?
A period after the main engagement, often 6 to 12 months, in which the consultant runs light-touch reviews, coaches an internal coordinator and tracks the measures until they hold.
What happens in kaizen follow-up?
The team checks that the new standard is being followed, closes open actions and confirms the measures held. The first 90 days matter most.
How often should a sustain review happen?
Monthly reviews with the coordinator plus a quarterly gemba walk works for most sites. Adjust to how fast the area drifts.
Doesn’t a sustain retainer create dependence on the consultant?
It will if it has no exit. Build in a step-back point tied to the measures, and coach the coordinator to own it.
Score your best engagement
Which of your engagements would make the best sustain phase? Score one on the free 16-point Engagement Pick Scorecard and see the ongoing support it could become, with a sample session on your method. About 2 minutes.
Related
About the author
Matt Ainsworth is the founder of The Lean CPTO. He has 20+ years across product, technology, sales, marketing and communications in Australia and Japan (nearly a decade in Tokyo), has mentored founders for 10+ years, and helps leadership, L&D and consulting firms turn a program or method into ongoing support clients pay for every month.