What is a playbook?
A procedure written so that a stranger, or an agent, executes it the same way on a bad day.
Definition
playbook (n.) – a procedure written in four blocks, so that whoever runs it next gets the same result the author would: the command to perform, the verify step that proves it worked, the recover step for when it did not, and the gotcha that records what went wrong last time.
Most procedures are written as a list of actions. That is the command block alone, and it is the least valuable quarter of the document. A list of actions assumes the reader will notice when something has silently failed, and an unattended process notices nothing it was not told to look for.
The verify block states what success looks like in observable terms. The recover block states what to do when the check fails, which converts a stall into a decision. The gotcha block carries the surprise from the last run, written while it was fresh, which is the part that keeps the same mistake from being made a third time.
The difference between a playbook and a checklist is those last three blocks. A checklist tells you what to do. A playbook also tells you how to know it worked, what to do when it did not, and what bit somebody last time.
Playbooks are written during a real execution, not from memory afterward. Memory smooths over exactly the hesitations that the document needs to record.
The four blocks
Command: the action to take, specific enough to execute without interpretation. Verify: an observable check that the action took effect, stated as a condition rather than a feeling. Recover: what to do when the verify fails, including who to escalate to and when to stop rather than retry. Gotcha: the failure that has already happened here, recorded so it is not rediscovered.
A playbook missing its verify block is a checklist wearing a different name. A playbook missing its gotcha block is one that has not been run enough times to be trusted.
Why the gotcha block is the asset
Every procedure accumulates surprises. A supplier who fails in August, a report that is empty until a certain hour, a step that succeeds and reports failure. These are the facts that take a new person months to learn, and they are learned once and then lost when that person moves on.
Writing them into the procedure itself, rather than into a separate lessons document nobody opens, is what makes them survive. The gotcha is read at the moment it is relevant because it sits next to the step it belongs to.
When a playbook is finished
It is not. A procedure that has stopped producing amendments is either genuinely stable or no longer being watched, and those two look identical from the outside. The only way to tell them apart is to check.