You have probably been there. The event flyer goes up in the
breakroom three weeks ahead. “KAIZEN BLITZ — TEAM A — LINE 3 — NEXT
MONDAY.” There is food, there are sticky notes, there is energy. For
five days, a cross-functional team tears apart a workstation, redesigns
the flow, moves equipment, and by Friday afternoon, they are
celebrating. The before-and-after photos look fantastic on the plant
manager’s slide deck. The banner gets rolled up. Everyone goes back to
their regular jobs.
And then, six weeks later, somebody walks past Line 3 and notices
that the new flow has drifted back to the old flow. The shadow boards
have missing tools. The standardized work documents posted at the
station do not match what the operators are actually doing. The “24%
productivity improvement” that was reported up the chain? Nobody can
reproduce those numbers. The kaizen event — that intense,
well-intentioned burst of improvement activity — produced a demo, not a
transformation.
This is not an argument against kaizen events. Run properly, they are
one of the most powerful tools in the Lean toolkit for breaking through
inertia, demonstrating what is possible, and building momentum for
change. But the way most organizations run them, they are a performance.
A theatrical production with a run of five days and an audience of
executives who clap at the finale and then leave the theater wondering
why the show does not continue.
Let us talk about why kaizen events fail to stick, what they actually
look like when they work, and how to stop confusing activity with
achievement.
What a Kaizen Event
Is — and What It Is Not
A kaizen event (sometimes called a kaizen blitz, rapid improvement
event, or continuous improvement workshop) is a structured, time-bounded
activity in which a dedicated team focuses intensively on improving a
specific process or area. Typically lasting three to five days, the
event brings together operators, engineers, maintenance, quality, and
sometimes customers or suppliers to analyze a process, identify waste,
design improvements, implement them, and establish standards to sustain
the new state.
The concept comes from the Toyota Production System, where kaizen
means “change for the better” — small, incremental improvements made
continuously by the people who do the work. The irony is that in many
Western implementations, kaizen has come to mean almost the opposite: a
large, episodic burst of improvement imposed on a process by a temporary
team that then disperses.
In Toyota’s culture, kaizen is daily. It is an operator adjusting a
tool location by two centimeters because it reduces reach. It is a team
leader noticing a recurring micro-stoppage and investigating on the
spot. The event format — gathering a team for a concentrated week —
exists in Toyota too, but it sits on top of a foundation of daily
improvement habit. Most companies skip the foundation and go straight to
the event, expecting the event itself to create a culture of continuous
improvement. It cannot. A fishing trip does not teach someone to
fish.
Where Kaizen Events Go Wrong
The Selection Problem
Many organizations select kaizen event targets based on visibility
rather than value. A manager wants to show quick wins, so the team picks
something easy — reorganizing a stockroom, cleaning up a shadow board,
labeling cabinets. These improvements are real but superficial. They do
not touch the structural constraints that limit throughput, quality, or
cost. After several such events, the organization has a lot of cosmetic
before-and-after photos and the same fundamental problems it started
with.
The countermeasure is to tie event selection to the value stream map
and the site’s strategic objectives. Where is the constraint? Where is
the largest source of customer complaints? Where does the data show the
most significant quality loss? These are uncomfortable targets because
they are politically complicated and technically difficult. But they are
the targets where a kaizen event can produce genuine, measurable
impact.
The Composition Problem
A common mistake is staffing the event with managers and engineers
while pulling operators out for only an hour or two of “input.” This
produces solutions that look elegant on paper and fail on the shop floor
because the people who actually run the process were not the ones
designing the new state. The operators return to find their workstation
rearranged, their tools moved, their routine disrupted — and they had no
say in any of it. Resistance is not a personality flaw; it is a rational
response to having changes done to you rather than with you.
The fix is non-negotiable: operators from the target area must be
full participants in the event, not consultants consulted on the side.
They know where the real friction lives. They know which “improvements”
will actually make the job harder. And critically, their involvement is
what creates ownership — the psychological foundation of
sustainment.
The Implementation Problem
Friday afternoon at 4:30 PM. The team has redesigned the cell, moved
the equipment, written new standardized work, and trained the operators
on the new procedure. Everyone is tired and proud. The event facilitator
declares success. The plant manager shakes hands. Photos are taken.
What happens Monday morning?
In too many cases, the answer is: drift. The new standardized work
was written under time pressure and contains assumptions that do not
hold up under real production conditions. The operators who were trained
on Friday have forgotten half the details by Monday. The equipment that
was moved is not quite right — the conveyor is two degrees off, causing
intermittent jams that were not there before. The support team that was
supposed to follow up on open items gets pulled into a quality fire
elsewhere. Within two weeks, the process has reverted.
Implementation during a kaizen event should follow a simple rule: do
not attempt more than you can stabilize. It is better to implement three
changes thoroughly — with piloting, validation, training, and
documentation — than to attempt ten changes and leave all of them
half-done. The goal of the event is not to demonstrate how much you can
change in a week. The goal is to leave the area better than you found it
and positioned to continue improving.
The Measurement Problem
“We improved productivity by 30%!” This claim, made at the Friday
report-out, is almost always based on a comparison between the
worst-case baseline (deliberately or unconsciously chosen to make the
improvement look dramatic) and the best-case post-event performance
(measured during a controlled demo run, not during steady-state
production). Real productivity is measured over weeks, not minutes.
A robust measurement plan includes:
- A baseline period of at least two to four weeks before the event,
using routinely collected data (not a special study) - A stabilization period of at least two to four weeks after the event
before declaring the new state “established” - Ongoing monitoring for at least 90 days post-event to confirm the
improvement has held - Honest accounting that includes any negative side effects — did the
improvement in one area create a bottleneck in another?
What Good Looks Like
A well-executed kaizen event shares several characteristics that
distinguish it from the failure modes above.
Clear charter tied to business value. Before the
event begins, there is a one-page charter that defines the problem (not
the solution), the target metrics, the scope boundaries, and the team
composition. The charter is reviewed and approved by leadership,
ensuring alignment and preventing scope creep during the event
itself.
Pre-work that matters. The facilitator and team
leader spend one to two weeks before the event collecting baseline data,
mapping the current state, and identifying the key questions the team
needs to answer. This means that when Monday morning arrives, the team
hits the ground running rather than spending two days figuring out what
is going on.
Time in the gemba. A kaizen event that happens in a
conference room is a planning meeting, not an improvement event. The
team should spend significant time at the actual workplace — observing
the process, talking to operators, timing cycles, looking for waste. The
conference room is for synthesis and decision-making, not for
discovery.
Try-storming over planning. The best kaizen events
involve physical experimentation. Instead of debating whether a new
layout will work, the team builds it — with cardboard, tape, temporary
fixtures, whatever is available — and runs real product through it. This
approach, sometimes called “try-storming,” generates evidence rather
than opinions and catches problems that a PowerPoint would miss.
A documented 30-60-90 day follow-up plan. At the
report-out on Friday, the team presents not just what was accomplished
but what remains. Open items are assigned owners and due dates. A 30-day
check is scheduled. A 60-day audit is planned. A 90-day metrics review
is calendared. The event is framed as the beginning of the improvement,
not the completion.
The Sustainment Question
The single biggest predictor of whether a kaizen event’s gains will
hold is what happens in the 90 days after the event. Not the 5 days
during it.
This means that the most important person in the kaizen event process
might not be the facilitator or the team leader — it might be the area
supervisor who was not on the team but who will be responsible for
sustaining the changes. If that person is not engaged before, during,
and after the event, sustainment is in jeopardy.
Practical sustainment mechanics include:
- Daily verification by the supervisor for the first
two weeks, using a simple checklist: Is the new standardized work being
followed? Are the tools in the correct locations? Are the metrics being
tracked? - Weekly audits for the first month, with findings
addressed immediately — not queued for the next event - Operator feedback channels — a whiteboard at the
workstation where operators can note issues with the new process, with a
commitment from the supervisor to review and respond within 24
hours - Leadership gemba walks that specifically visit the
event area and ask about the improvements — not to admire them, but to
verify they are still in place and to ask what the team is working on
next
Building a
Kaizen Culture, Not a Kaizen Event Program
The organizations that get the most value from kaizen events are the
ones that view events as an accelerator of a broader improvement
culture, not as the culture itself. In these organizations, operators
make small improvements daily — adjusting a fixture, reorganizing a
bench, modifying a sequence. Team leaders facilitate weekly improvement
huddles. Supervisors coach on problem-solving methods. And kaizen events
are reserved for the problems that require concentrated,
cross-functional effort — the ones that cannot be solved by daily
incremental change.
This is the real lesson. A kaizen event is a tool, not a strategy.
When it is the only tool in your improvement system, every problem looks
like it needs an event, and the events become a substitute for the daily
discipline of continuous improvement. You end up with a calendar full of
blitzes and a culture empty of ownership.
The goal is not more events. The goal is fewer events — because the
daily improvement system is handling the routine problems, and events
are reserved for the genuinely complex challenges that warrant the
investment. If your organization is running thirty kaizen events a year
and the floor still looks the same, the problem is not the events. The
problem is what is happening — or not happening — on the 300 days when
there is no event.
Start there.
Peter Stasko is a Quality Architect with over 25 years of
experience in manufacturing quality, continuous improvement, and
operational excellence. He has led and participated in hundreds of
kaizen events across automotive, electronics, and industrial sectors —
and has seen firsthand why some transformations last and others
evaporate within a quarter. He writes about what actually works on the
factory floor, not what looks good in a slide deck.
