Facilitation & Kaizen Event Leadership

Plan and run a kaizen event: preparation, team, a day-by-day 5-day structure, facilitation skills, the 30/60/90 day sustain plan and common failures.

11 min read 11 sections Guide 15 of 17, IE Methods & Tools Updated

MONTUEWEDTHUFRI

New to this topic?

Read these first to get the most out of this guide:

5 Days
Classic Event Length
6-10
Ideal Team Size
30/60/90
Sustainment Checkpoints
50%+
Floor-Level Participants

What Is a Kaizen Event?

A kaizen event (also called a kaizen blitz or rapid improvement event) is a focused, time-boxed effort where a cross-functional team spends 3 to 5 days solving a specific problem or improving a defined process. Unlike daily kaizen (small, continuous improvements made by individuals) or multi-month projects, a kaizen event compresses analysis, redesign, and implementation into a single week. The team leaves with changes already made, not a report recommending changes.

ScopeRequests push at the scope line; only the approved change gets through the gateThe Scope guide

Event vs. Daily Kaizen vs. Project

Use a kaizen event when the problem is scoped enough to solve in a week, requires cross-functional input, and benefits from dedicated focus. Use daily kaizen for small, single-person improvements. Use a project when capital investment, engineering changes, or multi-month timelines are required. If the scope cannot be stated in one sentence, it is too big for a single event.

Types of Kaizen Events

Material flowMaterial travels from dock to line on the shortest path the layout allowsThe Material flow guide
TypeFocusTypical ScopeExample
Process KaizenSingle workstation or operationOne cell, one machine, one process stepReduce changeover time on Press #4 from 45 min to under 15 min
Flow KaizenMaterial & information flow across multiple stepsA value stream segment or production lineEliminate 3 days of WIP between welding and paint
System KaizenCross-functional business processOrder-to-ship, supplier-to-dock, new product introductionReduce order entry to shipment lead time from 14 days to 5

Pre-Event Preparation

A kaizen event is won or lost before Day 1. Poor preparation is the number one reason events fail. Allow 3 to 4 weeks of lead time and complete these steps:

Gemba walkGo see the work where it happensThe Gemba walk guide
Write a scope charterDefine the problem statement, target metrics (current vs. goal), boundaries (what is in scope and out), and success criteria. Get sponsor sign-off. If the charter is vague, the week will be unfocused.
Select the right team6 to 10 people. At least half should be operators or frontline staff who do the work daily. Include upstream and downstream stakeholders. Add one outsider with fresh eyes. Exclude anyone who cannot be freed from their normal duties for the full week.
Gather baseline dataCollect current-state metrics before the event: cycle times, defect rates, changeover times, WIP counts, walking distances. The team should not spend Day 1 hunting for data that should already exist.
Handle logisticsBook a team room near the gemba. Arrange coverage for team members' normal duties. Prepare supplies: sticky notes, timers, tape measures, cameras, flip charts. Notify affected areas that changes will happen during the week.

The 5-Day Kaizen Event Structure

TIMWOODS
The 8 wastesTransport, inventory, motion, waiting, overproduction, overprocessing, defects, skillsThe 8 wastes guide
Day 1: Observe
→
Day 2: Analyze
→
Day 3: Implement
→
Day 4: Refine
→
Day 5: Sustain
The majority of implementation happens on Day 3: try-storming beats brainstorming
DayThemeKey ActivitiesDeliverable
Day 1Current StateGo to the gemba. Observe full cycles. Time each step. Map the current process. Identify 8 wastes. Take photos and video.Current-state map with time, distance, & waste data
Day 2Analysis & DesignPerform root cause analysis on top waste drivers. Brainstorm countermeasures. Design the future state. Prioritize by impact and feasibility.Future-state map with action plan
Day 3Try-StormingBuild it. Move it. Change it. Test the new layout, new sequence, new standard work. Use cardboard mockups, tape on the floor, temporary fixtures. Fail fast and iterate.Working prototype of the new process
Day 4Test & StandardizeRun the new process with real production. Measure results. Fix what did not work. Write new standard work documents. Train affected operators. Add error-proofing.Validated process with documented standards
Day 5Present & SustainCompile before-and-after metrics. Present results to leadership and affected teams. Create the 30/60/90 day sustainment plan. Assign open-item owners and dates.Results presentation & sustainment plan

Team Composition

LISTEN · LEARN · LEADWEEK 1 → 13
First 90 daysA calendar of thirteen weeks fills in: listen, learn, then leadThe First 90 days guide

Who Should Be on the Team

  • Operators who work in the target process daily
  • Upstream and downstream process owners
  • A maintenance or engineering resource for technical changes
  • One "outsider" from a different area for fresh perspective
  • A trained facilitator who does not own the process
  • A sponsor who can approve resources and remove barriers

Who Should Not Be on the Team

  • Anyone who cannot commit to the full week
  • Senior leaders who will dominate the conversation
  • People sent involuntarily as punishment or filler
  • More than two managers: the team should be floor-heavy
  • Anyone who has already decided the answer before Day 1

Facilitation Skills

The facilitator's job is to guide the process, not provide the answers. A great facilitator makes the team successful without dominating the room:

ASKTRY
CoachingThe coach asks, the learner tries: two loops turning togetherThe Coaching guide
Set clear ground rules on Day 1All ideas welcome. No rank in the room. Phones away. Decisions by consensus. Disagree openly, then commit. Post these on the wall.
Ask, do not tellUse open questions: "What do you see?" "What makes this step difficult?" "What would happen if we tried it differently?" Draw answers from the team, especially quieter members.
Manage energy and paceAlternate between gemba observation, team discussion, and hands-on implementation. Break every 90 minutes. Watch for fatigue on Days 3 and 4 and adjust accordingly.
Keep the team on scopeGreat ideas that fall outside the charter go on a "parking lot" list. Acknowledge them, capture them, and move on. Scope creep kills kaizen events.

The Biggest Facilitation Mistake

Allowing the most senior person in the room to speak first. Once a manager states their opinion, operators stop sharing theirs. Always ask frontline team members first. Use round-robin or sticky-note voting to equalize voices.

The 30/60/90 Day Sustainment Plan

Most kaizen events produce great results during the week, and lose them within 90 days. Sustainment is not optional; it is the difference between lasting improvement and a temporary demo.

STEP · KEY POINT · WHY
Standard workThe current best way, written down, so it can be improvedThe Standard work guide
CheckpointFocusWhoKey Questions
30 DaysAdherenceFacilitator + Team LeadIs the new standard work being followed? Are open items closed? Are metrics trending as expected?
60 DaysStabilityProcess Owner + SponsorHave we sustained the gains through shift changes and staffing variation? Do new hires get trained on the new method?
90 DaysOwnership TransferProcess OwnerIs the area fully self-sustaining? Can we declare the event closed? What is the next improvement opportunity?

Measuring Kaizen Event Success

Every event must produce a clear before-and-after comparison on lead time, defect rate, travel distance, and WIP. Do not declare success at the end of the week. Measure at each sustainment checkpoint.

OPSCAPACITYFINANCE
Box scoreOperational, capacity and financial rows for the value stream, this week against last

The 90-Day Rule

Do not declare a kaizen event successful on Friday afternoon. True success is measured at the 90-day audit. If the gains are still holding, the new standard work is being followed, and the process owner has taken full ownership, then, and only then, is the event a success.

Common Kaizen Event Failures

BACKSLIDE
Why lean failsImprovement climbs, then slides back down where nothing holds itThe Why lean fails guide

Signs of a Strong Event

  • Tight scope defined weeks before the event
  • Team spends 70%+ of the week at the gemba, not in the conference room
  • Changes are implemented and tested during the week, not planned for later
  • Operators own the new process and helped design it
  • 30/60/90 sustainment audits are scheduled before the team disbands

Why Kaizen Events Fail

  • Scope is vague: "improve the area" with no measurable target
  • Key participants pulled away for "urgent" production issues
  • Management overrides the team's recommendations after the event
  • No sustainment plan: gains erode within weeks
  • The event becomes a PowerPoint exercise instead of hands-on change

Virtual & Hybrid Kaizen Events

Remote participation adds friction but is sometimes necessary. Keep the gemba connection by streaming live video from the floor: use a "gemba buddy" on-site who wears a camera and follows remote participants' instructions. Replace sticky notes with shared digital whiteboards and assign a tech facilitator to manage the tools. Shorten daily sessions to 4-5 focused hours to combat virtual fatigue, and extend the event to 7 days if needed to compensate.

PREPARE1PRESENT2TRY OUT3FOLLOW UP4
Job instructionTell, show, do, follow up: four steps pass the job from one pair of hands to the nextThe Job instruction guide

Key Takeaway

A kaizen event is not a meeting. It is a week of doing. The facilitator's job is to keep the team focused, the scope tight, and the changes real. Invest heavily in pre-event preparation, insist on hands-on implementation during the week, and never skip the 30/60/90 day sustainment audits. The best kaizen events leave behind not just an improved process, but a team that believes they can change anything, and that is how you build a lasting continuous improvement culture.

Interactive Demo

Plan a 5-day kaizen event. Walk through each day's activities and track scope completion.

5-Day Kaizen Event Planner

Walk through a 5-day kaizen event. Check off activities as you go and track scope completion.

🔍
Day 1: Current State
Understand the problem
0%
0%
Overall Completion
0/20
Activities Done

Ready for the full knowledge check? Guided scenarios and data export. Included with every plan.

PlanTake the advanced knowledge check
Share this guide: LinkedIn X Follow SymplProcess on LinkedIn
Take the advanced knowledge check Plan Included with every plan.

Take this to a room

The running order

For anyone planning a kaizen event. They should leave with a scope narrow enough to finish and a sustain plan booked before day one.

7 beats · 10 min
  1. 1

    An event is a week, not a programme

    A kaizen event is a focused burst on a narrow problem, with the people who do the work.

    • Its value is speed and focus, not scale.
    • It is not the improvement system. It is one tool inside one.
    • A plant that only improves during events improves five days a year.

    Ask the room When did we last improve something outside an event?

  2. 2

    Scope is the whole decision

    Most failed events failed at scoping, before anyone walked into the room.

    • One cell, one changeover, one process, not a value stream.
    • If it cannot be finished and running by Friday, it is too big.
    • A narrow scope finished beats a broad one half-done.
  3. 3

    The week has a shape

    Each day has a job, and skipping to solutions on Monday is the common failure.

    • Monday: see the current state, measure it, with the team.
    • Tuesday and Wednesday: analyse and try changes physically.
    • Thursday: run the new method and adjust.
    • Friday: standardise, train, report out.
  4. 4

    The team is the people who do the work

    An event staffed by engineers produces a solution operators will work around.

    • Operators, a maintenance person, a supervisor, and someone from outside for fresh eyes.
    • The outside person asks the questions the team stopped asking years ago.
    • Backfill their production time; do not ask them to do both.
  5. 5

    Change it physically, this week

    An event that ends with a list of recommendations was a workshop.

    • Move the bench. Build the rack. Cut the changeover. This week.
    • If it needs capital, do the part that does not and schedule the rest.
    • The team should be able to point at what changed on Friday.

    Ask the room What did our last event physically change?

  6. 6

    The sustain plan is booked before day one

    Standard work updated, a named owner, a metric on the board, and 30-60-90 dates.

    • Booked in advance, not decided in the last hour of Friday.
    • Without it, the gains are typically gone in thirty days.
    • The team should not disband until the standard is written.
  7. 7

    What we do next

    Pick a narrow problem, staff it from the floor, and book the sustain dates now.

    • Choose one cell or one changeover with a measurable current state.
    • Name the team and backfill them.
    • Book the 30, 60 and 90-day checks before the event starts.
    • Report out to leadership on Friday, in the area, not in a boardroom.

    Ask the room Which problem, and can we protect the people for a week?