Delivery Recovery Path

Steady one thing first so a setback stops spreading.

Delivery Recovery Path

What this fixes

A release breaks, a dependency fails, a key person drops out - and the team reacts everywhere at once. Each fast move feels productive, but the unsteadied mess makes the next problem worse: a rushed fix triggers a second incident; a dropped handover becomes tomorrow’s escalation. The original setback isn’t the main problem. The scramble that follows is - and it compounds. This gets the team to steady one anchor before it does anything else.

How this works

Picture an incident: the API is down, and while the team scrambles to patch it, the half-done deploy corrupts a second service, a stakeholder starts escalating, and the on-call engineer is now switching between three fires at once. The original incident caused the first problem. The team’s reactions created the next three.

This activity runs the compounding live. The team names a real setback, then the facilitator turns over escalation cards on a clock - each one a new blow. At every turn, the team chooses: to steady its one anchor or to react. React, and the next card hits harder. Steady the anchor first, and the team absorbs what comes. By the end, the team has felt, not been told, why stabilising beats scrambling - and it leaves with the next real move locked.

One anchor only - if you protect everything, you protect nothing. Steadying the anchor means protecting it from further damage this round - nothing more.

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

Time required

Team ✓

Team: 30–45 minutes, with a facilitator. Best run live, when a setback has just hit - or as a fast rehearsal soon after one.

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

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

When to use

Bring a real setback the team is in now, or one that just landed - not a hypothetical one.

Use it whenever:

  • a delivery is broken, and the team is reacting on instinct
  • a setback is spreading - one problem is spawning others
  • the team is firefighting several things at once, and nothing is settling
  • you can feel the scramble making things worse, not better
  • you want the team to build the reflex of steadying first, before the next setback

What you get

  • What the team held steady - the one anchor protected while the blows kept coming
  • A clear view of where reacting made things worse
  • The next real move, with an owner - made from stable ground, not mid-scramble

You’ve done it well when: the team can point to the anchor it protected, see how scrambling would have compounded the damage, and leave with one steady next move.

What you’ll notice

  • Each blow you took while scrambling landed harder
  • Steadying one thing first made the rest manageable
  • The setback itself did less damage than the scramble around it

Why this works

Under a setback, the instinct is to act on everything at once - but a system that hasn’t been steadied spreads damage, and every rushed reaction creates another problem to recover from. The scramble does more damage than the setback. Steadying one anchor first contains the spread, so the team recovers from stable ground instead of compounding the mess.

What you need

Everything comes in one kit:

Escalation cards. Introduce new setbacks, one per round (drawn face down).

Anchor card. Holds the one thing you’re protecting.

Board. Shows what’s protected versus what’s spreading.

Timer. Keeps each round short and under real pressure.

Capture sheet. Records the next move and the lesson.

Roles - Team: a facilitator runs it from the Guide (turns the cards, keeps time, holds the rules); everyone else takes part. The full kit details are in the facilitator guide.

Steps

  1. Name the setback (4 min). Team: appoint a facilitator first - they run it from the Guide. Then write the real setback in one line: what broke, what’s at stake right now.
  2. Choose your anchor (4 min). Pick the one thing you must keep steady - a service, a commitment, a person. To choose it, ask: if this collapses, what else immediately becomes harder? Choose the thing most others depend on. Write it on the anchor card, in front of the team. Protect everything, and you protect nothing.
  3. Run the escalation (14–18 min). The facilitator turns escalation cards on the clock, one per round. Before each card, ask one question first: what must wait so our anchor stays steady? Decide that, then deal with the card. Steadying means taking the action that protects the anchor from further damage this round - nothing more. If you react elsewhere instead, the next card hits harder.
  4. Review what happened (5–6 min). Stop the deck. On the board, see what stayed steady and what spread - where reacting made the next blow worse, and which escalation became avoidable once the anchor stayed steady.
  5. Decide the next move (4–5 min). From stable ground, pick the first move that keeps the anchor steady after this activity ends, and who owns it. Photograph the board. One steady step, no scrambling.

Output / Takeaways

  • A photo of the steadied board - the anchor held, the spread contained
  • The next real move, with an owner
  • The reusable habit: “what’s the one thing I steady first, before I react to anything?”

Important rules

  • Steady the anchor before reacting to anything new
  • One anchor only - if you protect everything, you protect nothing
  • Once chosen, the anchor cannot change during the activity - a new card is never a reason to switch anchors
  • Don’t preview the escalation cards - the not-knowing is the point
  • Keep rounds short - the clock keeps it real

Make the next move from stable ground, not mid-scramble

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

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