Kaizen and PDCA: Continuous Improvement in Practice

Beginner 8 min read · Updated 2026-10-31

Almost every company has a list of improvement ideas, and almost everywhere it gathers dust. That is rarely the fault of the ideas; usually there is no system. Kaizen and the PDCA cycle are that system: many small steps, each with a goal, an owner, a due date and a measurement. This lesson shows what that looks like in a value stream.

What does kaizen mean?

Kaizen combines the Japanese words kai (change) and zen (good). Masaaki Imai made the term widely known with his book "Kaizen" (1986). It describes a mindset: everyone improves a little every day instead of launching one big project a year. In English it is usually called continuous improvement.

Kaizen is distinct from kaikaku, radical change, such as converting a line into a cell. The two belong together: the future state of a value stream map is often a kaikaku step; after that, kaizen sustains the result and keeps improving it.

The PDCA cycle

The tool for kaizen is the PDCA cycle, also called the Deming cycle after W. Edwards Deming:

Plan: understand the problem, find the root cause, set a goal with a number.
Do: implement the change on a small scale, at one station, on one shift.
Check: measure whether the goal was reached.
Act: if yes, it becomes the standard. If no, the next round starts with new knowledge.

Most common mistake: plan and do, but never check. Then nobody knows whether the change worked, and the old state returns. Once a standard is reached, the SDCA cycle (standardize, do, check, act) sustains it until the next PDCA round begins.

Kaizen bursts on the value stream map

On a value stream map, planned improvements are drawn as kaizen bursts, right where the problem is. The example line has two: cut the changeover time at stamping from 60 to 10 minutes (this shrinks the batches and the supermarket after it) and raise the uptime of Welding 2 from 80 to 95% (this removes the downtime of one minute in five).

Both target wastes the map shows: the large batch and the downtime. A burst without an owner and due date does nothing, though. That is why the editor flags such actions in its checks.

Managing actions: who, by when, with what metric?

Every action needs four things: an owner (one person, not a team), a due date, a status (open, in progress, done) and a metric before and after. For changeover time, that is the timed minutes. The action list in the editor shows all bursts with these details and marks overdue dates in red. That way, everyone in the team meeting sees what is moving and what is stuck.

Three rules for daily practice

Fixed time slot: 15 minutes per week at the value stream, always at the same time.
Limit: no more than three open actions per team. Better to finish a few than to start many.
Measurement: every action with a metric before and after. Only then is "check" more than a gut feeling.

Forms of kaizen

Daily kaizen happens in shop floor management: small problems are captured on the board and solved within days. A kaizen event (also kaizen workshop or kaizen blitz) takes three to five days for a well-defined topic, such as a changeover reduction with SMED. For larger problems, the A3 report has proven itself: problem, root cause, countermeasure and result on one sheet, structured by PDCA.

Practice in the editor

Open the template "Steering bracket (current state)", click the kaizen bursts and enter owner, due date and status. The checks on the right show what is still missing.

Open the template in the editor Start blank

Free, no sign-up, in your browser. Metrics, timeline and checks are calculated automatically.

Frequently asked questions

What is the difference between kaizen and continuous improvement?

In substance, none. Continuous improvement is the common English term for the kaizen principle. Some companies mainly mean a suggestion system by it. Kaizen emphasizes daily, systematic improvement with PDCA.

What does PDCA stand for?

Plan, Do, Check, Act: plan, implement on a small scale, check, then standardize or start over. The cycle goes back to Walter Shewhart and was popularized by W. Edwards Deming.

What is a kaizen burst?

The symbol for a planned improvement on a value stream map. It sits where the action takes effect and should always have an owner and a due date.

Why does continuous improvement fail so often?

Usually check and act are missing: actions are implemented but not measured and not made the standard. On top of that come too many open topics at once and no fixed time slot.

How long does a PDCA cycle take?

As short as possible. Days for daily problems, a few weeks for a changeover reduction. Long cycles are a sign that the actions are too big.