Why continuous improvement programmes quietly die at month 18 — and the five behavioural shifts that decide whether yours survives past year three.
Most continuous improvement programmes die around month 18 — not because the methodology was wrong, but because the weekly rhythm of selection, deployment and reflection was never installed. Programmes that survive past year three treat cadence as the core discipline. Programmes that fail treat methodology as the core discipline.
The 5 Shifts framework distils 27 years of CI deployment — Shell, IBM, Credit Suisse, Royal Mail, KCA Deutag, Johnson Controls — into the five behavioural transitions that predict whether a programme compounds or collapses.
Stop treating the weekly improvement rhythm as a calendar item. Start treating it as the programme. Most initiatives are a training wave followed by silence; the teams that compound run one fixed rhythm where problems surface, decisions close and improvements ship every single week. A tool used once is a workshop. A tool used every Tuesday is a system. Cadence is the one discipline that makes every other CI tool work.
Stop starting at "what should we build?" Start at "what is actually happening?" Quality of problem definition predicts quality of outcome more than any tool or methodology.
A programme built on discrete projects ends when the projects end. A programme built on practice becomes how the organisation operates. This is the month-18 fork: project programmes deliver their business cases, celebrate and quietly dissolve, while practice programmes keep producing improvements nobody had to charter. The difference is design, not effort. Practice lives inside the operating rhythm and survives without a steering committee.
Teams forced to do CI deliver mediocre CI. Teams curious about their own process deliver compounding improvement. A compliant team fills in the A3 because the audit asks for it; a curious team pulls the data because they want to know why Tuesday is always worse. You cannot mandate curiosity, but you can build it: leaders who ask real questions, problems that are safe to raise, and small wins made visible until wondering about the process becomes normal.
The programmes that die are hero-dependent. The programmes that survive are system-dependent. Every organisation has the brilliant improver who carries the programme on energy and goodwill, and when that person leaves, the programme leaves with them. Systems survive succession: standard work that holds the gains, dashboards that keep reality visible, a cadence that runs whoever is in the room. When the hero moves on, the system keeps compounding. This shift is the most brutal and the most important.
The 5 Shifts is distilled from 27 years of deployment across 40+ organisations, including:
More than €1B in documented savings. See the full deployments →
Free 20-page PDF. The full framework with diagnostic questions for each shift.
10-question self-assessment scoring each of the 5 Shifts. Under 5 minutes.
€39. Twenty-five operator-grade templates — A3, SIPOC, TIMWOOD, VSM, Fishbone, 5 Whys — in PowerPoint, Excel, and Word.
A diagnostic call, not a sales call. You leave with a one-page CI architecture document covering stage-gates, KPI architecture, and operating cadence — delivered within 24 hours.
Book the Architecture Session