Meetings: speaking up, pushing back, closing

Meetings are live, unscripted, and social, which makes them the hardest channel for non-native speakers and introverts alike. The compensating good news: meeting English is highly formulaic. A few dozen stock moves cover interrupting, yielding, redirecting, clarifying, and closing, and using them smoothly is largely what "good in meetings" means.

Getting into the conversation

Interrupting politely is a legitimate skill, not a rudeness. The standard entries, from softest to firmest:

  • "Can I add something here?"
  • "Quick point on that:"
  • "Sorry to jump in, but this affects the decision:"
  • "Before we move on, one thing:"
  • "I want to flag something before we lock this in."

On video calls, use the raise-hand feature or type "quick point when there's a gap" in the meeting chat; both are fully professional. If you get talked over (it happens, accidentally and otherwise): finish anyway, calmly: "Let me just finish the thought: ..." Once is assertive; done evenly, it reads as composure, not conflict. And the mirror-image skill, for when you notice you interrupted: "Sorry, you were first; go ahead."

Two moves worth deliberate practice because they build others up while getting you the floor:

  • The return: "Going back to what Ana said a minute ago, I don't think we actually answered it." (Rescues lost points; the rescued person remembers.)
  • The invitation: "Yuki, you ran the last migration; what's your read?" (Brings in the quiet expert. Facilitators love people who do this unprompted.)

Clarifying and playing back

Asking for clarification in a meeting feels costly ("everyone else seems to follow") and almost never is; half the room usually shares your confusion. The stock phrases:

  • "When you say cache, do you mean the CDN or the application cache?"
  • "Can you say that another way? I want to make sure I'm following."
  • "Could we make that concrete? What would that mean for, say, the checkout flow?"

The power tool is the playback (also called mirroring): restating what you heard before responding to it. "Let me play that back: you're saying the migration is safe as long as writes are frozen, and the freeze needs two hours. Did I get that right?" Playbacks catch misunderstandings while they are still cheap, visibly honor the speaker, and buy you ten seconds to think. Negotiators, facilitators, and principal engineers all lean on this one constantly.

Don't be confused: "I don't follow" and "I don't agree" are different statements, and mixing them muddies meetings. "I don't follow the jump from X to Y" asks for the reasoning; "I follow the reasoning, and I disagree with the premise" is an objection (Chapter 5 applies). Saying "I don't understand" when you mean "I think that's wrong" is false modesty that confuses everyone; the reverse ("I disagree" when you actually just missed a step) starts fights about nothing.

Keeping a meeting on the rails

You do not have to be the organizer to steer; in fact, gentle steering from participants is a seniority signal. The moves:

  • The parking lot: "That's a real issue and I don't want to lose it, but it's not today's decision. Can we park it and I'll make sure it gets a thread?" (The parking lot is the list of deferred topics; the credibility rule is that parked items must actually get followed up.)
  • The scope check: "We're solving next year's problem; can we come back to the Q3 question?"
  • The timebox: "We have ten minutes left and two decisions to make; can we spend five on each?"
  • The rathole call: "We're three levels deep on a detail; I suggest we take it offline and get back to the main thread." ("Rathole" is the affectionate term for an unplanned deep tangent.)
  • The decision forcing move: "I'm hearing broad agreement on A with concerns about the timeline. Can we decide A-in-principle and assign the timeline question to someone?"

Disagreeing live

Everything from Chapter 5 applies, compressed by real time. The live-specific additions:

  • Acknowledge before countering: "I see the appeal, especially the cost side. Where I get stuck is the failure story: ..." The acknowledgment is not a concession; it is proof you listened, which is what earns you the room's attention for the counter.
  • Disagree with the last speaker without making it personal: address the idea's content, not "what Marcus just said": "The shared-queue approach worries me because..." rather than "Marcus is wrong because..."
  • When outnumbered and time is short, register and move: "I'm the minority view here; I want it noted that I think the retry budget is too low, and I'm fine proceeding if we add an alert on it." Registered dissent plus a concrete mitigation is the graceful minority position.
  • When it gets heated: slow down, drop volume, get concrete. "Let's take the temperature down a notch; I think we actually agree on the goal. The disagreement is only about sequencing, right?" Naming the shared ground shrinks the fight to its real size.

Presenting to executives and skip-levels

A special register, because senior leaders optimize ruthlessly for time:

  • Answer first. Executives ask "can we ship in March?"; the answer begins "Yes, if X" or "No, because Y", not with background. If they want the journey, they will ask. (This inverts the engineer's instinct to build up context before conclusions; fighting that instinct is the single highest-value habit in this section, and Chapter 16 drills it as a general structure.)
  • Know your one number. Whatever the meeting is about, have its central quantity loaded: the cost, the latency, the date, the headcount. "I'll get back to you" on the central number of your own topic is a bad look; on peripheral numbers it is fine and honest.
  • Flag uncertainty in ranges, not winces: "Between six and ten weeks; I'll have it to plus or minus a week after the spike" beats "umm, hard to say, it depends."

Closing: decisions, owners, dates

Meetings without written outcomes did not happen. The closing ritual, which anyone in the room can perform:

Before we drop: capturing what we decided.
1. We're going with per-tenant queues (option A). Dana signs off by Fri.
2. Ravi owns the sizing spike, results next Wednesday.
3. Parked: the multi-region question; I'll open a thread today.
Did I miss or mangle anything?

Then post exactly that to the channel or doc. The formula is decision, owner, date for every outcome; anything lacking one of the three is not yet an outcome. The person who reliably does this becomes, in the eyes of everyone senior, the person who makes meetings worth having.

Also part of closing well: declining meetings you should not be in ("I don't think I add much here; I'll read the notes, and ping me if the storage question comes up") and leaving ones that no longer need you ("I need to drop for another commitment; my input is in the doc, and I'm good with either option on the open question"). Both, said plainly, are marks of someone who treats time as shared property.

👉 Everything in this chapter assumed someone else was running the session. Sooner or later that someone is you: chairing the design review, driving sprint planning, hosting the brown bag, moderating the Q&A. The front-of-the-room phrasebook is next. On to Chapter 9.