The PDCA Cycle Explained: Plan, Do, Check, Act for Continuous Improvement

Understand the PDCA cycle step by step, see a practical example and learn how Plan, Do, Check, Act helps teams solve problems and keep improving.

Share on Linkedin Share on WhatsApp

Estimated reading time: 7 minutes

Article image The PDCA Cycle Explained: Plan, Do, Check, Act for Continuous Improvement

Most teams have lived through this situation: a problem appears, someone proposes a quick fix, the fix is rolled out everywhere, and a few weeks later the same problem is back. The issue is rarely a lack of effort. It is usually a lack of method. The PDCA cycle, short for Plan, Do, Check, Act, is one of the simplest and most widely used methods for solving problems and improving processes in a structured way. In this article, you will learn what each step means, see a practical example and discover how to avoid the most common mistakes.

Where the PDCA cycle comes from

The PDCA cycle has its roots in the work of Walter Shewhart, an American statistician who studied quality control in manufacturing in the first half of the twentieth century. His ideas were later developed and widely promoted by W. Edwards Deming, especially in Japan after the Second World War, where they influenced the quality movement and the philosophy of continuous improvement often called kaizen. For this reason, PDCA is also known as the Deming cycle or the Shewhart cycle.

Deming himself later preferred the name PDSA, replacing “Check” with “Study,” to emphasize learning from results rather than simply inspecting them. Both versions follow the same logic. Today, PDCA appears in management standards such as ISO 9001 and is used in manufacturing, healthcare, software development, education and public administration.

The four steps at a glance

StepMain questionTypical outputs
PlanWhat is the problem and what do we expect to change?Problem statement, root cause analysis, goal, action plan
DoHow do we test the plan on a small scale?Pilot implementation, data collection
CheckDid the results match what we expected?Comparison of results with goals, lessons learned
ActDo we adopt, adjust or abandon the change?Standardized procedure or a new plan

Step 1: Plan

Planning is usually the longest and most important stage. The goal is to understand the problem before trying to solve it. A good plan answers several questions:

  • What exactly is the problem, and how do we know it exists?
  • What data do we have about it?
  • What are the likely root causes? Tools such as the “5 Whys” or a fishbone (Ishikawa) diagram can help here.
  • What is the goal, ideally expressed in measurable terms?
  • What actions will we take, who is responsible and by when?

It is also useful to write down a hypothesis: “If we do X, we expect Y to improve by Z.” This makes the next steps much clearer.

Step 2: Do

In the Do stage, the team carries out the plan. Whenever possible, this should happen as a small-scale test: one shift, one department, one product line or a limited period. Testing small reduces risk and makes it easier to learn. During this stage, it is essential to collect data and record what actually happened, including unexpected difficulties.

Step 3: Check

Now the team compares results with the goal and with the original situation. Did the change work? Did it work as much as expected? Were there side effects? This is the moment to be honest. A test that did not work is still valuable, because it shows that a hypothesis was wrong and saves the organization from spreading an ineffective solution.

Step 4: Act

Based on what was learned, the team decides what to do next:

  • Adopt: if the change worked, standardize it. Update procedures, train people and roll it out more widely.
  • Adapt: if results were partial, adjust the plan and run another cycle.
  • Abandon: if the change did not help, return to the Plan stage with a new hypothesis.

After Act, the cycle starts again. That is why PDCA is often drawn as a wheel rolling up a slope: each turn brings the process to a slightly better level, and standardization works like a wedge that prevents it from sliding back.

A practical example

Imagine a small online store that receives frequent complaints about late deliveries.

  1. Plan: the team reviews a month of orders and discovers that most delays happen with orders placed on Friday afternoons, because packing only resumes on Monday. The hypothesis is that adding a short packing shift on Saturday mornings will reduce late deliveries. The goal is to cut late orders by half.
  2. Do: the store tests a Saturday shift for four weeks and records the dispatch date of every order.
  3. Check: the data shows a clear drop in delays, but also an increase in labor costs. The team calculates whether the improvement in customer satisfaction justifies the cost.
  4. Act: the store decides to keep the Saturday shift during peak seasons only and updates its schedule. A new cycle begins to investigate the remaining delays.

PDCA in project management

Although PDCA was born in quality management, its logic fits naturally into projects. Planning, executing, monitoring and adjusting are core activities in any project. Agile approaches use a similar rhythm: short iterations, frequent reviews and retrospectives in which the team decides what to change next time. Understanding PDCA helps project managers turn lessons learned into concrete improvements instead of simply documenting them.

Common mistakes to avoid

  • Rushing the Plan stage: jumping to solutions without understanding causes often leads to fixes that do not last.
  • Skipping Check: without measuring results, there is no way to know whether a change actually helped.
  • Not standardizing: improvements that are not documented and trained tend to disappear.
  • Running only one cycle: PDCA is meant to be repeated. Its strength comes from continuous, incremental learning.

Conclusion

The PDCA cycle turns problem solving into a learning process: plan carefully, test on a small scale, check the results honestly and act on what you learn. Its simplicity is exactly what makes it powerful in businesses, projects and even personal goals. If you want to strengthen your skills in planning and managing work, explore the free Project Management courses on Cursa and put a PDCA cycle into practice on your next challenge.

Total Cost of Ownership: Why the Cheapest Quote Is Rarely the Cheapest Purchase

The sticker price is only part of what you pay. Learn how to build a total cost of ownership view before approving any significant purchase.

Incoterms Explained: Who Pays, Who Ships and Who Carries the Risk

A plain-language guide to Incoterms: what these three-letter codes decide, how risk transfers, and which mistakes cost importers money.

Safety Stock and Reorder Points: How to Decide When to Buy More Inventory

Learn how lead time, demand variability, safety stock and reorder points work together so you avoid stockouts without tying up cash.

Profit vs. Cash Flow: Why a Profitable Business Can Still Run Out of Money

Profit and cash are not the same thing. Learn how accrual accounting creates the gap, and which habits keep a growing business solvent.

How to Validate a Business Idea Before You Invest Money in It

Practical steps to test whether people actually want your business idea, before spending months and savings building it.

Understanding Inflation: How It Affects Your Money and Savings

Learn what inflation is, what causes prices to rise, and simple strategies to protect the value of your money and savings over time.

What Are ETFs and How Do They Work? A Beginner’s Guide

Learn what ETFs are, how they work, their main advantages and risks, and why they have become a popular tool for beginner investors.

SMART Goals: How to Set Objectives That Actually Get Done

Learn the SMART goals framework: how to make objectives Specific, Measurable, Achievable, Relevant and Time-bound, with clear examples.