The Kaizen week went well. The team was energized. The before-and-after photos were impressive, the report-out drew applause from leadership, and the savings estimate looked real. Ninety days later, someone walks through the area and it looks almost exactly like it did before the event. The action list is sitting in a spreadsheet no one has opened in weeks.
Now the floor is skeptical. When the next event is announced, the reaction is “another one of those.” Leadership starts to wonder whether lean really works in this business.
It does. But a Kaizen event is a change mechanism, not a sustain mechanism. It is very good at creating a better way of working in a short period. It does nothing, on its own, to keep that better way in place after the team disperses and the facilitator leaves. That job belongs to a sustain system — and in most organizations where Kaizen fails to stick, the sustain system was never built.
Why gains fade: the five usual causes
1. The wrong problem was chosen
Events are sometimes selected because an area is visible, because a leader asked for one, or because it is “time for a Kaizen.” If the problem is not tied to a business metric that people care about, nobody has a reason to protect the result.
2. The scope was too big
A team cannot redesign an entire value stream in five days. Oversized events end with a long list of unfinished actions — and unfinished actions are where results go to die.
3. No one owns the result
During the event, the team owns the change. After it, ownership has to transfer to a specific person — usually the area leader. If that transfer is not explicit, the change belongs to no one, and it erodes.
4. The new method was never standardized
If the improved method exists only in the heads of the event team, it will drift as soon as people change shifts, new operators arrive, or pressure builds. Without standard work, there is nothing to return to and nothing to audit against.
5. Leaders never checked
People pay attention to what their leaders pay attention to. If no leader visits the area to check the new standard, ask about the metric, or help remove obstacles, the message is clear: the event is over.
Isn’t this just an accountability problem?
Partly, yes. But lean treats accountability structurally rather than personally. Instead of relying on individuals to remember and care, it builds routines that make checking, follow-up and escalation automatic. Leader standard work, visual metrics, a named owner and scheduled reviews turn accountability from a personality trait into a process. That is what makes it sustainable across shifts, turnover and busy seasons.
Building the sustain system
Before the event: select and scope for sustainment
Sustainment starts before the event begins. For every proposed event, confirm:
- A business metric — delivery, capacity, quality, cost, safety — with a baseline and a target
- A process owner who will own the result after the event and is part of the team or its sponsor
- A scope the team can realistically complete in the event week, with most changes implemented rather than listed
- Follow-up dates for 30, 60 and 90-day reviews, already on the calendars of the owner and the sponsoring leader
Good preparation — data, current-state observation, materials and resources arranged in advance — also means more is finished during the week and less is left on the action list.
During the event: build the base, then standardize
Workplace organization is often the right first move inside an event. Clearing what is not needed and giving everything a defined place creates the stable, visible base on which a new standard can be built. It is a foundation for the work, not a program of its own.
From there, the team designs and trials the improved method. Before the event ends, it should be captured as standard work: the sequence, the timing, the key points, and the quality checks. Standard work should be simple, visual and posted where the work happens. Our standard work guide covers how to write it well.
The team should also set up a simple visual board in the area showing the target metric, current performance and open actions.
At the report-out: transfer ownership explicitly
The report-out is not just a celebration. It should formally hand ownership to the process owner, confirm the open action list with a named owner and date for every item, and confirm the 30/60/90-day review dates. Leadership’s role at the report-out is to commit to supporting the owner, not just to applaud.
After the event: leader standard work
Leader standard work is a defined routine for leaders at each level — what they check, how often, and what they do when they find a gap. For a Kaizen area, it might include:
- Team lead: check standard work adherence at the start of every shift
- Supervisor: review the area’s visual board daily and address open actions
- Manager: walk the area weekly, ask about the metric, and help remove obstacles
- Senior leader: attend the 30/60/90-day reviews
This layered checking is what catches drift early, while it is still easy to correct.
30, 60 and 90 days: structured reviews
Each review asks the same questions:
- Is the metric holding at or better than the target?
- Is standard work being followed? If not, why not — is the standard wrong, or is something preventing it?
- Which actions are closed, and which are overdue? What is blocking them?
- Has anything changed in the area (people, products, equipment) that affects the standard?
When a result has slipped, the review is a problem-solving opportunity, not an inquest. Often the standard needs adjusting based on real experience — which is exactly how continuous improvement is supposed to work.
From events to a daily improvement system
Events are powerful, but an organization that only improves through events improves in bursts. The long-term goal is a daily improvement system in which problems are raised, solved and standardized continuously, with events reserved for bigger changes. The sustain routines described above — visual boards, leader standard work, structured reviews — are the building blocks of that system. For more on the difference, see Kaizen events vs. continuous improvement.
A quick diagnostic for your past events
Look at your last five Kaizen events and answer honestly:
| Question | If the answer is no… |
|---|---|
| Was the event tied to a business metric with a baseline? | Tighten event selection |
| Is there a named process owner today? | Assign ownership explicitly |
| Was standard work written and posted? | Standardize before the event closes |
| Is anyone auditing to the standard? | Introduce leader standard work |
| Were 30/60/90-day reviews held? | Schedule them before the event starts |
| Are most actions closed within 30 days? | Scope smaller; implement more during the week |
Most organizations find that the same one or two gaps explain most of their faded events.
Common mistakes
- Measuring success at the report-out instead of at 90 days
- Running events to hit a quota rather than to move a metric
- Leaving more on the action list than was implemented
- Treating workplace organization as the goal instead of the foundation
- Letting the facilitator own the follow-up instead of the process owner
How QMSLean helps
We review your past events to find what held and what slipped, build an event pipeline tied to business metrics, and facilitate events that end with standard work, a visual board and a named owner. We coach leaders on leader standard work and run the 30/60/90-day reviews alongside your team until your own facilitators and process owners carry the system.
See our situation page: “Our Kaizen events don’t stick.” Related reading: building a continuous improvement culture and choosing between A3, Kaizen and Six Sigma.
Tell us what’s going on
Describe what happened with your last few events and a Lean practitioner will reply with how we would approach it. Request a Situation Review, try the free ROI Calculator, or contact us at [email protected].
Is this your situation?
See how QMSLean solves it — and request a Situation Review
Frequently Asked Questions
Why do Kaizen event results fade after a few months?
Usually because the sustain system was missing: no named process owner, no standard work capturing the new method, no leader follow-up, and no scheduled reviews. Oversized scope and events not tied to a business metric are also common causes.
What is leader standard work?
A defined routine for leaders at each level describing what they check, how often, and what they do when they find a gap. It makes follow-up and accountability routine rather than dependent on individual memory.
What happens at 30/60/90-day Kaizen reviews?
The process owner and sponsoring leader check whether the metric is holding, whether standard work is followed, which actions are closed or overdue, and what has changed in the area — then solve any gaps.
Where does 5S fit into a Kaizen event?
Workplace organization is often the opening move inside an event, creating a stable, visible base for the standard work that follows. It works best as a foundation for the improvement rather than as a standalone program.
How big should a Kaizen event scope be?
Small enough that the team can implement most of the changes during the event week. If more is left on the action list than was implemented, the scope was too large.