Back to BlogLean Management

    PDCA Cycle: Plan-Do-Check-Adjust (Plan-Do-Check-Act) for Continuous Improvement

    By , CEO and founder, TeamAssurancePublished Last updated

    PDCA Cycle: Plan-Do-Check-Adjust (Plan-Do-Check-Act) for Continuous Improvement

    PDCA stands for plan-do-check-act, also written plan-do-check-adjust. It is a four-step improvement cycle. In the plan step you set a target and predict the result of a change; in the do step you try it on a small scale. You then check the result against the prediction and act: standardise what worked, or adjust and start the next cycle.

    At a glance

    • Steps: plan, do, check, act (or adjust), repeated as a cycle.
    • Variant: PDSA replaces Check with Study to stress learning from the result.
    • Basis: a scientific approach of prediction, small experiments and checking the outcome.
    • Related: what is PDCA? and the A3 report, which is PDCA on one page.

    Here's your definitive guide to the PDCA cycle (plan-do-check-adjust, or plan-do-check-act) – one of the pillars of Lean, continuous improvement and operational excellence.

    The plan do check adjust cycle, also called plan do check act, is the engine room of continuous improvement. It is the most widely known and used improvement cycle. This simple, yet highly effective, methodology is at the heart of every improvement or learning opportunity in a Lean thinking organisation. However, it may also be the least well understood in practice.

    In my experience many organisations follow a 'PDCA lite' version which is really just Plan and Do or simply just Do, Do, Do, Do. They take a shotgun approach to improvement; simply hoping for the best. All too often we waste time, effort and scarce resources on improvement efforts. Our activity is based on hunches and assumptions that are not well conceived, executed or tracked.

    Why treat PDCA as a scientific approach?

    The PDCA methodology is based on the scientific approach of prediction, developing a hypothesis, conducting experiments, observing and checking the outcome, applying critical thinking and attempting to learn from the outcome.

    The scientific approach has resonated through the ages. This method has driven countless breakthroughs and innovation through time simply by designing and executing experiments. It's the approach used by Francis Bacon, Galileo Galilei, Thomas Edison to name a few. As human beings we naturally think and behave this way – particularly as children.

    We experiment with the world around us to learn, to grow, and to develop our knowledge through continual trial and error. Consider how we learn to walk, talk and engage with the wide world around us. This continues for us throughout life as we learn and adapt to our situation and current circumstances. We evolve and grow toward our objectives both professional and personal.

    These days the method is visualised as a circle with the four quadrants of the PDCA process. The circular motion is an indication of the sequence of the method. Plus it's a reminder of the perpetual nature of continuous process improvement.

    The first to show it as such was Walter Shewhart, also known as 'the father of statistical quality control'. However, Shewhart originally had only three steps – Specification, Production, Inspection – known as the Shewhart cycle.

    A quality engineer named W. Edwards Deming edited Shewhart's book in 1930. Using these learnings, Deming adopted and evolved Shewhart's model. Eventually, Deming became famous in Japan for teaching the Japanese quality control tools and techniques. Deming taught that we should think about change and improvement like a scientific experiment as a way of testing, and developing your understanding of the process. The result of Deming's work significantly improved product quality in Japan and resulted in the evolution of Plan, Do, Check, Adjust (also known as the Deming cycle or Deming wheel) as we know it today.

    PDCA can apply to the macro as much as it does the micro. This allows the tool to be used for hoshin kanri (policy deployment) at a strategic level, to be used as value stream implementation, to support organisational change processes, to facilitate training or the smallest process changes and improvements.

    Ultimately through practice, repetition, structure and discipline, PDCA becomes habitual. We end up with a way of thinking woven into the DNA of an organisation, its environment, and its people.

    What happens in each step of plan-do-check-adjust (PDCA)?

    PDCA is a loop: each Adjust leads into the next Plan.

    Plan

    Plan is firstly about establishing and understanding our current state – where we are right now.

    Before we set off planning the next step it is critical we know the terrain we find ourselves in to begin our journey. We must grasp the current condition of our process and establish the objective or target.

    Identifying the problem properly is the part most teams rush. Write the problem as a gap between what should happen and what is happening, with a number and a place: "orders wait an average of 40 minutes at the dispatch dock against a standard of 15" is a problem; "dispatch is slow" is a complaint. Go and see the process, gather the facts and get to the likely cause before you choose a countermeasure. A well-defined problem is half the plan.

    Plan should be about breaking the objective down into manageable chunks. We must gain clarity of the potential obstacles and prioritise them. With this we formulate our hypothesis, in turn defining the next step. If we take this step we are predicting a particular or desired outcome. Plan should provide clarity on what we are going to do, how it will be done, and when we are going to do it.

    As part of a cyclical process Plan will also incorporate component parts of the Adjust phase of the previous cycle as we will have had key learnings and reflections to inform the new planning phase.

    Do

    Do is simply about executing the improvement plan. Do is about taking action – obvious, yes, but so often we find inertia in the planning phase. Do is where we test the hypothesis and run the process according to our plan.

    This is often done on a small scale or short cycle to ensure feedback and learning is rapid. As the philosopher Mike Tyson once said: "Everyone has a plan until they get punched in the mouth."

    In other words: you won't know the value of your plan until you test it in the field.

    Check

    The check phase is about observing, measuring, understanding, and receiving confirmation on how our plan has worked versus what we predicted.

    Without a check stage or metrics how will we know if the plan has been effective or not (and to what degree)? What will be checked? How will it be measured? When should we check? Who will check? What are the definitions of success or failure based on our plan?

    Checking should highlight not only the overall outcome but will capture the key process metrics by which the outcome was achieved.

    Adjust

    The adjust phase is where we stop to reflect and learn from what has happened in Plan, Do, Check. You will more often see this stage called the act phase, as in PDCA plan do check act. Adjust is perhaps a more logical fit since this component is really about learning and reflective practice, but the two names describe the same step.

    Reflect

    We reflect on:

    • What has worked well?
    • What has not?
    • What we have learned from our experience?
    • What have we learned from our checks, measures, feedback and observations?

    However, merely reflecting on the findings is insufficient. It is imperative for the team to take decisive action based on these insights.

    Take Action

    1. Adjust and reassess: Adjustments and reassessments are conducted when the outcomes of the implemented plan do not meet the expected results. This sub-stage focuses on identifying areas for improvement and refining the approach for better outcomes.

    2. Provide feedback: Feedback plays a pivotal role in the Adjust phase. This involves gathering input from various stakeholders, including employees, customers, and other relevant parties. By actively seeking feedback, organizations can make informed decisions and enhance their processes accordingly.

    3. Standardize processes: It is essential that corrective measures are deployed, and all procedures are standardized. This ensures that the improvements identified and implemented previously are integrated systematically. Standardization guarantees consistency in the execution of activities, ensuring operational stability and long-term success.

    It is rare that everything goes perfectly, according to our plan. The adjust phase provides time and space to ensure we capture, standardise and sustain our gains and learnings. It allows us to understand the gaps and opportunities for further innovation or improvement.

    What does a PDCA example look like?

    Here is how one turn of the cycle might look for the dock problem above. The numbers are illustrative.

    StepWhat the team does
    PlanTrucks wait 40 minutes on average to be loaded against a 15-minute standard. The team walks the dock and finds pallets are staged only after a truck arrives. Countermeasure: stage the next two loads before the booked arrival time. Prediction: average wait time falls below 20 minutes.
    DoTrial the change on the day shift for two weeks, with the dock lead recording every arrival and loading start.
    CheckCompare the recorded wait times with the prediction and with the night shift, which kept the old method. Look at the misses: which loads still waited, and why?
    Act (Adjust)If the wait times fell as predicted, write the staging step into the standard work for both shifts and keep measuring. If not, use what the check phase showed (late bookings, say) to plan the next cycle.

    Notice that the cycle does not end at Act. The new standard becomes the baseline for the next Plan, which is why the Deming wheel is drawn as a circle rather than a line.

    What rewards does PDCA bring?

    PDCA sounds simple in essence and can be easily glossed over, leading to poor application. But if executed well, and internalised by your teams, it is an absolute powerhouse. The meta cycle embeds intentional and deliberate practice toward improvement.

    Frequently asked questions about PDCA

    Is it plan-do-check-act or plan-do-check-adjust?

    Both are in use and both describe the same PDCA cycle. Plan-do-check-act is the older and more common wording. Plan-do-check-adjust is the wording many Lean practitioners prefer, because the last step is about adjusting the plan or the standard based on what the check showed, not just taking more action.

    What does plan-do-check-adjust mean?

    Plan-do-check-adjust means improving a process in small, repeated cycles. You plan a change and predict its result, do it as a small trial, check what happened against the prediction, then adjust: keep and standardise what worked, or change the plan and run the cycle again.

    What are the 4 steps of PDCA?

    Plan: define the problem, analyse the cause and plan a countermeasure with a predicted result. Do: implement it, usually on a small scale. Check: measure the result against the prediction. Adjust (or Act): standardise the change if it worked, otherwise learn from the gap and start the next cycle. See standard work for how a proven change is locked in.

    What happens in the plan and do steps of PDCA?

    Plan: define the problem as a gap with a number, find the likely cause and choose a countermeasure with a predicted result. Do: carry out that plan, usually as a small trial, and record what happens so the check step has real data to compare with the prediction.

    Is PDCA the same as the Deming cycle?

    Yes. The Deming cycle, Deming wheel and Shewhart cycle are all names for the same plan-do-check-act loop. Walter Shewhart first drew it and W. Edwards Deming popularised it, which is why both names stick.

    Where is PDCA used?

    PDCA is used wherever a process needs to improve in a controlled way: daily management huddles, A3 problem solving, quality systems, safety corrective actions and strategy deployment. The scale changes from a single shift to a full year, but the four steps stay the same.

    What is the difference between PDCA and PDSA?

    PDSA replaces Check with Study to stress that the point is learning from the result, not just inspecting it. Deming preferred PDSA for that reason; in practice the two cycles are used the same way.

    How is PDCA used in daily management?

    Every tier meeting is a small PDCA cycle: the plan is the target, the do is the shift, the check is the review of actual against target, and the adjust is the action assigned when there is a gap. Larger problems move into an A3, which is PDCA on one page.

    How does PDCA fit the wider continuous improvement framework?

    Standardised problem solving techniques, Standard Operating Procedures (SOPs), and Tiered Daily Management are just some of the adjacent Lean tools and processes that support the entire PDCA loop. To optimise our use of PDCA we must ensure alignment of all the people, processes and systems involved in the greater continuous improvement framework. No one element should be developed in isolation.

    The illustration below demonstrates how we designed the interconnected TeamAssurance platform to avoid locally optimised, disconnected 'Point Solutions' (digital or analog) that do not help, and may even hinder your progress when it comes to continuous improvement.

    If you're a business in need (or a consultant with clients in need) and you'd like to implement or enhance a PDCA approach, contact us for a demonstration of the TeamAssurance platform today.

    About the author

    Matt Mafrici

    CEO and founder, TeamAssurance

    Operations and continuous improvement practitioner; builds daily management systems with manufacturers, miners, food and pharmaceutical producers in Australia and abroad.

    LinkedIn profile · All articles