Kaizen Event Steps: How to Plan and Run a 3–5 Day Improvement Event
A kaizen event is a short, focused workshop where a small cross-functional team fixes one specific process problem. Most of the work happens before and after the event week, which is why events that skip preparation or follow-up tend to fade. This guide gives you the ten steps, a sample five-day agenda, the roles, a charter template and a worked example you can adapt.
What a kaizen event is
The ASQ glossary defines kaizen as a Japanese business philosophy of continuous improvement through small, incremental changes, pursued by staff at every level. The same glossary describes kaizen events, also called kaizen blitzes, as focused, facilitated improvement workshops: a cross-functional team works for three to five days to achieve a specific improvement in one defined process area. You can read it in the ASQ glossary entry on kaizen.
So there are two ideas with one name:
- Kaizen the philosophy: everyone improves their own work a little, every day.
- The kaizen event: a time-boxed team effort aimed at one process.
Events are a common lean tool. For how lean and Six Sigma fit together, see Six Sigma vs Lean Six Sigma.
When to run one, and when not to
| Good fit for an event | Better handled another way |
|---|---|
| One clear process with a visible problem | A vague problem nobody can describe |
| Causes can be seen by watching the work | Causes that need weeks of data and statistical testing; use DMAIC |
| Fixes within the team’s authority | Fixes that need large capital or system changes |
| Quick wins that can be tested in days | A redesign of a whole product or service |
These are our rules of thumb. An event can also feed a longer project: use the event to remove obvious waste, then use DMAIC for what remains.
The three phases at a glance
The timings below follow VelAction, a lean consultancy, in its guide to the kaizen event. It describes the whole cycle, including planning, the event week and follow-up, as about six weeks. Treat them as typical, not fixed.
| Phase | Typical timing | What happens |
|---|---|---|
| Before | Charter at least 4 weeks ahead; logistics, data and communication 1–3 weeks ahead | Choose the focus area, write the charter, pick the team, collect baseline data, book the room and cover their regular work |
| During | 3–5 days | Train, observe the process, find root causes, design and test improvements, report out |
| After | Leftovers in 1–2 weeks; audits at 30, 60 and 90 days | Finish open actions, standardize the new way, check that gains hold |
The ten steps
- Choose the problem. Pick one process and one measurable pain point, such as long lead time, rework or missed deadlines.
- Write the charter. State the problem, scope, goal, team and dates on one page. See the template below.
- Pick the team. VelAction says teams are typically 5 to 10 people. Include people who do the work, people upstream and downstream, and someone from outside the area who will ask naive questions.
- Collect baseline data. Measure the current state before the event, such as lead time, number of handoffs and error rate. Without a baseline you cannot show improvement.
- Prepare logistics. Book a room near the work area, arrange materials, and plan cover for team members’ normal duties.
- Kick off and train (day 1). Review the charter, teach the few tools the team needs, and agree ground rules.
- Go and see (day 1–2). Walk the process where it happens. Map it, time it, and note waste such as waiting, rework and unneeded steps. See what a business process is for a mapping method.
- Find root causes and design fixes (days 2–4). Ask why repeatedly, list ideas, rank them by impact and effort, then try the best ones straight away on a small scale.
- Report out (last day). Present before and after, what changed, and what is still open to the sponsor and stakeholders.
- Follow up. Close leftover actions within one to two weeks, update the standard way of working, and audit at 30, 60 and 90 days.
Roles
The roles below follow VelAction’s guide. Small events may combine some of them.
| Role | What they do |
|---|---|
| Champion | A senior manager who removes barriers and approves changes |
| Facilitator | A lean-experienced coach who trains the team and keeps the event on track |
| Team leader | Owns the event and does most of the planning, often the process owner |
| Team members | People from the work area and related functions |
| Stakeholders | People affected by the changes, included in decisions |
| Support team | Facilities, IT and others who help with things the team cannot do alone |
A sample five-day agenda
This is our sample, based on the pattern in the sources above. Adjust it to the size of the problem.
| Day | Focus | Typical output |
|---|---|---|
| 1 | Kick-off, training, first look at the process | Agreed goal and ground rules; first process map draft |
| 2 | Process walk, data collection, root causes | Current-state map with times; list of causes |
| 3 | Design the future state; start trials | Future-state map; trial results |
| 4 | Implement and refine; draft standard work | Revised procedure; training material |
| 5 | Wrap-up, report-out preparation and presentation | Report-out deck; open-actions list with owners |
Common tools used across the week include process maps, spaghetti diagrams, the “five whys,” an impact-effort matrix, 5S, visual controls and standard work. For mapping tools, see process modeling tools and techniques.
Kaizen charter template
Kaizen event charter: [event name]
Dates: [start] to [end] · Location: [room and work area] · Champion: [name]
1. Problem statement: [What is wrong, where, and how big? Use a number.]
2. Scope: Starts at [first step] · Ends at [last step] · Out of scope: [list]
3. Goal and measures: [Measure] from [baseline] to [target]
4. Team: Leader [name] · Facilitator [name] · Members [names]
5. Constraints: [Budget limits, areas that cannot change, safety or compliance rules.]
6. Baseline data: [What was measured, when and by whom.]
7. Report-out: [Date, time, audience]
8. Follow-up: Leftover actions due [date] · Audits at 30 / 60 / 90 days: [dates and owner]
A worked example
The numbers below are made up to show how results are reported. They are not typical figures. Imagine a finance team whose supplier invoices take too long to approve.
| Measure | Before | After the event | Change |
|---|---|---|---|
| Average days to approve an invoice | 12 | 8 | −33% |
| Handoffs between people | 7 | 4 | −43% |
| Invoices needing rework | 18% | 10% | −44% |
What the team did. It mapped the process on day 1 and found that invoices waited in two inboxes for approval. It removed one approval for low-value invoices, added a checklist for the data-entry step, and moved the matching step next to the purchasing desk. It tested these changes on a small batch before rolling them out.
Follow-up. The team lead tracked the same three measures at 30, 60 and 90 days. If results slip, check whether the new procedure was written down and taught.
A note on results. VelAction says typical gains from events are 20% to 50%, but also warns that reported results often include projections and tend to be inflated. Measure real results, not forecasts.
Common mistakes
The first five come from VelAction’s list of pitfalls. The last two are our additions:
- Treating events as the whole programme. Daily improvement by the people doing the work matters more than occasional workshops.
- Chasing dramatic numbers every time. Some events should aim for learning.
- Relying on outside facilitators forever. It slows the pace. Train internal ones.
- Marathon weeks. Late nights breed resistance and make volunteers hard to find.
- No cover for regular work. Team members, especially office staff, may return to a large backlog.
- No baseline. You cannot prove improvement without a before measure.
- No follow-up. Without audits, old habits return.
Learn more
Kaizen events sit inside the wider toolbox of lean and Six Sigma. Start with what Six Sigma is, then see our guides to the Six Sigma Green Belt course and Lean Six Sigma certificates. All of our process-improvement guides are in the Six Sigma hub.
Online providers such as Coursera and Udemy list lean and Six Sigma courses. We may earn a commission if you sign up, at no cost to you. We are not affiliated with any university. Check each syllabus and update date.
Frequently asked questions
What is a kaizen event?
A short, focused workshop where a cross-functional team improves one specific process. ASQ’s glossary says it typically runs three to five days.
What are the steps of a kaizen event?
Choose the problem, write a charter, pick the team, collect baseline data, prepare logistics, train and kick off, observe the process, find root causes and test fixes, report out, then follow up.
How long does a kaizen event take?
The event itself is usually three to five days. Including planning and follow-up, one source puts the whole cycle at about six weeks.
How many people should be on the team?
VelAction says teams typically have 5 to 10 people. Include people who do the work and those upstream and downstream.
What is the difference between a kaizen event and DMAIC?
An event is a short workshop for problems that can be seen and fixed quickly. DMAIC is a longer, data-heavy method for problems with unclear or complex causes.
How do you make improvements last?
Write the new method as standard work, train the people affected, and audit at 30, 60 and 90 days.
Browse certificate, course and degree programs side by side.