Page 171 · Module 07, Operate with Precision · this screen continues that page

All 108 frameworks
7.6BeginnerModule 07 · Operate with Precision

PDCA Cycle

Turn every experiment into a learning that compounds

The prompt

Copy & paste ready
7.6PDCA Cycle
Act as a continuous improvement facilitator using the PDCA cycle. Problem or opportunity : [WHAT YOU WANT TO IMPROVE] Current baseline : [THE METRIC OR SITUATION AS IT IS NOW] Hypothesis : [WHAT YOU THINK WILL IMPROVE IT AND WHY] Guide me through a full PDCA cycle: PLAN : Define the problem precisely. State the hypothesis : If [ACTION] then [RESULT] because [REASON]. Define success criteria. Design the smallest useful experiment. DO : What exactly should be done, by whom, by when? What data needs to be collected during the test? CHECK : How will we compare results to the hypothesis? What would confirm it? What would disprove it? ACT : If confirmed - how to standardise and scale? If disproved - what does this tell us for the next PDCA cycle? PDCA Cycle for Learning Plan Act Define problem and form Standardize and improve hypothesis Check Do Analyze results Run experiment at small scale
LabelsReplace theseSwap the role below

LabelsReplace theseSwap the role below

Pro tip, from the book

The Check step is where most PDCA cycles fail. Teams see a positive result and immediately scale without asking whether the result matched the hypothesis. A result can be positive but the hypothesis still wrong meaning you got lucky, not right. Always check against the hypothesis, not just the outcome number.

Who should run this prompt

Module role profile

Who should audit and improve your operations? Operations problems hide in plain sight — in the handoffs nobody notices, the processes nobody has documented, and the decisions nobody has questioned. The roles on this page bring the discipline of people who have built systems that run without heroics. Use them to find what is broken before it breaks you, and to build what scales before you need it to.

Choose any role to drop it into the prompt above. Only the highlighted opening clause changes — the rest of the prompt stays exactly as printed.

Internal rolesThink from inside the organisation
Outside perspectivesChallenge your blind spots

◆◆◆◆◆ → ◆ seniority, board level down to specialist outside the organisation

How to make any role sharper

  1. Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
  2. Add what they care most about: "You care most about [X]" shapes every word of the output.
  3. Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
See also: 1.3 Role Prompting - The Expert Chair

Use this when

The problem it solves

Your team tries things, some work and some don't, but the learning doesn't carry forward. The same mistakes reappear. Successful experiments don't get systematised. You're improving through trial and error instead of through a repeatable process.

How the framework works

From the printed page

The PDCA (Plan-Do-Check-Act) cycle was developed by W. Edwards Deming in the 1950s and became the foundation of continuous improvement philosophy in Japan and beyond. Plan (define the problem, form a hypothesis, design the experiment), Do (run the experiment on a small scale), Check (analyse the results against the hypothesis), Act (standardise what worked, abandon what didn't, run the next cycle). The cycle is designed to be continuous every Act step feeds the next Plan. When PDCA is embedded in a team's operating rhythm, the team improves structurally, not randomly.

The method, in four moves

Do these in order
1

Run PDCA on one small improvement per week — short cycles beat large infrequent ones.

2

Write the hypothesis before starting 'if we do X, we expect Y because Z.'

3

In the Check step, compare results to the hypothesis, not just whether results were good.

4

The Act step must result in either a new SOP or a killed idea, no undecided outcomes. "We'll decide later" is the failure mode PDCA is built to kill. An Act step that ends in maybe isn't an Act step, it's an unfinished cycle, and the learning it should have produced never gets locked in

Where the framework comes from

W. Edwards Deming — PDCA / Shewhart Cycle, adapted from Walter Shewhart, 1950s

When this page changes, your copy of the book does not have to.

The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.

If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.

Framework7.6 of 108
Printed onPages 170171
Prompt extracted18 Sept 2026
Costs to readNothing, no account

Copying is free. An account keeps them.

Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.

See how it works
Save this framework to your own list
Pick up where you left off on another device
Send a colleague a link with your name on it