Definition
PDCA (Plan-Do-Check-Act) is a four-step cycle for solving problems and testing improvements. A team plans a change based on the cause of a problem, tries it on a small scale, checks the result against the goal and then standardises or adjusts it.
Where PDCA comes from
The cycle goes back to Walter Shewhart, who applied the scientific method to quality control, and to W. Edwards Deming, who taught it in Japan after the Second World War. That is why PDCA is also called the Deming cycle or Shewhart cycle. Deming himself later preferred PDSA (Plan-Do-Study-Act) to stress learning from the results.
In Lean, PDCA is the engine of Kaizen: every improvement, large or small, is treated as an experiment. It is also the logic behind problem-solving formats such as the A3 report.
The four steps of PDCA
- PlanDescribe the problem with facts, set a measurable goal, find the root cause and plan a countermeasure. Most of the thinking belongs in this step.
- DoTry the countermeasure on a small scale, for example on one line or for one week, and record what happens.
- CheckCompare the result with the goal. Did the change work? Were there side effects?
- ActIf it worked, make it the new standard work and share it. If not, learn from it and start a new cycle with a better idea.
PDCA examples
Production: a packing station misses its output target because operators search for labels. Plan: the team times the searching and finds that the labels for six variants are mixed in one box, so it plans a labelled holder per variant. Do: the holder is tested for one week on the early shift. Check: the searching stops and the shift meets its target. Act: the holder becomes the standard on all shifts and goes into the work instructions.
Office: invoices keep coming back from accounts payable. Plan: the team finds that a missing order number is the main reason and plans a mandatory field on the order form. Do: the field is tested with one group of suppliers. Check: after a month the team compares the returns with the other suppliers. Act: the field is rolled out to all suppliers.
Common PDCA mistakes
- Jumping from Plan straight to a full roll-out without a small test.
- Skipping Check: the change is made, but nobody measures whether it worked.
- Planning without understanding the root cause, so the countermeasure only treats a symptom.
- Forgetting Act: a successful change is never standardised and slowly disappears again.
- Running one big cycle a year instead of many small ones. Short cycles help teams learn faster.
Go deeper
PDCA: questions and answers.
What is the difference between PDCA and PDSA?
They describe the same cycle. Deming preferred Study instead of Check to make clear that the third step is about learning from the results, not only inspecting them.
How long does a PDCA cycle take?
As long as the problem needs. A small improvement at a team board can run through the cycle within days; a complex problem may take several weeks.
How are PDCA and the A3 report connected?
An A3 report is a one-page problem-solving document that follows the PDCA logic. The left side usually covers the Plan step, from background to root cause, and the right side covers the countermeasures, results and follow-up.