You have seen it happen. The kaizen event finishes on Friday. The
team presents their results to management. There are congratulations,
photographs, perhaps a banner hung over the improved workstation. The
metrics look excellent. The before-and-after comparison is dramatic.
Everyone agrees this is what continuous improvement looks like.
Then you walk through that same area six weeks later. The
standardized work document is pinned to a board nobody reads. The shadow
board for tools has missing outlines where someone rearranged things for
convenience. The cycle-time reduction everyone celebrated has slowly
crept back to its original number, and nobody seems alarmed because
nobody is tracking it anymore. The improvement did not survive contact
with Monday morning.
This is not a failure of kaizen. Kaizen, properly understood, is one
of the most powerful ideas in manufacturing. The word itself means
“change for better,” and the philosophy behind it — that improvement
should be continuous, incremental, and driven by the people who do the
work — has transformed industries around the world. Toyota’s production
system, the gold standard of manufacturing excellence, is built on this
foundation. Small improvements, every day, by every person, accumulating
over time into capabilities that competitors cannot replicate.
But something happens between the philosophy and the practice.
Organizations adopt the language of continuous improvement without
building the discipline to sustain it. They run kaizen events as
projects with start dates and end dates rather than as expressions of an
ongoing culture. They measure the success of an improvement by the
magnitude of its initial impact rather than by its durability over time.
And they create a paradox: a continuous improvement program that
produces improvements which are anything but continuous.
The result is an organization that gets worse at improving while
believing it is getting better. It accumulates improvement events the
way it accumulates quality certifications — as artifacts of performance
rather than evidence of it. And the gap between what the improvement
program reports and what the production floor experiences grows wider
with each passing quarter until the program becomes something people
participate in rather than something they believe in.
The Event Trap
The most common distortion of kaizen is the transformation of a
continuous process into a discrete event. Kaizen events, sometimes
called kaizen blitzes or rapid improvement events, are structured
workshops where a team focuses intensely on improving a specific process
over a compressed timeframe, typically three to five days. They can be
extraordinarily effective. The intensity creates focus. The
cross-functional team brings perspectives that no single function
possesses. The compressed timeline forces decisions that endless
analysis would postpone indefinitely.
The problem is not the event itself. The problem is that the event
becomes the entire program.
When an organization equates continuous improvement with kaizen
events, several things happen. First, improvement becomes episodic
rather than continuous. It happens in bursts separated by long periods
of stasis, like a heart arrhythmia rather than a steady pulse. The gains
from each event decay during the intervals between events, and the
organization must spend a portion of each subsequent event recovering
ground it has already gained rather than advancing into new
territory.
Second, improvement becomes the responsibility of a specialized team
rather than the daily practice of every person on the floor. The kaizen
event team becomes the improvement team, and everyone else becomes an
audience. Operators learn that improvement is something that happens to
them, not something they do. They wait for the next event instead of
making improvements themselves. The organization’s improvement capacity
concentrates in a small group of people rather than distributing across
the entire workforce, and that small group becomes a bottleneck.
Third, the focus on events creates a bias toward improvements that
are visible within the event’s timeframe. Teams gravitate toward changes
that produce immediate, measurable results because those results
validate the event’s existence and justify its cost. Improvements that
are more subtle, more systemic, or more long-term — the kind that
compound over months and years into transformative capabilities —
receive less attention because they cannot be demonstrated in a Friday
afternoon presentation to management. The organization optimizes for the
spectacle of improvement rather than the substance of it.
The Sustainability Gap
Every improvement has a half-life. The new standard work degrades as
operators take shortcuts. The visual management system fades as people
stop updating it. The redesigned layout slowly reverts as equipment
drifts back to positions of convenience rather than positions of
efficiency. The statistical process control chart that was the
centerpiece of the kaizen event becomes just another piece of paper on
the wall.
This is not because people are lazy or resistant to change, though
those factors exist. It is because sustainability requires a system, and
most kaizen events produce improvements without producing the system
needed to sustain them.
A sustainable improvement requires several things that the typical
kaizen event does not provide. It requires ongoing measurement — not
just the before-and-after comparison, but a continuous stream of data
that shows whether the improvement is holding or decaying. It requires
accountability — someone whose explicit responsibility is to monitor the
improvement’s sustainability and intervene when it starts to slip. It
requires integration into the management system — the improvement must
become part of the daily routine, part of the standard work, part of
what supervisors check during their walks. And it requires adaptation —
the conditions that made the improvement effective will change, and the
improvement must change with them.
Most kaizen events address none of these requirements. They end with
a presentation, a celebration, and a handoff that is more theoretical
than actual. The team returns to their regular jobs. The area
supervisor, who may or may not have been deeply involved in the event,
is now responsible for sustaining improvements they may not fully
understand. And the improvement begins its slow decay into
irrelevance.
The mathematics of this are brutal. If an organization runs twelve
kaizen events per year and each improvement decays by thirty percent
within three months, the organization’s net improvement over time
approaches zero. It is running on a treadmill, expending enormous energy
to stay in the same place. The improvement program reports impressive
activity metrics — events completed, people trained, dollars saved on
paper — but the production floor sees no lasting change. The program
becomes performative.
The Suggestion System That
Isn’t
The kaizen philosophy depends on one critical assumption: that the
people closest to the work have the best insight into how to improve it.
This is why Toyota’s production system emphasizes every worker’s
authority and responsibility to identify problems and propose solutions.
The suggestion system is not a bonus program. It is the nervous system
of the organization, transmitting information from the point of
execution to the point of decision.
Most organizations that adopt kaizen miss this entirely. They create
suggestion systems that are bureaucratic, slow, and unrewarding. An
operator submits a suggestion and waits weeks for a response. The
suggestion is evaluated by a committee that has never stood at the
workstation in question. The criteria for approval prioritize cost
savings over safety, ergonomics, or quality improvements that are real
but difficult to quantify. The suggestions that are approved are
implemented by engineers who may not consult the person who submitted
the idea. And the feedback loop — the critical mechanism that tells the
submitter their idea was heard, considered, and valued — is either
absent or so delayed that it has no motivational impact.
The result is predictable. Suggestion rates drop to near zero within
a few months of the program’s launch. The organization concludes that
its people do not have ideas, which is never true. What its people do
not have is a system that makes submitting ideas worth their time. The
improvement capacity of the frontline workforce — the most underutilized
resource in most manufacturing organizations — remains untapped while
the kaizen event team runs another event to solve a problem that an
operator could have prevented months ago with a twenty-dollar fixture
and five minutes of conversation.
The Metrics Illusion
Every continuous improvement program measures itself. The metrics
vary — number of events, ideas implemented, cost savings, cycle-time
reductions, defect-rate improvements — but the practice is universal.
Organizations track their improvement activity because they need to
justify the program’s existence, demonstrate return on investment, and
identify areas for further improvement.
The problem is that most improvement metrics measure activity rather
than impact. They count events held, suggestions submitted, and people
trained without measuring whether the improvements from those events are
still in place, whether the suggestions were actually good ideas, or
whether the trained people are applying what they learned. The metrics
create a picture of a thriving improvement program that may bear little
resemblance to the reality on the production floor.
Cost savings are particularly vulnerable to distortion. Improvement
teams are motivated to estimate savings aggressively because aggressive
estimates justify the event’s cost and demonstrate the program’s value.
These estimates are rarely audited. A kaizen event that reportedly saved
one hundred thousand dollars per year may produce actual savings of
thirty thousand, or ten thousand, or nothing at all if the improvement
decays before it can generate meaningful returns. But the one hundred
thousand dollar figure is what gets reported, what gets aggregated into
the program’s annual total, and what gets presented to management as
evidence of success.
Over time, the accumulated distortion creates a credibility gap.
Finance begins to question the improvement program’s numbers. Production
managers observe that their actual costs are not declining in proportion
to the reported savings. Operators notice that the improvements
celebrated in reports do not match their daily experience. And the
improvement program, rather than being a source of competitive
advantage, becomes another corporate function whose primary product is
its own reporting.
The Cadence Problem
True continuous improvement, the kind practiced at Toyota and other
genuinely excellent manufacturers, operates on a daily cadence. Every
shift begins with a brief meeting where problems from the previous shift
are communicated. Every workstation has a visual display showing current
performance against target. Every supervisor walks the floor on a
regular schedule, checking standard work adherence and asking operators
what problems they are experiencing. Every problem triggers a structured
response that is tracked to completion.
This daily cadence is the engine of continuous improvement. It is
unglamorous, repetitive, and relentless. It does not produce dramatic
before-and-after presentations. It does not justify banners or
celebrations. But it is what keeps improvements alive and what surfaces
new improvement opportunities before they become crises.
Most organizations cannot sustain this cadence. It requires a level
of management discipline, floor presence, and standard-work adherence
that conflicts with the firefighting mode most manufacturing managers
operate in. The daily meeting gets shortened or skipped when production
is behind, which is exactly when it is most needed. The supervisor’s
standard walk gets postponed because there is a more urgent problem
elsewhere. The visual management display stops being updated because
nobody has time to update it. And the continuous improvement cadence,
which was supposed to prevent the problems that cause the firefighting,
is the first thing sacrificed to the firefighting it was supposed to
prevent.
This is a self-reinforcing failure mode. The organization stops
improving continuously because it is too busy dealing with problems. The
problems become more frequent and more severe because the organization
stopped improving continuously. And the cycle accelerates until the
improvement program exists in name only while the production floor
operates in perpetual crisis mode.
Building What Lasts
The alternative to this failure mode is straightforward in concept
and demanding in execution. It requires the organization to value
sustainability over spectacle, daily discipline over periodic events,
and frontline empowerment over specialist expertise.
Start by measuring sustainability explicitly. For every improvement,
define the metric that will indicate whether it is holding. Track that
metric weekly for the first month, monthly for the first quarter, and
quarterly thereafter. Make sustainability a visible part of the
improvement program’s reporting. If an improvement decays, investigate
why and address the root cause rather than simply re-running the
event.
Distribute improvement capability across the organization rather than
concentrating it in a specialized team. Train supervisors to lead small
improvements within their areas. Give operators the authority and the
time to make changes within defined boundaries. Make improvement part of
everyone’s job description and everyone’s performance evaluation, not
just the kaizen team’s.
Redesign the suggestion system for speed and responsiveness. Set a
maximum response time of forty-eight hours for any suggestion. Give
frontline supervisors the authority to implement small improvements
without committee approval. Close the feedback loop every time, even
when the answer is no — especially when the answer is no, because a
prompt and respectful rejection builds more trust than a slow and
bureaucratic approval.
Establish the daily cadence and protect it ruthlessly. The daily
meeting is not optional. The supervisor’s floor walk is not optional.
The visual management display is not decorative. These are the
mechanisms that sustain improvements and surface problems, and they must
be treated with the same discipline as production schedules and safety
protocols.
And stop measuring activity. Count improvements that are still in
place six months after implementation rather than events completed.
Track the trend of key process metrics over time rather than the
cumulative reported savings of individual events. Ask operators whether
their work is actually improving rather than asking the improvement team
whether they are busy.
Kaizen is not an event. It is not a program. It is not a department.
It is a discipline — the discipline of getting a little bit better every
day, everywhere, by everyone. Organizations that understand this build
capabilities that compound over time into advantages that competitors
cannot buy, copy, or shortcut. Organizations that do not understand this
build an impressive archive of improvement reports while their
production floors get slowly, steadily worse.
The choice between these outcomes is not complicated. It is just
hard. And most organizations, given the choice between doing the hard
thing that works and the easy thing that looks good, will choose the
easy thing every time. Their improvement programs reflect that
choice.
Peter Stasko is a Quality Architect with over 25
years of experience in manufacturing quality systems, continuous
improvement, and operational excellence. He has led kaizen
transformations across automotive, electronics, and heavy industry
sectors on three continents.
