What is the PDSA cycle?

    Short answer

    The PDSA cycle is a repeating four-step loop for testing a change: Plan it with a prediction, Do it on a small scale, Study the results against the prediction, then Act by adopting, adapting or abandoning the change. Teams run several short cycles, each one building on what the last taught them.

    Last updated · TeamAssurance

    Key facts

    • Four steps: Plan, Do, Study, Act, repeated as a loop rather than run once.
    • Core idea: write a prediction first, then learn from the gap between prediction and result.
    • Output: a decision to adopt, adapt or abandon the change, with the learning recorded.

    What happens at each step of the PDSA cycle?

    1. Plan. Name the problem, the change you will test and the measure that will show whether it worked. Write a prediction, for example "scrap on this line will fall from 6% to 4% this week". Decide who does what and when.
    2. Do. Run the test as planned, on a small scale. Note what actually happens, including surprises.
    3. Study. Compare the data with your prediction. Ask what you learned, what surprised you and whether the change or something else caused the result.
    4. Act. Choose one of three options: adopt the change and standardise it, adapt it and start a new cycle, or abandon it and try something else.

    How do you chain PDSA cycles?

    The cycle is meant to be repeated. A common pattern is to start tiny and widen the test as confidence grows:

    CycleScaleQuestion it answers
    1One operator, one shiftDoes the idea work at all?
    2One line, one weekDoes it work with normal variation?
    3Whole area, one monthDoes it hold up at full scale?

    Each Act step feeds the next Plan step, so the learning carries forward instead of being lost between trials.

    What goes on a PDSA worksheet?

    One page is enough: the objective, the change, the prediction, the measure and baseline, the owner and dates, what was observed, what was learned and the decision taken.

    Example: a packing line changeover

    A food plant wanted shorter changeovers on a packing line. Cycle 1 had one team try a pre-staged tool trolley, predicting a cut of 10 minutes. The study showed 6 minutes saved, because labels were still fetched from a store. The team adapted the plan to stage labels too. Cycle 2 ran for a week across both shifts and met the target, so the team adopted the new method and wrote it into standard work.

    For the definition of PDSA and how it compares with PDCA, see What is PDSA? and What is PDCA?.

    How TeamAssurance helps

    TeamAssurance's Kaizen Ideas method takes an improvement through planning the change, trying it, measuring the result and standardising it. Each idea has an owner, a due date and tracked progress, so every cycle is visible. Improvements are reviewed through tiered daily management and can be linked to strategic goals.

    Frequently asked questions

    How long should one PDSA cycle take?

    As short as lets you learn something, often days or a few weeks. Short cycles give faster feedback and keep the risk of a failed test low.

    Why write a prediction in the Plan step?

    A prediction makes the Study step honest. Comparing the result with what you expected shows what you actually learned, rather than just whether the number moved.

    When does the PDSA cycle end?

    When the change is adopted and written into standard work, or when you drop the idea. After adoption, keep monitoring it, and start a new cycle when the next improvement is identified.