top of page

PDCA: Why "Plan-Do-Check-Act" Is a Discipline, Not a Suggestion | OEC Insights

  • Feb 23
  • 3 min read

By Allan Ung | Founder & Principal Consultant, Operational Excellence Consulting (OEC)

Updated: 20 July 2026


OEC Implementation Insights 

Implementation is where success or failure happens. At OEC, we go beyond awareness to provide structured, practical guidance on Lean, TPM, ISO, and quality systems. Each article in this series highlights proven steps, common pitfalls, and practical insights — and connects directly to facilitation‑ready training presentations that help teams move from learning to doing.


Most teams view PDCA as a generic flowchart for "getting things done." They run a cycle, see a minor improvement, and call it a day. That isn't PDCA—it’s just trial and error. The true power of PDCA lies in its role as a scientific discipline that forces your organization to stop guessing and start learning. If your problem-solving efforts feel like an endless cycle of "fixing," you are missing the rigour that makes this methodology a competitive advantage.


As a consultant, I’ve found that the difference between mediocre and high-performing teams is how they handle the "Check" phase. If you aren't rigorously comparing your results to your predictions, you aren't practicing PDCA; you're just hoping for the best.


TPM implementation roadmap in 6 steps
PDCA Problem Solving in 6 Steps

Step 1: Define the Problem (Plan): The "Target State"


Clearly articulate the gap between where you are and where you need to be.


  • Practitioner’s Insight: If you can’t define the problem in one sentence, you aren't ready to solve it. A vague problem statement guarantees a vague, ineffective solution.


Step 2: Analyze Root Causes (Plan): The "Scientific Inquiry"


Use structured tools to peel back the layers of the failure until you reach the systemic driver.


  • Practitioner’s Insight: We often skip this because we think we "already know" the answer. Challenge your own intuition. If your analysis doesn't surprise you, you likely haven't dug deep enough.


Step 3: Develop and Test Solutions (Do): The "Controlled Experiment"


Implement your best countermeasure on a small scale, treating it as an experiment rather than a permanent fix.


  • Practitioner’s Insight: Keep the "Do" phase humble. The goal here is to learn what works, not to prove you were right from the start. Small, reversible tests are the safest way to innovate.


Step 4: Measure Results (Check): The "Truth Serum"


Evaluate your outcomes against the objectives you set in the "Plan" phase.


  • Practitioner’s Insight: This is the most frequently skipped step. Be honest with the data. If the solution didn't deliver the expected result, don't ignore the numbers—embrace the learning and adjust your hypothesis.


Step 5: Standardize Successful Practices (Act): The "Baseline"


Integrate the winning countermeasure into Standard Work to lock in your gains.


  • Practitioner’s Insight: Improvement without standardization is just a temporary spike. If you don't update your process to reflect the new way of working, your team will naturally drift back to the old, inefficient habits.


Step 6: Reflect and Repeat (Act): The "Iterative Engine"


Review what you learned and move to the next challenge immediately.


  • Practitioner’s Insight: PDCA is a rhythm, not a project. The strength of your organization is directly proportional to how many PDCA cycles your team completes in a year.


The Common Pitfalls of PDCA Problem Solving


  • The "Vague Target" Trap: Starting without a clear, measurable objective, which makes it impossible to know if you actually succeeded.


  • The "Root Cause Bypass": Succumbing to the pressure of time and implementing a "quick fix" that ignores the underlying process failure.


  • The "Checkless" Cycle: Failing to measure outcomes, which turns the entire process into a blind gamble.


  • The "One-Time" Syndrome: Treating PDCA as a single event rather than a continuous, cultural habit.



👉 Ready to build a culture of disciplined, scientific problem-solving? Implementation is where success is won or lost. To move your team from "hoping it works" to "knowing it works," download the facilitation‑ready OEC Problem Solving Essentials Toolkit here for the complete suite of structured slides, case-based examples, and group activities to guide your team through the PDCA rhythm.



About the Author


Allan Ung, Founder & Principal Consultant, Operational Excellence Consulting (Singapore)

Allan Ung is the Founder and Principal Consultant at Operational Excellence Consulting (Singapore). A Certified Lean Six Sigma Black Belt and Certified Management Consultant, Allan has led transformation initiatives at Microsoft, IBM, and Underwriters Laboratories (UL). His facilitation‑ready training toolkits and courses are used worldwide to help leaders and teams embed Lean practices, solve problems systematically, and deliver sustainable customer value. Learn more and explore the full catalog at www.oeconsulting.com.sg



Further Learning Resources


The TQM foundation


Problem solving and corrective action

This article is part of the OEC Implementation Insights series — practical guides linked to facilitation‑ready training presentations.

bottom of page