Pressure Stabilisation System

Stop pressure in one place from destabilising everything around it.

Pressure Stabilisation System

What this fixes

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.

How this works

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.

Time required

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.

When to use

Bring a real pressure situation that’s spreading across teams - live or recurring.

Use it whenever:

  • pressure on one team keeps becoming a problem for the teams around it
  • an incident or a crunch spreads firefighting well beyond where it started
  • rushed handoffs under pressure are creating errors downstream
  • pressure keeps spreading from one team to another, and the system still feels unstable
  • you keep telling people to stay calm, and it isn’t changing anything

What you get

A map showing exactly where pressure spreads - and the two or three changes that stop it spreading further.

  • A map of where pressure is spreading, not just where it starts
  • The two or three handoffs are doing the most damage
  • A circuit-breaker on each - a protected channel, comms rule or decision boundary

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.

What you’ll notice

  • The source wasn’t where most of the damage was
  • Containing the spread calmed the system faster than reducing the load
  • The pressure stopped becoming everyone else’s problem

Why this works

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.

What you need

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).

Steps

  1. Set up (5 min). Appoint a facilitator first - they run the activity from the Facilitator Guide. Name the one real pressure situation you’re working on.
  2. Map the flow (9–11 min). Lay your work out as a chain of dependencies - who hands what to whom. Map what actually happened, not the process everyone wishes they followed. Keep it to the path the pressure actually travels.
  3. Pass the pressure (9–11 min). Place pressure tokens at the source and pass them along the chain. Add one token each time a handoff forces another team into extra or reactive work. Watch where they pile up.
  4. Find the worst spread points (9–11 min). The handoffs with the biggest pile-up are where pressure is being passed on the worst - not necessarily the source. Ignore the source; focus only on where pressure multiplied most, and mark the two or three worst.
  5. Break the spread (11–13 min). At each marked handoff, ask: “What is the smallest change here that would stop this pressure from reaching the next team?” Place a circuit-breaker on it - a protected channel, a comms rule, a decision boundary. Contain the spread; don’t try to reduce the original load yet.
  6. Commit (5–6 min). Name the circuit-breakers you’ll put in place, each with an owner and when it goes in. Capture the map and the spread points. Photograph the board.

Output / Takeaways

  • A map of where pressure spreads, with the worst handoffs marked
  • A circuit-breaker for each, with an owner and a date
  • A first containment you’ll put in place this week

Important rules

  • Stop pressure spreading before you try to reduce it
  • Don’t try to solve the original incident during this activity - solve the spread
  • Follow the spread, not the blame - this is about handoffs, not people
  • Break the worst two or three spread-points, not all of them
  • A circuit-breaker is something concrete - a channel, a rule, a boundary

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

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