Page 163 · Module 07, Operate with Precision · this screen continues that page
All 108 frameworksThe prompt
Copy & paste readyLabelsReplace theseSwap the role below
Pro tip, from the book
Shared accountability between lanes is the number one predictor of process failure. When two roles both touch a step, both assume the other is checking it. The fix is always the same: assign one person as Accountable (using RACI) and make the handoff explicit with a defined output format and a confirmation step.
Who should run this prompt
Module role profileWho 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.
◆◆◆◆◆ → ◆ seniority, board level down to specialist◈ outside the organisation
How to make any role sharper
- Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
- Add what they care most about: "You care most about [X]" shapes every word of the output.
- Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
Use this when
The problem it solvesWork keeps falling through the cracks at the same points. Two people think someone else owns the handoff. Processes that should be smooth have invisible gaps that only become visible when something goes wrong.
How the framework works
From the printed pageA Swimlane diagram maps a process across multiple roles or departments, with each role occupying its own horizontal lane. Every action in the process is placed in the lane of the person responsible. Handoffs where work moves from one lane to another, become immediately visible. The diagram reveals where delays, duplications, and accountability gaps cluster. For complex multi-team processes, it is the clearest way to see the whole picture at once. AI can generate swimlane descriptions and identify the highest-risk handoffs when given process context.
The method, in 3 moves
Do these in orderMap each role involved in the process as a separate lane. 2. Mark every handoff explicitly, the arrows between lanes are where most failures happen.
Look for lanes with the most incoming arrows, that person is your bottleneck.
After mapping, identify the one handoff that fails most often and redesign it first. See exactly where handoffs break before they break again A swimlane diagram shows you where the handoff breaks, not why. If a lane has too many incoming arrows, the fix is rarely "work harder", it's usually a workload or ownership problem the diagram alone won't solve.
Where the framework comes from
Process improvement methodology — swimlane diagrams formalised 1940s onwards
Pairs well with
As printed with this frameworkModule 07 — Operate with Precision
Build systems that run without you and improve without being told.
12 frameworks, printed on pages 160–183.
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.
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.