Kaizen event runbook: plan, run, and follow up

Purpose

Run a focused 3–5 day kaizen event that produces measurable gains and locks them into everyday work. This runbook helps teams prepare, run experiments safely, capture learning, update standards, and create a simple sustainment plan so improvements stick.

Outcomes (the Hungers this serves)

• Deliver measurable process improvement (cycle time, first-pass yield, lead time, cost per unit, throughput, etc.).
• Embed changes into standard work and routines so improvements persist.
• Transfer knowledge so teams can repeat and extend improvements elsewhere.

Before the event — planning checklist

• Define clear scope and objective (what metric will change, by how much, by when).
• Record baseline metrics (how you measure success). Capture data and sampling method.
• Secure an executive sponsor and a local process owner.
• Assemble a cross‑functional team (process operator, engineer, quality, maintenance, supervisor, materials, customer rep where relevant).
• Reserve physical space, tools, materials, and access to systems during the event.
• Prepare a high‑level process map or SIPOC and photos of the area.
• Create a one‑page event charter (see template below).
• Set communications: announce goals, expected outcomes, and follow‑up cadence.

Event charter (one page)

• Title / Process
• Scope (start/end, included/excluded)
• Business case (baseline metric and target)
• Sponsor and process owner
• Team members and roles
• Planned dates and location
• Risks / constraints

Roles & responsibilities

• Sponsor: Clears resources, removes barriers, approves scope and targets.
• Process owner: Owns follow‑through and sustaining standards after the event.
• Facilitator / Kaizen lead: Keeps the agenda, ensures PDCA discipline, documents outcomes.
• Data owner / Measurement lead: Verifies baseline and post‑change measurements.
• Team members: Contribute ideas, test quick experiments, and document standard work.

Sample 3‑day agenda (adaptable to 4–5 days)

1. Day 1 — Observe the current state: walk the process, validate the baseline, map the process, identify wastes and root causes (fishbone/5 whys).
2. Day 2 — Generate and prioritize countermeasures; design safe quick experiments and updated process flows; prepare materials and training for pilots.
3. Day 3 — Pilot changes, collect measurement data, evaluate results, refine, and create proposed standard work and control plan.

When extending to 4–5 days, use extra time for deeper piloting, more rigorous measurement, stakeholder training, or addressing supply/IT changes that require coordination.

Measurement plan

• Define primary metric(s) and how they are measured (units, sampling frequency, owner for measurement).
• Record baseline values and acceptable variation; capture secondary metrics (safety, quality, morale) to detect side effects.
• Use simple before/after comparisons with short sampling windows during the pilot; avoid large statistical tests unless needed.

During the event — practical steps

• Start each day with a short huddle to align tasks and owners.
• Keep experiments small, observable, and reversible where possible.
• Log every experiment: hypothesis, steps, expected result, measurement window, outcome (see Experiment Log template below).
• Use rapid cycles of PDCA: Plan, Do, Check, Act — document decisions and rationale.
• Take photos, capture videos of improved flow, and record updated layouts for standard work.

Experiment log (template)

• Date / Experiment ID
• Hypothesis (If we do X, then Y will change by Z)
• Steps to run experiment
• Measurement method and owner
• Result and analysis
• Decision (adopt / revise / reject) and next steps

After the event — sustainment and handover

• Assign clear action owners and due dates for each follow‑up item; capture in an Action Tracker.
• Update standard work, checklists, visual controls, and training materials immediately after pilots are accepted.
• Schedule short audits or gemba checks: week 1, week 4, month 3 as a minimum. Sponsor or process owner should review results.
• Capture lessons learned in a short knowledge artifact (what worked, what didn’t, data, photos, who to contact).

Action tracker (minimum fields)

• Action description
• Owner
• Due date
• Status (Not started / In progress / Complete)
• Verification (who verified and when)

Common pitfalls and how to avoid them

• Problem: Vague scope or no clear metric. Fix: Create a one‑page charter with measurable targets.
• Problem: No sponsor follow‑through. Fix: Get sponsor commitment to review follow‑up checks and remove barriers.
• Problem: Changes not standardized. Fix: Require updated standard work and a verification step before closing actions.
• Problem: Too many ideas and not enough follow‑through. Fix: Prioritize experiments by impact and ease, limiting active experiments to what can be supported.

Quick checklist for closing the event

• Baseline and post‑pilot measurements recorded and reviewed.
• Standard work updated and signed by process owner.
• Action tracker has owners, dates, and verification steps.
• Sponsor review completed and acceptance recorded.
• Follow‑up checks scheduled (W1, W4, M3).
• Knowledge capture artifact created and shared.

Templates & tools (starter list)

• Event charter (one page)
• Process map / SIPOC template
• Baseline data capture sheet
• Experiment log
• Action tracker with verification field
• Standard work template (step, time, image, owner)

Next steps for toolkit owners (capability notes)

Consider packaging this runbook with interactive forms for the charter, experiment log, and action tracker so teams can save submissions, track progress, and report outcomes centrally. Also consider making the runbook part of a reusable Kaizen Events Toolkit that teams can copy and tailor for site‑specific hungers.

Quick references

• Typical event length: 3–5 days (use longer when IT, suppliers, or engineering deliverables are required).
• Focus on measurable impact and a simple sustainment plan—doing so prevents temporary gains from slipping away.