Can another builder run your playbook?
A playbook is ready to share when another builder can use it to make the right call without you in the room. Try a four-case exercise, then use the same handoff test on one of your own workflows.
Download the peer exerciseStart with the decision you keep making yourself
Imagine a founder handling four messages from print shops trying a proofing tool. Each needs a different next step. Writing “handle onboarding support” gives a teammate little to work with. A usable handoff gives them the product instructions, the one known issue, and enough evidence to decide what to do with a new message.
From today’s onboarding messages, return one decision for each case. Record the detail that decided it and the next action. When evidence is missing, ask one question before filing anything.
To capture your own procedure, dictate a first draft or type it. Name the input, the choice you made, the observation that settled it, and the point at which someone should stop. Use a fictional example when the real one belongs to a customer. A colleague needs your decision rule and a case they may reuse.
If you use Wispr Flow, review its cloud transcription and storage settings before choosing what to dictate. In Colabio, a manager can enable daily updates from the desktop app. Those updates reach the organization’s dashboard and team feed. Review your text and its audience before submitting. The practice packet below works in an ordinary text editor. Wispr Flow data controls · Colabio’s desktop update notes.
Hand a peer the packet and keep the key
- Give your peer the four-case Markdown packet. It contains the instructions, the known issue and four fictional messages. They can do the exercise offline.
- Ask them to work alone and fill in one row per message. Save that first pass before offering hints. Record both a matching decision and the observation used to reach it.
- Open the answer key together. Treat a correct guess and a reasoned result as different outcomes. If a different question would resolve the same missing detail, count it as a sound answer.
The exercise borrows two established support practices. Mozilla asks for steps, expected behavior and observed behavior. GitHub lets a team reference an existing issue when two reports describe the same problem. Mozilla’s bug-writing guide · GitHub’s duplicate issue guide.
What should happen to each message?
Reveal the four decisions and their evidence
- Maple
File a new issue - Both clean orders showed two preview pages and exported one. Record the saved version, the export steps, the expected two pages and the observed single page. Issue 17 covers a different action.
- Birch
Explain the workflow - The shop used Save draft, which keeps work inside the shop. Explain that Send proof invites the reviewer. Let the shop decide when its customer should receive the invitation.
- Elm
Request missing detail - “The link stopped working” leaves several explanations open. Ask what the reviewer saw when opening it, such as an error or an approval screen. A redacted description is enough to take the next step.
- Cedar
Link to existing issue 17 - Mobile approval, a stale Sent status on the open order list and a refresh that reveals Approved all match the existing report. Add the new observation there so one person can follow both reports.
Change the instruction that caused the disagreement
Suppose a peer links every approval complaint to issue 17. Spell out both details the match requires. The reviewer approved on a phone, and refreshing fixes the shop’s status. Then give them a fresh case in which refreshing leaves the status unchanged. A reader following the revised rule should ask for more evidence before linking that case to issue 17.
Keep the revision date, the reason for the change and one example a future reader can replay. When sharing the playbook with a group, give the next builder the clean packet. Keep your original customer material in its approved workspace. For a workflow that includes an AI coding step, add an acceptance test to the build prompt.
Share what you’re building
Send a working title and a short description for private review. Add a deck if you have one.
Open the short applicationApplying creates no commitment.