PDCA is a four-step cycle — Plan, Do, Check, Act — used to test small changes before rolling them out fully.
PDCA (Plan-Do-Check-Act) is a simple four-step method teams use to test an idea on a small scale, learn from it, and improve a process without taking on big risk. If you've ever tried a small marketing test before a full launch, or run a pilot before a company-wide rollout, you've already used a version of it. This guide covers where it came from, how each step works, and how to build a repeatable template for your own projects.
[Image placement suggestion: a simple four-quadrant wheel graphic showing Plan, Do, Check, Act, placed right below the intro paragraph.]
What Is PDCA (Plan-Do-Check-Act)?
It stands for Plan, Do, Check, Act — a repeating cycle of small experiments that helps teams solve problems without guessing. Instead of rolling out one big change at once, you plan a small change, test it on a limited scale, check the results, then act by standardizing it or trying again.
The idea traces back to the scientific method: form a hypothesis, test it, check the results, then decide what's next. That's why it feels familiar even to people who've never heard the acronym — it's structured trial and error, done on purpose instead of by accident.
Where Did the PDCA Cycle Come From?
The PDCA cycle grew out of Walter Shewhart's "Specify-Produce-Inspect" loop for quality control in the 1930s. W. Edwards Deming expanded it into a four-step version for Japanese industry leaders in the 1950s — hence the names Deming cycle, Deming wheel, and Deming model.
Japanese manufacturers, including Toyota, adopted and shaped the version used today. Deming later promoted a related version, PDSA (Plan-Do-Study-Act), arguing "study" better captured learning than "check." Both remain in active use.
What Are the Four Steps of the PDCA Model?
The PDCA model works because each step has a clear job — skip one, and you usually repeat the whole cycle. Here's what happens at each stage.
Plan
Define the problem, set a measurable goal, and form a hypothesis about what might help. Decide what success looks like before you start.
Do
Test the change on a small scale — one team, one campaign, one shift — instead of rolling it out everywhere. The goal is learning, not full execution.
Check
Compare results against the Plan step's goal. Did the change work, partly work, or not at all? Look at the data, not just gut feeling.
Act
Standardize the change if it worked, adjust and re-test if it partly worked, or drop it and try a new hypothesis if not. The cycle begins again.
| Step | Core Question | Typical Output |
| Plan | What problem are we solving, and what's our hypothesis? | Goal, KPI, test plan |
| Do | Can we test this on a small scale first? | Pilot, prototype, MVP |
| Check | Did the result match the goal? | Data, analysis, insights |
| Act | What should become permanent? | Standard process or next test |
How Does PDCA Project Management Work?
PDCA project management means treating a project as a series of small, checkable experiments instead of one long push to the finish line. Teams use this to catch problems early, since every phase includes a checkpoint instead of waiting until the end to find out something went wrong.
In practice, this fits naturally into sprint reviews, retrospectives, and phase-gate reviews. A project manager might use PDCA project management to test a new status-reporting format with one team before a companywide rollout, or to pilot a vendor process before signing a full contract.
New workflow: Plan the change → Do a trial with one team → Check for delays or errors → Act by rolling out or revising
Vendor pilot: Plan evaluation criteria → Do a trial order → Check quality and cost → Act by approving or rejecting the vendor
Risk mitigation: Plan the fix → Do it on one workstream → Check if the risk reoccurs → Act by standardizing it across the project
How Do You Build a PDCA Template?
A PDCA template is simply a document — a form, spreadsheet, or whiteboard grid — with four sections to fill in as you move through the cycle. A shared template keeps everyone recording the same information in the same place, making results easier to compare across cycles.
What Should the Template Include?
Plan section: problem statement, goal, hypothesis, success metric
Do section: what was tested, who was involved, timeframe
Check section: actual results vs. target, data source
Act section: decision made, next steps, owner
Where Should You Keep It?
Most teams keep it in a shared doc, whiteboard tool, or project management board so it's visible to everyone and updated in real time, rather than buried in someone's notes.
How Does PDCA Connect to Leading SAFe's Inspect and Adapt?
PDCA is the engine behind SAFe's Inspect and Adapt (I&A) event. Rather than treating continuous improvement as a vague aspiration, SAFe builds Deming's four-step cycle into its planning cadence, giving teams a repeatable structure to get better every Program Increment (PI) instead of relying on ad hoc fixes.
Here's how the mapping works in practice. At the end of every PI, teams plan improvements during the I&A event's structured problem-solving workshop — surfacing what went wrong, why, and what might fix it. They Do those changes by carrying them into the next PI as concrete backlog items or process adjustments. They check the results against PI objectives, velocity, and quality metrics gathered along the way. Finally, they act by standardizing whatever worked across teams, or reframing the hypothesis if it didn't.
Leading SAFe essentially takes PDCA out of individual teams' hands and formalizes it into a scaled, recurring, organization-wide cadence — turning isolated experiments into enterprise-level continuous improvement.
Where Is the PDCA Model Used Today?
The model isn't limited to factories anymore. Common uses include:
Manufacturing and Lean/Six Sigma programs — reducing defects and waste
Software and Agile teams — running retrospectives and process experiments
Marketing — A/B testing campaigns before a full rollout
Healthcare — improving patient safety processes in small, measurable steps
Customer service — piloting new scripts or tools with one team first
[Image placement suggestion: a simple row of industry icons — factory, laptop, megaphone, stethoscope, headset — showing where this framework gets applied. Works well next to this list.]
How Does This Framework Compare to PDSA and Six Sigma's DMAIC?
The framework and PDSA are close cousins — PDSA swaps "Check" for "Study" to emphasize deeper learning, but the loop is otherwise the same. DMAIC (Define, Measure, Analyze, Improve, Control), used in Six Sigma, suits complex, data-heavy processes, while this cycle works better for quicker, smaller-scale improvement.
This framework: Plan, Do, Check, Act — is best for fast, small-scale improvement cycles.
PDSA: Plan, Do, Study, Act — best for learning-focused iterations
DMAIC: Define, Measure, Analyze, Improve, Control — best for complex, data-heavy processes
How Does This Framework Compare to the OODA Loop?
The OODA loop suits fast, competitive decisions; this framework suits steady, repeatable process improvement. OODA (Observe, Orient, Decide, Act) comes from military strategy, for situations where conditions change fast and a decision can't wait for a full test cycle. This framework instead measures a small test before committing, better suited to improving a stable process than reacting in real time.
Origin: This framework comes from manufacturing and quality control; OODA comes from military strategy and combat decision-making
Steps: This framework runs Plan, Do, Check, Act; OODA runs Observe, Orient, Decide, Act
Pace: This framework is deliberate and test-and-measure; OODA is fast and real-time
Best fit: This framework suits process improvement and quality control; OODA suits competitive or rapidly changing situations
What Are the Benefits and Limitations of This Approach?
Running small, checkable cycles lowers the risk of big rollouts, builds a habit of continuous improvement, and gives teams a shared language for solving problems. The main limitation is speed: it isn't the best fit for urgent fixes, and it depends on teams measuring the Check step honestly instead of jumping straight to Act.
Bringing It Full Circle
PDCA turns improvement into a habit, not a one-time push. Whether you're refining a marketing test or scaling it across teams, the cycle holds. Want to see it applied at an enterprise level? A Leading SAFe Course walks through exactly how this plays out in practice.
Place this right after the FAQ, as the final block on the page — it closes the loop (literally) on the PDCA topic while giving readers a natural next step toward your Leading SAFe content, without it reading as a bolted-on plug.
What Other Questions Do People Ask About This Framework?
1. Who invented PDCA?
Walter Shewhart created the original cycle, and W. Edwards Deming developed it into the four-step version used today.
2. How long should one cycle take?
Depending on the problem, many teams run cycles from one week to a few months, then repeat.
3. Is this only used in manufacturing?
No — today it's used in software, marketing, healthcare, and general project management.
4. What happens after Act?
The cycle restarts: the standardized result becomes the new baseline for the next Plan step.
Frameworks like Leading SAFe also build inspect-and-adapt loops into their planning cadence, showing how deeply this cycle is embedded in modern teamwork.
