Operations Process model

PDCA Cycle

Introduces changes through a repeatable Plan, Do, Check, Act cycle to develop a workable standard.

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.

Core question

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

Plan PDCA Cycle Method guide

Start comparison

Give feedbackIs this method useful to you?

Participants: 1-8
Time: 30–90 minutes for planning and review; Do runs as a bounded test over the required operating period.

The steps form one complete method run.

Plan
Test plan
Define problem, aim, theory, prediction, measures, test scope, and guardrails.
Do
Executed test
Run the change in the bounded area; record observations, deviations, and unexpected effects.
Check
Expected-versus-observed finding
Compare result with prediction and baseline; assess variation, side effects, and learning.
Act
Act decision
Standardise, adapt, or abandon the learning; set owners, review, and next cycle.

Add new evidence at review and version decisions with the prior state.

A good fit when

Bei einer Verbesserung, die erst im Alltag beweisen muss, was sie kann, führt die Methode in kleinen Lernschleifen vor. Sie verbindet Planung, Prüfung und Standardisierung zu einem wiederholbaren Lernmodus.

Ideal for

Continuous improvement
Process optimization
Small experiments

Not good for

Acute incidents
One-time strategy decisions
Unclear metrics

Outputs

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

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

First step

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

Open the method guide

Where to go next?

Operations

Standard Work Analysis

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

Operations

Kaizen Event

Bundles the next improvement cycle into a focused workshop.

Deep dive

Purpose

For an improvement that still has to prove itself in everyday work, the method runs it through small learning loops. It connects planning, checking, and standardization into a repeatable learning mode.

How it works

A change is deliberately kept small so that effect and side effect stay clearly readable. Observation then decides whether the adjustment is adopted or changed further. The cycle turns learning into a regular operating pattern rather than an exceptional action.

In detail

PDCA turns problem solving into a learning cycle instead of a one-time action. In Plan, the problem is understood and a hypothesis is formed; in Do, the change is tested in a limited way. Check compares result and expectation, and Act decides on adjustment, standardization, or the next cycle. That keeps improvement empirical and easy to continue.

Facilitation

Define measurable expectations and a small safe scope before the test. Keep learning points visible and make sure Act is not skipped. Good moderation keeps the cycle closed instead of turning it into a simple task list.

The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.

Open method guide

Your perspective

Does this method help with your work?

Your feedback helps shape the next improvements to methodatlas.

Sources and topics

Topics

Continuous improvement Lean Experiments

Sources

PDCA Cycleasq.orgASQ (American Society for Quality) resource page; describes the four Plan, Do, Check, Act phases of the PDCA cycle.

In playbooks

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

Artifact templates

PDCA Cycle: WorksheetSet subject, evidence, roles, flow, and review.

markdown

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

Alternatives and neighbors

Fitting alternatives with decision guidance, followed by other related methods.

All methods

Operations

DMAIC

Instead of PDCA Cycle, choose DMAIC when you want to steer improvement in a measurable, data-based, and fixed analysis sequence.

Operations

8D Problem Solving

Instead of PDCA Cycle, choose 8D Problem Solving when you want to work through a problem in a disciplined way with clear roles, actions, and verification.