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.
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.
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.
Bring a real setback the team is in now, or one that just landed - not a hypothetical one.
Use it whenever:
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.
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.
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.
Output / Takeaways
Important rules
Make the next move from stable ground, not mid-scramble
Planning to facilitate this activity? Access the resources below to get started.