The Last Person Has to Do It
Telephone, except the message is a procedure and the person at the end of the chain has to actually carry it out on a machine. Nobody laughs at the garbled version this time, because it either works or it does not — and the part that went missing is never the part you would have guessed.
A written instruction — do this, then that, unless the light is on — is retold from memory by four people in turn. Something always survives intact and something always dies. Which part of the instruction is most likely to still be there at the end?
You take the last seat. Three people have already retold the brief before it reached you — you get what is left, and you have to work the panel with it.
How the room version works. This device is player 1. You read the full brief, it disappears, and you write what you can in 120 characters. Then you hold up a QR code and the next player points their normal camera app at it — no app to install, nothing to join, no account. It opens on their phone with only your version of the brief. The last player gets the panel. Nothing is sent anywhere: the whole chain travels inside the link.
Read it, hold it, and be ready to write it down in one short line. Do not show this screen to anyone else.
This is all you get. When it disappears you write it out again from memory — no scrolling back.
This is the instruction as it reached you. Set the panel up and press Execute. Order counts — the panel remembers what you did and when.
Nothing done yet.
What the original brief actually asked for
Where it went, hop by hop
The edge case nobody built
A customer says "renew it automatically — unless they've claimed twice this year." By the time it reaches the developer it is "renew it automatically." The exception was the entire reason for the request, and it is the first thing a chain drops, because it is the hardest clause to hold in your head while summarising the rest.
The runbook step that moved
"Drain the node, then restart the service" becomes "drain the node and restart the service" one handover later. Both sentences name the same two actions and only one of them is safe. Ordering is invisible in a summary — it survives as a word like "then", which reads like filler and gets edited out first.
"I told them exactly what to do"
You did — and they repeated it to the person who actually does it. Nouns transfer beautifully down a chain; the conditions attached to them do not. The test of a delegated instruction is not whether it was understood, it is whether it can be re-told and still be right.
Same failure, one hop
Ask for a summary of a document that itself summarised a spec and you have run this game with machines in the seats. The losses land in the same places: the negations, the unlesses, the ordering. What survives compression is what was concrete, which is exactly backwards from what mattered.
Put the conditions first
Chains compress from the end and from the middle. An instruction that opens with its exception — "if the amber lamp is dark, everything below changes" — keeps it, because the first clause is the one people retell first while they still have room.
Make them do it, not say it
"Does that make sense?" is answered yes by someone who has lost the exception, because they do not know it is gone. Ask them to carry it out, or to tell it back to a third person — a retelling is the only test that catches a silent loss.
An instruction is not one thing that degrades evenly — it is a bundle of clauses with wildly different survival rates. Objects and actions travel; conditions, order, negations and exceptions fall off, and those are almost always the clauses the instruction existed for. So when the work finally gets done wrong, the person who did it was following what they were given. The failure happened three people earlier, and nobody in the chain could see it happening.