All methods

Kaizen Event

Typical duration:
4h

An intensive, time-boxed improvement workshop where a cross-functional team analyses a specific process, identifies waste, and implements changes within days.

Purpose

A Kaizen Event (Kaizen Blitz or Rapid Improvement Event) concentrates improvement energy into a short burst. Unlike continuous small improvements, a Kaizen Event tackles a significant process problem with a dedicated team and delivers measurable results within one to five days.

At a glance

AttributeDetail
Group size5 – 12
Duration4 hours (condensed) to 5 days (full)
DifficultyHigh
Facilitation styleFacilitator-led with heavy participation
SettingOn-site at the process location

How to run

  1. Scope and charter (30 min) — Define the target process, improvement goals, boundaries, and success metrics.
  2. Current-state mapping (60 min) — Map the process as-is using value-stream mapping or process flow diagrams. Identify waste: waiting, overproduction, defects, motion, etc.
  3. Root-cause analysis (30 min) — Use 5 Whys or fishbone diagrams to find the systemic causes of the biggest wastes.
  4. Design future state (45 min) — Redesign the process to eliminate or reduce waste. Map the future-state flow.
  5. Implement changes (45 min or days) — Make the changes: rearrange workstations, update procedures, automate steps, remove hand-offs.
  6. Verify and standardize (30 min) — Run the improved process. Measure results against the baseline. Document the new standard.
  7. Report out (15 min) — Present results to leadership. Celebrate wins.

Materials needed

  • Value-stream mapping supplies (large paper, markers, sticky notes)
  • Baseline metrics for the target process
  • Improvement charter template
  • Camera or device for before/after documentation
  • Stopwatch for time observations

Pitfalls & common mistakes

  • Scope too broad — Focus on one process, not the entire value stream.
  • No baseline data — Without before-and-after metrics, improvement claims are unverifiable.
  • No management support — Changes that require budget or authority need pre-approval.
  • Improvements not sustained — Without standard work and follow-up audits, the process drifts back.

Inclusion & accessibility

  • Include frontline workers who actually perform the process.
  • Use visual mapping so language barriers are reduced.
  • Ensure the event location is accessible to all participants.

Variations

  • Virtual Kaizen — For remote teams, use digital process mapping and implement changes through tooling updates.
  • Mini Kaizen — A 4-hour condensed version focusing on one specific waste.
  • Kaizen newspaper — Track all improvement ideas in a shared log; implement during dedicated Kaizen days.

When NOT to use this

  • If the problem is a people issue (conflict, skill gap) — coaching or training is more appropriate.
  • If there is no authority to implement changes — secure sponsorship first.
  • If the process is about to be replaced entirely — improve the new process instead.

Source & further reading

  • Imai, M. (1986). *Kaizen: The Key to Japan's Competitive Success*. McGraw-Hill.
  • Rother, M. & Shook, J. (1999). *Learning to See*. Lean Enterprise Institute.

Turn the building blocks into an agenda

Create the day, drag the blocks into the order you have in mind, and let the times work themselves out. Or describe what you are planning to your AI and let it write the first draft.

Try it free for 14 days
Kaizen Event · GoodWorkshop