How to run a 5-day Kaizen event (without it falling apart on day 2)
A Kaizen event (sometimes called a Kaizen blitz or rapid improvement event) takes a bounded problem, a cross-functional team, and 5 dedicated days — and ships a measurable improvement at the end. Done right, it outperforms a 3-month DMAIC on the right kind of problem.
Day 1 — Map current state
VSM of the target process with real data. Walk the Gemba. Waste walk across DOWNTIME. By end of day: current-state VSM on the wall, top wastes identified and costed.
Day 2 — Design future state
Root cause on the top 2-3 wastes. Future-state VSM. Countermeasure brainstorm. By end of day: team aligned on 3-5 specific countermeasures to pilot this week. Not 50. Five.
Day 3 — Pilot
Implement the countermeasures, small-scale. Observe, measure, adjust. Do NOT try to roll out to the whole area yet. The goal is proof of concept by end of day.
Day 4 — Validate + refine
Measure pilot results against baseline. Refine what's not working. Update the future-state map with what actually worked. Draft the sustainment plan.
Day 5 — Closeout + handover
Final report-out to leadership with baseline, countermeasures, pilot data, rollout plan, sustainment plan. Process owner named. 30/60/90 day review dates set. Event officially closed.
Four failure modes
- Scope too big — a Kaizen covers one value stream, not a plant
- Team not dedicated — if leadership lets people 'drop in,' the event collapses
- Executive not present at closeout — no signoff means no sustainment
- Rollout planned but never scheduled — gains drift within 30 days