Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The PDCA cycle—Plan, Do, Check, Act—is a repeatable way to test a change, learn from the results, and decide what to do next. In project management, it helps teams improve a specific process or delivery practice; it does not replace a project plan, schedule, or governance structure.

What the PDCA cycle means

PDCA is a continuous-improvement loop: identify an opportunity, plan a change, try it, examine the evidence, then adopt or revise the change based on what the team learned. The cycle is designed to repeat rather than end with a one-time decision. The American Society for Quality (ASQ) describes PDCA as a model for change that can be used on small or large scales.

What happens in each of the four steps?

Plan

Define a specific opportunity for improvement and the change you want to test. Before starting, agree on the current baseline, the intended result, a useful measure, and when the team will review the results. Those choices make it possible to tell whether the test helped.

Do

Put the planned change into practice. When practical, start with a small-scale test so the team can learn without committing to a wider rollout before it has evidence.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Check

Review the test against the baseline and intended result. Analyze what happened, whether the change contributed to it, and what the team learned. A measurement alone may not explain why a result changed; use an appropriate analysis method when the problem calls for one.

Act

Choose the next step based on the findings. If the change worked, standardize or expand it and continue monitoring it. If it did not, revise the plan and run another cycle; if the evidence does not support continuing, stop or reconsider the proposed change.

How to apply PDCA to project work

Use PDCA to answer a bounded improvement question, not as the project’s entire management system. For example, a project team could test a revised handoff process on a small portion of its work, compare cycle time or rework with its baseline, review what changed, and then standardize a useful practice or try a revised version. This is an illustrative example, not a reported project result.

  1. Choose one improvement question. Keep the change narrow enough to test, such as whether a different handoff reduces delays or rework.
  2. Set the baseline and review point. Record the current result, decide what evidence would indicate improvement, and agree when to examine the test.
  3. Run the test. Apply the change to a manageable portion of work when possible, rather than assuming it is ready for project-wide adoption.
  4. Assess and decide. Compare results with the baseline, consider what may explain them, and adopt, revise, or stop the change.
  5. Carry learning forward. If the team adopts the change, incorporate it into relevant working practices and keep monitoring whether it remains useful.

PDCA and a project schedule do different jobs. ASQ describes Gantt charts as tools for showing tasks, timing, duration, and completion status; PDCA structures learning about whether a change improves work. A team can use both: the schedule tracks planned work, while PDCA helps test and refine how that work is done.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
Rank #3
Sale
A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Seventh Edition and The Standard for Project Management (ENGLISH)
  • book
  • A Guide to the Project Management Body of Knowledge (PMBOK Guide) – Seventh Edition and The Standard for Project Management (ENGLISH)

What a PDCA example can—and cannot—show

ASQ describes the Pearl River, New York School District’s A+ Approach to Classroom Success. The district analyzed student data and used assessment results to make mid-course corrections, including reteaching material or changing teaching methods. Successful curriculum design and teaching methods were then treated as standardized practices shared among teachers. ASQ notes that the district received the Malcolm Baldrige National Quality Award in 2001, but the cited description gives no quantified outcome attributable to PDCA.

The example also illustrates a limitation: PDCA provides a structure for acting on evidence, but does not itself prescribe how to analyze data or identify root causes. Depending on the problem, teams may need separate methods for root-cause analysis, prioritization, risk management, scheduling, and project governance.

Rank #4
Sale
Harvard Business Review Project Management Handbook: How to Launch, Lead, and Sponsor Successful Projects (HBR Handbooks)
  • Harvard Business Review Project Management Handbook: How to Launch, Lead, and Sponsor Successful Projects
  • Harvard Business Review Press
  • BLANK BOOK

When PDCA is useful—and when it is not enough

  • Use it when a team has a specific process or delivery practice to improve, can try a change, and can gather evidence about the result.
  • Pair it with other tools when the work also needs task dependencies, timing, scope decisions, risk controls, or formal decision rights.
  • Do not treat a cycle as proof. A change may fail, produce mixed results, or require further analysis; the value is in learning and making the next decision deliberately.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

How PDCA relates to quality management standards

ISO 10006:2017 provides guidance for quality management in projects, covering project characteristics, quality-management principles and processes in projects, and a project quality plan. Separately, ISO’s archived process-approach guidance describes PDCA as useful for defining, implementing, and controlling corrective actions and improvements. These references establish relevant quality-management context; they do not make PDCA a substitute for project-specific planning.

ISO material also discusses PDCA in relation to processes and quality management systems, but the surfaced ISO 9001 page is identified as a draft-edition page. Do not treat wording from that page as a current compliance requirement without verifying the applicable edition and requirements for your organization.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

The model is also used beyond project scheduling. The U.S. Environmental Protection Agency organizes its environmental management system development material around Plan-Do-Check-Act.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.