Kaizen Event Facilitator Kit
A facilitator-ready, practical playbook to plan, run, and sustain a focused 3‑day kaizen. Includes a pre-event scoping checklist, day-by-day facilitator scripts with time blocks and prompts, an experiment-tracking template, a convert-to-standard-work plan, and a sustainment audit checklist you can adapt or convert into interactive forms.
Welcome — What this kit helps you achieve
This compact facilitator kit helps teams plan and run a focused 3‑day kaizen that produces measurable, implemented improvements and becomes part of day‑to‑day standard work. Use it to avoid common failures like loose scope, no metrics, unclear owners, or improvements that fade when leadership attention moves on.
Core outcome
At the end of the kaizen you should have: a clear problem statement, a small set of agreed experiments, one or more implemented changes with measured impact, owners assigned to sustainment actions, and a short plan to convert the change into standard work.
Quick agenda (3 days)
- Pre-event (planning) — 1 to 2 weeks before: scope, sponsor alignment, baseline data collection, invite right people, prework for operators.
- Day 1 — Understand & plan: observe the process, map current state briefly, confirm root causes, agree success metrics, design experiments.
- Day 2 — Run experiments & implement: test rapid experiments, collect results, iterate; begin implementing validated changes.
- Day 3 — Harden & handoff: finalize improvements, create standard work drafts, assign sustainment owners, schedule audits and follow‑ups.
Pre-event scoping checklist (facilitator use)
Use this to confirm whether the kaizen is properly framed and likely to deliver sustained value.
- Problem statement: short, specific, measurable. Example: "Reduce operator changeover time on Cell A from 22 min to 12 min to increase productive hours by X per shift."
- Business case / expected benefit: estimated time/cost savings, quality impact, safety improvement, or lead time reduction.
- Sponsor: name and role with authority to approve changes and resources during the event.
- Scope boundaries: machines, shifts, parts, upstream/downstream limits — what is in and out.
- Baseline data collected: OEE, cycle time, scrap rate, first pass yield, downtime logs as appropriate.
- Team composition: include operator(s), supervisor, maintenance, quality, planner, and a data/measurement owner. Max 6–10 people on the core team.
- Logistics: workspace, whiteboards, materials for experiments, measurement tools, camera for before/after evidence.
- Prework for participants: short observation assignment, bring one example problem, collect one shift of baseline data.
- Success metrics & acceptance criteria: specific target(s) and definition of 'done' for the kaizen.
Day‑by‑day facilitator script (practical prompts)
These are lightweight scripts you can read or adapt. Keep timeboxes tight and measurable.
Day 1 — Observe, agree, design (8–9 hours)
- Start (15 min): Welcome, sponsor message, confirm problem statement and success metrics. Ask: "If this is successful, what will be different by next month?"
- Gemba walk (60–90 min): Observe process with team, ask open questions, capture facts, photos, and timings.
- Current state & data review (60 min): Share baseline data, confirm root-cause hypotheses. Facilitator prompt: "What evidence supports this hypothesis?"
- Prioritize causes (30 min): Use simple voting to focus on 1–2 highest‑impact causes.
- Design experiments (90–120 min): For each cause, create a Plan-Do-Check-Act (PDCA) micro‑experiment with owner, duration, measurement plan.
- End of day (15 min): Capture action list for Day 2, confirm materials and owners. Quick reflection: "What did we learn today?"
Day 2 — Test, measure, iterate (8–9 hours)
- Start (15 min): Review experiments and measurement method. Reconfirm who collects what data and when.
- Run experiments (3–4 hours): Execute short trials. Facilitator tip: keep one experiment small enough to run within a single shift.
- Measure & debrief (90 min): Collect data, compare to baseline, decide whether to adopt, adapt, or abandon each experiment.
- Implement validated changes (120 min): If an experiment succeeds, implement it more broadly (fixtures, markings, part bins, simple fixtures, SOP drafts).
- End of day (15 min): Document improvements, update experiment tracker, list sustainment actions needed.
Day 3 — Standardize & handoff (6–8 hours)
- Start (15 min): Review measured wins and remaining risks.
- Create or update standard work (120–180 min): Draft step-by-step visual instructions, responsibilities, checklists, and one‑point lessons. Involve the operator who will own the work.
- Assign sustainment owners (30 min): For each action, set owner, due date, and audit frequency.
- Handover & sponsor review (30–60 min): Present results and sustainment plan to sponsor; confirm approvals or resource commitments.
- Close (15–30 min): Celebrate wins, quick lessons learned, and schedule follow-up audit dates.
Experiment tracking template (copyable)
Keep experiment records simple and visible. Suggested fields:
- Experiment ID
- Title/Idea
- Owner
- Plan (what will change)
- Duration (e.g., 2 shifts)
- Measure(s) (baseline value, target, measurement method)
- Results (numeric outcome, observed effects)
- Decision (Adopt / Adapt / Abandon)
- Next steps (who will implement and by when)
Example row (short): Experiment 1 — change bin location; Owner: J. Perez; Duration: 2 shifts; Measure: average pick time (baseline 35s → target <20s); Result: 18s; Decision: Adopt; Next: update SOP by Friday (owner: J. Perez).
Convert improvements into standard work
- Document the new steps with photos and short captions.
- Train operators using the new standard work and observe for one shift.
- Update job aids, checklists, and visual signals on the line.
- Set a 30‑ and 90‑day audit schedule and record actions from audits.
- Make the change part of the shift handover checklist and operator onboarding.
Sustainment audit checklist (use weekly → monthly cadence)
Audit questions for owners or auditors. Score yes/no and capture evidence.
- Is the new standard work posted at the point of use and readable? (Y/N)
- Did the operator follow the documented steps during the audit? (Y/N) — if no, why?
- Are the visual aids / markings / bins in the expected locations? (Y/N)
- Are the measured metrics still within target? (Y/N) — include numeric value.
- Were any defects, delays, or safety issues observed related to the change? (Y/N)
- Has ownership been maintained (owner present and accountable)? (Y/N)
- Are there any improvement suggestions from operators since the change? (Y/N) — note them.
- Next audit date and assigned auditor.
Roles, responsibilities & facilitator tips
- Facilitator: keep time, maintain focus on metrics, neutral coach, ensure decisions are recorded and owners assigned.
- Sponsor: unblock resources, approve changes, receive final handoff.
- Operator(s): primary knowledge holders and eventual owners of the standard work.
- Maintenance: evaluate machine fixes and simple preventive actions during the event.
- Quality/Data owner: ensures measures are defined and data capture is reliable.
Facilitator tips: keep experiments small and measurable; avoid big, multi‑week pilots inside a 3‑day event; surface low‑cost, high‑impact fixes first; and document decisions visibly so momentum isn't lost.
Common pitfalls & how to avoid them
- Pitfall: Vague problem statement → Fix: force a metric and an owner during scoping.
- Pitfall: No baseline data → Fix: collect one shift/day of key measures before the event.
- Pitfall: Too many simultaneous experiments → Fix: limit to 2–4 experiments and prioritize by expected impact.
- Pitfall: Changes not standardized → Fix: draft standard work on Day 3 and schedule audits immediately.
How to use this kit with platform capabilities
Turn the Experiment Tracking Template and Sustainment Audit Checklist into interactive forms so teams can save results, run reports across events, and track long‑term sustainment. See Capability Enhancement Notes below for recommended next steps.
Closing — ready to run
Keep this kit close to your kaizen board. Use it as a facilitation script and a minimal process control system: scope clearly, measure quickly, experiment aggressively, and standardize what works. Small, repeated, measured wins build credibility and create capacity for larger improvements.
Discussion
Comments and conversation will live here.