Playbooks the team will follow¶

A playbook written by one analyst and filed away is a document. A playbook worked out by the people who will run it, from what an exercise or a real incident just taught them, is a practice. The difference shows the first time something goes wrong at speed: the second one is likelier to get followed, because the people following it helped decide what it says.

So the material comes from what already happened. A scenario lab that stalled at a particular handoff, a live experiment where the runbook described a system that had moved on, a retrospective that named the decision nobody owned: each of those is a playbook waiting to be written down. What belongs in it is the small set of actions and decision points that carried the weight, who holds which call, and the responses that worked, kept short, specific to the team, and revisited as things change rather than frozen the day they were agreed.

Kept that way, a playbook stops being shelf-ware and becomes part of how the team actually operates, and the loop from exercise to practice to the next exercise closes instead of leaking away.

Last updated: 3 July 2026