Running Your First Kaizen Event

There are two ways a kaizen event fails. The first is poor scoping — the team tries to solve everything and solves nothing. The second is poor follow-through — great ideas are generated but implementation is assigned to the "regular workload," where they die quietly.

A well-run kaizen event has a narrow, specific scope; a full-time, cross-functional team; and a non-negotiable commitment that changes will be implemented before the team leaves the floor on Day 5.

Before the Event: Three Weeks of Preparation

Do not skip the pre-work. The event itself is for action, not analysis. Before Day 1, the team lead should have: defined the scope boundary clearly (one process, one cell, one value stream segment), conducted baseline time studies and documented the current state, and identified the target condition — what "good" looks like at the end of Day 5.

Day 1: Observe and Document

Go to the Gemba. Every team member walks the process, watches it run, and records observations. No ideas, no solutions — just observation. At the end of Day 1, the team maps the current state in detail: time elements, waiting, defects, motion, WIP levels. You will see things you never noticed before. That is the point.

Day 2: Analyze and Design

Using the current-state data, identify the top three wastes and their root causes. Design the future state — not a dream state, but a state achievable in 72 hours with the materials at hand. Assign every improvement a single owner and a deadline within the remaining days.

Days 3–4: Implement

This is where kaizen events fail or succeed. The team physically implements the changes: moves equipment, makes shadow boards, writes standard work, adjusts jigs and fixtures. No PowerPoints. No recommendations. Real changes, measurable today.

Day 5: Measure and Sustain

Run the process under the new standard. Measure the actual improvement against baseline. Identify the 30/60/90-day follow-up actions and assign them with owners. Present to plant leadership — not a status report, but a demonstration of the improved process.

One caution: do not run a kaizen event unless leadership is committed to implementing what the team proposes. Nothing destroys a CI culture faster than a team that works hard on genuine improvements and is told "thanks, we'll think about it."