Good miscommunication examples show the exact words said, the different words heard, and the line that would have stopped the gap. The common kinds are mirrored left and right, a list counted from the wrong end, one nickname used for two things, and a missing detail the listener filled in. Each has a short, repeatable fix.
Why miscommunication examples teach more than rules
Rules such as "be specific" are easy to agree with and hard to apply, because nobody thinks they are being vague. A concrete example shows the precise sentence that failed and why it sounded fine to the speaker. Seeing the failure lets a team spot the same pattern in their own talk next time.
A bomb defusal round is an unusually good source of examples. In Bomb Appétit, the Defuser sees the bomb and cannot read the manual, and the Experts read the manual and never see the bomb. Every action depends on words, and a wrong action is a strike. So each miscommunication leaves a clear mark: a red light, a faster timer, and a team that can usually point to the sentence that caused it.
The table below collects ten examples. They are invented to show common patterns, not transcripts, and the rule outcomes depend on the rule seed, so treat each as an illustration.
| # | What was said | What was heard | What happened | The fixed line |
|---|---|---|---|---|
| 1 | "Press the left one." | Left from the Expert's imagined view | Wrong key pressed, strike | "Press the key on your left as you face the bomb." |
| 2 | "Cut the second wire." | Second from the bottom | Wrong wire cut, strike | "Cut the second wire from the top." |
| 3 | "Press the ring one." | Circle with a ring, not square with one | Wrong glyph pressed, strike | "Square with a ring inside, top right key." |
| 4 | "Cut the last red." | "Cut the last," then "red" as a remark | Last wire cut instead of last red one | "Cut the last red wire. That's the fourth from the top." |
| 5 | "Hold it." | Hold the lever, not the button | Lever held, button ignored, seconds lost | "Big Button: hold it down, wait for my word." |
| 6 | "There's a vowel." | A vowel in the indicator label | Wrong Color Echo table used | "Serial number has a vowel: the letter A." |
| 7 | "Blue, green, blue." | Only the newest flash | Partial sequence pressed, strike | "Full sequence from the start: blue, green, blue." |
| 8 | "The word is their." | "There" | Wrong row in the Word Grid table | "T-H-E-I-R, their." |
| 9 | "Three batteries." | "Free batteries"? Asked twice | Ten seconds lost, no strike | "Batteries: three. Three." |
| 10 | "We're on one strike." | Nothing; Expert was reading | Old column used on Color Echo, strike | "Strike. One strike. Everyone switch columns." |
Notice that most of the fixed lines are only slightly longer than the originals. Fixing a miscommunication rarely takes a speech. It takes the one word the speaker assumed.
Left and right miscommunication: whose point of view?
Left and right get swapped when the speaker and the listener picture the object from different sides. The person facing the bomb means their own left. An Expert imagining the bomb may picture it facing them, which mirrors everything. The fix is to name whose view the direction comes from, every time, or to swap directions for positions.
The trouble is that "left" feels absolute to the person saying it. It is their left, after all. The listener, with no picture of their own, builds one, and nothing guarantees it faces the same way. In one room, the Experts may be sitting across the table from the Defuser, which makes the mirror literal.
Two fixes work well. The first is to anchor every direction to the Defuser: "on your left as you face it." The second is to replace direction with a count from a stated edge: "first key, counting from the left as you look at the bomb." Both add a few words and remove the guessing.
Some modules settle the question in the manual. The Labyrinth page says columns count from the left and rows count from the top, and it moves the Defuser's light with arrow buttons. Once the team agrees the Defuser's view sets left, the Expert's directions and the arrows line up.
The post on why a bomb bans pointing covers the wider problem: a gesture carries direction for free, and words have to rebuild it.
Which end do you count wires from?
A list has two ends, and "the second wire" means two different wires depending on which end you count from. The Defuser may count from the end their eye lands on first. The Expert assumes the end the manual uses. The fix is to say the starting end with every position: "second from the top."
On the Wires module the manual settles it: wires are counted from the top, starting at one. That helps only if both sides use it. A Defuser who just described the bottom wire ("the bottom one's black") may slide into counting upward from there without noticing.
The same trap appears elsewhere. The Recall module counts button positions from the left. Wire Panels runs wires from numbered posts on the left to lettered posts on the right, which gives each wire a name that does not depend on counting at all. Where the module offers a label like that, use it instead of a count.
A good habit for long lists is to read the whole list once with its direction ("from the top: blue, red, white, red, black") and then refer to positions by both number and color. "Fourth from the top, the red one" gives two independent ways to find the wire. If they disagree, the listener knows to stop.
Counting from zero is a rarer cousin of this problem. Some people, especially programmers, start at zero without thinking. The manual starts at one, so say "first" rather than a number when in doubt.
One name for two symbols: the naming clash
A naming clash happens when a team's nickname for one thing also fits another. "The ring one" is unique until a second glyph with a ring appears. The fix is to name by both parts, shape and mark, the way the manual does, and to retire any nickname that has become ambiguous.
The Glyph Keypad shows four keys, each with a glyph. The manual describes a glyph as an outer shape with a mark inside, such as a circle with a dot. Shapes include circles, squares, triangles, diamonds, hexagons and arches. Marks include dots, bars, pluses, rings and zigzags. Any single part of a name, like "ring" or "triangle," can easily match more than one glyph on a page.
Using both parts every time is the simplest cure. "Square with a ring" is a full name. "Ring" is half a name. The manual prints the full names under its pictures, so the Expert can read them back word for word.
Colors clash too. Two people may call the same wire "orange" and "red," or a striped wire "red" when the Tangled Wires page treats red and blue striped as its own kind. Agree on the color list before the round, and read colors from the manual's own words.
Sound-alike words are a related clash, at the level of sound rather than meaning. The Word Grid page warns that many of its words sound alike and asks the Defuser to spell every one. The plain-words guide covers how to spell sound-alike words out so they survive a call.
Why does one sentence become two miscommunication examples?
One sentence often contains two separate failures: the speaker left something out, and the listener filled the gap with a guess. Both happened, so both people can learn from it. Asking who was wrong misses the point. The better question is where in the sentence the two pictures split.
Take example four from the table: "Cut the last red." The speaker dropped the word "wire" and spoke quickly, so "red" sounded like an afterthought. The listener heard "cut the last" as complete and treated "red" as a comment. Each person made a reasonable move from their side.
This is why fixing only one side does not stick. Tell the speaker to be clearer and they will be, until the next stressful moment. Tell the listener to check and they will, until they feel sure. A team that fixes both sides, a full sentence from one and a read back from the other, has two chances to catch the same slip.
The earlier communication games post explains why Experts hear something different from what the Defuser said, from the description side. That gap between what one person sees and what the other builds in their head is the root of almost every example in the table.
When you debrief a strike, try splitting the sentence into its two halves on purpose. Ask the speaker what they meant, then ask the listener what they heard. Write both down. The difference is usually one word.
When a miscommunication is nobody's fault
Some miscommunications happen when both people did everything right inside their own frame, but the frames did not match. The clearest case at a bomb is a rule seed mismatch: the Defuser and Experts follow perfect instructions from a manual that belongs to a different bomb. Fix the frame first, then the words.
Every rule in the manual comes from a number called the rule seed. Change the seed and every rule changes. The bomb and the manual must use the same seed, and the manual's first page warns that a different number means different rules. A team that skips the seed check can describe and repeat flawlessly and still strike, because the manual is answering a question nobody asked. The standard manual, rule seed 1, is the default start.
Other frame problems are smaller. An Expert reading a printed manual from an earlier seed, a Defuser using a different bomb view than the one the Expert imagined, or a needy module waking up mid-sentence and pulling the Defuser away. Each can make good words land wrong.
The useful response is the same in every case: stop, check the shared facts, then start again. Seed number, strike count, which module, which direction. If those match, the words will usually work.
Not every lesson needs a bomb. A classic drawing exercise, where one person describes a picture and another draws it, produces many of the same mismatches on paper. The comparison of the communication drawing exercise and a bomb round shows how to run both and compare what goes wrong.