A new plant manager arrives. Within months, the kaizen calendar has gaps and improvement boards go stale. The departure gets blamed, but the deeper problem was a system that depended on one sponsor.
A lean program lasts when operating routines, standards, resources, and accountability outlive the person who introduced them. The seven signs below reveal where leadership turnover could expose a weak system.
Academic work on why lean implementations fade keeps landing on the same cluster of causes. A study of failure factors in sustaining lean manufacturing in the automotive industry found that many manufacturers struggle to sustain lean, with only a few ultimately succeeding, and that most of the factors deciding the outcome are organizational: leadership, culture, internal collaboration, resource management, and knowledge management. Research into what separates successful from sustainable lean production adds a related distinction: the factors that make a program work initially are not identical to the factors that keep it working afterward.
Key Takeaways
- Make lean independent of individual leaders. Document operating routines, responsibilities, and handover procedures so improvements survive leadership changes.
- Embed improvement into daily operations. Combine kaizen events with regular team huddles, problem-solving, and follow-up reviews.
- Give supervisors ownership and resources. Include improvement in their responsibilities, protect time for it, and provide practical coaching.
- Turn metrics into operational decisions. Assign each indicator an owner, a trigger, and a clear action rather than using data solely for management reports.
- Build capability across the workforce. Document standard work, train every shift, and enable line teams to implement improvements without relying on continuous improvement (CI) specialists.
- Measure sustainability, not just savings. Track participation, audit completion, supervisor capability, and whether improvements remain effective after 90 days.
1. The program carries one person’s name
A program named after its sponsor can look like the previous leader’s agenda when somebody new takes charge. Give it an operational identity instead of a personality.
Document daily reviews, escalation rules, board standards, and audits so staff can explain the system without naming its creator. Include these routines in the handover for every incoming manager.
2. Improvement happens only in events
Event-driven improvement is fragile because it contains no self-sustaining mechanism. Events require planning, backfill, and executive attention, so they are often the first thing to slip when priorities shift, and meanwhile the results of past events decay quietly because nothing in the daily routine maintains them. The evidence on that decay is uncomfortable reading. A field study of 65 kaizen events in eight manufacturing organizations notes that organizations rarely sustain the full change from such events and that their impact can shrink substantially, or disappear entirely, as time passes. What mattered was what happened in the work area afterward: an event’s perceived impact several months later was significantly related to how much employees learned from one another, how far their awareness and sense of responsibility extended beyond their own area, and how fully the changes were accepted.
Where the program is durable, events exist alongside daily improvement rather than instead of it. Teams make small changes in their own areas every week without a facilitator present, and events handle only the problems too large for that. Building toward this means installing a low-friction daily routine: a short team huddle, a visible problem log, a rule that small changes can be made locally without approval, and a weekly slot in which the supervisor works one problem through to closure. The U.S. Environmental Protection Agency (EPA) lean guidance describes follow-up as a formal phase of the kaizen method, not an optional addition, and notes that follow-up events are sometimes scheduled at 30 and 90 days to check performance and adjust what is needed to hold the gains. Yet follow-up is frequently skipped.
3. Middle managers attend but do not lead
Executives can fund lean, but supervisors decide what happens at the start of every shift. They determine whether boards are used, problems escalate, and operators have time to improve work. Lean therefore needs middle-management ownership, not attendance alone.
Supervisors are often measured and staffed for output while improvement is added without time or cover. When the shift runs short, the unfunded activity disappears first. That is a resourcing problem, not necessarily resistance.
Put improvement on supervisor scorecards, protect time in the weekly plan, and teach supervisors to lead problem-solving. Review their span of control: nobody can coach a team effectively while covering an unmanageable workload.
4. Metrics flow upward but never inform a floor decision
A report made for a distant sponsor may vanish when the sponsor leaves. A measure used to decide today’s response to downtime or defects has a reason to survive.
Pair each indicator with an owner, an agreed trigger, and an action. For example, investigate repeated micro-stops during the daily line review rather than merely adding the count to a monthly slide.
5. Knowledge lives in people rather than in standards
Individual expertise is the most fragile form of process knowledge there is, and it is steadily walking out of the building. Deloitte and the Manufacturing Institute project that as many as 1.9 million manufacturing jobs could go unfilled by 2033 if manufacturers cannot close their skills and applicant gaps. When replacements are that scarce, every retirement takes undocumented method with it, and unlike a machine, that method cannot be bought back.
Write critical standard work with experienced operators, train each shift, and audit it periodically. Start with tasks showing the greatest variation or consequence. Update the standard whenever the team establishes a better way.
6. Continuous improvement is a department, not a behavior
When specialists run every event and maintain every board, operations learns to outsource improvement. If that small team is reduced or leaves, most of the capability leaves with it.
Make the CI team a coach. Track how many supervisors can lead problem solving and what share of changes line teams implement themselves. Capability should spread rather than concentrate.
7. Nobody’s job description or budget contains it
Improvement done during lunch or overtime competes with every urgent production request. A new manager inherits no explicit role, time allowance, or budget, so the practice is easy to discontinue.
Write improvement into role descriptions, schedules, and supervisor reviews. Fund modest quick-win materials and recurring training. Formal ownership matters more than a large launch budget.

What makes a continuous improvement culture fragile when leaders change?
Beyond the seven signs, three structural conditions leave a plant unusually exposed. The first is initiative fatigue. If the site has been through several improvement programs in a decade, each arriving with new language and new boards, then people have learned that programs pass, and they will wait this one out politely. Reusing existing routines instead of launching something visibly new is more effective than it sounds, precisely because it does not trigger that pattern recognition.
The second is results without a system. A program can deliver real savings for two years purely on the drive of a strong leader, and those savings mask the absence of any underlying structure until the leader departs. Financial performance is therefore a lagging indicator of program health, and it should never be used to judge durability.
The third is incentives pulling in the opposite direction. If schedulers are measured on machine utilization, they will build inventory no matter what the value stream map recommends. Lean Enterprise Institute commentary on kaizen backsliding makes the point directly: unless the underlying policies driving behavior change, people revert regardless of how capable or motivated they happen to be.
What separates lean programs that become part of daily operations from ones that fade?
Laid side by side, the two look quite different across every dimension that matters.
| Dimension | Fades | Becomes operating structure |
| Identity | Named after a leader or a vendor | Described by what it does |
| Cadence | Quarterly events | Daily, weekly, and monthly routines that interlock |
| Ownership | The CI department | Line management, coached by specialists |
| Measures | Reported upward | Used at the point of decision |
| Knowledge | Held in people | Held in standards, audited and updated |
| Resourcing | Goodwill | Time and budget inside the plan |
| Success criterion | Savings delivered | Savings delivered and the system still running |
| Handover | Informal | Documented, with onboarding for new leaders |
That final row is the one plants most often omit, and it costs little to build. When a new area manager starts, they receive an organization chart, a safety induction, and a production target, yet they almost never receive a written description of the improvement system they are now responsible for running. A structured handover of a few hours is among the lowest-cost protections available against program decay.
What should be built into a lean rollout so it survives staff turnover?
Build a management operating system that documents meeting schedules, escalation, audits, and board standards. Protect supervisor improvement time and add system health to performance reviews. This makes lean part of daily work rather than a special initiative.
Spread capability through operator-authored standard work, scheduled audits, a problem-solving qualification path, and an onboarding pack for every new supervisor. Name deputies for critical roles before anyone leaves.
Set aside a small improvement budget and audit changes after 90 days. The retention rate reveals whether a result has become routine or depends on the original project team.
Building these during delivery rather than bolting them on afterward is the practical difference between a result and a capability, which is why Implementation Engineers treats capability transfer as a defined phase of work through the enCompass framework, and why the sustainability phase concentrates on routines, skills, and ownership rather than on a closing report.
In practice, the operating system is designed before execution starts. During planning and readiness, Implementation Engineers specifies its Performance Excellence Operating System alongside schedules, metrics, skills development, and behavior change, so the daily and weekly routines that will carry the improvements are defined up front rather than improvised at handover. Execution then runs jointly with the client’s workforce, so the people who will own the new methods help build them, and progress is judged by observed behavior as well as by activity and results.
[IE to supply: a two- or three-sentence anonymized client example or practitioner quotation, for example a plant where the improvement system held through a change of plant manager and what made the difference. Delete this note if not used.]
Why do kaizen events stop happening after year one?
Kaizen calendars usually thin out for ordinary reasons: staff cannot be released from production, sponsors or facilitators leave, problems outgrow the team’s skills, or nobody validates the savings. Events also fade when earlier gains reverse. After repeated workshops whose changes disappeared, crews have little reason to join another. Restore follow-up and ownership before filling the calendar again.
What metrics reveal that a lean program has quietly stalled?
Savings are lagging evidence. Look first at participation, leadership, audit completion, and whether completed improvements still work three months later. These leading measures expose drift while there is time to respond.
| Type | Metric | Healthy | Stalled |
| Leading | Improvement ideas per employee per year | Rising and spread across the workforce | Falling, or concentrated in a few people |
| Share implemented by line teams without CI support | Rising | Close to zero | |
| Supervisors qualified to lead problem solving | Growing | Flat or shrinking | |
| Standard work audits completed on schedule | Consistently on schedule | Slipping, then “we do them informally” | |
| Attendance at tiered reviews | Consistent | Delegated down, then skipped | |
| Coincident | Improvements still holding at 90 days | High and stable | Declining quarter over quarter |
| Audit scores | Improving, or stable at a high level | Plateaued for three quarters | |
| Time from problem to countermeasure | Shortening | Lengthening, or no longer tracked | |
| Lagging | Overall equipment effectiveness (OEE), scrap, and conversion cost | Trending with the program | Drifting back toward baseline |
| Savings validated by finance | Consistent | Declining, or no longer measured |
Where to go from here
Test the program before the next leadership change. Ask five employees how improvement works, inspect recent follow-ups, and check whether the system has named owners and funded time. A lean program becomes durable when that structure survives its sponsor.
Implementation Engineers works inside operations to install lean as operating structure rather than as an initiative, building the routines, standards, and capability that keep results in place after the engagement ends and after the people who started it have moved on. You can see our approach to manufacturing performance and to building an operating system that sustains results.
Frequently asked questions
What are the warning signs a lean manufacturing program won’t survive leadership turnover?
Look for seven patterns: sponsor-led identity, event-only improvement, passive supervisors, reports without floor decisions, undocumented knowledge, CI specialists doing everyone’s work, and no protected role or budget.
Should a new plant manager relaunch the lean program under a new name?
Usually not. Staff who have watched programs come and go read a relaunch as a sign that this one will pass too. Keeping the existing routines, owners, and boards, and improving them visibly, signals continuity instead.
What should a handover to a new plant manager include?
A written description of the improvement system: the meeting cadence, escalation rules, audit schedule, board standards, named owners, the open problem log, and the most recent 90-day checks. A few hours of structured handover is among the lowest-cost protections against program decay.
What role does middle management play in whether lean manufacturing sticks?
Supervisors turn strategy into daily behavior. Give them responsibility, coaching, time, and scorecard weight, or production pressure will crowd improvement out.
Can a lean program survive cuts to the continuous improvement team?
Only if capability already sits with line managers and operators. Where specialists run every event and maintain every board, a smaller CI team takes most of the capability with it. Track how many supervisors can lead problem solving and what share of changes line teams make themselves.
What is the difference between leading and lagging indicators of lean program health?
Leading indicators, such as ideas per employee, team-led fixes, and audit completion, move first and show whether the system is still running. Lagging indicators, such as OEE, scrap, and validated savings, confirm results later, often after drift has already set in.