Facilitation Guide: Running a Stress Test
Turn any stress test into a focused 60–90 minute group session that ends in a concrete next step.
A stress test is most useful when a community runs it together, out loud, rather than one person reading it alone. This guide turns any test in the library into a structured session. It works for a forming group anticipating problems, or an established one auditing where it actually stands.
The format is deliberately the same for every test, so the ritual becomes familiar: recognise → locate → choose one rung → assign an owner.
Before you start
- Pick one test. Just one. Resist the urge to “do a few” — depth beats coverage. If you’re not sure which, run the Self-Assessment first and take your top result.
- Choose a facilitator who will guard the process, not win the argument. Ideally someone with no strong stake in this particular failure.
- Choose a notetaker. The session is wasted if its decision isn’t written down.
- Set aside 60–90 minutes and make sure the people most affected are in the room.
The session, step by step
| # | Step | Time | What happens |
|---|---|---|---|
| 1 | Frame | 5 min | Facilitator reads the test’s “Sound familiar?” aloud. No discussion yet — just let it land. |
| 2 | Private signal | 5 min | Everyone privately marks which of the “Signs this is happening to you” they recognise. Private first, so the room doesn’t anchor on the loudest voice. |
| 3 | Surface | 15 min | Share how many signs each person marked, not who’s to blame. Agree one question: is this live for us, or a future risk? |
| 4 | Locate | 10 min | Place yourselves on the maturity ladder (L0 implicit → L3 enforced & rehearsed) using evidence, not aspiration. “We talked about it once” is not L2. |
| 5 | Choose one rung | 15 min | Pick the single next rung up. Identify which RCOS structure from “How RCOS prevents this” gets you there — usually one template to write or adopt. |
| 6 | Owner + date | 10 min | Assign a named owner and a real date. A rung with no owner and no date is a wish, not a decision. |
| 7 | Close | 5 min | Notetaker records the decision in your learning log: the test, where you placed yourselves, the rung, the owner, the date. |
If the test is already live
If step 3 lands on “this is happening now,” switch from the test’s prevent path to its “If it’s already happening” triage steps, and treat step 5 as “what stabilises this this week” rather than “what structure prevents it long-term.” Build the durable structure afterward, once the immediate pressure is off.
Facilitation cautions
- Keep it structural, not personal. The whole point of RCOS is that these are system failures, not character flaws. If a name comes up, move the conversation back to the role or the rule. “Whose job is this, and is that written down?” beats “why didn’t you handle it?”
- Watch the room reproduce the failure. Running the Dominant Speakers test while two people dominate the session is common — and useful. Name it gently when it happens.
- Heat is data. If a step gets tense, you’ve probably found the real issue. Slow down rather than smoothing it over; that smoothing-over is itself the Conflict Avoidance failure.
- One rung, not a rebuild. The goal is a single, owned step — not a plan to fix everything. Communities that try to jump from L0 to L3 in one meeting usually achieve L0.
Making it a habit
A single session helps; a cadence transforms. Many communities run one stress test per month or quarter, working through the library or re-running their highest-severity tests. Over a year that’s a structured, low-drama tour of every way the community could quietly break — and a written record of what you did about each one.