Most improvement programs lose momentum within two to three years. The common reasons they stall, the warning signs, and a practical way to restart a program so that it delivers again.
In its first year, the program was everyone's favourite topic. Twenty people were trained, a dozen projects were completed and the savings were presented at the board meeting. By year three, the project board had last been updated six months earlier, half the trained Green Belts had left or moved roles, and the steering committee meeting was regularly cancelled for "more urgent business". Nobody decided to stop the program. It simply ran out of energy.
This pattern is so common that it deserves its own diagnosis.
Why programs stall
- Projects disconnected from business priorities. When projects are chosen because they suit the method, not because they matter, leaders lose interest.
- Savings nobody believes. If finance cannot see the claimed savings in the accounts, the program loses credibility. Benefits tracking needs to be agreed with finance from the start.
- Leadership attention moves on. A new CEO, a crisis or a new initiative replaces improvement as the priority.
- Trained people without time. Belts are expected to deliver projects on top of full-time jobs, and the projects quietly slip.
- No system for sustaining gains. Results fade, and the organisation concludes improvement does not work.
- Too much bureaucracy. Templates, gates and reports that slow projects down more than they help.
- The experts leave. Capability concentrated in a few people walks out of the door with them.
Warning signs
- Fewer projects started each quarter than completed.
- Projects running far beyond their planned duration.
- Steering meetings cancelled or poorly attended.
- Savings reported but not visible in the profit and loss.
- People describing the program by its name rather than its results.
How to restart
- Reconnect to strategy. Ask the leadership team what the business must achieve in the next 12–18 months, then choose a small number of projects that directly support it.
- Start small and visible. A few high-impact projects, delivered fast, rebuild credibility better than a large relaunch.
- Fix benefits tracking. Agree definitions and validation with finance, and report only validated results.
- Protect time. Belts need dedicated time for their projects, agreed with their managers.
- Simplify. Keep the method, cut the paperwork.
- Use a mix of methods: kaizen events for quick wins, DMAIC for chronic problems and just-do-it fixes for the obvious ones, as we argued in Lean or Six Sigma? Usually both.
- Build leadership routines: regular gemba walks and project reviews that leaders actually attend.
- Develop internal leaders, so capability does not depend on a few people or outside help.
What a healthy program looks like
- Projects chosen from a prioritised pipeline linked to business goals.
- Results validated by finance and visible in the accounts.
- Leaders who ask about improvement in their routine meetings.
- Capability spread across many people, not concentrated in a few.
- Improvement that has become part of how work is done, not a separate initiative.
Restarting a program is often easier than starting one. The people, the knowledge and the memory of early success are still there. What is usually missing is focus and leadership attention, and both can be restored.
