A focused week to tear apart one specific problem.
A kaizen event is one of the most useful and most abused tools in lean. The format is simple: pull a small team off their normal duties for three to five days and have them tear apart one specific problem on the shop floor. Used well, an event produces a real change to how the work gets done by Friday. Used badly, it produces a binder of action items that fade within a month. The difference is almost always in the scope and the follow-up, not the workshop itself.
"An event without a daily habit underneath is a fireworks show. Bright, brief, gone."
A typical event runs five days with a team of four to eight people, including the workers who actually do the job. Day one is current-state observation. The team watches the process, times the cycles, walks the floor, and documents what is really happening. Day two is analysis. The waste in the process gets named, root causes get discussed, and the team picks a small number of specific changes to test. Day three and four are the actual experimentation. Changes get tried on the floor, with the team measuring results in real time. Day five is consolidation: the new method gets written down, the standard work gets updated, and the team presents what they did to leadership.
The shape of a useful event is narrow scope and immediate testing. "Reduce setup time on the main mill from 90 minutes to 30 minutes" is a workable scope. "Make the shop more efficient" is not. Inside the narrow scope, the team has full authority to try changes without waiting for permission. That authority is what makes the format productive. If a team has to ask leadership before moving a bin, the week is over before the bin gets moved.
The follow-up is what makes the event matter. Most events fail not on day five but on day 35. The new standard the team set survives only if a specific person checks on it every day for the first month, sees where it drifts, and updates it. Without that, the changes erode and the binder of results goes on a shelf.
Imagine a 40-person machine shop where the setup on the main mill takes 90 minutes and the team runs giant batches to amortize the cost. Lead times have crept out to six weeks. Daily kaizen is not going to fix this. The setup is a chronic problem that needs a concentrated push.
A five-day event would put the lead operator, two machinists, the shift lead, and the maintenance tech in a small team. Day one they video three full setups. Day two they break the setup into internal and external steps and identify a handful of changes (pre-stage tooling, swap two screws for quarter-turn fasteners, move the program load to before the spindle stops). Day three and four they test the changes on real setups. By Friday they have the setup down to 35 minutes and a one-page new standard posted at the mill.
Six weeks later, the setup is still 35 minutes because the shift lead has been checking on it every Monday and updating the standard when small drift shows up. That is what a working kaizen event looks like, and the post-event discipline is most of the work.
A kaizen event is the workshop format; the daily habit underneath is kaizen itself. Within an event, the team may produce a point kaizen (a narrow local improvement) or, with broader scope, a flow kaizen aimed at the whole value stream. When the change being attempted is too large for a week-long event, the right pattern is usually kaikaku, a structured large-scale redesign rather than a sprint.
The questions we hear most about this term.
Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.
Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.
.svg)
.svg)
%201.svg){kind=logo}
.png)
.svg)
.svg)
