Running a Kaizen Event: Plan, Run and Follow Up a Rapid Improvement
How to prepare, run and follow up a kaizen event or rapid improvement workshop, with a sample agenda and the failure modes to avoid.
Gidoka · Last reviewed October 24, 2026 · 5 min read
Most kaizen is quiet: a team member moves a shelf, rewrites a confusing form or adds a check that catches an error. Sometimes, though, a process needs more than small daily fixes. It might cross several roles, involve a stubborn bottleneck or simply need a group of people to stop, look at it together and change it while they're all in the room.
That is the job of a kaizen event, also called a kaizen workshop, kaizen blitz or rapid improvement event. A small cross-functional team sets aside a few days, studies one process at the place where the work happens, makes changes, tests them and standardizes the result.
This guide covers where the format comes from, how to plan one, what happens during the event, and the follow-up that decides whether the gains last.
What a Kaizen Event Is
The Lean Enterprise Institute (LEI) defines a kaizen workshop as a group kaizen activity, commonly lasting five days, in which a team identifies and implements a significant improvement in a process. Its classic example is creating a continuous flow cell within a week. Participants learn the relevant principles, go to the gemba to assess actual conditions, make and test changes, standardize the new process and report out to senior management.
The U.S. Environmental Protection Agency (EPA), which documents lean methods in its sustainability resources, gives a wider range: events are generally organized to last between one day and seven days, depending on the scale of the process and problem. EPA notes that teams often implement chosen improvements within 72 hours of starting and typically favor solutions that don't involve large capital outlays.
According to LEI, the format has roots at Toyota. It describes jishuken, Japanese for "self-learning," as hands-on workshops that Toyota's Operations Management Consulting Division developed to build skills and raise the level of the Toyota Production System in an area. Outside Toyota, LEI says, jishuken became common in the form of the five-day kaizen workshop.
Events Versus Daily Kaizen
An event isn't a substitute for everyday improvement. LEI calls kaizen events excellent for developing capability and making substantial changes quickly, but warns that leaders should not rely on them alone, because steady daily kaizen is what builds frontline problem-solving capability over time.
A useful rule of thumb: use an event when the change is too big or crosses too many roles for daily kaizen, but not so big that it needs a long project. LEI uses a separate term, kaikaku, for radical improvement, such as moving equipment over a weekend to switch from batches to single-piece flow.
Phase 1: Planning and Preparation
EPA describes preparation as choosing a target area, then narrowing it to a specific problem. Good target areas, in its list, include places with a lot of work in progress, processes with significant bottlenecks or delays, areas where quality or performance doesn't meet customer expectations, and areas with significant market or financial impact.
Then focus. "Fix the shipping area" is too vague. "Cut the time from order received to package shipped" is a problem a team can work on in a week.
Next, assemble the team. EPA stresses including workers from the targeted process, sometimes supplemented by people with fresh perspectives, and making sure everyone understands the organization's improvement process before the event. Team members are expected to set aside most of their regular duties for the event's duration. For a small business, that's the hardest part, so schedule it deliberately, arrange coverage, and keep the scope small enough to match.
Before day one, a sponsor should agree on:
- The problem statement and a measurable goal.
- Boundaries: where the process starts and ends, and what is out of scope.
- What the team can change without further approval.
- Baseline numbers, such as current lead time or error rate.
- Who will own the process afterward.
Phase 2: The Event Itself
Here is one possible shape for a hypothetical five-day event at a small online retailer working on order-to-ship time. Shorter events compress the same sequence.
- Day 1: Learn and observe. Review the goal and any needed principles, then go to where the work happens. EPA describes this as building a shared understanding of the current state. Follow real orders, time each step and note waiting.
- Day 2: Analyze. EPA mentions tools such as value stream mapping and the "5 whys" for spotting waste and root causes. Ask of each step whether it adds value toward the process's goal.
- Day 3: Try changes. Brainstorm options, then test them. EPA notes that ideas are often tested on the shop floor or in mock-ups. Cardboard, tape and a trial run beat a long debate.
- Day 4: Refine and standardize. Keep what worked, drop what didn't and write the new method down so anyone can follow it.
- Day 5: Measure and report out. EPA suggests recording new cycle times and the savings from eliminated waste. LEI describes the team reporting out to senior management.
A few ground rules help: the people who do the work have the strongest voice, ideas get tested rather than argued, and no one is blamed for how the process used to work.
Phase 3: Follow-Up
EPA calls follow-up a key part of the event, aimed at making sure improvements are sustained and not temporary. Team members track key measures, and follow-up reviews are sometimes scheduled 30 and 90 days after the event, with people in the process asked for feedback and suggestions. Posting results on a board everyone can see keeps attention on them.
Practical follow-up steps:
- Keep a short open-items list with owners and dates; events rarely finish everything.
- Check the new standard is actually being used, at the place the work happens.
- Compare the measures against the baseline at 30 and 90 days.
- Share what was learned with teams doing similar work.
Why Events Fail
LEI lists several failure modes worth taping to the wall:
- The number of kaizen events becomes the key measure, instead of meaningful results such as safety, cost, quality and delivery.
- Gains are quickly lost as workers and managers return to the old way of working.
- Management doesn't involve frontline workers.
- Specialized engineers removed from daily operations lead the improvement instead of frontline managers and operators.
Small organizations can add one more: scheduling an event no one can actually attend. A two-day event with the right people beats a five-day event with the wrong ones.
Key takeaways
- A kaizen event is a short, focused workshop in which a team studies one process, changes it, tests it and standardizes it.
- LEI describes events as commonly lasting five days; EPA describes a range of one to seven days.
- Prepare carefully: a specific problem, a baseline, clear boundaries and people from the process.
- Go to where the work happens, test ideas with quick mock-ups and write down the new method.
- Follow up at intervals such as 30 and 90 days, and keep daily kaizen going between events.
Sources
Spotted something out of date? Let us know.