# How to Communicate Under Pressure When the Timer Speeds Up

- Author: Bomb Appétit (https://bombappetit.com)
- Published: 2026-10-20
- Category: Communication
- Canonical: https://bombappetit.com/blog/how-to-communicate-under-pressure-timer-speeds-up

> How to communicate under pressure: what a speeding timer does to your words, the short phrases that survive it, and how a team resets its talk after a strike.
To communicate under pressure, shrink every message to one fact or one action, name the thing you mean before you describe it, and get a spoken check before anyone acts. When a mistake lands, stop for a moment, say where the team stands, and restart the exchange from its first line instead of carrying on mid-sentence.

## What pressure does to the way people communicate

Pressure changes talk in predictable ways: people speed up, drop the subject of their sentences, talk over each other and stop checking. Each change feels like it saves time. Together they turn clear instructions into half-messages that only make sense inside the speaker's head, which is exactly where the listener cannot see.

Watch any team near the end of a countdown and the pattern repeats. Early on, the person describing a puzzle says "the keypad, top left key, it's a circle with a dot in it." Two minutes later the same person says "the dot one." The words shrank, but the listener's knowledge did not grow to fill the gap.

Volume goes up while content goes down. Several people answer at once, each with a slightly different idea, and the person who has to act picks whichever voice was loudest. That choice has nothing to do with which voice was right.

Checking is the first habit to vanish. A repeat that took two seconds in the calm opening feels like an indulgence once the clock is short, so people skip it. Ironically, that is the point in a round where an error costs the most, because there is no time left to recover from one.

Bomb Appétit makes all of this visible. One player, the Defuser, sees the bomb and cannot read the manual. The Experts read the manual and never see the bomb. Every mistake the Defuser makes is a strike, and each strike makes the countdown run faster, so the pressure climbs exactly when the talking gets worse. If you want the precise speeds, the Defuser's guide explains [how the timer behaves as strikes pile up](/blog/game-where-you-defuse-a-bomb-defusers-seat#how-does-the-timer-behave-in-a-game-where-you-defuse-a-bomb).

## Why do sentences get shorter and vaguer under pressure?

Sentences shrink under pressure because the speaker is trying to save seconds, and the cheapest words to cut are the ones the speaker already knows: which module, which end, which color. Those are precisely the words the listener lacks. Clarity drops first because the speaker cannot hear their own gaps.

Consider what a speaker actually knows at the moment of talking. They are looking at the thing. They know they mean the second wire from the top, so "the second one" sounds complete to them. The listener has no picture at all and has to guess whether "second" counts from the top or from the bottom.

Pronouns are the worst offenders. "It," "that one" and "the other" all point at something, but only for the person who can see where the finger would go. On a call, or with the manual and the bomb on separate screens, the pointer is gone and the pronoun points at nothing.

Vagueness also creeps in through shared history. After a team has named a glyph "the ladder," everyone feels sure what the ladder is. Under pressure, a new symbol that looks a little like a ladder gets the same name, and now one word covers two keys. Nobody notices until a wrong press lights a strike.

The fix is not to talk slower across the board. It is to keep three things in every message even when everything else gets cut: the name of the module, a position with its direction, and one feature the listener can check against the manual. "Wires, third from the top, blue" is short and still complete.

## Phrases that hold up under pressure

The phrases that survive pressure are short, fixed and front-loaded: the module name first, then the fact, then the action. A team that agrees on a handful of set phrases before the round can reach for them without thinking. Set phrases also make a missing piece obvious, because the gap sounds wrong.

Here are phrases worth agreeing on before you start. They are examples, not rules from the game, so change the wording to suit your group.

- **"Next: Wires."** Announces which module is being worked, so the right Expert listens and the others stay quiet.
- **"Reading the list now."** Tells the Defuser that silence is work, not confusion.
- **"Stop. Say that again."** A single request to repeat, not a new question layered on top.
- **"Third from the top, blue. Cutting?"** The Defuser's version of the instruction, said out loud as a question.
- **"Yes, cut."** The only words that should come before the cut.
- **"Strike. Two left."** Reports the damage without blame.

Notice what is missing from that list. There is no "I think," no "maybe try," and no "the one we talked about." Hedges sound polite in a calm meeting. In a countdown they leave the listener unsure whether they just heard an order or a thought.

Numbers deserve a set format as well. Decide whether you count from the top or the left, then say the direction every time: "second from the left" never needs a follow-up question. The Wires page in the manual counts from the top starting at one, which makes "from the top" a free default for that module.

The habit of saying an instruction back and getting a yes before acting is the strongest phrase of all, and it has a name. The guide to [closed loop communication: say it, repeat it, confirm it](/blog/closed-loop-communication-say-repeat-confirm) breaks down each of its three steps and shows which messages need one.

## Resetting team communication after a strike

After a strike, a team should not carry on mid-sentence. The safest move is a short reset: stop, say the strike count, name the module, and restart the exchange from its first line. It takes about ten seconds and stops a single mistake from setting off a second one while everyone is still rattled.

A strike changes more than the clock. It can also change the answer. On the Color Echo module, the manual picks its column by the number of strikes on the bomb right now, and after a wrong press the current sequence starts again using the new column. An Expert who keeps reading the old column is answering for a bomb that no longer exists.

### The four-step reset routine

The words below are invented examples. Use your own, but keep the order.

| Step                    | What happens                                                                   | Example words                                     |
| ----------------------- | ------------------------------------------------------------------------------ | ------------------------------------------------- |
| 1. Stop                 | Everyone stops talking and the Defuser takes hands off the bomb.               | "Stop. Hands off."                                |
| 2. Say the strike count | The Defuser reads the strike lights so every Expert has the same number.       | "That's one strike. Timer's faster."              |
| 3. Name the module      | The team agrees which module took the strike and who owns it.                  | "It was Color Echo. Sam, that's yours."           |
| 4. Restart the exchange | The Defuser describes the module again from scratch and the Expert rereads it. | "Color Echo, starting over. First flash is blue." |

Step two matters most on modules whose rules read the strike count. Saying the number aloud forces every Expert to update it. Step four matters on every module, because the description given before the strike may have been the problem.

Do not use the reset to work out who caused the mistake. That conversation can wait until the bomb is defused or gone. During the round, the only useful question is what to say next.

## How do you stay calm under pressure in games with a timer?

Staying calm under pressure in games with a timer comes from routine more than willpower. A player who knows exactly what to say next has less room to panic. Agree on your phrases and the reset before the clock starts, so the stressful moment calls for a script rather than a decision.

Breathing is the oldest advice and still useful in a small way. One slow breath out before speaking lowers the pitch and pace of the next sentence, and a steady voice tends to steady the rest of the table. The game's own how-to-play page puts it briefly: a strike is not the end, take a breath, then go faster.

Look at the timer less. The Defuser can see it, and online the Experts see the countdown too, along with the strike count and how many modules are solved. Reading the clock aloud every few seconds adds nothing the team can act on. Give one time call when it changes a decision, such as "two minutes, skip to the easy one."

Practise on a forgiving mission first. The opening missions give five minutes for one to three modules, which leaves time to rehearse phrases while the stakes are low. Later sections pack more modules and needy interruptions into the time, and the phrases you rehearsed will be what comes out of your mouth there.

Some teams find calm in giving each person one job. When several Experts all try to answer every question, pressure multiplies. When each Expert owns a few pages, most of the table can relax while one person speaks. The [full list of missions](/missions) shows which ones start to need that split.

## When pressure is a reason to stop talking for five seconds

A pause is the right move when the team no longer agrees on the basic facts: which module, how many strikes, which end to count from. Five seconds of silence costs less than an action built on two different pictures. Pausing is also right when two people are talking over each other.

Silence feels wrong when a clock is running, which is exactly why teams avoid it too long. The trick is to make the pause a set move with a name. "Freeze" or "hold" tells everyone it is deliberate, not a sign that someone has given up.

Use the pause to collect one fact, not to debate. A good pattern: the Defuser says "hold," everyone stops, the Defuser reads out the one fact in doubt ("four wires, from the top: red, red, white, blue"), and the owning Expert speaks next. Nobody else talks until that Expert has finished.

The listener's side of this pause matters as much as the speaker's. Holding a question until the speaker finishes, and tracking numbers in order, are the habits covered in [how to be a good listener in communication](/blog/how-to-be-a-good-listener-in-communication). Under pressure, the listener's patience is what keeps the pause short.

There is a limit. A team that pauses after every step will run out of clock. Pause when the facts are in doubt, not when the answer is merely hard. Speed comes back once the picture is shared again. The guide to time attack games explains [when a fast team should slow down](/blog/time-attack-games-faster-without-strikes#when-should-a-fast-team-slow-down), and the broader post on [time attack games that get faster without strikes](/blog/time-attack-games-faster-without-strikes) shows where the seconds actually go.

When you are ready to test any of this, [open a bomb on the play page](/play) and try one round with the reset routine written on a sticky note beside the manual. Afterwards, ask each player which phrase they actually used. Keep those and drop the rest.