Kaizen event versus daily kaizen
Kaizen means change for the better. Daily kaizen is the stream of small improvements teams make as part of normal work, often raised and reviewed in tier meetings. A kaizen event concentrates effort on one problem that daily kaizen has not solved: a bottleneck, a long changeover, a recurring quality defect, a layout that causes handling. The team stops its normal work for the week, so the problem gets several days of full attention instead of ten minutes a day.
What is a kaizen blitz?
A kaizen blitz is the same thing as a kaizen event. The word "blitz" stresses speed: the team does not write a report recommending changes, it makes them during the week, tests them on the floor and leaves a new standard behind. Rapid improvement event (RIE), often used in healthcare, and kaizen workshop are other names for the same format.
Choosing the right problem
Good candidates are problems that are important, bounded and stubborn: one line, one cell or one process, with a measure that can be seen to move within the week. A value stream map is a common source, because it shows where the biggest delays and handoffs sit. Problems that need capital approval, a new system or months of data are better run as projects.
What happens on each day of a kaizen event
The classic format is five days, after two to four weeks of preparation. Shorter events compress the same sequence.
| Day | Focus | Typical outputs |
|---|---|---|
| Before | Prepare | Charter with scope, target and team; baseline data; diaries cleared; leadership sponsor named |
| Day 1 | Understand | Training in the basics; walk the process; current-state map; time observations; agreed problem statement |
| Day 2 | Analyse | Waste and root causes identified; ideas generated; first changes tried on the floor |
| Day 3 | Improve | Best ideas implemented and tested; layout, tools or sequence changed; results measured |
| Day 4 | Standardise | New standard work written; people affected trained; visual management updated |
| Day 5 | Report | Before-and-after results presented to leaders; open actions assigned; 30-day check booked |
| After | Sustain | Actions reviewed weekly; 30-, 60- and 90-day checks; standard audited |
The rule that separates a kaizen event from a meeting is that changes happen during the week. If an idea needs a part or a contractor, the team makes a temporary version and records the permanent fix as an action.
Kaizen event examples
- Changeover reduction. A packaging line team films a format change, separates internal and external work using SMED, prepares parts and tools before the line stops, and writes a new changeover standard.
- Cell layout. An assembly team maps operator walking, moves benches and parts racks into a U-shaped cell, and balances the work to takt time.
- Quality defect. A team traces a recurring defect with a fishbone diagram and the 5 whys, finds an unclear setting, and adds a poka-yoke and a visual check.
- Office process. A customer service team maps how an order is entered, removes duplicate data entry and rewrites the work instruction.
- Hospital discharge. A ward team maps the discharge process, finds patients waiting for paperwork, and moves the steps that can happen the day before.
What makes an event succeed
- A specific, measurable target and a narrow scope.
- The people who do the work on the team, not only engineers and managers.
- Leadership available during the week to remove obstacles and approve changes.
- A follow-up list that is actually reviewed, usually in the area's tier meeting.
Common failures
- Scope too wide, so the week ends with a plan instead of a change.
- No baseline data, so the result cannot be shown.
- The new standard is not trained or audited, and the process drifts back within weeks.
- Too many events and too little daily kaizen, so improvement happens only when a facilitator is in the building.
Kaizen event checklist
Before the event:
- Charter agreed: problem, scope, target, boundaries, sponsor.
- Baseline data collected for the measure you want to move.
- Team of six to ten chosen, including operators, and their work covered.
- Materials ready: maps, stopwatches, tape, labels, access to maintenance.
During the event:
- Current state observed at the process, not described from memory.
- Changes made and tested on the floor each day.
- New standard work written and the people affected trained.
After the event:
- Open actions have an owner and a date, and are reviewed in the tier meeting.
- 30-day check booked to confirm the result holds.
- What worked shared with similar areas.
A one-page A3 report template works well as the event charter and the record of results.
Where events fit in an improvement system
Events are powerful but episodic. A mature operation uses them for problems that need concentrated effort, while daily kaizen, structured problem solving and leader standard work carry the improvement load between events. Every event is a large PDCA cycle: plan before the week, do and check during it, and act by standardising and following up afterwards.