← Back to Blog
GUIDE9 min read · March 2026

PDCA in Manufacturing: The Complete Guide to Plan-Do-Check-Act

PDCA is the backbone of ISO 9001, lean manufacturing, and Six Sigma. Yet most teams run it wrong — they Plan, Do, skip Check entirely, and never Act. Here is how to use it correctly.

What is PDCA?

PDCA (Plan-Do-Check-Act) is a four-phase improvement cycle developed by Walter Shewhart and popularised by W. Edwards Deming. It is the foundation of ISO 9001:2015 §10.3 (Continual Improvement) and the operating framework behind Toyota Production System, Six Sigma, and every modern quality management methodology.

The cycle is deceptively simple: identify a problem, hypothesise a solution, test it on a small scale, measure the result, and either standardise the improvement or adjust the hypothesis and run the next cycle. The power is in the repetition — each cycle builds on the last, driving continuous improvement rather than one-time fixes.

Plan

Define the problem with data. Describe the current condition. Identify the root cause using 5 Why or Fishbone analysis. Set a specific, measurable target condition. Define what success looks like before you start. Write a hypothesis: "If we do X, we expect Y because Z."

Do

Implement your countermeasure — but start small. Test on one shift, one product, one line before full rollout. Document exactly what was done, what challenges arose, and what was adjusted during implementation. The Do phase is an experiment, not a permanent change.

Check

Measure the result against the target you set in Plan. Use the same metrics. Was the hypothesis proven? By how much? Were there unexpected effects? This is the phase most teams skip — and it is the most important. Without Check, you are not running PDCA, you are just doing things.

Act

If the target was met: standardise the improvement. Update Standard Work, train all operators, update control plans. If the target was not met: the information you gathered in Check is the input to the next Plan phase. Either way, you move forward.

PDCA vs DMAIC vs A3 vs 8D — which do you use?

All four frameworks ask the same questions in different orders with different names. Choose based on your audience and problem complexity:

PDCAMost shop floor improvement problems. Fast cycles, simple to run, no special training required. Best for: CT reduction, WIP reduction, quality improvements, line balancing.
A3When you need to communicate the problem and solution on one page to management or across teams. Toyota's standard problem-solving communication format. Essentially PDCA on one sheet of A3 paper.
8DRequired by automotive customers (Ford, GM, Stellantis, IATF 16949) when a quality escape reaches a customer. Formal, structured, customer-facing. Same data as PDCA — different format and language.
DMAICComplex, statistically-driven problems requiring months of data analysis. Six Sigma Black Belt territory. Use when PDCA has been tried and the root cause is not yet understood after multiple cycles.

The key insight: the underlying data is identical across all four. If you run a PDCA project properly — problem statement, root cause, countermeasures, before/after metrics, standardisation — you have everything needed to produce an A3, 8D, or DMAIC report without doing any additional work. VeSiMy generates all four from the same project data.

The most common PDCA failure modes

✕ Skipping the Check phase
The improvement gets implemented and declared successful before any measurement is done. Without Check, there is no learning — only assumption. Require before/after data for every PDCA cycle, no exceptions.
✕ Corrective actions that address symptoms
The countermeasure fixes the visible problem without addressing the root cause. Three weeks later the problem returns. A properly completed 5 Why, attached to the Plan phase, prevents this.
✕ No standardisation in Act
The improvement works and then reverts within 60 days because Standard Work was never updated and operators gradually drift back to the old method. Act must include updating documentation and retraining.
✕ Starting too big
Teams try to solve the entire problem in one PDCA cycle. Keep cycles small — one problem, one step, one shift. Fast cycles with clear learning are more valuable than slow comprehensive projects.

Run your first PDCA cycle free

VeSiMy's PDCA tool guides you through all four phases and exports your project as PDCA, A3, 8D, DMAIC, or OODA — whichever format your audience requires. Free to start — no credit card.

Start your PDCA project free →