Lean Six Sigma and Change Management: Why CI Initiatives Fail
Early Wins, Fading Gains
A Lean Six Sigma programme launches with energy. A green belt cohort is trained, a handful of projects are chartered, and within six months there are measurable results: a process that took four days now takes two, a defect rate that ran at 8% has been cut to 2%. Leadership celebrates. Then, quietly, the gains erode. Six months later the process is back to three days. The defect rate is creeping upward. The dashboard that tracked the improvement metric has stopped being updated. The project sponsor has moved on to the next initiative.
This pattern is so common that many practitioners treat it as inevitable. It is not. The root cause is rarely a flaw in the Lean or Six Sigma methodology itself. It is almost always a failure of change management — the discipline of ensuring that the human and organisational side of change is addressed as rigorously as the technical side.
The Specific Change Management Failures That Derail CI
When continuous improvement programmes stall, the failure can usually be traced to one or more of a familiar set of patterns.
Insufficient sponsorship is the most common. The sponsor attends the kick-off, endorses the project charter, and then effectively disappears. They receive status reports but do not act on them. When the project team needs organisational support — release time from department heads, access to data, decisions about scope — the sponsor is unavailable. Without active sponsorship, CI projects run into resistance they cannot overcome.
Team members not released from their day jobs is the second most common failure. A green belt is chartered to lead a project but is still expected to perform their full regular role simultaneously. The project gets what is left over after the day job is done, which is rarely enough. This is a structural problem, not an individual one — it reflects a decision by leaders to treat the CI programme as an add-on rather than a priority.
Solutions implemented without front-line ownership create the conditions for reversion. When a project team designs and implements a solution that the people doing the work did not help create, those people often lack both the understanding and the motivation to sustain it. The first time the new process is inconvenient, they revert to the old way. The improvement was never theirs to keep.
No management system reinforcement means that even well-designed improvements decay. Standard work that is not checked reverts to whatever is most convenient. Metrics that are not reviewed in regular meetings stop mattering. Leaders who do not visibly model the new behaviours send the message that the old ways are still acceptable. The discipline required to sustain a process improvement is different from the creativity required to design it — and both are necessary.
Finally, the next project not building on the first means that each CI effort starts from scratch rather than deepening the organisation's capability. Programmes that treat each project as isolated miss the cumulative learning that makes continuous improvement genuinely continuous.
Applying Structured Change Management to a CI Programme
The insight that has most changed how leading CI programmes are run is simple: change management frameworks designed for large organisational transformation — Kotter's 8-step model, Prosci's ADKAR model — apply equally well to CI programmes and individual projects.
Kotter's 8-step model is useful at the programme level. Creating urgency sets the foundation; building a guiding coalition ensures the right leaders are actively involved; creating short-term wins maintains momentum. Anchoring new approaches in the culture is the step most programmes skip — and the one that determines whether gains persist.
ADKAR operates at the individual level. Awareness of the need to change, Desire to support it, Knowledge of how to change, Ability to demonstrate the new behaviour, and Reinforcement to sustain it — each is a potential failure point. ADKAR helps practitioners diagnose accurately rather than applying generic resistance management.
Making CI Self-Sustaining
Sustaining improvement requires embedding change management into the CI programme design from the outset, not treating it as a corrective when things start to slip.
Practically, this means: securing a formal sponsor commitment that includes ongoing involvement, not just kick-off attendance; building front-line involvement into the project design so that the people who will sustain the change help create it; establishing management system routines — daily or weekly reviews of key metrics, regular gemba walks, leader standard work — that make the improved process the default; and designing each project to build on the previous one so that the organisation accumulates capability rather than just completing projects.
The organisations that sustain CI gains are those that treat change management not as a communications activity attached to the end of a project, but as the central challenge the programme exists to solve.
XNM Consulting helps organisations design and sustain continuous improvement programmes that deliver lasting results. If you would like to discuss how structured change management could strengthen your CI initiative, our strategic advisory practice is a good place to start.