# PDCA Cycle: Plan-Do-Check-Act for Process Improvement > Learn the PDCA cycle (Plan-Do-Check-Act), a 4-step loop for process improvement. See each phase, an example, and when to use it to refine results at work. Source: https://asana.com/resources/pdca-cycle ## PDCA cycle: Plan-Do-Check-Act for process improvement #### Summary The PDCA cycle, which stands for Plan-Do-Check-Act, is a simple four-step method for making ongoing improvements. In this guide, you’ll see how each step works, look at a real-world example, and find out when to use this cycle to help your team test ideas, improve processes, and achieve better results.The PDCA (Plan-Do-Check-Act) cycle is a four-step problem-solving strategy for [continuous improvement](/resources/continuous-improvement). Rather than a one-and-done process, it's an ongoing feedback loop where teams develop hypotheses, test ideas, and refine their approach over time. Since PDCA is based on repeating steps, it gives teams the flexibility to tackle many different business challenges. #### Master AI-Powered Workflow Optimization Ready to revolutionize your team's productivity with AI you can trust? Join industry leaders from Asana and Anthropic to learn proven strategies for implementing AI across your workflow stages and unlock the full potential of Asana's AI Studio. - [Watch the webinar](https://resources.asana.com/how-to-transform-your-workflows) ## PDCA cycle history The PDCA cycle originated in the 1920s with [Walter Shewhart](https://en.wikipedia.org/wiki/Walter_A._Shewhart), the father of statistical quality control, and was later expanded by W. Edwards Deming. In his book [Economic control of quality manufactured product](https://www.worldcat.org/title/economic-control-of-quality-of-manufactured-product/oclc/7543940), Shewhart applied the scientific method to quality control in manufacturing. Shewhart's thesis was further developed by [W. Edwards Deming](https://en.wikipedia.org/wiki/W._Edwards_Deming), who championed Shewhart's work. Deming expanded on Shewhart's idea and used the scientific method not only for quality control but also [process improvement](/resources/process-improvement-methodologies). Deming went on to teach the method he called the Shewhart cycle to Japanese engineers. There, the Shewhart cycle mixed with kaizen (the Japanese principle of continuous improvement, which was developed by [Kaoru Ishikawa](https://en.wikipedia.org/wiki/Kaoru_Ishikawa#Contributions_to_improvement_of_quality)), the Toyota production system, and lean manufacturing to become what we now call the Plan-Do-Check-Act (PDCA) cycle. Nowadays, the Plan-Do-Check-Act cycle is commonly used in [lean project management](/resources/lean-project-management). This methodology has many names, including: - Plan-Do-Check-Act cycle, or PDCA cycle - Deming cycle or Deming wheel - Shewhart cycle - Control cycle - Plan-Do-Study-Act cycle or PDSA cycle ## 4 steps to use the PDCA cycle The PDCA process has four steps: planning, doing, checking, and acting. Since it’s a cycle, you start again from the beginning each time you finish. Step Purpose **Plan** Identify the problem, set goals, and outline what you'll test **Do** Implement the plan on a small scale to test your hypothesis **Check** Review results and compare them against your expected outcomes **Act** Roll out successful changes or restart the cycle with new insights ### 1. Plan The first step to any process improvement or project planning is to figure out what you need to do. Like any [project plan](/resources/project-management-plan), this includes a variety of information, including: - The [project objectives](/resources/how-project-objectives) - Success metrics - The [project deliverables](/resources/what-are-project-deliverables) or end result - [Project stakeholders](/resources/project-stakeholder) - The [project timeline](/resources/create-project-management-timeline-template) - Any relevant [project risks](/resources/project-risk-management-process) or [constraints](/resources/theory-of-constraints) You can use the PDCA cycle for many types of projects. Whether you’re starting something new or working on quality improvement, spending time on careful planning helps set your project up for success. Remember, PDCA is a cycle, so you don’t need to have every answer at the start. Each time you go through the cycle, review your plan to make sure it still matches your goals. - [Read: Create a better project plan in just 7 steps](/resources/project-management-plan) ### 2. Do After you finish your project plan, the next step is to put it into action. PDCA, like other lean methods, focuses on making small, gradual changes. In the Do phase, try out your plan on a small scale to see if it works. - [Read: Understanding the iterative process, with examples](/resources/iterative-process) ### 3. Check Look over the test you did in the Do phase to see if everything went as planned. You’ll probably find some things to improve. The Check phase helps you catch these small issues before they become bigger problems. If necessary, revisit your project plan to ensure it continues to meet your objectives. Alternatively, if you realized you need to make a change to the project plan, you can use a [change control process](/resources/change-control-process) to do so now. ### 4. Act After the check, move to the Act phase, which includes rolling out the full project or using a [corrective action plan](/templates/corrective-action-plan) to implement the process improvement. Don't forget that the PDCA cycle is a cycle. If needed, return to the Plan phase to continuously improve your project or processes. ## PDCA cycle example Here’s an example of how the PDCA cycle works: Imagine a marketing team wants to improve their email campaign open rates. **Plan:** The team identifies that their current email open rate is 15%, below the industry average of 21%. They hypothesize that personalizing subject lines could increase engagement and define success as reaching a 20% open rate within one month. **Do:** The team implements personalized subject lines for a small segment of their email list, using the recipient's first name and referencing their recent website activity. **Check:** After two weeks, the team reviews the data. The personalized emails achieved a 23% open rate compared to 14% for the control group. They also notice click-through rates improved by 8%. **Act:** Based on these results, the team rolls out personalized subject lines across all email campaigns. They document their findings and identify the next improvement opportunity: testing send times to further boost engagement. This example shows how the PDCA cycle enables teams to make [data-driven decisions](/resources/data-driven-decision-making) and continuously refine their processes. ## When should you use the PDCA cycle? The PDCA cycle is a helpful approach for managing projects and improving processes. It works best for teams that are open to ongoing improvement and repeating steps as needed. The Plan-Do-Check-Act cycle is particularly useful when you want to: - Streamline and improve a repetitive work process - Develop a new business process - Get started with continuous improvement - Rapidly iterate on change and see immediate results - Minimize errors and maximize outcomes - Test multiple solutions quickly ## Benefits of the PDCA cycle The PDCA cycle has several benefits for teams focused on continuous improvement. **Pros:** - Helpful for teams looking to get started with continuous improvement - Flexible methodology for virtually any project - Quickly implement change and see results - Use the PDCA as your [standard operating procedure](/resources/sop-template) to increase org-wide standardization without the use of a [project management office (PMO)](/resources/pmo-project-management-office) - Proven continuous improvement methodology **Cons:** - You need support from senior management in order for the PDCA cycle to be particularly effective - The real value of PDCA comes from repeating the cycle many times. It’s not very effective if you only use it once. - Requires time to implement and learn - PDCA isn’t the best choice for urgent projects, because you usually need to run the cycle several times. ## Put the PDCA cycle into practice The PDCA cycle is an effective way to implement continuous improvement and [problem solving](/resources/problem-solving-strategies). By planning carefully, testing on a small scale, reviewing results, and acting on what you learn, your team can make incremental progress toward better processes and outcomes. To get the most out of the PDCA cycle, set your projects up for success with [project planning tools](/uses/project-planning). Plan, manage, and track your team's projects to hit your deliverables on time. [Get started](/create-account) and see how Asana can help you put the PDCA cycle into action. - [Create a business process management template](/templates/business-process-management) ## Frequently asked questions about the PDCA cycle #### What's the difference between PDCA and PDSA? PDCA and PDSA are nearly identical; the only difference is the third step: "Check" compares results against expectations, while "Study" emphasizes deeper analysis. W. Edwards Deming preferred PDSA because "Study" better captures the intent of understanding why results occurred. #### Is PDCA Lean or Six Sigma? PDCA is a universal cycle that supports both Lean and Six Sigma. Lean uses it to eliminate waste through small changes, while Six Sigma applies it within its DMAIC framework to reduce variation. #### How does PDCA relate to Kaizen? PDCA is the foundational way to practice Kaizen, the Japanese philosophy of continuous improvement. While Kaizen focuses on small, daily changes, PDCA provides the structured process for testing and evaluating those improvements. - [Project management](/resources/project-management) - [Project portfolio management 101](/resources/what-is-project-portfolio-management) Project management Business strategy #### Writer If you manage various initiatives across different teams and departments, you know how hard it can be to capture progress and share results in one place. Project management tools ... - [Asana app in ChatGPT: go from ideas to action](/resources/chatgpt-asana-integration) AI at work #### Content writer You just spent 30 minutes in ChatGPT working through an idea — outlining a campaign, mapping out next steps, pressure-testing a plan.It’s clear, structured, and actually feels rea ... - [How to set and achieve project milestones](/resources/project-milestones) Project management Goals #### Head of Content, Asana Not all project plans are created equal. You may have goals, tasks, task owners, and deadlines. You may have dependencies and deliverables. But did you remember to include project ... - [10 team management skills to start building today](/resources/team-management-skills) Leadership Project management Collaboration Inspire & Impact Collection #### Writer What sets a good manager apart from a bad one? It isn't the work you do or the workflows your team uses. Rather, good managers focus on their team. By prioritizing supporting your ... - [What is the Plan-Do-Check-Act (PDCA) cycle?](/resources/pdca-cycle) Project management Workflow automation - [Writer](/author/julia-martins) The PDCA (Plan-Do-Check-Act) cycle is a four-step problem-solving strategy for continuous improvement. Rather than a one-and-done process, it's an ongoing feedback loop where team ...