Project & Product Managementbeginner1-4 weeks per cycleEst. 1939 by Walter Shewhart / W. Edwards Deming

PDCA Cycle

Also known as: Deming Cycle, Plan-Do-Check-Act, Shewhart Cycle

A four-step iterative management method for continuous improvement: Plan the change, Do (implement) it on a small scale, Check the results, and Act to standardize or adjust.

Quick Reference

Memory Aid

Plan it, Do it (small), Check it (measure), Act on it (standardize). Repeat forever.

TL;DR

The simplest improvement cycle: Plan a change hypothesis, Do a small-scale test, Check the results against your hypothesis, Act to standardize or adjust. Never stop cycling.

What Is PDCA Cycle?

PDCA is the simplest improvement cycle: Plan what you want to change, Do it on a small scale, Check whether it worked, and Act — either standardize it or try something different. Then repeat.

Without data, you're just another person with an opinion.

W. Edwards Deming

PDCA embodies the scientific method applied to management. Plan develops a hypothesis about what change will improve outcomes. Do tests that hypothesis in a controlled way. Check compares results against expectations. Act decides whether to adopt, adapt, or abandon the change. The cycle never truly ends — each Act sets up the next Plan. PDCA is the foundation for virtually every modern improvement methodology, from Lean to Six Sigma to Agile retrospectives.

📊

PDCA Cycle (Deming Wheel)

A continuous improvement cycle: Plan a change, Do a small test, Check the results, Act to standardize or adjust.

Plan

Identify & hypothesize

Do

Test on small scale

Check

Measure results

Act

Standardize or adjust

Origin & Context

Shewhart proposed the concept in the 1930s. Deming refined and popularized it in Japan in the 1950s, where it became foundational to the Japanese quality movement and Toyota Production System.

Core Components

1

Plan

Identify the problem, analyze root causes, and develop a hypothesis for improvement.

Example

Plan: Customer complaints about delivery speed increased 20%. Root cause analysis suggests the order review step adds 2 days. Hypothesis: Automating review will reduce delivery time by 2 days.

2

Do

Implement the change on a small scale to test the hypothesis.

Example

Do: Automate order review for one product line as a pilot for 2 weeks.

3

Check

Measure results and compare to the hypothesis.

Example

Check: Delivery time for the pilot dropped by 1.5 days. Customer complaints for that line fell 35%.

4

Act

If successful, standardize and scale. If not, analyze why and plan the next cycle.

Example

Act: Results positive but not fully at target. Standardize automation for this line and plan a second cycle to address the remaining 0.5-day gap.

💡

Did You Know?

Deming actually preferred 'PDSA' (Plan-Do-Study-Act) because 'Study' implies analyzing and understanding the data, while 'Check' can be reduced to a simple pass/fail. Despite Deming's preference, PDCA became the more popular acronym. The cycle was originally conceived by Walter Shewhart in the 1930s — Deming refined and popularized it.

When to Use PDCA Cycle

Scenario 1

Daily operational improvement

Problem it solves: Provides the simplest framework for testing and implementing process improvements.

Real-World Application

A warehouse team uses PDCA weekly: Plan (identify the biggest source of picking errors), Do (test a new shelf labeling system in one aisle), Check (measure error rate), Act (roll out to all aisles or try a different approach).

Scenario 2

Foundation for larger improvement methodologies

Problem it solves: PDCA is the engine inside Lean, Six Sigma, and other frameworks.

Real-World Application

Every kaizen event follows PDCA. Every Six Sigma DMAIC project embeds PDCA. Every Agile retrospective is a PDCA cycle for team process.

The most neglected step is Check. Teams often implement changes (Do) and assume they worked without measuring. Always compare results to your Plan hypothesis.

How to Apply PDCA Cycle: Step by Step

Before You Start

  • A problem or improvement opportunity
  • Basic measurement capability
  • Willingness to experiment
Tools:PDCA worksheetBasic measurement toolsRoot cause analysis tools (fishbone, 5 Whys)
1

Plan

Define the problem, gather data, analyze root causes, and develop a change hypothesis.

Tips

  • Use data, not assumptions, to understand the problem

Common Mistakes

  • Skipping root cause analysis and jumping to solutions
2

Do

Implement the change on a small scale.

Tips

  • Keep the test small and time-limited to reduce risk

Common Mistakes

  • Rolling out the change everywhere before testing
3

Check

Measure results and compare to your hypothesis.

Tips

  • Use the same metrics you measured in Plan for comparison

Common Mistakes

  • Not measuring, or changing metrics mid-cycle
4

Act

Standardize if successful; adjust and re-plan if not.

Tips

  • Document the new standard so improvements stick

Common Mistakes

  • Moving on without standardizing, allowing regression

Value & Outcomes

Primary Benefit

The simplest, most universal framework for testing and implementing improvements systematically.

Additional Benefits

  • Reduces risk by testing on small scale first
  • Embeds the scientific method into daily management

What You'll Learn

  • How to apply scientific thinking to operational improvement
  • How to test changes before full-scale implementation

Typical Outcomes

Steady, low-risk process improvementsA culture of experimentation and learning

Best Practices

📋 Preparation

  • Start with a clear problem statement and data
  • Define success criteria before starting

🚀 Execution

  • Keep cycles short — 1-4 weeks
  • Always measure in Check, don't skip it

🔄 Follow-Up

  • Standardize successful changes
  • Start the next PDCA cycle immediately

💎 Pro Tips

  • PDCA is fractal — you can run multiple cycles at different levels simultaneously
📌

Toyota's 1,000 PDCAs Per Day

At Toyota, front-line workers are expected to run small PDCA experiments as part of daily work. A typical Toyota assembly plant runs an estimated 1,000+ micro-improvements per year through PDCA thinking, contributing to Toyota's legendary manufacturing quality and the Toyota Production System.

Limitations & Pitfalls

Too simple for complex, multi-variable problems

Mitigation: Use DMAIC (Six Sigma) for complex problems requiring statistical analysis

Requires discipline to complete all four steps — most people skip Check

Mitigation: Make Check a formal step with defined metrics and a review meeting

Apply PDCA Cycle with Stratrix

Turn this framework into a professional strategy deck in under a minute. Stratrix applies PDCA Cycle automatically to your business context.

Try Stratrix Free