Your team is under serious pressure - a deadline slipping, an incident, a crunch - and it isn’t staying in one place. It gets passed on: a rushed handoff turns one team’s stress into another team’s emergency, and soon the whole delivery is unstable. The instinct is to tell people to stay calm and push harder. But the problem isn’t the pressure itself - it’s that every rushed handoff creates more pressure for the next team, until the whole system becomes unstable.
A production incident hits Team A mid-release. To recover fast, they skip the usual handoff and fire urgent requests at QA, DevOps and Security. QA delays testing another release. DevOps drops its planned work. Security breaks off an audit. By the next morning, four teams are working under pressure - even though only one team had the original incident. The incident didn’t spread; the handoffs did.
In the activity, the team maps how work moves between teams, then passes pressure tokens along the chain to follow how one pressure event spreads through the handoffs. Wherever the tokens pile up, the team puts one simple circuit-breaker - a protected channel, a comms rule, a decision boundary - to stop the pressure spreading further.
Team: one person runs the activity using the Facilitator Guide. The teams that hand work to each other take part.
Team ✓
Team: 45–60 minutes, with a facilitator. Best with the people across the handoffs, not just one team.
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 10 minutes. It’s a downloadable PDF on this page.
Bring a real pressure situation that’s spreading across teams - live or recurring.
Use it whenever:
A map showing exactly where pressure spreads - and the two or three changes that stop it spreading further.
You’ve done it well when: the team can point to where pressure was being passed on and has put something concrete in place to contain it - without anyone having to work harder.
Pressure itself isn’t what overwhelms a delivery. The real damage happens when pressure spreads from one team to the next through rushed handoffs and reactive decisions. By stopping that spread at a few critical handoffs, the whole system becomes more stable - even if the original pressure remains. That’s why it works faster than trying to reduce the pressure itself.
Everything comes in one kit. Here is each part, and when you use it:
The dependency board (core). A board where the team lays out its work as a chain of who hands what to whom. This is the map the pressure travels along.
Pressure tokens. Tokens that the team passes along the chain to act out a pressure event. One or two start at the source; at each handoff, the team adds tokens for the extra stress that handoff creates downstream - so the pile-up becomes something you can see on the table.
Circuit-breaker cards. Cards naming ways to contain spread at a handoff - a protected channel, a comms rule, a decision boundary. Used once the worst spread points are clear.
Starter-scenario cards (optional). Example pressure situations. Use one only if the group has no real situation of its own. Otherwise, set them aside.
Roles - Team: a facilitator (runs the flow, passes the tokens, holds the focus on spread, not blame) and participants (lay out the dependencies, watch the cascade, place the circuit-breakers).
Output / Takeaways
Important rules
Planning to facilitate this activity? Access the resources below to get started.