Kaizen meaning
Kaizen is written 改善 in Japanese: kai (改) means change and zen (善) means good, so the literal kaizen meaning is "change for the better". In everyday Japanese it simply means improvement. In lean it means something more specific: a culture of continuous improvement in which every person, every day, looks for a better way to do the work and makes the change.
The idea grew out of the Toyota Production System, where improvement is part of every job rather than a project handed to specialists. Masaaki Imai brought the word to Western managers with his 1986 book Kaizen: The Key to Japan's Competitive Success, which framed kaizen as many small incremental improvements made over the long term, in contrast with occasional large investments in new technology.
Kaizen principles
The kaizen methodology rests on a handful of principles that most lean practitioners would recognise:
- Go to gemba. Improvement starts from observing the actual work where it happens (genchi genbutsu), not from a meeting room.
- Small steps, often. Many small changes carry less risk, cost little and arrive sooner than one large redesign.
- Everyone takes part. Operators, team members, supervisors and managers all see problems and all are expected to act on them.
- Standardise before you improve. Without a current standard there is nothing stable to improve, and no way to tell whether a change helped.
- Data over opinion. Before-and-after facts decide whether the change stays.
- Fix the process, not the person. Problems are treated as signals from the system, which keeps people willing to raise them.
- Reduce waste. Most kaizen targets one of the 8 wastes of lean or the wider muda, mura and muri: waiting, motion, defects, overburden and the rest.
Daily kaizen vs kaizen events
Kaizen happens at two speeds. Both are needed: a site that runs only events improves in bursts, while one that relies only on daily kaizen may never tackle its bigger problems.
| Daily kaizen | Kaizen event | |
|---|---|---|
| Frequency | Every day, every shift | A few times a year per area |
| Size of change | Small, often under a day's effort | A whole process, layout or changeover |
| Who | The team that does the work | A cross-functional team of six to ten |
| How long | Hours to a few days | Three to five days, plus preparation and follow-up |
| How it is tracked | Idea or action list reviewed at the tier meeting | Event charter or A3, with a 30-day follow-up list |
A kaizen event, also called a kaizen blitz, concentrates effort on one problem that daily kaizen has not solved.
The kaizen process
Every kaizen, large or small, follows the PDCA cycle (plan-do-check-act). A practical continuous improvement process looks like this:
- Spot the problem or idea. Anyone notices waste, a defect, a safety risk or a better way, and raises it.
- Understand the current state. Go and see, measure what happens now, and find the cause with a problem solving tool such as the 5 whys.
- Plan and try the change. Agree a countermeasure, predict its effect and test it on a small scale.
- Check the result. Compare what happened with the prediction, using the same measure as before.
- Standardise and share. If it worked, update the standard work, train the people affected and copy it to similar areas; if not, learn and go round again.
Kaizen examples
These kaizen examples show how small the changes can be:
- Manufacturing changeover. Operators film a changeover, find time lost searching for tools, and build a shadow board with every tool at the machine. The improved process becomes the new changeover standard.
- Warehouse picking. Pickers notice two look-alike products stored side by side. They re-slot one and add colour-coded labels, and pick errors on that line become rare.
- Hospital ward. Nurses walk a long way to fetch common supplies. The team sets up a small stock point near the beds with a simple reorder card.
- Office approvals. A purchase request passes through four signatures. The team maps the steps, removes two that add nothing, and sets a limit below which the team leader approves.
None needed capital spend or a specialist. Each was found by the people doing the work and kept because it was written into the standard.
What is a kaizen board?
A kaizen board is a visual board where a team tracks its improvement ideas from raised to done. Typical columns or fields are:
- Idea or problem, in a sentence, with the date raised.
- Owner, the person who will move it forward.
- Status, such as new, in progress, testing or done.
- Result, what changed and whether the measure moved.
The board earns its place when it is reviewed in the team's tier meeting: new ideas are added, stalled ones are unblocked or escalated, and finished ones are recognised. A board that sits on a wall without a review rhythm becomes a suggestion box with better graphics.
Kaizen vs lean vs Six Sigma
Lean is the overall management system, built on the 5 lean principles of value, value stream, flow, pull and perfection. Kaizen is the improvement habit inside lean that drives toward perfection. Six Sigma is a data-heavy method for reducing variation, usually run as DMAIC projects by trained specialists. Many sites use all three: kaizen for everyday problem solving, Six Sigma for complex variation problems, and lean to connect them to flow.
Kaizen vs kaikaku. Kaikaku means radical change: a step change such as a new layout, a new line or a move from batch to flow, usually led by management. Kaizen improves the process step by step; kaikaku replaces it. Mature operations use kaikaku occasionally and kaizen constantly, and a kaikaku is followed by kaizen to stabilise the new process.
How to sustain kaizen
Kaizen fades when it depends on enthusiasm alone. It lasts when it is built into how leaders spend their time:
- Leader standard work. Reviewing the idea list and coaching problem solving are written into leader standard work, not left to spare time.
- Gemba walks. On gemba walks, leaders go to the work, ask about problems and check that new standards are being followed.
- Recognise ideas. Thank people publicly for ideas and implemented changes, and count implemented changes rather than ideas submitted.
- Close the loop quickly. Every idea gets an answer within days, even if the answer is "not now, and here is why".
- Connect to goals. Link improvement to the measures that matter for the site, so teams can see why their kaizen counts.