# Shift-huddle facilitator guide — Turbine 7

> Kit 9 · Turbine 7 · 30-minute huddle at the start of a night shift · for shift leads · fictional case

## Purpose

Rehearse the restart-or-hold call as a crew, once a month, using the simulator and one real alarm from the last month. The aim is a shared language for the four patterns, so that "rising, nobody's looked" means the same thing to everyone on the desk.

## Before the huddle (10 minutes, shift lead)

- Pick **one real alarm** from the last month where a restart decision was made. Remove names. Note the trend, who inspected, and what happened.
- Open the simulator (`/work/turbine-7/simulator` or the 3D version) on the wall screen. Check it runs.
- Print the alarm-pattern card, one per person.
- Have the agreed escalation boundary to hand (if your site has not agreed one, do that first; see the case page).

## Running order (30 minutes)

| Time | Step | What the shift lead does | What to listen for |
|---|---|---|---|
| 0–3 | **Frame** | "Tonight's question: what decides a restart? Not the alarm, the pattern." Hand out the card. | — |
| 3–13 | **One shift, together** | Play one simulator shift on the wall. For each case, ask the crew to call it **before** anyone clicks. Then click the majority call. | People naming the evidence ("trend's still going up") rather than the alarm ("it's only a temperature alarm") |
| 13–18 | **Debrief the pattern** | Open the debrief table. For any case the crew got wrong or split on, ask: "What would you have needed to see to change your call?" | Whether people can say what evidence they looked for, and where it was |
| 18–26 | **The real alarm** | Present last month's alarm without the outcome. Crew names the pattern and the call, then you reveal what happened. | Disagreement is useful: it shows where the escalation boundary is unclear |
| 26–30 | **Commit** | Each person says one thing they will check before their next restart. Agree one handover-note habit for the month. | Concrete checks ("open the trend, find the inspector's name"), not intentions |

## Facilitation notes

- **Do not score people.** The simulator scores; the huddle discusses. Nobody's result is recorded.
- **Let the production pressure in.** If someone says "but the desk would never accept a hold there", that is the conversation to have. Ask what reply would work, using the card's "number, risk, next step".
- **Escalation is not failure.** When the crew splits, the right answer is often "escalate", and that is a legitimate call.
- **Keep the real alarm anonymous.** The point is the pattern, not who made the call.

## After the huddle

- Note any case where the crew disagreed with the simulator's best call, and send it to the kit owner (see the scenario authoring notes). It may be a gap in the case, or a site rule the case does not reflect.
- Note any disagreement about the escalation boundary and take it to the operations meeting.

## Materials

Simulator (2D or 3D) · alarm-pattern card · one anonymised real alarm · escalation boundary (one page).