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

All 108 frameworks
7.9IntermediateModule 07 · Operate with Precision

Kaizen Continuous

Improvement

The prompt

Copy & paste ready
7.9Kaizen Continuous
Act as a Kaizen facilitator. My business / team : [DESCRIBE YOUR OPERATION AND TEAM SIZE] Area to improve : [SPECIFIC PROCESS, FUNCTION, OR BEHAVIOUR] Current state : [HOW THIS AREA WORKS TODAY - SPECIFICALLY] Run a Kaizen session on this area: OBSERVE : What waste exists in this process? (Waste = time, effort, rework, waiting, errors) ANALYSE : What is the root cause of the biggest waste? Use the 5 Whys ask why 5 times. IMPROVE : What is the smallest change that would meaningfully reduce this waste? Define the change in one sentence. MEASURE : How will we know the improvement worked? Name the metric and the target. SUSTAIN : How do we make this improvement permanent? What system or habit locks it in? Achieving Continuous Improvement 1 2 Weekly Kaizen 3 4 Celebrate Wins Review Implement Kaizen Focus on Process Reward Log Discuss small improvements to Identify system improvements made foster culture Record failures, not human improvement suggestions daily
LabelsReplace theseSwap the role below

LabelsReplace theseSwap the role below

Pro tip, from the book

Kaizen's power is not in the size of any single improvement it is in the compound effect and the culture it creates. A team that makes one small improvement per week makes 50 per year. After three years, the cumulative effect of 150 deliberate improvements makes the business unrecognisable from where it started. The math is simple. The discipline is the hard part.

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

Small improvements, everyday, forever. The philosophy that built Toyota.

Where the framework comes from

Toyota Production System, Japan, 1950s · Masaaki Imai, Kaizen, 1986

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.9 of 108
Printed onPages 176177
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