Meetings, presentations & speaking on calls¶

At a glance

Priority: P0 · Complexity: ⅗ · Est. time: 3 h · Phase: 2 · Prereqs: Pace, pauses, filler words & clarity, Structuring spoken answers You're done when: you can open, signpost, interrupt, clarify, disagree and summarise in a live meeting using ready phrases, and you have delivered a 5-minute presentation with a timed structure and a call-tactics checklist you applied.

Drilled in Week 5 (facilitating), Week 8 (5-minute presentation), Week 11 (calls and video) and Week 20 (10-minute technical talk).

Why it matters¶

Most of your Staff-level influence happens in rooms you do not control: design reviews, incident bridges, planning, steering committees. In these settings, airtime, framing and timing matter as much as technical correctness. A correct point made late, mumbled or without a landing phrase disappears. On video calls, non-native listeners, latency, and muted or "one-way" formats amplify this.

Common gaps for a fluent non-native speaker who is technically senior:

Waiting for a perfect sentence, so the moment passes.
Interrupting either too little (never getting in) or clumsily (cutting people off).
Disagreeing too indirectly ("maybe we could consider...") so nobody notices, or too bluntly, which hurts relationships.
Not summarising, so decisions are not recorded and the meeting repeats itself.

Core concepts¶

1. The meeting speaking toolkit (the six moves)¶

Every useful contribution is one of six moves. Learn a phrase set for each.

A. Opening (a meeting or a section)

Purpose	Phrases
Open a meeting	"Thanks, everyone. We have 30 minutes, and we need to leave with a decision on X." · "Let's start with the goal: ..."
Set the agenda	"I'd suggest three items: A, B, and C. Does that work?" · "Let's timebox the first item to 10 minutes."
Open a presentation	"By the end of this, I'd like your decision on X." · "I'll cover three things: ..., ..., and ..."
Frame a review	"The question for this review is whether the design meets the latency target. I'm not asking about naming today."

B. Signposting

"First... second... finally..." · "Let me start with context, then the options, then my recommendation."
"Moving on to..." · "That brings me to the risks." · "Before I go on, any questions on this part?"
"To summarise so far..." · "Just to recap the three options:..."
"I'll come back to that in a moment." · "I'll park that for now." (US/UK informal: "park it")

C. Interrupting politely and entering the conversation

Situation	Phrases
Get in (video call)	"Can I add something?" · "Sorry to jump in, ..." · "Quick point on that." · Raise the hand feature, then "When there's a gap, I'd like to add..."
Interrupt someone rambling	"Sorry to interrupt: can I check I've understood? You're saying..." · "Let me stop you there for a second, ..."
Stop a side-topic	"That's important; can we park it and come back at the end?" · "Let's take that offline." (informal)
Handle being interrupted	"Let me just finish this point." · "One more sentence and then I'll pass it to you."
Interrupt a monologue on a bridge	"Time check: we're at ten minutes. Where do we stand on the decision?"

D. Clarifying

"Just to make sure I've understood: you mean X, not Y?" · "Can you say more about what you mean by 'stable'?"
"When you say 'soon', what timeframe do you have in mind?"
"Could you give an example?" · "What would success look like here?"
Paraphrase: "So the constraint is that the vendor API is unavailable before March. Have I got that right?"
Hearing problem: "Sorry, you broke up. Could you repeat the last point?" (better than "what?")

E. Buying time

"That's a good question; let me think about how to frame it."
"I don't have that number in front of me. My estimate is X, and I'll confirm by end of day."
"Let me check with the team and come back to you by tomorrow."
"Can I take that as an action, so I give you a proper answer?"

F. Disagreeing and pushing back (respectfully)

Use the agree-then-alternative and question-first patterns; hedge the tone, not the substance (see Conditionals, modals & hedging).

Strength	Phrases
Gentle	"I see it slightly differently." · "I wonder whether..." · "Could there be a risk that..."
Medium	"I understand the reasoning, but I'm concerned about X." · "I'd push back a little on that: ..." · "My worry is that..."
Direct (firm, still polite)	"I disagree with that, and here's why: ..." · "I don't think we can commit to that date, given X." · "I can't support this approach as it stands."
Question-first	"What would we do if the vendor misses the date?" · "How does this handle the peak season case?"
Alternative	"What if we ...?" · "An alternative would be..." · "Would it help if we phased it?"

Avoid: "That's wrong", "You don't understand", "No, but..." as a reflex; and avoid the bare "Yes, but" when you actually disagree, because it can confuse.

G. Summarising and closing

"Let me summarise what we've agreed: A, B, C. Owners and dates: ..."
"So the decision is X; the open question is Y, owned by Priya, due Friday."
"Before we finish, is everyone clear on the next step?"
"I'll send a written recap by end of day. Please correct me if I've missed anything."
Ending in a positive but specific way: "Thanks. That was a productive session."

2. Running a meeting (facilitating)¶

Purpose, outcome, agenda, timebox in the invite. A meeting without a decision or a shared output is a status broadcast; make it async.
Roles: facilitator, timekeeper, notetaker. Rotate them, and do not always take the notes yourself.
Airtime management: "Let's hear from people who haven't spoken yet." · "Sanjay, you've worked on this. What's your view?" (invite by name, but give a chance to opt out).
Parking lot: capture off-topic points in a visible list.
Decision record: the last 3 minutes are for decision, owner, deadline.
Facilitating a design review: ask the author to state the problem, constraints and options first; timebox questions per section; separate clarifying questions from critique.

3. Presenting: structure and delivery¶

A 5-10 minute presentation skeleton

Hook and stake (30 s): why this matters to this audience.
Ask or main message (15 s): "I want your approval on X."
Context (1 min): only what the audience needs.
Options or content (3-5 min): at most three parts; one visual per part.
Recommendation or summary (1 min): the same message.
Ask and next step (30 s).
Q&A.

Slide rules of thumb: one message per slide; the title is the takeaway ("p95 latency doubled after the migration"), not a topic label ("Latency"); numbers large; no more than about 30-40 words per slide; you speak the reasoning, the slide holds the evidence.

Delivery tactics

Memorise your first two sentences and your last one.
Pause after each slide transition; do not talk while clicking.
Look at the audience or camera on the key sentence, not at the slide.
Read numbers aloud with context: "eleven percent, up from two."
For jargon: define on first use, once.
Handle Q&A: repeat or paraphrase the question, answer in one to two sentences with PREP, and check: "Does that answer your question?" See Executive presence & handling Q&A.

4. Speaking on calls and video calls¶

Problem	Tactic
Latency and talking over	Wait about one second after someone stops. Use hand-raise or chat "+1" queue.
You never get in	Prepare one point in advance and say "I have a point on X when there's a gap." Use the chat as a signal.
Big group, poor audio	Slow to ~110-120 wpm; front-load the message; paste a summary in chat.
Accents and unfamiliar names	Confirm by paraphrase; spell names once; use text.
Overlap and interruptions	"Sorry, go ahead." then "Can I finish my point?"
Screen sharing	Announce: "I'm sharing my screen; can you see the diagram?" Narrate what you click: "I'm opening the trace for request 4471."
Silent room (no reactions)	Ask a specific question: "Ravi, does this match what you saw in staging?"
Multitasking temptation	Close chat apps; take handwritten notes to stay present.
Time zones	State time in both zones; recap in writing for people who missed it.

Phone-only or audio-only: voice carries all the information, so use more explicit signposts and slightly more pitch variation; state names before speaking in a group ("This is Rahul...").

5. Meeting language: register contrasts¶

Too blunt	Too vague	Just right
"That won't work."	"Maybe there might be some challenges."	"I'm concerned it won't meet the 200 ms target because of X. Could we test it first?"
"You're wrong about the deadline."	"The deadline could possibly be a bit tight."	"I don't think we can hit 15 March without dropping the reporting scope."
"Let's move on."	"Perhaps we might want to think about moving forward?"	"Let's move on; I'll pick this up offline with you."
"What?"	"Sorry?" (repeatedly)	"Sorry, could you repeat the last point?"

Resources¶

Resource	Type	Why this one	Level	Cost
Toastmasters International	community	Structured practice with evaluation for both prepared talks and impromptu speaking	all	freemium
TED	video	Study talk structure (hook, message, evidence, ask) and delivery; pick engineering talks	intermediate	free
Atlassian Incident Management Handbook	guide	Roles and phrases for incident calls: incident commander, comms lead, status updates	intermediate	free
BBC Learning English	audio/video	"The English We Speak" and business English series on meeting and interruption language	intermediate	free
Cambridge Dictionary	reference	Look up exact register labels (formal, informal) for meeting phrases	all	free
Presentation Zen (Garr Reynolds)	book	Slide design and delivery: one message, minimal text	intermediate	paid
Crucial Conversations (Patterson et al.)	book	Structured disagreement and high-stakes dialogue	intermediate	paid
YouGlish	interactive	Search "I'd push back", "let me play that back", "I wonder whether" to hear natural rhythm and stress	all	free

Hands-on lab (90 min)¶

Phrase card (15 min). Build a one-page card of 3 phrases per move (opening, signpost, interrupt, clarify, buy time, disagree, summarise) that you will actually use. Keep it visible on calls for a week.
Live experiment (over one week). In three real meetings, use one interrupt phrase, one clarifying question and one closing summary. Log what happened.
5-minute talk (40 min). Prepare and record a 5-minute presentation of a design decision using the skeleton above. Use a slide titled with a takeaway. Include one number stated with context.
Review (20 min). Watch with the checklist: hook in 30 s? message stated? signposts? pauses? final ask? Re-record the first minute.
Call tactics audit (15 min). Score your setup: mic distance, camera height, background noise, mute habit, chat summary habit.

Expected output: a phrase card, a three-meeting log, and a recorded 5-minute talk with a rubric score (see Shadowing & self-review method).

Questions¶

L1 — Recall¶

Q1. Name the seven functions in the meeting toolkit.

Answer

Opening, signposting, interrupting/entering, clarifying, buying time, disagreeing, summarising/closing.

Q2. What does "park it" mean, and what register is it?

Answer

Defer a topic to later, usually recorded on a "parking lot" list. Informal to neutral business English (common in both US and UK).

Q3. Give the recommended structure of a 5-10 minute presentation.

Answer

Hook/stake, main message or ask, context, up to three content parts, recommendation/summary, ask and next step, Q&A.

Q4. Why should slide titles be takeaways rather than topics?

Answer

A takeaway title ("p95 doubled after the migration") tells the audience what to conclude even if they only read titles, and forces you to know your message. Topic labels ("Latency") leave the interpretation to the audience.

L2 — Apply¶

Q5. A colleague is repeating a point for the third time on a bridge. Interrupt politely in one sentence.

Answer

"Sorry to jump in; I think we're aligned on that. Can we move to the rollback decision?" It acknowledges, gives a reason and redirects with a specific target.

Q6. Rewrite to disagree at medium strength: "Your estimate is wrong; it will take twice as long."

Answer

"I'd push back a little on the estimate: I think the data migration alone will take about six weeks, which would double the total. Could we walk through the assumptions?" States the concern, gives a specific reason and invites discussion.

Q7. You do not know the answer to an executive's question in the meeting. Write two options.

Answer

"I don't have that figure in front of me; my estimate is roughly 20%, and I'll confirm by end of day." Or: "Let me take that as an action and come back to you tomorrow with the exact figure." Never invent a number.

Q8. Write a 25-word closing summary for a meeting that decided to defer the migration to Q3, with Priya owning the vendor call by Friday.

Answer

"To summarise: we're deferring the migration to Q3. Priya owns the vendor call, due Friday. I'll send a written recap today; please correct anything I've missed." Decision, owner, date, follow-up.

L3 — Judge and choose¶

Q9. During a video call, a senior leader states an incorrect fact about your system. Compare: (A) correct immediately in the meeting; (B) message them privately; (C) ask a question. Which and why?

Answer

It depends on stakes. If it affects a decision in this meeting, correct now, gently: "Can I check one thing? I believe the dependency is on the v2 API, not v1; would it change the recommendation?" (C shading into A.) If it is minor or tone-sensitive, use B afterwards. Public corrections should be brief, factual and framed around the decision, not the person.

Q10. When is "Let's take this offline" a good idea, and when is it a problematic phrase?

Answer

Good: side topics, detail affecting only two people. Problematic: when used to avoid a hard disagreement or when it never happens. Follow it with an owner and time: "Let's take it offline: I'll set up 15 minutes with you tomorrow."

Q11. Is "I'm not sure I agree" a good disagreement phrase?

Answer

It is softened and polite but can be too vague: listeners may not register a disagreement. Fine as an opener; follow with the reason. If the issue is important, use a firmer phrase: "I don't think we should commit to that date, because...".

Q12. Choose which is better for a large call with non-native speakers: idioms ("let's not boil the ocean") or plain phrases. Defend.

Answer

Plain phrases: idioms are culturally specific and hard to parse under poor audio. Use a plain equivalent ("let's limit the scope") with an occasional idiom when the audience is known to understand. See Idioms for work and Listening, asking questions & cross-cultural communication.

L4 — Staff-level¶

Q13. You run a design review where one senior architect dominates and the junior authors go silent. What do you do?

Answer

Reset structure: "Let's take questions per section, one at a time." Invite the authors: "Ananya, what was your thinking on this trade-off?" Cap airtime: "Thanks, I'd like to hear from others before we come back." Ask for written comments in the doc for the remainder. In 1:1 afterwards, give the architect feedback (SBI). The aim is a review that surfaces the best ideas, not the loudest.

Q14. A VP interrupts your presentation at slide 2 with a question that your slide 8 answers. How do you respond?

Answer

Answer briefly now if it is the VP's priority: "Short answer: yes, it costs about $40k; I'll show the breakdown in a few slides." Or reorder: "Would you like me to jump to that now?" Do not say "I'll get to that" and withhold the answer. The audience's question defines the structure; keep control by proposing the path.

Q15. You must deliver bad news (a three-week delay) to a 20-person steering committee on a call. Outline your first 60 seconds.

Answer

Bottom line first: "The launch will slip by three weeks, to 22 November." Pause. Cause in one sentence: "The vendor API change forced us to rework the tracking integration." Impact: "No customer impact today; the risk is the peak-season window." Recovery: "We've added two engineers and cut reporting from scope; I'll present the options in the next five minutes and need a decision on scope today." No apologies loop, no blame. Post the same text in chat. See Executive updates, summaries & escalations.

Real-world use cases¶

Incident bridge: structured updates every 15 min, clear roles, chat summary.
Architecture review board: author states problem-options-recommendation; reviewers clarify then critique.
Quarterly planning: disagreement phrases used to challenge scope without personal conflict.
Vendor negotiation call: buying time and clarifying, disagreeing firmly (see Negotiation & saying no).
All-hands demo: narrate what you click; keep the message to three points.

Pitfalls & anti-patterns¶

Waiting to speak until you have the perfect sentence.
Starting a point with "sorry" three times (apologising for existing).
Saying "it's a bit tricky" when you mean "it will not work".
Dropping a decision without summarising owners and dates.
Reading slides aloud verbatim.
Talking while sharing a screen without telling people where to look.
Long context before the ask.
Assuming silence means agreement on a call.

Checklist¶

I have a phrase card with 3 phrases for each of the seven moves.
I opened, interrupted, clarified and summarised in real meetings and reviewed the result.
I gave a 5-minute presentation with takeaway-titled slides and a clear ask.
I have a call setup and etiquette checklist (mute, latency, chat recap).
I can disagree at three levels of firmness without changing the message.
I answered all L3 questions out loud in < 3 min each.