The PDCA Cycle – The Scientific Heart of Continuous Improvement
- Chris Merriman

- Dec 2
- 2 min read
If problem-solving sits at the centre of Lean Thinking, then the PDCA (Plan, Do, Check, Act) cycle is the engine that drives it. Also known as the Shewhart or Deming Cycle, PDCA provides a simple but powerful structure for learning and improvement.
The cycle works like this:
Plan: Identify an opportunity and develop a clear plan, including success measures
Do: Test the change on a small scale and gather data
Check: Analyse results to understand whether the change delivered the expected outcome
Act: Standardise if successful. If not, reflect, adapt and prepare the next experiment
Why PDCA Still Matters
PDCA has been around for decades, yet its value is still underestimated. Leaders often jump straight to tools — fishbone diagrams, 5-whys, process maps — and overlook the core scientific thinking that sits behind them.
Most organisations are comfortable with Plan and Do. Where discipline often slips is in Check and Act. We assume that because something has been implemented, it must be working. In reality, without learning loops and data-driven reflection, improvements rarely stick.
Every Improvement Is an Experiment
At Manufacturers Network, we treat every change as a hypothesis. We form a theory, design a test, and learn from the results. Even when confidence is high, no improvement is guaranteed. Real environments are messy. People, processes and conditions vary. Unintended consequences often surface.
Testing first on a small scale allows teams to explore how reality matches the prediction, exactly like a science experiment in school. The goal isn’t to prove the theory right; it’s to understand what is true.
This mindset shifts improvement from “implementation” to “learning.”
Predict, Measure, Learn
To fully apply PDCA, the Planning phase must include:
A clear prediction
Defined measures
A plan for gathering data
Then, in the Check phase, we compare expected and actual results objectively.
If the improvement achieved what we predicted, the theory holds up. We can move to standardise, embed and extend the change.
If not, if results fall short, are inconsistent, or create new issues, we haven’t failed. We’ve learned something we didn’t previously know. That learning becomes the foundation for the next cycle. This is the iterative nature of improvement: the faster we cycle, the faster we learn.
A Common Language for Improvement
At Manufacturers Network, PDCA is built into our mindset, our programmes and our tools. We encourage scientific thinking at every level, from boardroom strategy to frontline problem-solving.
This approach provides:
A structured method for problem-solving
A rhythm for regular, incremental improvement
A shared language across functions and teams
Greater engagement through evidence-based decision-making
PDCA is not a tool; it is a discipline. When applied consistently, it builds capability, strengthens operational performance and creates a culture where learning becomes the norm.
%20LJLandscape%20(1).png)



Comments