Recovery Playbook

Turn one planned setback into a recovery the team can repeat every time.

Recovery Playbook

What this fixes

Every team recovers from setbacks - but almost none capture how. The moves that steadied things last time live in a few people’s heads, so every new setback starts with the same scramble. This activity turns one successful recovery into a short playbook the whole team can run next time, instead of reinventing it under pressure.

How this works

Imagine your production system goes down on a Friday evening. The team eventually recovers - but only because three experienced engineers instinctively know what to do. Six months later, the same thing happens, two of them are away, and the team starts from scratch again.

This activity takes that kind of setback and turns it into something the whole team can repeat.

The team runs the setback as a simulation. Every few minutes the facilitator introduces another problem. The team responds as it normally would. Afterwards, everyone marks the few actions that actually stabilised the situation. Those actions become the recovery playbook.

Team: one person acts as the facilitator - they run the activity using the Facilitator Guide while everyone else takes part.

Time required

Team ✓

Team: 60–75 minutes, with a facilitator. Best run when there is not a live crisis - ahead of the next setback, while the team can think clearly.

The time required is indicative and will depend on the nature of the problem and the size of the team.

The facilitator must read the short facilitation guide first - about 8–10 minutes. It is a downloadable PDF on this page.

When to use

  • your team keeps meeting setbacks with the same improvised scramble
  • recovery depends on one or two people who happen to know what to do
  • you’ve survived incidents but never captured what actually worked
  • you want a recovery the whole team can run, not re-invent, next time
  • you’re building the team’s resilience between crises, not during one

What you get

  • A short, reusable recovery playbook - the sequence that actually stabilises your team
  • The trigger that says ‘run this now’, and who owns each step
  • A shared picture of where the team scrambles - and what to do instead

What you’ll notice

  • Improvising the recovery costs time and effort - you pay it at every setback
  • A written recovery is done once, then used again
  • The team already knew how to recover - it just never wrote it down

Why this works

Teams often recover successfully - but only because the right people happen to know what to do. Simulating the setback shows which actions actually stabilised the situation. Writing those actions down turns one successful recovery into something the whole team can repeat.

What you need

Everything comes in one kit:

Escalation cards  drive the simulation - each introduces a new blow.

The board  tracks the setback, the scramble, and the recovery sequence.

Playbook sheet  where the reusable recovery is captured.

Timer  keeps the simulation rounds under real pressure.

Markers  for writing the sequence and the trigger.

Roles - Team: a facilitator runs the simulation and the capture from the Guide; everyone else takes part. The full kit detail is in the facilitator guide.

Steps

  1. Pick the setback (6 min). Team: appoint a facilitator first - they run it from the Guide. Then choose one real setback your team has faced or realistically could. Make it concrete enough to play out.
  2. Run the simulation (17–20 min). The facilitator turns escalation cards on the clock, one per round - each a new blow. Respond exactly as you would in real life. Don’t stop to design a better recovery.
  3. Mark what worked (11–13 min). Individually, each person marks the moves they believe stabilised the situation. Compare answers - and discuss where you disagree (you will). You’re looking for the actions that genuinely changed the outcome - not everything the team did.
  4. Capture the playbook (18–21 min). Write the moves that worked as a short sequence: the first thing to steady, who does what, and in what order. Keep it short enough to use under pressure.
  5. Lock the trigger (8–10 min). Agree on the signal that says ‘run this now’ - the early sign of the setback. Write it at the top of the playbook, name an owner, and photograph it.

Output / Takeaways

  • A short, reusable recovery playbook the team keeps
  • The trigger that starts it, and an owner for each step
  • The reusable habit: “we don’t re-invent our recovery - we run it”

Important rules

  • Run the simulation before writing anything - the scramble must be real first
  • Capture only the moves that actually worked, not everything you did
  • Keep the playbook short - a long one won’t be run under pressure
  • Every playbook needs a trigger - without it, no one knows when to start
  • This is for between crises - not a tool to run mid-incident (use Delivery Recovery Path then)

Planning to facilitate this activity? Access the resources below to get started.

MIndn
Execution must be smooth. Not chaotic or stressful.
Built by Witmer.