What is PDCA Cycle (Plan-Do-Check-Act)?

The PDCA Cycle (Plan-Do-Check-Act) is a four-step, iterative method for continuous improvement and problem-solving. Teams plan a change, do it on a small scale, check the results against expectations, and act by standardizing what worked or revising what did not. Repeating the loop drives steady, data-informed gains.

How the PDCA Cycle Works

PDCA is a closed loop, not a one-time project. Each turn of the cycle produces evidence that feeds the next, so improvements compound over time. Popularized by W. Edwards Deming (who credited Walter Shewhart, giving rise to the alternate name the Shewhart or Deming Cycle), it underpins many quality and lean systems, including ISO 9001 and the Toyota Production System.

The Four Steps

  • Plan — Identify the problem or opportunity, analyze the current state, set a measurable objective, and design a change or experiment with a clear hypothesis about the expected result.
  • Do — Implement the change on a small scale or as a controlled trial. Keeping the test small limits risk and makes the effect easier to isolate.
  • Check — Compare the actual results to the objective set in Plan. Study the data, confirm whether the hypothesis held, and identify what you learned.
  • Act — If the change worked, standardize it and roll it out more widely. If it did not, adjust the approach and start a new cycle. Either way, the loop repeats.

A common variant, PDSA (Plan-Do-Study-Act), swaps “Check” for “Study” to stress deeper analysis of results rather than a simple pass/fail check. The intent is the same.

Benefits of PDCA

  • Structured problem-solving that reduces guesswork by testing changes before full rollout.
  • Lower risk, because ideas are validated on a small scale first.
  • A culture of continuous improvement in which frontline teams routinely surface and test ideas.
  • Standardization of proven changes, so gains are locked in and not lost over time.

Common Pitfalls

  • Skipping Check. Rolling out a change without measuring results turns PDCA into “Plan-Do-Hope.”
  • Running the cycle only once. PDCA is meant to iterate; a single pass rarely captures the full benefit.
  • Vague objectives in the Plan step, which make the Check step impossible to evaluate honestly.
  • Failing to standardize in the Act step, so improvements quietly erode as people revert to old habits.

Relation to Lean and Continuous Improvement

PDCA is one of the core engines of kaizen and lean manufacturing. In the Plan and Check phases, teams often use root cause analysis to make sure they are solving the underlying problem rather than a symptom. Where kaizen describes the mindset of ongoing incremental improvement, PDCA provides the repeatable, disciplined loop that turns that mindset into measured results.

How VSight helps

The hardest part of PDCA is often the Act step: capturing a proven change so that everyone follows it the same way, every time. VSight Workflow lets you standardize and document improved processes as digital work instructions, standard operating procedures (SOPs), and checklists, with built-in task management, so the version that passed the Check step becomes the new standard your frontline team actually works from.

VSight is a connected worker platform. Alongside VSight Workflow, VSight provides AR remote assistance, letting a remote expert see a technician’s live camera feed and guide them in real time with augmented-reality annotations, useful when a Do or Check step needs specialist input on site. VSight is GDPR, HIPAA, and ISO 27001 certified.

Ready to standardize your improvements? Request a demo.

Related terms: kaizen, lean manufacturing, root cause analysis.

Frequently asked questions

What does PDCA stand for? PDCA stands for Plan-Do-Check-Act, a four-step, iterative method for continuous improvement and problem-solving. Teams plan a change, do it on a small scale, check the results against expectations, and act by standardizing what worked or revising what did not.

What is the difference between PDCA and PDSA? PDSA (Plan-Do-Study-Act) is a common variant that swaps the Check step for Study to stress deeper analysis of results rather than a simple pass or fail check. The intent of both cycles is the same.

Why is the PDCA Cycle important? PDCA gives teams a structured way to test changes on a small scale before full rollout, which lowers risk and reduces guesswork. Because it is a repeating loop, it builds a culture of continuous improvement and locks in proven changes so gains are not lost over time.

How does VSight help with the PDCA Cycle? The hardest part of PDCA is often the Act step, and VSight Workflow lets you standardize and document improved processes as digital work instructions, standard operating procedures, and checklists so the version that passed the Check step becomes the new standard. VSight also provides AR remote assistance, letting a remote expert see a technician’s live camera feed and guide them with augmented-reality annotations when a step needs specialist input on site.