Kaizen Event Management

The failure wasn’t on Day 3 or Day 5. It happened in the four weeks before Day 1.

Knowing the five-day structure and actually running an event that holds its gains are two different things.

Pre-Event: The Work That Determines the Outcome

Event Charter — Six Required Components

1. Problem statement — specific, measurable, current. “Pick productivity in Zone 4 averaging 142 lines/hr against 185 line/hr standard” — not “Zone 4 has issues.”
2. Baseline data — actual WMS performance numbers from the past 30–90 days. Not anecdotes. If you don’t have a baseline, you are not ready to run the event.
3. Target metric — specific and achievable in 5 days. “Improve Zone 4 pick rate to 170 lines/hr” — not “improve Zone 4 performance.”
4. Scope boundaries — what is in scope AND what is explicitly out of scope. The out-of-scope list is as important as the in-scope list. “Excludes WMS configuration changes, capital expenditures, and staffing level decisions” prevents the team from chasing the wrong solution.
5. Team composition — who is in the room every day. See below.
6. Deliverables — the exact list of outputs that must exist by end of Day 5.

Baseline data must be collected before the event starts — not during Day 1. Baseline collection takes 1–2 weeks. Plan for it.

Team Selection — The Single Biggest Variable

If I had to name the one factor that most predicts whether a Kaizen event succeeds or reverts, it is team composition.

Non-negotiable rule: The supervisor whose team operates the target process must be in the room every day. Not observing from a distance. Not joining for the Day 5 presentation. In the room, all day, from Day 1 through Day 5.

Why: The supervisor is the person who will enforce the new standard on Day 6, Day 30, and Day 90. If they didn’t co-design the solution, they don’t own it. When a production crunch hits on Day 45 and the floor reverts, a supervisor who wasn’t in the room will let it slide. One who spent Day 3 running trial runs alongside their team will push back.

Ideal team composition for a pick operation:

Member	Commitment
Area supervisor	Full 5 days — non-negotiable
2–3 operators from target process	Rotate if needed; always have ≥1 operator voice in the room
CI engineer (facilitator)	Full 5 days
IE / IE analyst	Full 5 days (time study, standards support)
“Fresh eyes” representative	Someone from a different dept/facility who asks obvious questions
WMS/systems support	On call Days 1–3; same-day availability

What to avoid: Team of CI engineers and managers with no frontline representation. Supervisor who “drops in” periodically. Team >12 people (diffused accountability, every decision requires a vote).

If the supervisor cannot commit to all five days, delay the event. An event without the supervisor present full-time is theater, not improvement.

The Five-Day Cadence

Day 1 — Baseline and Current State

Morning (≤2 hours): training and orientation on tools (VSM, spaghetti diagram, waste walk); review charter and ground rules. Afternoon: go to the Gemba.

On the floor, document:

• Time every step of the process — 20–30 individual observations, not averages
• Spaghetti diagram: map the actual physical movement path of one operator through one complete cycle
• WIP count at each stage: units waiting, orders held, buffer inventory between steps
• Photos and video (before photos are essential for Day 5 and for sustaining audits)

End of Day 1: Completed current-state VSM or process map; quantified cycle times at each step; spaghetti diagram showing movement waste. Teams are almost always surprised by what the data shows. That surprise is productive.

Day 2 — Brainstorm and Future State Design

Morning: Run current-state data through the waste identification lens. Structured brainstorm: diverge first (no criticism for 30 min), then converge using an effort-impact 2×2.

Effort-impact quadrant focus: Low effort / high impact is where the 5-day event can execute. High effort ideas → action register as post-event projects.

Afternoon: Produce the future state map — a specific, achievable configuration the team can begin implementing Day 3. Physical changes (racking, labels, cart redesign), process changes (step sequence, handoffs), and visual management changes (shadow boards, floor markings, kanban signals) — specified with enough detail that someone can execute without further interpretation.

Day 3 — Trial Runs on the Floor

The hardest day and the most important one.

Test the future state design under real operating conditions. The first trial run will reveal at least one wrong assumption. The relocated printer now blocks the pick cart path. The new pick sequence reduces travel but creates congestion at Station 3. This is not failure — this is the value of Day 3.

Iterate: Run trial → time it → identify what broke → fix → run again. By afternoon: a version tested, timed, and refined under real conditions.

If trial runs produce numbers worse than baseline — figure out why. Usually a scoping problem: team tried to fix too many things at once and created new waste while eliminating old waste. Narrow scope on Day 3 if needed. A smaller validated improvement is worth more than a large theoretical one.

Day 4 — Standardize and Train

Assumes Day 3 produced a validated future state.

1. Standard work documentation: JBS cards that live at the workstation. Photos, not just text. Clear enough that a new associate can orient in <5 minutes.
2. Train every operator in the affected area before end of Day 4 — not “next week when there’s time.” Before Day 4 ends. The new process must be the norm on Day 6 before event momentum fades.
3. Measure final results vs. baseline — this is the official post-event metric for the ROI calculation and Day 5 presentation.

Day 5 — Present and Commit

Morning: Finalize the action register. Items the team identified as valuable but couldn’t complete in 5 days (POs needed, minor WMS configuration change, updated training documentation needing sign-off). Every item: named owner, due date, priority ranking — not a team, not a department, a person.

Afternoon: Present to leadership. Format:

• Current state map → future state map
• Before/after data + before/after photos
• Quantified improvement metric
• ROI rough calculation
• 30/60/90-day action register
• Keep to ≤20 minutes

Name the post-event sustaining champion during Day 5 — almost always the area supervisor who was in the room all week. They own the new standard, action register execution, and the 30/60/90-day check-ins.

Required Deliverables — All Six, No Exceptions

Deliverable	Owner
Future state map	CI engineer
Standard work (JBS cards at workstations)	CI engineer + supervisor
Action register with named owners and dates	CI engineer
Improvement metric (before vs. after)	CI engineer
Before/after photos	CI engineer
ROI calculation (even rough)	CI engineer

If any of these are missing, the event is incomplete. Do not close the event without them.

30/60/90-Day Check-Ins

50–70% of Kaizen gains erode within 6 months without structured follow-up.

Check-in	Questions	Action if problem
30 days	Is the new standard followed? Are metrics holding? Is the action register being executed?	If metrics slipped: “what in the environment made it easier to revert?” — not “why aren’t people following the standard?“
60 days	Are action register items completed? Have refinements emerged from practical experience?	8 overdue action items with no owners = structural problem
90 days	Final validation. Calculate actual sustained improvement vs. original baseline	Update VSM to new current state — this becomes the baseline for the next event

The single biggest predictor of sustained gains: Was someone explicitly named as the post-event owner, with their name attached to specific metrics and review dates? Not a team. A person.

Target Selection Criteria — All Three Required Simultaneously

1. Pareto of pain: The problem is in the top 20% of waste or cost data. Requires actual WMS data, not gut feel.
2. Leadership sponsorship: DC manager is personally invested and will attend Day 5.
3. Measurable baseline: Actual data on the current state exists. If you can’t measure where you start, you can’t measure whether you succeeded.

Common Failure Modes

Failure mode	Prevention
Scope creep	”Excludes X, Y, Z” in the charter out-of-scope list; protect scope actively on Days 2–3
No post-event ownership	Name sustaining champion before Day 5 ends; schedule 30-day check-in before everyone leaves the room
ROI never measured	Calculate it even when the math is rough; document in the annual CI program summary