Plan-Do-Study-Act

Plan-Do-Study-Act is the lesser-known sibling of Plan-Do-Check-Act, and the word swap was deliberate. W. Edwards Deming, who carried Walter Shewhart's original PDCA cycle into Japanese manufacturing after World War II and then into Western quality thinking in the 1980s, came to dislike the word Check. He felt it implied a binary verification, did the change pass or fail, and that the binary framing discouraged the kind of curious, careful examination of results that actually produces learning. Study, he argued, was the right verb. The change was small, but Deming did not make small changes for no reason.

"Most improvement is not in the change. It is in what you notice when you look at the results."

How PDSA works

The cycle has the same four phases as PDCA. The work happens in roughly the same way.

1. Plan. Write down the problem in specific terms. Form a hypothesis about the cause and propose a countermeasure. Predict what will change if the countermeasure works, in numbers when possible.
2. Do. Run the change as a small pilot. One shift, one machine, one product, one batch. The Do phase is an experiment, not a launch.
3. Study. Compare actual results to the prediction. Ask what was learned, including what was unexpected. Look for side effects, operator reactions, downstream impacts. Sit with the data long enough for the surprises to surface.
4. Act. Decide. If the change worked, standardize it across the operation. If it did not, return to Plan with the new learning.

The whole point of the Study renaming is to slow down the third step. The Check version of the cycle can become a status meeting where the team confirms the change worked and moves on. The Study version is supposed to be a longer pause, a real examination of what happened. In practice, the verb only matters if the team treats it as a real instruction. A lazy PDSA is no better than a lazy PDCA.

Most PDSA loops on a shop floor are two to four weeks long, the same as PDCA. The cycle repeats continuously, with each pass building on the learning from the last.

Where PDSA fits on the shop floor of a small manufacturer

Imagine a 25-person small-batch food processing shop where a packaging line has been throwing about two seal failures per shift, costing rework and occasional customer complaints. The shop's quality lead has been a healthcare nurse in a previous life and uses the PDSA vocabulary out of habit.

Plan, week one. Hypothesis: seal failures correlate with a temperature drift on the heat-bar after long pauses, not with the operator. Prediction: a five-minute warm-up cycle after any pause longer than ten minutes will cut failures by at least half. Do, week two. Try the warm-up rule on the night shift only, with the lead operator logging every pause and every failure on a clipboard at the line.

Study, end of week two. Failures drop from 14 in a week to 4. The prediction was met. But the operator notices something else: two of the four remaining failures happen on the first three packages of a fresh roll of film. Nobody had connected film roll changes to failures before. That is the kind of finding that Study is supposed to surface and that a hurried Check might miss.

Act. The warm-up rule is standardized across shifts. The next PDSA targets the film-roll-change finding.

That is PDSA at small scale. The cycle is the same as PDCA; the difference is the discipline of looking at the results long enough for the unexpected pattern to appear.

Common mistakes with PDSA

• Rushing through Study. The renaming exists to prevent this. Sit with the data long enough for the surprises to surface.
• Treating Study as a status update. It is supposed to be an analytical session, not a meeting about whether the change happened on time.
• Studying without the pilot operators. The richest findings are in their stories. Bring them into the session.
• One-and-done PDSA. The cycle is meant to repeat. A team that runs one PDSA loop a year is not running PDSA.
• Treating PDSA and PDCA as interchangeable in name only. They are mechanically similar but the emphasis is different. Use the verb you intend to honor.

PDSA and related Lean tools

PDSA is the Deming variant of Plan-Do-Check-Act; the two cycles are functionally similar with one deliberate word change. The Six Sigma counterpart for variation-driven problems is DMAIC. The one-page document many shops use to capture a PDSA cycle is an A3, which holds the plan, hypothesis, results, and follow-up in a single visible artifact. PDSA is one of the iterative engines behind kaizen.