The binder problem: a team spends six weeks producing a complete playbook, launches it, and nobody opens it after week two. It failed at the point it tried to be complete.
One play, written well, gets used. Ship that first.
What a play is
Four parts. Missing any one and it is not a play.
- The trigger. The signal or moment that starts it. Without this a play is
a document waiting to be remembered, and it will not be.
- The steps. Who does what, in order, with the tools named.
- The artefacts. The actual email, the actual call structure, the actual
handoff note. Not a description of them.
- The QA. What a manager inspects before it ships, and what good looks
like.
Most playbooks have step two and nothing else, which is why they read as advice.
Run it from a recording
The technique that produces usable plays: pick a real instance where the play went well, and reverse-engineer it in the room.
Listen to the call or read the thread together, then write down what actually happened. That produces artefacts in real language rather than the aspirational version people write from memory.
If you cannot find an instance of the play going well, that is the finding: you are documenting a hypothesis, not a play, and it should be labelled as one.
Write the trigger and the QA first
Reversing the usual order fixes the usual failure.
Ask the trigger question before anything else: what makes a rep start this today? If the honest answer is "when they remember", either find a real trigger or accept the play will not run.
Then the QA: what would a manager check? A play nobody inspects decays inside a quarter.
Only then write the steps. It feels backwards and it produces plays that fire and hold.
The room, and the length
Reps who run the play, one manager, one enabler to write. Two hours per play, not a day. If it takes longer the play is too large and should be split.
Ship one, measure, then write the next
Release one play. Watch it for two weeks:
- Did it fire? Trigger check.
- Did people follow it? Steps and artefacts check.
- Did the manager inspect it? QA check.
Fix whichever failed before writing play two. A team that writes twelve plays before checking whether one works has produced a binder.
Where this sits
Playbooks are Motion in the Tenbound Pipeline Architecture Standard, with a foot in Mastery, since a play is also the teaching artefact for a skill.
The live library is at playbooks. For the manager habit that keeps plays alive, see SDR coaching.