Running a team session
One page for whoever runs it. An hour: ten minutes to get everyone aboard, three shifts, ten minutes to talk.
Before the day: orientation is homework
- Host a team session from the title menu (HOST A TEAM SESSION), press START, and send everyone the join link it shows. The link walks them through making an account, downloading the right build and the join code.
- Ask everyone to play ORIENTATION on their own before the day. It's ten minutes, it's the first button on the title menu, and it teaches all five chairs. Nobody should learn the buttons while four colleagues wait.
- Leave progression off (the default). Everyone plays at base stats, so nobody's out-leveled by a teammate who plays at home.
- Everyone needs the same version. An out-of-date build is refused with a message that says which version to get; the join link has the download.
Assign chairs against real jobs
In the break room you ASSIGN chairs. For the first shift, put people where their job already is. They'll recognize the work, and the jokes land:
| Chair | What it does on the bridge | Who it fits at work |
|---|---|---|
| Command | signs off, pays the bills, calls the jump. Nothing fires without them | the lead, PM or manager: whoever approves things |
| Engineering | the power budget, heat, patching what broke | infra, platform, SRE |
| Science | scans, locks targets, notices when a readout is wrong | data, ML, research |
| Helm | points the ship where everyone needs it and holds it steady | product or frontend engineers, designers |
| Guns | the one action everything else enables; waits for the chain | whoever ships: the deploy button in human form |
For shift 2, press ROTATE. Doing a teammate's job for fifteen minutes is the part people talk about afterwards.
Three shifts
- About fifteen minutes each, with the break room between them. Three is the default and the right number: one to learn, one rotated, one to get good.
- Don't coach during a shift. Let them find the talking themselves. Do say "you can ping that" once, if a chair has gone silent.
- Watch for the quiet. When nobody has said anything for a minute, that's the moment the debrief card will remember.
The ten-minute debrief
After the last shift, the debrief card opens for everyone: what each person caught from Clancy and how, the PERFECT shots and who was in them, pings and handoffs, and the quietest stretch. Then it asks two questions.
- Give everyone a minute to read the card.
- "When did someone catch Clancy, and how did they notice?" Five minutes. Ask the person, not the room. Most catches are someone noticing a number didn't move. That's the same skill as reviewing AI output at work, and it's worth saying out loud.
- "Where did we stop talking?" Five minutes. Start from the quietest stretch on the card. Ask what each chair was waiting for.
The card counts things; the people explain them. Keep it about Clancy and the ship, never about who was slow. If someone says "that was me," say "that was the bridge."
The first time Clancy slops
It happens in the first few minutes. Clancy announces it, cheerfully, and is wrong. Say something like:
"That's Clancy. He's confident. Is he right? Someone check the real gauge."
Then let them work it out. What fixes it:
- VERIFY cancels an order Clancy is holding ("One sec, let me think about that…"), if you press it within about a second.
- For anything else (a wrong heading, a power matrix "balanced" for you, a "Done!" where nothing happened), press the order again, or a teammate calls it out and fixes their part.
The joke is the tool, never the person who trusted it. Everyone has shipped something an assistant got confidently wrong. That's why it's funny.