Lean teams use kaizen because small changes are cheap and quick to test. Over time they add up, and they build a culture where everyone solves problems.
Where it comes from
Kaizen is a core principle of the Toyota Production System. Masaaki Imai's book on kaizen helped popularize the term outside Japan.
At a glance
Small steps, held in place
Swipe sideways to see the whole diagram.
How to apply Kaizen
- 1
Pick a problem worth solving
Choose a specific issue tied to safety, quality, delivery or cost. Keep the scope small enough to act on within days or weeks.
- 2
Go to the gemba
Observe the work where it happens. Talk with the people doing it and gather simple data on the current state.
- 3
Find the root cause
Use five whys or a fishbone diagram to get past symptoms. Agree on the cause before choosing a fix.
- 4
Try a countermeasure
Make a small change and test it quickly. Prefer low-cost ideas the team can implement itself.
- 5
Check results and standardize
Compare results to the baseline. If the change works, update standard work so the gain sticks.
- 6
Share and repeat
Post the improvement on a visible board and recognize the people behind it. Then pick the next problem.
Worked example
A 30-person support team notices that tickets bounce between queues. An agent suggests a short triage checklist at intake, which the team tests for two weeks. Reassignments fall, so the checklist becomes part of standard work.
Common mistakes
- Collecting ideas in a suggestion box without fast feedback or follow-through.
- Running big kaizen events and skipping the daily, small improvements in between.
- Implementing changes without checking results or updating the standard.
When Kaizen is not the right tool
Kaizen improves an existing process in small steps. When the process itself is wrong, such as a layout that cannot meet demand, a bigger redesign may be needed.
Lean writers call that radical change kaikaku. Kaizen then sustains and refines the new design.
Kaizen meaning
Kaizen is a Japanese word usually translated as "change for the better" or "continuous improvement". In lean it means small, steady improvements made by the people who do the work, every day.
The word is written with two characters. 改 (kai) means change, and 善 (zen) means good. Together they read as a change toward good, which is why the word has no built-in sense of size: a kaizen can be tiny.
Kaizen principles
Most descriptions of kaizen share a few principles. Improvement is everyone's job. Small changes are tested quickly. Problems are treated as chances to learn, not as blame. Facts come from going to the place where the work happens, the gemba.
Standards matter too. A change that works becomes the new standard, so the next improvement starts from a higher base. The continuous improvement page explains the cycle that ties these together.
Kaizen event
A kaizen event, sometimes called a kaizen blitz, is a focused improvement workshop that usually runs for three to five days. A small cross-functional team studies one process, makes changes on the spot and leaves a new standard behind.
Events are useful for problems that need several people at once. Daily kaizen handles the many small fixes in between. The kaizen event guide covers the preparation, the agenda and the follow-up.
Running a kaizen event
Preparation comes first: a clear scope, a target, current data and a cross-functional team. The event itself usually lasts a few days at the process.
The team maps the current state, tests changes on the spot and leaves a new standard. A follow-up after the event checks that the gains held and closes open actions.
Kaizen tools
Kaizen uses the problem-solving tools in this library: PDCA, five whys, fishbone diagrams and A3 reports.
An idea board or kaizen software tracks daily ideas from submission to result.