PDSA vs PDCA: Why the Plan Do Study Act Cycle Leads to Better Results
A practical guide to improving quality, reducing rework, and strengthening customer trust.
In The Hitchhiker’s Guide to the Galaxy, Zaphod Beeblebrox relied on his Joo Janta 200 Super-Chromatic Peril Sensitive Sunglasses. At the first sign of danger, they turned black and prevented him from seeing anything alarming. It is an amusing illustration of avoidance, but hardly a reliable strategy for running a laboratory or a business. Closing our eyes to problems does not make them disappear. In quality management, the opposite is true. The more clearly and honestly we see issues, the better equipped we are to improve.
In my previous article, “42 Reasons Why Quality Matters,” I explored how strong systems, customer satisfaction, employee morale, and leadership shape organisational success. This follow-up article goes deeper into one of the most powerful tools for continuous improvement. It explains why the Plan-Do-Study-Act (PDSA) cycle remains the heartbeat of quality, and why understanding it properly is essential for reducing errors, improving processes, and creating lasting results.
Why PDSA, Not PDCA? A Subtle Change with a Major Impact
Many people were first introduced to this cycle as Plan-Do-Check-Act. The idea is similar, but the mindset is very different. W. Edwards Deming, one of the most influential thinkers in quality, shifted from “Check” to “Study” for a reason.
“Check” suggests a quick comparison. It implies a binary question, such as “Did we meet the target?” This often encourages a compliance mindset rather than an inquiry mindset. It can tempt teams to tick boxes, gather superficial data, or explain away results without learning from them.
“Study,” on the other hand, encourages curiosity. It requires us to ask “What happened, and why did it happen?” It involves analysing data, considering variation, examining behaviour, and interpreting results with context. This deeper reflection leads to genuine insights and better decisions. It turns the cycle into a learning loop instead of an inspection loop.
PDSA is not about passing or failing. It is about understanding.
Plan: Creating Clarity Before Action
The planning stage sets the foundation for success. It begins with a clear problem or improvement opportunity. Good planning requires accurate data, thoughtful observations, and honest conversations. It also requires defining the outcome we want to achieve. “Improve customer experience” is too vague. “Reduce sample turnaround time from seven days to five over the next quarter” is specific and measurable.
Plan also includes:
- Root cause analysis
- Success criteria
- Defining the test or pilot size
- Responsibilities and timelines
- Identifying risks and constraints
Strong planning ensures that the improvement is purposeful rather than random. It reduces reliance on guesswork and increases the likelihood of meaningful results.
Do: Testing in a Controlled, Measured Way
The “Do” stage often reveals why implementation is both essential and challenging. This phase is not about rolling out full-scale change. It is about conducting a small, controlled test.
This approach:
- Minimises disruption
- Allows real-world observation
- Creates space for honest feedback
- Reduces the risk of unintended consequences
Documenting what actually happens during this stage, including deviations from the plan, is crucial. These notes become invaluable during the study phase.
Study: Turning Information into Insight
This is the most important stage of the cycle. It is where PDSA truly separates itself from PDCA.
Study requires deliberate analysis. Teams look at the data, the observations, the feedback, the customer responses, and the operational impact. They focus on understanding, not just measuring.
They ask:
- Did the change achieve the intended result?
- What did we learn?
- What surprised us?
- What do customers or stakeholders say?
- What conditions influenced the outcome?
This reflective process prevents knee-jerk reactions. It builds organisational intelligence. It also strengthens cross-functional collaboration because people share insights rather than just conclusions.
As the Guide famously reminds us, “Don’t Panic.” The Study phase encapsulates that calm logic. It helps teams avoid rushing into permanent changes before they truly understand what happened.
Act: Embedding or Adjusting Based on Evidence
The final stage is where decisions are made. Act means:
- Adopt the change if it worked
- Adapt the change if it partially worked
- Abandon the idea and return to the beginning if the results were not favourable
The key is that no outcome is wasted. Even unsuccessful tests create learning. Improvement becomes iterative and ongoing. Over time, these small, thoughtful cycles become habits that shape culture.
How PDSA Reduces Rework, Errors, and Disputes
PDSA is not simply a tool for improvement. It is a tool for prevention. Testing ideas on a small scale reduces the likelihood of large-scale failure. Studying results carefully uncovers root causes before they cascade into errors that require rework.
This cycle reduces:
- Process breakdowns
- Miscommunication
- Inconsistency
- Customer complaints
- Disputes over results
- Staff frustration
Instead of reacting to problems, teams anticipate them. Instead of firefighting, they analyse. Instead of applying quick fixes, they build long-term solutions.
This leads to fewer disruptions, smoother operations, and stronger customer relationships.
What Makes PDSA Succeed? Six Critical Success Factors
Although the cycle is simple, its success depends on deeper organisational behaviours.
- Leadership Support
Leaders must model openness, patience, and curiosity. They need to support thoughtful planning and refuse to rush to full implementation before proper study.
- Psychological Safety
Teams must feel safe to speak up, report issues, and share unexpected results. Without safety, the study phase collapses.
- Good Data
Intuition is useful, but it’s not really where the main game is at. It’s evidence that is essential. Reliable data ensures that decisions rest on facts, not assumptions.
- Cross-Functional Collaboration
The best learning comes from diverse perspectives. When technical staff, quality leaders, managers, and customer-facing roles collaborate, insights deepen.
- Documentation
Recording what was done and what was learnt prevents organisational amnesia. It also strengthens audits, training, and future improvement work.
- Iteration
One cycle rarely solves a problem. PDSA is a rhythm. It builds excellence gradually, deliberately, and repeatedly.
A Final Thought
Quality is not about perfection. It is about learning faster and performing better. The PDSA cycle is the structured approach that enables this. Like a trusted towel in The Hitchhiker’s Guide, it prepares organisations for whatever challenges arise. It helps teams remain steady, curious, and confident.
At MAS Management Systems, we help laboratories make quality practical, purposeful, and profitable. If you want support in applying PDSA effectively or strengthening your quality culture, contact us. We help organisations ask better questions, design better processes, and achieve better outcomes.
PEOPLE WHO READ THIS ARTICLE ALSO ENJOYED:
