A team spends three days in a workshop. The wall fills with sticky notes. Everyone agrees the process needs to improve. A long action list is created, the report-out goes well, and the room feels positive.
Then two weeks later, very little has changed. The same delays are still there, the same workarounds are still being used, and the same people are still frustrated by the same problems.
That was not a Kaizen event. That was a meeting.
A real Kaizen event is a focused improvement workshop where a team observes the actual process, understands the problem, tests improvements, updates the standard, and follows up until the new way of working becomes normal. It should not be a talking shop. It should create visible change.
Toggle between a talking shop and a real Kaizen event.
What Is a Kaizen Event?
A Kaizen event is a structured, time-boxed improvement activity where a cross-functional team works intensively to solve a defined process problem or improve a specific area of work.
Most Kaizen events last between one and five days, depending on the size of the problem and the amount of change that can realistically be tested during the event. The important point is not the length of the workshop. The important point is that the event has a clear problem, a clear scope, the right people involved, and a practical route from problem to action.
Simple Definition
A Kaizen event is a focused improvement workshop where a team works on a specific process problem, usually at the Gemba, and aims to leave with implemented improvements, updated standards, owners, measures and a follow-up plan.
A good Kaizen event normally includes:
- A focused process problem, not a vague improvement theme.
- People who understand and perform the work.
- Observation of the real process, not just discussion in a meeting room.
- Baseline data so the team knows whether improvement happened.
- Practical countermeasures that can be tested quickly.
- Updated standard work so the new method is sustained.
The best events I have seen involve the people doing the work, not just managers discussing the work. Operators, technicians, planners, maintenance teams and supervisors often understand the real causes of waste far better than the people looking at the process from a distance.
A Kaizen event moves from a defined problem to standardised follow-up.
Kaizen Event vs Daily Improvement
Kaizen is often translated as continuous improvement, but the word can be used in different ways. This causes confusion because daily improvement, Kaizen events, Kaizen blitz activities and larger problem-solving projects are not the same thing.
Daily Kaizen is the habit of making small improvements regularly. These are usually local, low-risk changes made by the team as part of normal work. A Kaizen event is more structured. It brings people together for a defined period of time to work on a specific process problem. A Kaizen blitz is usually a very fast, intensive version of a Kaizen event, often completed in one to three days.
| Improvement Type | Best For | Typical Timeframe | Expected Output |
|---|---|---|---|
| Daily Kaizen | Small local improvements that the team can make quickly. | Ongoing | Small changes, removed frustrations and better team engagement. |
| Kaizen Event | Focused process issues where a team needs time to observe, analyse and improve. | 1–5 days | Implemented improvements, updated standards and follow-up actions. |
| Kaizen Blitz | Urgent, visible waste where rapid action is possible. | 1–3 days | Fast changes, simple countermeasures and immediate ownership. |
| Project / DMAIC | Complex, data-heavy issues where root causes are not obvious. | Weeks or months | Deeper analysis, validated root causes and controlled solutions. |
Use the smallest improvement method that fits the problem. If the issue can be solved by the team in ten minutes, you do not need a three-day event. If the issue is complex, unstable or heavily data-driven, a Kaizen event may be too light and a structured root cause analysis or A3 problem-solving approach may be more suitable.
Select the right improvement method for the type of problem.
When Should You Run a Kaizen Event?
A Kaizen event works best when the problem is visible, process-based and practical enough to improve quickly. It is especially useful when a team already knows an area has waste, but needs focused time and cross-functional support to remove it.
Good Kaizen event topics often involve flow, waiting, motion, handovers, layout, replenishment, changeovers, material availability or repeated quality issues. These are areas where observation at the Gemba can quickly reveal problems that are hidden in reports.
Good Reasons to Run a Kaizen Event
- The process has visible waste.
- The problem crosses more than one function.
- The work can be observed directly.
- Improvements can be trialled quickly.
- The process needs better flow or clearer standards.
- The expected benefit is meaningful enough to justify focused time.
Poor Reasons to Run a Kaizen Event
- The problem is unclear or too broad.
- There is no baseline data at all.
- The right people are not available.
- The issue needs long-term capital approval before anything can change.
- Management wants a workshop to look busy.
- No one is willing to own the actions afterwards.
A Kaizen event should not be run entirely in a meeting room. If the team cannot observe the process, speak to the people doing the work, and test some form of change, the event is probably not ready.
Score whether your topic is ready for a Kaizen event.
What Makes a Good Kaizen Event Topic?
The quality of the topic often decides the quality of the event. A vague topic creates vague discussion. A specific topic creates focus, better data and clearer action.
A good Kaizen event topic should be specific, measurable, process-based, visible at the Gemba, achievable within the event scope, and linked to business impact. It should describe the process problem clearly enough that the team knows where to look and what success means.
Weak Kaizen Topics
- Improve production.
- Reduce quality problems.
- Fix planning.
- Make the warehouse better.
These are too broad. They do not define the process, the measure, the baseline or the expected outcome.
Stronger Kaizen Topics
- Reduce changeover time on Line 2 from 48 minutes to under 30 minutes.
- Reduce material waiting time in Cell 3 by 40%.
- Improve picking accuracy in the warehouse from 94% to 98%.
- Reduce walking distance for operators on Assembly Cell A by 30%.
These give the team a process, a baseline, a target and a reason to act.
The topic should be narrow enough to act on but important enough to matter. “Improve production” may sound strategic, but it is too broad for a practical event. “Reduce average changeover time on Press 4 from 52 minutes to below 30 minutes within six weeks” is much stronger because the team knows exactly what to investigate.
Rewrite a weak Kaizen topic into a measurable event objective.
Who Should Attend a Kaizen Event?
A Kaizen event should involve the people who understand the work and the people who can help remove barriers. If the event only includes managers, the team may miss the real causes of waste. If it only includes operators, the team may struggle to make decisions that need support from maintenance, quality, planning or leadership.
The best team is usually cross-functional but still small enough to move quickly. For many events, six to ten people is enough. Larger groups can work, but only if the facilitator keeps the event structured and prevents it becoming a general discussion forum.
Process Owner
Owns the process and is accountable for the result after the event. This person must support the new standard once the workshop ends.
Operators
Bring real process knowledge, workarounds, frustrations and improvement ideas. They know what actually happens, not just what the procedure says.
Support Functions
Maintenance, quality, planning, supply chain or engineering may be needed depending on the problem being solved.
CI Facilitator
Keeps the event structured, helps the team use Lean tools, and prevents the workshop drifting away from the problem.
Sponsor
Removes barriers, supports decisions and confirms that the event is aligned with business priorities.
Supervisor or Team Leader
Connects the event to daily management, shift routines, action follow-up and team communication after implementation.
The key principle is simple: involve the people closest to the work. A Kaizen event is not something done to a team. It should be done with the team.
Click each role to see what they contribute to the event.
Example Kaizen Event Agenda
The agenda should match the problem, but most practical Kaizen events follow a similar pattern: prepare properly, understand the current state, improve the process, standardise the new method, and follow up after the event.
The example below is a practical three-day agenda. It also includes Day 0 preparation because many events fail before they begin. If the problem, scope, data and attendees are unclear, the event will lose time trying to organise itself.
A practical 3-day Kaizen event agenda with preparation and follow-up.
Day 0 — Preparation
Before the event, define the problem, collect baseline data, confirm the scope, invite the team, prepare any current-state information and agree the target. This does not need to be perfect, but the team should not arrive with a blank page.
Day 1 — Understand
Start with the problem statement, the target and the scope. Then go to the Gemba. Observe the process, speak to the people doing the work, map the current state, identify waste and review the available data. The aim is to understand how the process actually behaves.
Day 2 — Improve
Use tools such as 5 Whys, fishbone diagrams, waste walks, spaghetti diagrams and impact-effort prioritisation. Develop countermeasures and test changes where possible.
Day 3 — Implement and Standardise
Implement quick wins, update standard work, assign remaining actions, confirm owners and due dates, define follow-up metrics, and prepare the report-out. If the event ends with only an action list and no changed process, it has not gone far enough.
Follow-up — Sustain
Review the actions, verify the metrics and confirm whether the new process is being followed. The report-out is not the finish line. Sustainment is where most Kaizen events succeed or fail.
Kaizen Event Example in Manufacturing
Imagine a manufacturing cell that regularly misses its output target. The team believes the operators are busy all shift, but the cell still falls short. A quick review shows that the issue is not one single large breakdown. The loss is spread across material waiting, excessive walking, searching for parts and unclear replenishment.
The Kaizen team starts by observing actual work. They create a simple process map, capture a spaghetti diagram, review where materials are stored, and compare the expected work sequence with what operators actually do. This is where the team discovers that operators are not just building product. They are repeatedly walking to fetch materials, waiting for replenishment, searching for consumables and adjusting their sequence around missing items.
The team then tests a small number of practical countermeasures:
- Move frequently used materials to point-of-use storage.
- Create a visual replenishment trigger.
- Revise the cell layout to reduce walking.
- Update the work sequence and standard work.
- Add a daily check to the team’s Gemba board.
Before and after view of a cell layout improvement.
Waiting Reduced
Material waiting reduced by 55% because replenishment was clearer and materials were moved closer to the point of use.
Motion Reduced
Walking distance reduced by 40% because the layout supported the work sequence instead of forcing operators to work around it.
Output Improved
Output improved from 82 to 96 units per shift. The remaining gap was moved into a focused action plan.
This is a good example because the event did not try to solve every production issue. It focused on a specific cell, a specific output gap and observable waste. The team changed the process, updated the standard and created follow-up measures.
What Outputs Should a Kaizen Event Produce?
A Kaizen event should produce more than a slide deck. The outputs should make the improvement visible, measurable and manageable after the workshop has ended.
At minimum, a practical Kaizen event should create:
Problem Statement
A clear description of the issue, where it happens, how big the gap is, and why it matters.
Current State Map
A simple view of how the process currently works, including delays, handovers, rework and visible waste.
Waste and Root Cause Analysis
A structured view of the problems discovered through observation, data review and questioning.
Future State Design
A practical view of how the process should work after improvement, including flow, roles and controls.
Action Plan
Clear actions with owners, due dates, priorities and status. Use an action plan template rather than loose notes.
Updated Standards
Revised standard work, visual controls, training notes, layout standards or checks needed to sustain the change.
The event should also capture before-and-after metrics, follow-up dates, the process owner, open risks and any remaining barriers. If these outputs are missing, the improvement will rely on memory and enthusiasm instead of management routines.
The tangible outputs a Kaizen event should produce.
How to Sustain the Gains After a Kaizen Event
A Kaizen event is only successful if the improvement survives after the workshop. Many events feel successful during the report-out, but the process slowly drifts back because the new method was never built into daily work.
This is where standard work, visual management and daily management matter. The new process needs to be clear, trained, checked and reviewed. Otherwise, the team has only created a temporary improvement.
Sustainment turns an event improvement into the new normal.
Sustainment Actions
- Update the standard work document or visual standard.
- Train affected employees and shifts.
- Add simple visual controls where needed.
- Review the key metric daily or weekly.
- Assign a process owner for the new method.
- Audit the new process until it is stable.
What Causes Gains to Fade
- Actions are not followed up.
- Operators are not trained on the new method.
- Old layouts, labels or forms remain in place.
- The team reports success too early.
- No one checks whether the new standard is being followed.
- Metrics are not reviewed after the event.
The most important question after a Kaizen event is not “did we have a good workshop?” It is “has the process actually changed, and is the new way being followed?”
Common Kaizen Event Mistakes
Kaizen events are powerful when they are focused and practical. They become wasteful when they are used as a substitute for clear ownership, decision-making or daily management.
Bad vs good Kaizen event behaviours.
Mistake 1 — No Clear Problem Statement
The event starts with a broad theme like “improve productivity” and quickly becomes unfocused. The team talks about everything and solves very little.
Mistake 2 — No Baseline Data
The team changes the process but cannot prove whether it improved. Even simple baseline data is better than relying on opinion.
Mistake 3 — Excluding Operators
The people who know the process are left out. The result is often a solution that looks good in theory but fails in real work.
Mistake 4 — Too Many Actions
The event creates a huge action list, but little is implemented during the workshop. Focus on the critical few changes that will move the measure.
Mistake 5 — No Follow-up
The event ends at the report-out. Actions remain open, standards are not checked and the process drifts back.
Mistake 6 — Using Workshops to Avoid Decisions
Sometimes the obvious fix is already known, but the organisation asks for another workshop instead of making the decision. That is not continuous improvement; it is delay.
If the event ends with only a presentation and a list of future actions, challenge whether it has gone far enough. A practical Kaizen event should change something about the process.
How to Run a Kaizen Event Step-by-Step
The steps below give you a practical structure you can adapt for manufacturing, warehouse, office, service or transactional processes. The tools may change, but the logic stays the same: define, observe, analyse, improve, standardise and follow up.
Define the Problem
Clarify the gapStart with a focused problem statement. Describe what is happening, where it happens, how often it happens, the size of the gap and why it matters. Link to a business impact such as output, quality, safety, delivery, cost or employee frustration.
Useful link: how to write a good problem statement.
Agree what improvement would look like. The target should be measurable and realistic within the event scope. For example, reduce changeover time from 48 minutes to below 30 minutes, or reduce material waiting by 40%.Set the Target
Define success
Include the people doing the work, the process owner, relevant support functions, a CI facilitator and a sponsor or decision-maker. Avoid making the team so large that progress becomes slow.Select the Team
Bring the right people
Watch the work happen. Capture facts, timings, movement, handovers, queues, defects, searching, waiting and workarounds. A Kaizen event should be grounded in the real process.Observe the Process
Go to the Gemba
Create a simple current state map, process flow, layout sketch or spaghetti diagram. The point is not to create perfect documentation. The point is to help the team see waste clearly.Map the Current State
Make the work visible
Use waste identification, 5 Whys, fishbone analysis or data review to understand why the gap exists. Avoid jumping to solutions before the team has understood the problem.Identify Waste and Root Causes
Understand before acting
Generate improvement ideas, then prioritise them based on impact, effort, risk and speed of implementation. Focus on changes that can be tested quickly and linked back to the target.Develop Countermeasures
Prioritise practical changes
Trial the improvement where possible. Move materials, change the sequence, test a visual control, adjust the handover, simplify the form or run a quick pilot. Learning from a small test is usually better than debating a perfect solution.Test and Implement
Make real changes
Update standard work, visual standards, checklists, training material or daily management routines. This is what prevents the process from drifting back after the event. Useful link: standard work template.Standardise the New Method
Lock in the gain
Confirm owners, due dates and review dates. Track the key measure after the event and verify whether the improvement has held. Close actions formally and escalate barriers when needed.Follow Up and Measure
Prove and sustain
Download a Kaizen Event Template
If you are planning a workshop, use a Kaizen event template to keep the event structured. A good template should help you define the problem, capture the current state, identify waste, prioritise countermeasures, assign actions, update standards and track follow-up.
You can also support the event with related Lean templates such as an action plan template, A3 template, standard work template and improvement follow-up tracker.
Frequently Asked Questions
What is a Kaizen event?
A Kaizen event is a focused improvement workshop where a cross-functional team works on a defined process problem over a short period of time. The goal is to understand the current state, identify waste, implement improvements and sustain the gains.
How long should a Kaizen event last?
Most Kaizen events last between one and five days. A smaller event may only need one day, while a more involved process improvement may need several days plus preparation and follow-up.
What is the difference between Kaizen and a Kaizen event?
Kaizen refers to continuous improvement generally. A Kaizen event is a structured, time-boxed improvement activity focused on a specific problem or process.
What is a Kaizen blitz?
A Kaizen blitz is a fast, intensive type of Kaizen event, often completed in one to three days. It is usually used when the problem is visible, urgent and practical changes can be made quickly.
Who should attend a Kaizen event?
A Kaizen event should include the process owner, operators or people doing the work, relevant support functions, a CI facilitator and a sponsor or decision-maker. The people closest to the work should always be involved.
What should happen after a Kaizen event?
After a Kaizen event, actions should be completed, standard work should be updated, affected employees should be trained, and results should be reviewed through daily management, audits or follow-up meetings.
