What PDCA is — and the one-word correction Deming insisted on
The cycle's bones come from Walter Shewhart, the Bell Labs physicist whose 1920s–30s statistical quality-control work introduced the idea that improvement follows a repeating loop of specification, production, and inspection — refined into a cycle of hypothesis and test. W. Edwards Deming carried it further and, through his lectures in postwar Japan, into the practice of Japanese manufacturing — from which lean, kaizen and modern continuous improvement descend. Deming, characteristically, credited it as the Shewhart cycle; Japanese practice named it the Deming cycle; the abbreviation PDCA stuck worldwide.
The four phases: Plan — define the problem, analyze root causes, and commit to a falsifiable hypothesis: if we change X, metric Y will improve, because Z — with success criteria written down before anything runs. Do — run the change small: one line, one team, one week; a controlled trial, not a rollout. Check — compare what happened against what the Plan predicted. Act — if the hypothesis held, adopt and standardize; if not, abandon or adjust; either way, the next turn starts from what this one learned.
And the correction: Deming himself preferred PDSA — Plan, Do, Study, Act — and was insistent about it. 'Check' smells of inspection: did the result pass? 'Study' demands more: what actually happened, including the parts nobody predicted? The distinction sounds pedantic and is instead the whole method — a cycle that only checks conformance learns nothing from surprises, and surprises are where the learning lives. We keep the common name and Deming's meaning. Context: decision-making models.
When to use it — and when not to
PDCA earns its keep when:
- ✓Improving a recurring process — support flows, deployment pipelines, onboarding, quality problems — anything that runs often enough for small experiments to read out.
- ✓The change is reversible and trialable. PDCA's power is cheap iterations; if you can pilot small, you can afford to be wrong fast.
- ✓Building an improvement culture. The loop teaches hypothesis-thinking: teams that run honest PDSA stop confusing activity with learning.
And where it fails or misfits:
- ✗Plan-Do-Plan-Do. The commonest corruption: teams ship change after change and never study results. Without the S, it's just churn with ceremony.
- ✗Success criteria after the fact. If 'what would success look like?' is answered after the data is in, every cycle succeeds and nothing is learned. Criteria date-stamp before the Do.
- ✗Act = a slide. A cycle that ends in a readout instead of a changed standard (or an explicit abandonment) has a hole where its fourth phase should be.
- ✗One-shot, irreversible decisions. PDCA is for iterating; a market entry or an acquisition doesn't get a second turn. Those need decision trees, scenarios, and the rest of the toolbox.
Step by step, with a worked example
Illustrative scenario: an invented support team whose first-response time has crept badly. One full turn:
- 1Plan — diagnose before hypothesizing. The team pulls a sample of slow tickets and finds a pattern: triage waits on a daily assignment meeting. Hypothesis: if tickets auto-route by category on arrival (X), median first-response time drops by a third (Y), because the assignment wait is the dominant delay (Z). Success criterion, written down now: median under 4 hours across two weeks, with no rise in re-routing rate (the counter-metric that catches gaming).
- 2Do — small. Auto-routing on two ticket categories, one team, two weeks. The rest of the flow unchanged, so the comparison stays clean.
- 3Study — against the prediction, including the surprises. Median fell to 3.6 hours — hypothesis holds. But re-routing rose in one category: the auto-router misfiles billing-adjacent tickets. That surprise is the phase's real yield; 'Check' would have shipped it as a pass.
- 4Act — standardize the win, cycle the surprise. Auto-routing becomes the documented standard for the categories where it held. The billing misfiling becomes the next cycle's Plan. Both decisions recorded with their reasoning.
- 5Turn again. The next cycle inherits the last one's evidence — which is the entire compounding logic of the method, and exactly what evaporates when cycles live in slide decks.
PDCA as an argument tree
In decision-quality terms, PDCA feeds commitment to action — it is the rare framework whose fourth phase is acting — and disciplines information: the Study phase generates evidence on a schedule. Its weak point is memory between cycles. On an argument tree:
Hypothesis → root claim
"Auto-routing cuts first-response time by a third because assignment wait dominates." Falsifiable, dated, with success criteria attached — before the trial runs.
Root-cause analysis → the supporting case
The ticket-sample evidence supports the claim; a teammate's alternative diagnosis (staffing, not routing) attaches as a counterargument, on the record before the experiment adjudicates.
Study results → evidence on the claim
The 3.6-hour median lands as support; the billing misfiling lands as a flagged surprise with its own node — visible, not buried in a readout appendix.
Act → a recorded decision, cycles → a chain
Standardize-or-abandon is recorded with reasoning, and the next cycle links back. A year of improvement becomes an auditable chain of argued experiments instead of a folder of decks.
PDCA supplies commitment and evidence-on-a-schedule; the argument tree supplies the sound reasoning that makes each cycle's learning survive to the next. See decision quality.
PDCA vs the alternatives
| If your question is… | Reach for | Why not PDCA |
|---|---|---|
| Which strategic objectives to improve toward | Balanced Scorecard | The scorecard sets direction; PDCA is the loop inside one objective |
| Whether the organization can absorb a big change | McKinsey 7S | PDCA iterates within the system; 7S diagnoses the system |
| A one-shot, irreversible commitment | Decision trees / CBA | No second turn means no cycle |
| Managing a register of standing risks | Enterprise risk management | Different loop: monitoring exposure, not improving a process |