When you didn't catch it: recovery in real time

Someone asks you a question and you have no idea what they said. Maybe the audio cut out, maybe their accent is unfamiliar, maybe they mumbled, maybe you were reading a different thread and heard nothing at all. This is the most quietly dreaded moment in a second language, and the truth is liberating: everyone lands here, native speakers included, and the entire skill is the recovery. The only move that actually fails is the silent nod, because a guessed answer to an unheard question is a bug you plant in public and pay for later. This chapter is the recovery bank, graded by how much you missed and why.

The one principle

There are three different failures hiding under "I didn't get it", and they need three different repairs:

Don't be confused: didn't hear it, didn't understand it, and wasn't listening are separate problems. Didn't hear is an audio failure (the words did not arrive: bad line, mumbling, a dropped syllable); the fix is "say that again", possibly louder or slower. Didn't understand is a meaning failure (the words arrived but did not parse: unfamiliar jargon, an ambiguous referent); the fix is "what do you mean by X?", and a repeat of the same words will not help. Wasn't listening is an attention failure (you drifted); the fix is an honest, quick "I lost you, one more time?". Diagnosing which one you have is half the recovery, because asking someone to repeat when your real problem was the meaning just gets you the same sentence twice (Chapter 9's "I don't follow" versus "I don't agree", one layer earlier).

You missed a word or two (you heard most of it)

The highest-skill recovery, because it pinpoints the gap and asks for the least. Echo the sentence up to the hole:

  • "The exchange races the... what? I lost one word."
  • "You want it done by when, sorry?"
  • "Pin the epoch and then... say the last part again?"
  • "Sorry, the tool you mentioned, what was it called?"

The partial echo is better than "can you repeat that?" for two reasons: it proves you were tracking (so it costs you no credibility), and the speaker repeats three words instead of a paragraph. Native speakers do exactly this all day.

You missed the whole thing (heard nothing useful)

A clean, light ask, no drama:

  • "Sorry, say that again?" (the friendly workhorse)
  • "Could you repeat that? I didn't catch it."
  • "One more time? I lost that."
  • "Say that once more, slowly?" (when speed was the problem)

Register note from Chapter 33: "Sorry?" and "Say again?" are the everyday forms; "What?" reads abrupt in most rooms; "Pardon?" is fine but a touch formal. Pick one and own it; the fumble is not asking, it is pretending.

You heard it fine but don't understand it

Do not ask for a repeat; ask for the meaning, and show which part lost you:

  • "I heard you, but I'm not sure I follow: do you mean the CDN cache or the app cache?"
  • "When you say 'reconcile', what exactly are we reconciling?"
  • "I'm with you up to the watermark part; can you unpack that one?"
  • "Say more? I want to make sure I'm answering the question you're actually asking."

Asking "what do you mean?" is not a confession of ignorance; it is often the sharpest thing said in the meeting, because half the room was quietly unsure of the same word (Chapter 25).

The speaker is genuinely hard to understand

Unfamiliar accent, fast talker, soft mumbler, non-native speaker straining for a word, or a bad connection. The rules here are as much about kindness as recovery, because the person is already working hard.

  • Blame the channel, never the person. "The audio's a bit rough on my end, could you repeat the last part?" is the universal face-saver, and native speakers use it constantly. It works whether the real problem is the line or the accent, and it never makes anyone feel judged.
  • Ask for one specific thing, not "everything again": "I caught the first half; from 'and then the worker' onward, once more?"
  • Move it to text when speech keeps failing: "Would you mind dropping the command in the chat? I want to get it exactly right." Numbers, names, versions, and identifiers should go to text regardless of accent (Chapter 24).
  • Confirm by echo, so they don't have to keep repeating: "Let me play it back: pin the epoch, then exchange, right?" This ends the loop faster than a third repeat and shows you got there.
  • Never remark on the accent itself. Not "your accent is hard to follow", not "sorry, your English is fast", not even a well-meant "where's that accent from?" mid-task. The only sentences you need are about the audio and the content. And the same courtesy runs the other way: when you are the one being strained to understand, "could you slow down for me?" is your right to ask, with zero apology for your own accent.

Don't be confused: patience and condescension look similar and land oppositely. Slowing down, choosing plainer words, and confirming by playback are patience, and they help. Finishing the person's sentences for them, over-nodding, exaggerated slow loud speech, or a relieved "ohhh, you mean...!" are condescension, and they sting. The test: are you adjusting the channel (pace, medium, checking you got it) or performing your own effort at them? Adjust the channel silently; never make your listening look like charity.

You completely zoned out

The honest one, and the hardest to say. You were on another tab, your mind wandered, you were composing your own next point. The recoveries, by how much cover you have:

  • Full honesty (usually best, especially in small groups): "Sorry, I drifted for a second there; could you repeat the question?" / "Honestly, my mind was elsewhere; one more time?" People respect the admission far more than they would a bluffed answer, and everyone has been there.
  • Light face-saver: "Sorry, I was half in the doc; say that again?" (a true-enough reason that is not self-flagellation)
  • The context grab, when you need to reconstruct: "Can you give me the last sentence again? I want to answer the right question." (buys you the thread back without a full confession)

What you do not do is answer anyway and hope. A confident answer to a question you did not hear is the one move that turns a five-second recovery into a credibility problem when it lands on the wrong thing.

You already asked twice

Asking a third time feels unbearable, so switch modes instead of repeating the same failing channel:

  • "I'm clearly not getting this by ear; could you drop it in the chat?"
  • "Let me not make you say it a fourth time. I'll catch it in the recording and follow up in the thread."
  • Ask a neighbor quietly, or in a DM: "What did they just ask?" (entirely normal; someone always caught it)
  • Own it lightly and move on: "That one's on me and my headphones; I'll get it from the notes." Then actually do.

Switching the medium (voice to text, ear to recording, ask the room to ask a colleague) breaks the loop that repetition alone cannot.

You realize mid-answer you misheard the question

You started answering and the faces tell you it is the wrong answer. Stop cleanly and reset; do not plow on:

  • "Wait, I think I'm answering a different question. Were you asking about the read path or the write path?"
  • "Let me back up: I heard 'cost', but you might have said 'cause'. Which one?"
  • "I've clearly gone sideways; say the question once more and I'll aim better."

Catching your own miss mid-sentence and resetting reads as attentiveness, not failure (Chapter 23's repair, applied to comprehension).

The reverse: they didn't understand you

Since misunderstanding runs both ways, the mirror skill. When someone asks you to repeat, or looks lost:

  • Rephrase, don't just repeat louder. Saying the identical sentence again, louder, rarely helps; the problem was usually the words, not the volume. "Let me say that differently: ..."
  • Cut to the plain version: "Shorter: the retry can double-charge. That's the whole worry."
  • Check which part landed: "Did the part about the cache make sense, or should I start there?"
  • Offer text for the precise bits: "I'll type the exact flag name; easier to read than hear."
  • Never sigh or show irritation at being asked to repeat; the person asking did the brave thing, and your patience decides whether they ask next time or start nodding silently, which is the outcome you least want (Chapter 22).

In writing, when the message itself is unclear

Chat and email have their own version: a message so terse or garbled you cannot act on it. Ask, specifically:

  • "Not sure I follow: do you mean we should roll back, or hold?"
  • "Quick check, is 'it' the deploy or the migration? Want to act on the right one."
  • "Can you say that another way? I'm reading it two ways and they need opposite actions."

The same rule as everywhere: naming the ambiguity ("I'm reading it two ways") is faster and cleaner than guessing and being wrong.

A note for non-native speakers

Some cultures treat asking someone to repeat as a loss of face, for you or for the speaker. In default international-English workplaces it is the opposite: asking is normal, expected, and respected, and it is the bluff that carries the real cost, because engineering answers get audited by reality. The colleague who asks "sorry, say that again?" three times in a meeting and then gives a correct answer looks far better a week later than the one who nodded smoothly and built the wrong thing. Clarity beats smoothness, every time (Chapter 17).

👉 That closes the response banks. The remaining chapters are pure reference: the jargon glossary that decodes the dense technical vocabulary, then the cheat sheet and the practice plan. On to Chapter 45.