To ask clarifying questions that get a quick, useful answer, ask one closed question at a time about the single detail that decides what happens next. "How many red wires, exactly?" gets a number in a second. "Can you tell me more about the wires?" gets a paragraph. Ask before acting, and stop once the decision is settled.
Why clarifying questions beat a confident guess
A clarifying question costs a few seconds. A wrong guess costs whatever the mistake costs, plus the time to recover from it. When the action cannot be undone, the question is almost always cheaper. Guessing feels faster only because its cost arrives later.
On a bomb in Bomb Appétit, the arithmetic is plain. A wrong cut or a wrong press is a strike. Each strike speeds up the countdown, by a quarter after the first and by half after the second, and the default third strike ends the round. A question that takes three seconds is cheap next to a clock that now runs faster for the rest of the round.
Guesses also hide uncertainty. An Expert who says "probably the third wire" sounds like they are giving an instruction. A Defuser who acts on it has no idea the Expert was unsure. A question puts the doubt where both people can see it.
Closed or open: which clarifying questions save time?
Closed questions save time. They have a short, fixed set of answers: yes or no, a number, a color, one of two options. The listener can answer without composing anything. Open questions are useful only at the very start, when you do not yet know what to ask about.
"Is the last wire black?" takes one word to answer. "What does the end of the panel look like?" invites a description, which the Expert then has to search for the useful part.
A good pattern is one open question to start ("What's on this module?"), then closed questions only. The open question gets the overview; the closed ones pin down the facts the rule needs. The Defuser's first description often answers most of them in advance, so an Expert should hear it in full before asking anything, as set out in hearing the whole description first.
Offering a choice is another closed form that works well: "Is that spelled T, H, Y, M, E, or T, I, M, E?" The listener picks one and the matter is closed.
Which details should a clarifying question go after?
Go after the detail that changes the answer. Every rule turns on a few facts: a count, a color, a position, a word, a casing detail. Ask about those and nothing else. If an answer would not change what you tell the person to do, the question is wasting time.
The manual makes this easier because each line names its own deciding facts. The examples below are invented, but each matches a kind of condition that appears on a real module page. The exact rules depend on the manual's rule seed.
| Module | Example clarifying question | The rule detail it settles |
|---|---|---|
| Wires | "How many wires, top to bottom?" | Which wire-count list to read |
| Wires | "Exactly how many are red?" | Lines that depend on how many wires of a color there are |
| Wires | "What color is the bottom wire?" | Lines that start "if the last wire is" a color |
| Big Button | "What word is on the button?" | Lines that check the button's label, such as HUSH or ZING |
| Big Button | "How many batteries in total, every side?" | Lines with more or fewer than a number of batteries |
| Big Button | "Now you're holding: what color is the strip?" | Which countdown digit to let go on |
| Word Grid | "Display word: spell it for me?" | Which button position to read, since many display words sound alike |
| Passcode | "Second wheel: is there an R on it?" | Which listed words survive the second wheel |
| Tangled Wires | "Is there a star under that wire?" | One of the four facts that pick the wire's letter |
| Tangled Wires | "Is the light above that wire on?" | Another of the four facts, alongside red and blue |
Casing details, the serial number, batteries, indicators and ports, come up across many modules, so they are worth collecting once at the start. The post on reading the serial number out without ambiguity covers how to ask for it and hear it right.
When should you stop asking clarifying questions?
Stop when you can give one instruction you are confident in. Every question after that point only delays the action. If you find yourself asking a fourth or fifth question on the same module, you are probably searching the page while the listener waits. Say "checking" and read.
There is also a limit on the listener's patience. A Defuser who is asked six questions in a row starts answering faster and less carefully. Fewer, better-aimed questions get better answers.
Once you have the facts, give the instruction and have it said back before anything happens. That final step is not another question; it is a check. The method is set out in the three steps of a closed-loop call, and it is what turns a clarified fact into a safe action.
The question mistake: asking two things in one breath
Asking two things at once usually gets one answer. "How many wires and what color is the last one?" often comes back as "five", with the color forgotten, or "black", with the count dropped. The asker then cannot tell which part was answered. Ask one question, wait for the answer, then ask the next.
Double questions feel efficient because they save a turn. In practice they cost one, since the missing half has to be asked again. They also invite mismatched answers: "two" might be the number of red wires or the number of batteries, if both were asked at once.
The fix is mechanical. Before speaking, check that your sentence has one question mark's worth of content. If it has two, say the first, stop and wait.
Under a running clock this gets harder, because the urge to bundle grows as time drops. Communicating under pressure as the timer speeds up covers what to say when seconds are short, and the repeat-it-back drill for active listening gives a way to practise the answering side. Both work best after a quick read of the how to play page, so everyone knows the roles before the first question.