methodatlas
Method guideOperations

PDCA Cycle

A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.

ComplexityLow
Time1 h bis mehrere Wochen
Participants1-8
FormatWorkshop + async
MaturityCanonical
Plan PDCA Cycle
01

Prerequisite

What needs to be finished first

Complete firstClear boundary

Set one concrete improvement opportunity and a small reversible test boundary; capture baseline and guardrails.

Without a boundary, cases, periods, or variables become mixed.
Complete firstEvidence access

Problem and target state, prediction, test plan, measurements, deviation log, and standard/next-cycle decision

Missing sources remain visible as uncertainty.
02

Preparation

What needs to be ready before start

Materials

Problem and target state, prediction, test plan, measurements, deviation log, and standard/next-cycle decision

People / roles

Improvement owner · process participants · data owner · decision owner for standardisation

Pre-read

Set one concrete improvement opportunity and a small reversible test boundary; capture baseline and guardrails.

Time needed

30–90 minutes for planning and review; Do runs as a bounded test over the required operating period.

Setup

Prepare a workspace with Plan · Do · Check · Act; separate example from live data.

03

Core question

The one question this method answers

Which small change will we test, what do we predict, what occurred, and how will learning enter the next cycle?

04

Flow

Phases with goal, actions, output and pitfall

Eine Änderung wird bewusst klein gehalten, damit Wirkung und Nebenwirkung klar lesbar bleiben. Anschließend entscheidet die Beobachtung, ob die Anpassung übernommen oder weiter verändert wird. Der Zyklus macht Lernen zu einem regulären Betriebsmuster und nicht zu einer Ausnahmeaktion.

PDCA Cycle · working structure

Fictional example

Fictional values show the actual method fields.

Test plan

Define problem, aim, theory, prediction, measures, test scope, and guardrails.

If slots fall to eight/hour, p80 wait drops below 15 minutes on two Saturdays; stop above 10% rejection.

Executed test

Run the change in the bounded area; record observations, deviations, and unexpected effects.

Cap on 9 and 16 Nov; Support counts rejections, Warehouse measures wait; outage on day two marked.

Expected-versus-observed finding

Compare result with prediction and baseline; assess variation, side effects, and learning.

p80 is 12 vs 18 minutes; rejection 7%; warehouse calls unchanged. Prediction met, residual issue open.

Act decision

Standardise, adapt, or abandon the learning; set owners, review, and next cycle.

Provisionally standardise slot cap; Lea owns; review in four weeks. Next cycle tests inventory sync.

All values are fictional.

Reference · original teaching example

  1. 1

    Plan

    Test plan

    Goal

    Test plan: Define problem, aim, theory, prediction, measures, test scope, and guardrails.

    Inputs for this step

    • Set one concrete improvement opportunity and a small reversible test boundary; capture baseline and guardrails.
    • Problem and target state, prediction, test plan, measurements, deviation log, and standard/next-cycle decision

    Actions

    • Define problem, aim, theory, prediction, measures, test scope, and guardrails.

    Output

    Test plan

    Define problem, aim, theory, prediction, measures, test scope, and guardrails.

    Quality check

    Does the plan contain an observable prediction and a bounded test?

    Pitfall

    The plan only says improve waiting time and has no prediction. Specify change, expected signal, test scope, and stop rule.

    Timing: 20–35 minutes

  2. 2

    Do

    Executed test

    Goal

    Executed test: Run the change in the bounded area; record observations, deviations, and unexpected effects.

    Inputs for this step

    • Test plan

    Actions

    • Run the change in the bounded area; record observations, deviations, and unexpected effects.

    Output

    Executed test

    Run the change in the bounded area; record observations, deviations, and unexpected effects.

    Quality check

    Was the plan followed and every deviation recorded promptly?

    Pitfall

    Additional changes are silently added during the test. Stop extra changes or record them with time and effect.

    Timing: One or more operating cycles

  3. 3

    Check

    Expected-versus-observed finding

    Goal

    Expected-versus-observed finding: Compare result with prediction and baseline; assess variation, side effects, and learning.

    Inputs for this step

    • Executed test

    Actions

    • Compare result with prediction and baseline; assess variation, side effects, and learning.

    Output

    Expected-versus-observed finding

    Compare result with prediction and baseline; assess variation, side effects, and learning.

    Quality check

    Are prediction, result, uncertainty, and guardrails assessed together?

    Pitfall

    Only the desired metric is examined. Check all guardrails and side effects and explain departures from the theory.

    Timing: 20–30 minutes

  4. 4

    Act

    Act decision

    Goal

    Act decision: Standardise, adapt, or abandon the learning; set owners, review, and next cycle.

    Inputs for this step

    • Expected-versus-observed finding

    Actions

    • Standardise, adapt, or abandon the learning; set owners, review, and next cycle.

    Output

    Act decision

    Standardise, adapt, or abandon the learning; set owners, review, and next cycle.

    Quality check

    Is it clear what becomes standard and which open question starts the next plan?

    Pitfall

    Success causes immediate broad rollout without further control. Document validity range, standard, monitoring, and next learning question.

    Timing: 15–25 minutes

05

Artifact

What comes out at the end

Sketch: what the artifact looks like

PDCA · Deming-KreisVerbesserungen als kleinen Lernzyklus planen, testen, prüfen und in Standards oder den nächsten Zyklus überführen
PDCA CycleDas Visual zeigt Plan, Do, Check und Act als geschlossenen Lernzyklus mit Messwert, Standardisierung und nächstem Verbesserungszyklus.Verbesserungen als geschlossenen Lernzyklus führenPDCA macht aus Veränderung ein Experiment: Erwartung formulieren, begrenzt testen, messen und daraus Standard oder nächste Schleife ableiten.LernenHypothese prüfenkleiner Test statt großer WurfSoll-Ist-VergleichStandardisierenPlanProblem, Ziel, Hypothese undMessgröße klärenDoÄnderung klein und kontrollierttestenCheckErgebnis mit ErwartungvergleichenActstandardisieren, anpassen oderneu planenMesswertvorher definierte EvidenzStandardneue Arbeitsweise verankern
Form

PDCA cycle record with plan, prediction, test execution, expected-versus-observed review, and Act decision.

Versioning / ownership

Record date, owner, source state, and review date; preserve prior versions.

Tool alternatives
  • PDCA cycle sheet
  • Measurement and deviation log
  • Standard or next-cycle plan

pdca-cycle-working-template.md

Set subject, evidence, roles, flow, and review.

PDCA Cycle: Worksheet

Question

To be confirmed

Desired outcome

To be confirmed

Scope

Complete run Time: 30–90 minutes for planning and review; Do runs as a bounded test over the required operating period.

Complete this worksheet on paper or in your own document during the work.

Preparation for this scope

Method setup

  • Materials: Problem and target state, prediction, test plan, measurements, deviation log, and standard/next-cycle decision
  • Roles: Improvement owner · process participants · data owner · decision owner for standardisation
  • Advance information: Set one concrete improvement opportunity and a small reversible test boundary; capture baseline and guardrails.
  • Overall time needed: 30–90 minutes for planning and review; Do runs as a bounded test over the required operating period.
  • Setup: Prepare a workspace with Plan · Do · Check · Act; separate example from live data.

Prepare for the work steps

Plan: Test plan

  • Set one concrete improvement opportunity and a small reversible test boundary; capture baseline and guardrails.
  • Problem and target state, prediction, test plan, measurements, deviation log, and standard/next-cycle decision

Do: Executed test

  • Test plan

Check: Expected-versus-observed finding

  • Executed test

Act: Act decision

  • Expected-versus-observed finding

PDCA Cycle · working structure

Test plan

Define problem, aim, theory, prediction, measures, test scope, and guardrails.

...

Executed test

Run the change in the bounded area; record observations, deviations, and unexpected effects.

...

Expected-versus-observed finding

Compare result with prediction and baseline; assess variation, side effects, and learning.

...

Act decision

Standardise, adapt, or abandon the learning; set owners, review, and next cycle.

...

The blank worksheet contains prompts only.

Reference · original teaching example

Plan: Test plan

Expected artifact: Test plan

Define problem, aim, theory, prediction, measures, test scope, and guardrails.

Entry:

...

  • Does the plan contain an observable prediction and a bounded test?

Do: Executed test

Expected artifact: Executed test

Run the change in the bounded area; record observations, deviations, and unexpected effects.

Entry:

...

  • Was the plan followed and every deviation recorded promptly?

Check: Expected-versus-observed finding

Expected artifact: Expected-versus-observed finding

Compare result with prediction and baseline; assess variation, side effects, and learning.

Entry:

...

  • Are prediction, result, uncertainty, and guardrails assessed together?

Act: Act decision

Expected artifact: Act decision

Standardise, adapt, or abandon the learning; set owners, review, and next cycle.

Entry:

...

  • Is it clear what becomes standard and which open question starts the next plan?

Open questions and next steps

...

Method guide: https://methodatlas.meierhoff-systems.de/en/methods/pdca-cycle/run-sheet

06

Example output

Concrete filled scenario, fictional example

Fictional example for orientation. Counts and timings describe this case and are not universal requirements.

pdca-cycle-beispiel.md

Concrete filled scenario, fictional example

Fictional teaching example: PDCA Cycle · working structure

Test plan

If slots fall to eight/hour, p80 wait drops below 15 minutes on two Saturdays; stop above 10% rejection.

Executed test

Cap on 9 and 16 Nov; Support counts rejections, Warehouse measures wait; outage on day two marked.

Expected-versus-observed finding

p80 is 12 vs 18 minutes; rejection 7%; warehouse calls unchanged. Prediction met, residual issue open.

Act decision

Provisionally standardise slot cap; Lea owns; review in four weeks. Next cycle tests inventory sync.

07

Pitfalls

Recognize symptoms and steer against them

Quick overview, the full text is in the matching phase in the flow

  1. Test planThe plan only says improve waiting time and has no prediction.View in phase
  2. Executed testAdditional changes are silently added during the test.View in phase
  3. Expected-versus-observed findingOnly the desired metric is examined.View in phase
  4. Act decisionSuccess causes immediate broad rollout without further control.View in phase
08

Stop criteria

When to pause, resolve prerequisites, or choose another approach

Stop Plan: Does the plan contain an observable prediction and a bounded test?
Stop Do: Was the plan followed and every deviation recorded promptly?
Stop Check: Are prediction, result, uncertainty, and guardrails assessed together?
Stop Act: Is it clear what becomes standard and which open question starts the next plan?

Method after Walter A. Shewhart and W. Edwards Deming. Curated with 1 sources.

Sources: PDCA Cycle

Flow, timeboxes, and pitfalls are editorially curated practice recommendations based on the listed sources.

Where to go next?

Paper illustration for Standard Work Analysis.
Operations
Standard Work Analysis

Anchors the confirmed result as a new, documented work standard.

Paper illustration for Kaizen Event.
Operations
Kaizen Event

Bundles the next improvement cycle into a focused workshop.

View in playbookTurn Retrospective into ImprovementMove from team feeling to prioritized learning points, experiments, and verifiable change.

Finished the method guide?

Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.

Go to profileMore methods