Kaizen Blitz (Kaizen Event)
A kaizen blitz, also called a kaizen event or rapid improvement event, is a short, focused improvement project: a small cross-functional team spends three to five consecutive days on one process, studies how the work really happens, and puts tested improvements in place before the week ends.
It is one of the main improvement methods in Lean production and can be used on a product, a service, a system, or a process.
When should you use a kaizen blitz?
A blitz works best when the problem sits inside one process or area that a team can see and change within a week. Typical targets are a cell or work area with long changeovers, a messy or unsafe layout, a step that builds up a queue, or an office process with too many hand-offs and approvals. It is a poor fit when the root cause is unknown and needs weeks of data, or when the fix needs capital spending or a system change that cannot happen during the event. Those problems usually suit a full DMAIC project instead.
Kaizen blitz team roles
| Role | What they do |
|---|---|
| Sponsor | Owns the area or process, approves the charter, removes roadblocks, and attends the report-out. See project sponsor. |
| Facilitator | Usually a Lean or Six Sigma practitioner who has run events before. Plans the week, teaches the tools, keeps the team on scope and time. |
| Team leader | Often the area supervisor or process owner, who will keep the new standard running after the week. |
| Operators | People who do the work every day. They are usually the largest group on the team. |
| Support | Maintenance, engineering, IT, or quality, on call for quick changes. |
| Outside eyes | One or two people from another area who ask the questions insiders no longer ask. |
Teams of roughly six to ten people are common. The whole team works on the event full time for the week; part-time teams tend to lose momentum.
The kaizen event charter
- Process and scope: where the process starts and stops, and what is out of bounds.
- Problem statement: what is wrong today, with numbers from the baseline.
- Goals and measures: for example lead time, work in progress, floor space, travel distance, changeover time, or first-pass yield, each with a baseline and a target.
- Team, dates, and sponsor sign-off.
- Limits: budget, what may be moved, and any safety or quality rules the team must keep.
What happens on each day of a kaizen event?
- Day 1, understand the current state. Short training on Lean basics and the eight wastes, then go to the gemba. Walk the process, draw a process map or a small value stream map, and confirm the baseline.
- Day 2, analyze. Time each step, separate value-added touch time from waiting, draw a spaghetti diagram of movement, and ask why problems happen (5 Whys, fishbone).
- Day 3, design and try. Sketch the future state, then try changes on the floor right away: move equipment, rebalance work, add visual controls or poka-yoke, apply 5S.
- Day 4, refine and standardize. Run the new method, measure it again, fix what does not work, and write the new work instructions.
- Day 5, train and report. Train everyone who works in the area, present before-and-after results to the sponsor and leaders, and agree a dated action list for anything not finished.
The original note on this page points out that some organizations may need to stop production in the area for part of the week to make the changes. That is why the date, the coverage plan, and any build-ahead of stock are agreed before the event starts.
Kaizen blitz versus everyday kaizen
| Kaizen blitz (event) | Everyday kaizen | |
|---|---|---|
| Time frame | 3–5 days, planned in advance | Continuous, every day |
| Size of change | Large step change in one area | Many small changes |
| Who | A dedicated cross-functional team | Everyone, in their own work |
| Risk | Gains slip back if there is no follow-up | Slow to show a big result |
| Best for | Layout, flow, changeover, a clear local problem | Keeping and improving standards over time |
The two work together: a blitz makes the step change, and daily kaizen keeps it and builds on it. A blitz with no daily kaizen behind it often drifts back to the old way within months.
Common reasons a kaizen blitz fails
- Scope too big for one week, so the team ends with a list instead of a changed process.
- No baseline, so nobody can show what improved.
- Operators left out, so the new method is not owned by the people who must run it.
- No follow-up, so the 30-day action list is never finished and the area slides back.
- Using it to cut heads. If people expect the event to remove their jobs, they stop offering ideas.
Exam notes
Green Belt and Black Belt exams treat the kaizen blitz as a Lean Improve-phase tool. Remember: short (3–5 days), focused on one process, cross-functional team that includes operators, changes made during the event rather than recommended, and a follow-up period to sustain the gain.
Frequently asked questions
How long does a kaizen blitz last?
The event itself usually lasts three to five working days. Plan on two to four weeks of preparation before it and about 30 days of follow-up after it.
Is a kaizen blitz the same as a kaizen event?
Yes. Kaizen blitz, kaizen event, kaizen workshop, and rapid improvement event all describe the same short, team-based improvement project. "Blitz" stresses the speed.
What results should a kaizen blitz report?
The measures named in the charter, each with its baseline and the result at the end of the week, plus the open action list with owners and dates. Results are checked again at the 30-day follow-up.
Can a kaizen blitz be used outside manufacturing?
Yes. Offices, hospitals, labs, and service teams run kaizen events on processes such as order entry, patient intake, approvals, and month-end close. The steps are the same; the waste is usually waiting, hand-offs, and rework instead of motion and inventory.
See also: kaizen and the PDCA cycle, value stream mapping, the eight wastes, and Lean production.
More on the gemba in this guide: what a gemba walk is, a gemba walk checklist, and gemba boards.
A kaizen blitz is one concentrated event. For kaizen as an everyday habit of small improvements, and how it connects to PDCA, see Kaizen (continuous improvement).
Last updated: · Published by Lean Six Sigma Training Guide (sixsigmatrainingfree.com) · How this guide is written