The PDCA Cycle is an iterative improvement method for planning a change, trying it, studying the results, and acting on what was learned.
Definition
PDCA stands for Plan, Do, Check, Act. It is a learning cycle for testing improvements, comparing results to expectations, standardizing successful changes, and revising the approach when results fall short.
PDCA is the practical engine behind Kaizen, daily improvement, standard work refinement, and many management-system routines.
History
PDCA is associated with Walter Shewhart and W. Edwards Deming. Deming later preferred Plan-Do-Study-Act because study emphasizes learning rather than simple inspection. The cycle became foundational in quality management, Lean, and continuous improvement.
When to Use
Use PDCA when the team can learn through controlled action, especially for small process changes, standard updates, countermeasure testing, daily management issues, and improvement ideas that need evidence before broad rollout.
Step-by-Step
- Plan: Define the problem, target, root cause, hypothesis, and test plan.
- Do: Run the test on a limited scale with clear ownership.
- Check: Compare results to prediction using data and observation.
- Act: Standardize, adjust, abandon, or run another cycle.
- Capture learning and communicate changes to affected people.
Examples
- Daily Kaizen: A team tests a new material location for one shift.
- Quality: A fixture change is piloted before updating control plans.
- Training: A revised job aid is tested with new operators and refined.
Common Pitfalls
- Skipping the prediction in Plan.
- Rolling out too broadly before learning.
- Calling implementation PDCA without checking results.
- No standardization after success.
- No rollback plan.
- Using PDCA for problems that need deeper root cause analysis first.