Scenarios: following and being heard in meetings

Live meetings move fast, and English at speed is where a lot of otherwise-strong engineers stall: you lose a question, you need a beat to think, the audio drops, or someone talks over you. This chapter is a dense bank of real exchanges shown from both chairs, the person struggling to follow and the person running the room, so you can grab a line and use it. Each one keeps the same move: soften the person, keep the substance sharp, and land on a next step or a specific fact rather than just politeness.

You did not understand a question

Question landed but the meaning did not. Q: "So how are you going to handle the backfill?" A: "Sorry, do you mean the historical rows or the new writes during migration? I want to answer the right one."
Ambiguous "it" in the question. Q: "Is it going to be ready by Thursday?" A: "By 'it' you mean the search endpoint, not the whole dashboard? The endpoint yes, the dashboard is next sprint."
You caught words, not intent. Q: "What's your thinking on the consistency model?" A: "Can you point me at what's worrying you? If it's read-after-write on the profile service, I can speak to that."
Reviewer asks something you did not parse. Q: "Why aren't you idempotent here?" A: "Let me make sure I follow: you mean the retry could double-charge? Say more and I'll answer directly."
Manager's question is too broad. Q: "Where are we on quality?" A: "Happy to answer. Do you want the flaky-test count, the p99, or the open bug list? I have all three."
You froze on a term in the question. Q: "Can we make this a sidecar?" A: "One sec, when you say sidecar do you mean a separate container in the same pod? Want to be sure before I say yes."
Other chair: you rephrase for someone stuck. Q: "Sorry, I don't think I understood the question." A: "My fault, let me rephrase: does the new rate limit apply per user or per API key?"
Question had two parts, you got one. Q: "Can you ship it this week, and does it need a migration?" A: "Two things there: ship, yes Wednesday; migration, no, it reuses the existing table."
You want to confirm before committing. Q: "You'll own the on-call handoff doc?" A: "To check I heard right: I write the runbook, you review it Friday? If so, yes."

You need more time before answering

Asked for a number you do not have. Q: "What's the blast radius if this fails?" A: "Give me thirty seconds, I want to check how many services call it before I guess."
Good question, no snap answer. Q: "Should we roll this into the platform team's work?" A: "That's a real decision, not a hallway yes. Let me think and reply in the thread by end of day."
You are being pushed for a date live. Q: "Just give me a date." A: "I'd rather give you a date I'll hit. Let me size it after this call and post it in the channel within the hour."
Question deserves the doc open. Q: "Can the cache handle Black Friday load?" A: "Let me pull the last load test before I answer, I don't want to go from memory on that one."
Buying a beat mid-sentence. Q: "So what's your recommendation?" A: "Let me sit with that for a second. Okay: option B, because it doesn't touch the auth path."
Other chair: you grant the pause. Q: "Can I get back to you on the exact latency?" A: "Of course, no need to guess. Drop it in the thread whenever you've checked."
You need to talk to someone first. Q: "Are you okay owning the vendor migration?" A: "I want to, but let me confirm capacity with Priya first and I'll answer by standup tomorrow."
Deflecting a trap for a real answer. Q: "Simple question, yes or no?" A: "It's genuinely a maybe, and a wrong yes costs us a week. Give me till 2pm and you'll get a real one."
You need the ticket in front of you. Q: "Did we account for the eu-west region here?" A: "Let me open the ticket, I don't trust my memory on region coverage."
Other chair: you offer to take it offline. Q: "I don't have the throughput numbers on hand." A: "No problem, that's not a live question. Send them in the channel after and we'll pick it up there."

You missed part of the conversation

You dropped off for ten seconds. Q: "So we agreed Dana takes it, right?" A: "Sorry, I lost the last bit. Can someone recap the last minute? I want to be with you."
You were on mute fixing audio. Q: "Any objection to that plan?" A: "I missed the plan, honestly, my audio cut. Two-line version before I vote?"
Thread scrolled past you. Q: "Following the doc I linked above?" A: "I don't see the link on my end, can you repost? Chat may have eaten it."
You joined the meeting late. Q: "Glad you're here, thoughts?" A: "Just joined, so catch me up in a sentence: are we deciding the queue tech or the timeline?"
Screen share froze on your side. Q: "See the error on line 12?" A: "Your screen's frozen for me, still on the login page. Can you re-share?"
Other chair: you rewind for the late joiner. Q: "Sorry, what did I miss?" A: "Quick recap: we hit a deadlock in staging, Ravi has a fix up, we're deciding whether to hotfix or wait for the release."
Two people talked at once and you lost both. Q: "So, agreed?" A: "You two overlapped and I caught neither. Can each of you give me the one-liner?"
You realize a decision passed you by. Q: "We're going with Postgres then." A: "Wait, when did we rule out DynamoDB? I want to make sure I'm not missing the reason."
Other chair: you notice someone drifted. Q: "Sam, you've gone quiet on us." A: "Sam, did that land, or did I lose you at the sharding part? Happy to back up."

You were not paying attention when asked

Caught looking away, own it clean. Q: "Yuki, what do you think?" A: "Honestly you caught me half in the incident channel, give me the question again and you'll have my full head."
You context-switched and missed it. Q: "Your call, ship or hold?" A: "Sorry, I was in a pager alert, can you repeat that? I don't want to answer the wrong question."
Named suddenly out of silence. Q: "Tomas? You've been quiet." A: "I was, I'll be straight: I zoned for a minute. What's the specific ask?"
You were reading the code being discussed. Q: "Do you agree with that estimate?" A: "I was heads-down in the diff you shared, so I missed the number. What estimate landed?"
Other chair: you re-ask without shaming. Q: "Uh, sorry, could you repeat that?" A: "No problem: does the payments team need this before or after their freeze?"
You admit it and redirect fast. Q: "Thoughts?" A: "I'll be honest, I lost the thread. Give me the one-sentence version and I'm right there."
Double-booked and half-listening. Q: "You good to present the design now?" A: "I was split across two calls, give me ten seconds to close the other and I'm fully here."
Other chair: you let a drifting teammate off easy. Q: "Sorry, I completely blanked, what did you ask?" A: "All good, it's a long meeting. I asked whether the auth work is on track for the freeze."

Asking someone to repeat or simplify

You need it once more, plainly. Q: "Which is why the coordinator fans out to the shards asynchronously." A: "Can you run that by me once more, slower? I lost you at the fan-out."
Jargon-dense answer, ask for plain. Q: "It's an eventually-consistent CRDT merge on conflict." A: "Say it like I've been out of the room: what happens when two people edit the same row?"
Acronym you do not know. Q: "We'll gate it behind the CDC pipeline." A: "What's CDC in this context? Want to be sure I'm picturing the right thing."
Ask for the shape, not the detail. Q: "And then it recomputes the whole projection." A: "Before the details, give me the one-sentence shape: what does this change for the user?"
Other chair: you offer to simplify. Q: "I think I follow, mostly." A: "Let me try it plainer: the old code retried forever, the new code gives up after three tries. That the part?"
You want the example, not the theory. Q: "It's a general backpressure mechanism." A: "Can you give me one concrete example? A real request going through it would help me a lot."
Fast explanation, ask to chunk it. Q: "So auth calls the vault, vault checks the policy, policy hits the cache, cache misses, then..." A: "Let's take it one hop at a time. First hop: auth calls the vault, why?"
Other chair: you check they got it. Q: "That was a lot, fast." A: "It was. Want me to redo it as a diagram, or was that clear enough to move on?"
Whiteboard moved too quick. Q: "And that arrow is the retry loop." A: "Can you go back one box? I lost which service owns the retry."

Asking someone to speak more slowly

Speaker is racing, kindly slow them. Q: "So what we're doing is moving the consumer group over and..." A: "Can I slow you down a touch? I want to catch all of it, not half."
You are taking notes and can't keep up. Q: "Three steps, first the flag, then the migration, then the cutover, done." A: "One at a time so I can write them down. First step again?"
Non-native ear, be honest and warm. Q: "It's basically a no-brainer, we just slap a queue in front." A: "You're a bit fast for me, no worries, just a notch slower and I'm with you."
Numbers went by too fast. Q: "p50 is 40, p99 is 900, budget's 300." A: "Slower on the numbers, please: p99 was nine hundred?"
Other chair: you self-correct your pace. Q: "Sorry, was that too quick?" A: "It was on me, I'll slow down. Rewinding: the config lives in the vault, and only the proxy reads it."
Live demo narrated too fast. Q: "Click here, then here, and it's deployed." A: "Can you narrate that a step slower? I want to reproduce it after."
Other chair: you pace for the room. Q: "Everyone still with me?" A: "I'll go slow here since it's the tricky part, stop me if I'm too fast."

Words aren't landing, ask to see it. Q: "The error is in the middleware, it's obvious." A: "Can you share your screen? Easier if we both look at the same stack trace."
You want the exact line. Q: "It fails somewhere around the parser." A: "Mind sharing the file? Point me at the exact line and I'll follow better."
Config drift, see the real values. Q: "Staging has the right settings, I promise." A: "Can you pull up the config and share? Let's read the actual values together."
Other chair: you offer to share first. Q: "I'm not picturing what you mean." A: "Let me just share my screen, one sec, this is faster to show than to say."
Dashboard beats description. Q: "Latency's been weird all morning." A: "Can you throw the Grafana board on screen? I want to see the shape of the spike, not just hear 'weird'."
Ask them to scroll to a spot. Q: "It's all in the PR." A: "You're sharing, can you scroll to the migration file? That's the part I'm unsure about."
Other chair: you check they can see it. Q: "Can everyone see my screen?" A: "Yes, but it's tiny on my end, can you bump the font? I can read it now, go ahead."

Saying you cannot hear the speaker

Audio dropping in and out. Q: "And the plan is (cutting out) by Friday." A: "You're breaking up, I got 'plan' and 'Friday' and nothing between. Can you repeat?"
They are far from the mic. Q: "Should we hold the release?" A: "You're really quiet on my side, can you get closer to the mic? Barely hearing you."
Room echo in a hybrid meeting. Q: "Does that work for everyone?" A: "There's a bad echo from the room, can whoever's in the office mute the extra laptop?"
Other chair: you catch you're on mute. Q: "You're on mute." A: "Classic, thanks. Starting again: the vendor confirmed the fix ships Tuesday."
Background noise drowning them. Q: "The point is the timeout, right?" A: "There's a lot of noise behind you, I lost the point. Can you find a quieter spot or type it?"
Ask them to switch to typing. Q: "Can you hear me at all?" A: "Your audio's rough today. Can you drop the key part in chat so we don't lose it?"
Other chair: you fix your own audio. Q: "We can't hear you well." A: "Give me one second, switching to headphones. Better? Okay, as I was saying."
Only one person can't hear. Q: "You following, Noor?" A: "Audio's fine for the room but muddy for me, must be my end, I'll rejoin. Keep going, I'll catch the recap."

Someone keeps interrupting you

Cut off mid-point, hold your line warmly. Q: "Yeah but the real issue is..." A: "Let me finish this one thought, it's ten seconds, then it's yours."
Second interruption, name it lightly. Q: "Actually, I think..." A: "Hang on, I keep getting cut off, let me land the point and I genuinely want your take right after."
They finish your sentences wrong. Q: "So you're saying we drop the feature." A: "Not quite, let me get there myself: I'm saying we ship it behind a flag, not drop it."
Other chair: you protect an interrupted teammate. Q: "As I was saying about the budget..." A: "Hold on, Ines was mid-sentence. Ines, finish, then Ravi you're up."
Reclaim after being talked over. Q: "(talks over you)" A: "I'll pause, go ahead, finish. Okay, back to what I was saying about the retry budget."
Interrupter is your manager. Q: "Let me jump in here." A: "Sure, go. One thing I'd love to close first though: the number you asked for is 12ms."
Other chair: you make room for the quiet one. Q: "Anyway, moving on to the rollout." A: "Before we move on, I cut Sam off earlier. Sam, what were you going to say?"
Chronic interrupter, set the pattern. Q: "Wait, but..." A: "I'll get to that, promise. Let me finish the thought so we're not half-answering."
Other chair: you catch yourself cutting in. Q: "So the fix touches three services and..." A: "Sorry, I jumped in on you. Go back to the three services, finish your point."

Someone dominates and blocks others

One voice has held the floor for minutes. Q: "And another thing about the architecture..." A: "Good points. I want to pull in the others before we go deeper, we haven't heard from the backend folks."
Steer airtime without a fight. Q: "I really think my approach is the only sane one." A: "Let's put both on the board and hear Dana's, she owns that service and hasn't spoken yet."
Other chair: you're the chair, open the floor. Q: "So that's why we should do it my way." A: "We've had a lot from one corner, which is useful. Priya, Tomas, what are we missing?"
Dominator repeats a settled point. Q: "As I said, the queue is the answer." A: "We heard that and it's noted. What I still need is the cost, can someone who's been quiet weigh in?"
Protect the agenda from a monologue. Q: "Which reminds me of a project back in 2019..." A: "Love the story, let's park it. We have eight minutes and one decision to land, back to the rollback plan."
A junior keeps getting spoken over. Q: "Yeah yeah, but the fix is simple." A: "Let's hear Yuki's version in full, no interruptions, she was closest to the incident."
Other chair: you name the imbalance gently. Q: "I've got a few more points on this." A: "I notice three of us have done all the talking. Going around the room, one sentence each, starting with Noor."
Redirect to a decision, not more debate. Q: "But I have more concerns about the design..." A: "Fair, and I don't want to lose them. Put them in the doc so we can decide today and address them there."

Don't be confused: "I don't understand the question" and "I don't have the answer yet" are different admissions, and mixing them costs you credibility. The first asks the room to clarify; the second asks the room to wait. Say which one you mean, because "let me think" when you actually didn't parse the question just delays the real clarification.

Don't be confused: slowing a speaker down is not the same as challenging them. "Can you go slower?" is about your ear, not their idea. If you actually disagree with the content, that is a different move (see Chapter 26); don't let a comprehension pause read as pushback, and don't hide real pushback inside a "wait, slower" either.

👉 Following a room is half the skill; the other half is bending it toward a decision when it drifts. On to Chapter 49.

Professional English for Software Engineers