Kaizen Project Reporting Roadmap
The complete 8-Step LEI Kaizen Reporting Framework applied across all four Kaizen types (Teian, Kobetsu Event, Kaikaku, Kakushin). Select your Kaizen type for contextual guidance, then expand each step for techniques, deliverables, and direct CILS tool links.
Select Kaizen Type for Contextual Guidance
Kaizen Event / Kobetsu Kaizen
Focused improvement eventA structured, time-boxed improvement event (typically 3–5 days) focused on a specific process, machine, or work cell. A cross-functional team is assembled, given dedicated time, and expected to achieve a measurable breakthrough improvement by the end of the event. Also called a "Rapid Improvement Event" (RIE) or blitz kaizen.
The Kaizen A3 Report — Mapping the 8 Steps to a Single Page
The Toyota A3 Report is the gold-standard format for summarising a Kaizen project on a single A3 sheet (420 × 297 mm). Each section of the A3 maps directly to the 8-step framework:
Left Side (Plan)
Steps 1–5 occupy the left half: Background, Current State (map), Analysis, Goals, and Target Condition.
Right Side (Do/Check/Act)
Steps 6–8 occupy the right half: Implementation Plan, Check Results, and Follow-Up / Standardisation.
Visual Principle
Every section should be predominantly visual — maps, charts, graphs. Minimal narrative text. If it cannot be shown visually, question whether it belongs on the A3.
Story Principle
The A3 should tell a complete story that a reader can follow from left to right: "Here is the problem → here is why → here is our goal → here is our plan → here is what we achieved → here is how we will sustain it."
Kaizen vs DMAIC — When to Use Each
Kaizen — Use When:
- Root cause is known or highly suspected
- Problem is primarily waste, flow, or process design
- Improvement can be implemented quickly (days–weeks)
- Front-line workers have the knowledge to solve it
- Statistical analysis is not required
- Kaizen Event: team is available for 3–5 dedicated days
DMAIC Six Sigma — Use When:
- Root cause is unknown and requires statistical investigation
- Problem is a variation or defect rate issue
- Multiple potential causes need data-driven screening
- Project spans 3–12 months
- DOE, hypothesis testing, or MSA is required
- Breakthrough improvement in process sigma is the goal
Note: Kaizen and DMAIC are complementary. Many organisations use Kaizen Events to implement the solutions identified during a DMAIC Improve phase.
Comparing the 4 Kaizen Types — Selection Guide
| Dimension | Kaizen Teian | Kobetsu Event | Kaikaku | Kakushin |
|---|---|---|---|---|
| Scope | Individual suggestion | One process/cell | Full process redesign | Strategic transformation |
| Change magnitude | Small (1–15%) | Medium (20–50%) | Large (30–70%+) | Breakthrough (>70% or entirely new) |
| Duration | Days | 3–5 days (event) | Weeks–months | Months–years |
| Who leads | Any employee | Facilitated team | Management + specialists | Executive leadership |
| Investment | Near zero | Low–medium | Medium–high | High |
| Risk | Very low | Low | Medium | High |
| PDCA cycle length | Weekly | Weekly | Monthly | Quarterly/annual |
| A3 Report depth | 1/2 page | 1 full A3 | 2–3 A3 pages | Full project report |
Kaizen Principles — Gemba, Genchi Genbutsu, and the Improvement Culture
Gemba (現場) — Go to the actual place: All kaizen work begins at the Gemba — the place where value is created. Never analyse a process from a conference room using second-hand data. Walk the process, observe the actual work, talk to the operators. Steps 2 and 3 of this roadmap require Gemba observation as a non-negotiable starting point.
Genchi Genbutsu — See for yourself: Leaders and engineers must personally observe the process to develop a deep factual understanding. Toyota's A3 process requires that the problem owner physically walks the process before writing anything on the report.
Hansei (反省) — Reflection: Step 8 (Follow-Up) is not just standardisation — it includes Hansei: honest reflection on what went well, what went poorly, and what was learned. Hansei drives the continuous learning cycle that makes kaizen self-sustaining.
Respect for People: Kaizen is not about reducing headcount. It is about freeing people from wasteful work so they can do higher-value activities. Every kaizen proposal must consider its impact on the people doing the work. For Kaizen Teian especially, this means actively soliciting and genuinely implementing frontline ideas.
Stop and Fix (Jidoka): A core Lean principle: when a problem is detected, stop the process and fix it immediately rather than passing defects downstream. This principle reinforces the importance of Step 3 (Analysis) — find root cause, do not just band-aid symptoms.