Module 5: Spoken Technical English
4. Meetings: Taking and Holding the Floor
Description
There's a scene almost every Spanish-speaking developer knows: the meeting moves forward, you have something valuable to say, you wait for the perfect gap to jump in — and the gap never comes. Someone else talks, the topic shifts, and your point stays inside. It wasn't that you didn't know the English. It was that you didn't know the mechanics: when to jump in, how to signal that you're about to speak, how not to lose the floor mid-sentence. Those mechanics can be learned, and that's what you're going to work on here.
The good news is that a work meeting isn't free-form conversation. It's a space with rules, with turns, with set phrases everybody uses. You don't need general conversational fluency to function in it; you need a handful of fixed formulas and the ability to read the right moment to use them. This is exactly what this guide promises: technical work communication. You're not going to improvise like a public speaker; you're going to operate a machine with known buttons, and those buttons are phrases you can have written in front of you.
Connection to the module: In the previous lesson you learned the standup, your first timed and scripted intervention. The standup is a short monologue: you speak, you finish, the next person goes. This lesson makes the jump to the interactive meeting, where the challenge is no longer what to say but when and how to jump in without getting run over. It's the skill that separates "I was in the meeting" from "I participated in the meeting." The next lesson will take one concrete piece of this — asking for clarification — and work on it in depth; here we mention it in passing, without exhausting it.
Before you start: where you're standing
This lesson assumes the whole guide's floor: you already read technical English with ease and can hold about two minutes of speech, with mistakes. If in a meeting you understand 70 percent of what's said and can form sentences even if they come out crooked, you're at the right level to work on turn-taking. Everything that follows is tactics, not English from zero.
If, on the other hand, a spoken meeting leaves you almost completely lost — you can't make out words, you can't form a sentence under pressure — the honest path isn't this lesson yet, but more general speaking and listening practice before you come back. That's fine: it's the right sequence, not a failure. This lesson pays off once you already have something to work with; forcing it without the floor just piles up frustration.
One thing that takes the pressure off right away: in a technical meeting nobody expects you to speak perfectly. The distributed teams of 2026 are full of accents — Indian, Brazilian, Polish, Filipino, your Latin American accent. The real standard isn't sounding native; it's being intelligible and clear. A grammar mistake that doesn't break the meaning is invisible in a meeting. What does stand out is not participating. Let's fix that.
The mechanics of the floor: what's really going on
Before the phrases, understand the physical problem. In an in-person meeting, the floor gets negotiated with the body: you lean in, open your mouth, someone sees you coming and yields. In an eight-person video meeting, all of that disappears. Nobody sees your body language, there's latency — the delay between when you speak and when others hear you, half a second or more — and if two people start at the same time, the audio collides and both go quiet out of courtesy. The result is that introverts and non-native speakers get shut out by the sheer physics of the channel, not by a lack of ideas.
The solution has three moves, and it's worth naming them because you're going to use them constantly:
| Move | What it is | What it's for |
|---|---|---|
| Signaling | Announcing you're about to speak before you say your point | Reserves the floor; others yield to you |
| Anchoring | Opening with a fixed phrase that occupies the channel | Buys you a second to think without giving up the floor |
| Closing | Explicitly marking that you're done | Stops someone from cutting you off thinking you already finished |
The useful analogy: asking for the floor in a video meeting is like merging onto a highway. You don't slow down waiting for a perfect gap — it doesn't exist. You speed up in the merge lane (you signal), you merge in decisively (you anchor), and once you're in you hold your speed to your exit (you close). Hesitating is the only thing that causes crashes.
What to expect: the first few times it'll feel abrupt, almost rude, to jump in with a fixed formula instead of politely waiting. It isn't. In Anglo meeting culture, signaling that you're about to speak is the polite and expected move. Prolonged silence is what reads as disengagement.
Signaling: how to reserve the floor
Signaling means saying a short phrase that means "I'm about to speak, give me the floor." It doesn't state your point yet; it just claims the space. It's the single most important tool in this whole lesson, because it solves the number-one problem non-native speakers face: waiting so long for the perfect moment that the moment never comes.
Phrases for signaling (in English, use them as they are):
"Can I jump in here?" — ¿Puedo entrar aquí? The most common and natural one on tech teams.
"I'd like to add something." — Quisiera agregar algo.
"Quick point on that." — Un punto rápido sobre eso. Promises brevity, which lowers resistance.
"Building on what Sarah said…" — Sumando a lo que dijo Sarah… Hooks onto whoever just spoke; very hard to turn down.
On video, combine the phrase with a raised hand on camera or the platform's "raise hand" button. The hand is your visual signal; the phrase is your audio signal. With both, it's almost impossible to get ignored.
There's an optimal moment to signal: when the speaker is wrapping up an idea, not in the middle of one. Listen for the falling intonation — in English, pitch drops at the end of a complete statement. That drop is your green light. Jumping in right there reads as good rhythm; jumping in during a rising pitch reads as an interruption.
Anchoring: not losing the floor mid-sentence
You already have the floor. Now the danger is different: you're stuck thinking about how to say something in English, you pause for two seconds, and in those two seconds someone assumes you're done and jumps in. You lost the floor while holding it in your hand.
The anchor is a filler phrase that occupies the channel while your head puts the idea together. Native speakers use them constantly; they're not nervous tics, they're signals of "I'm still talking, don't interrupt me." Having them ready is what buys you thinking time without handing over the microphone.
| Anchor in English | Translation / use |
|---|---|
| "So, the thing is…" | La cosa es que… Opens any explanation. |
| "What I mean is…" | Lo que quiero decir es… Rephrases when the first sentence came out wrong. |
| "Let me put it this way…" | Déjame ponerlo así… Gives you a full second to reorganize. |
| "There are two things here…" | Hay dos cosas aquí… Announces structure and reserves double the floor time. |
| "Bear with me for a second…" | Aguántame un segundo… Asks for patience while you think; totally acceptable. |
The classic non-native mistake is filling the pause with a Spanish "eeeh" or with silence. Silence invites people to cut you off. An anchor in English does the opposite: it holds the door open.
Analogy: the anchor is like putting your hand on the elevator door while you shift your bags around. You haven't fully stepped in, but the door isn't closing on you either. "Let me put it this way…" is that hand on the door.
The ace up your sleeve: written notes
Here's the worst-kept secret of people who look fluent in meetings: they almost always have notes in front of them. They're not improvising; they're reading, or at least leaning on a script they put together beforehand. And on video, nobody notices, because you're looking at the camera and your notes are on the same screen.
This changes everything for anyone who suffers from "my mind freezes in English." You don't have to generate English in real time under pressure. You have to read English you prepared calmly. And reading is your strongest skill — it's this guide's floor.
Before a meeting where you know you'll speak up, prepare a card with:
- Your main point, written as a complete sentence in English. Not a vague bullet — the exact sentence you're going to say. Example: "I think we should ship the fix behind a feature flag before the full rollout."
- One or two signaling phrases from the previous section, to open with.
- Two or three key technical terms you're afraid of mispronouncing, with their spelling in front of you so you don't hesitate.
- A backup question, in case someone asks you something and you need to return the ball with something prepared.
What to expect: with the card in front of you, the feeling shifts from "I have to invent English right now" to "I have to read this line at the right moment." The challenge drops from two problems (what to say + when) to just one (when). That's the entire difference between freezing up and participating.
The four moves of the body of the meeting
You already know how to get in and hold on. Now the four things you actually do inside a technical meeting: circling back to a point, disagreeing, proposing an action, and closing a topic. Each one has its formula.
Circling back to a point that got skipped
The conversation moved on and your idea got left behind unaddressed. Don't abandon it — bring it back by naming it explicitly.
"Going back to what I mentioned earlier…" — Volviendo a lo que mencioné antes…
"I don't think we closed the point about the migration." — No creo que hayamos cerrado el punto de la migración.
"Before we move on, can we finish the earlier topic?" — Antes de seguir, ¿podemos terminar el tema anterior?
Naming the point that got left dangling signals that you're following the meeting closely. Far from looking like a step backward, it reads as rigor.
Disagreeing without confronting
This is the one that scares people the most, and the most valuable. In Anglo work culture, disagreeing is normal and expected — but the packaging matters enormously. The universal formula is: validate first, disagree after, and frame the disagreement as a doubt, not an attack.
| Soft packaging (recommended) | What it communicates |
|---|---|
| "That makes sense, but I'm worried about…" | Tiene sentido, pero me preocupa… You validate, then flag the risk. |
| "I see it a bit differently." | Lo veo un poco distinto. Marks disagreement without denying the other person. |
| "Have we considered…?" | ¿Hemos considerado…? Disguises your objection as an open question. |
| "I might be missing something, but…" | Quizás se me escapa algo, pero… Gives you an out if you're wrong and lowers the other person's guard. |
Avoid the direct attack. "That's wrong" or "No, that won't work" are technically correct English, but they shut the conversation down and cost you political capital. The same idea with "I'm worried that approach might not scale" says exactly the same thing and makes you look like someone people enjoy working with.
What to expect: at first, softening this much will feel like it makes you look insecure. It doesn't, in this culture. Soft packaging is the mark of a senior professional, not an insecure one. Confidence comes across through clarity of the point, not the harshness of the tone.
Proposing an action
A meeting with no agreements is wasted time, and whoever proposes the concrete action gains visibility. The formula is direct: name the action, and if you can, the owner.
"So the next step would be to test this on staging first." — Entonces el siguiente paso sería probar esto en staging primero.
"Can we agree that I'll open a ticket and Ana will review it?" — ¿Podemos acordar que yo abro un ticket y Ana lo revisa?
"Let's timebox this to Friday and reassess." — Pongámosle límite hasta el viernes y reevaluamos.
Notice the pattern: action + owner + deadline. Those three things turn a conversation into an agreement.
Closing a topic with an explicit agreement
The most common mistake at the end of a discussion is assuming everyone understood the same thing. Don't assume it: close out loud, summarizing the agreement. This is called making the implicit explicit, and whoever does it earns a reputation for being organized.
"Okay, so to summarize: I'll do X, Ana does Y, we sync on Thursday. Does that work for everyone?" — Bien, resumiendo: yo hago X, Ana hace Y, sincronizamos el jueves. ¿Le sirve a todos?
"Just to confirm we're aligned: we're going with option B, right?" — Solo para confirmar que estamos alineados: vamos con la opción B, ¿cierto?
Ending with "Does that work for everyone?" forces an explicit yes and avoids the classic misunderstanding where everyone walks away with a different idea of what was agreed.
When someone talks over you
It's going to happen, especially because of video latency. Two people start at the same time and the audio collides. Here's the cultural trap: the non-native reflex is to always yield — go quiet out of politeness and insecurity. Yield once and nothing happens; yield every time and you disappear from the meeting.
The healthy rule: yield the first collision, recover with a phrase, and don't let go the second time.
When voices collide:
"Sorry, go ahead." — Perdón, sigue tú. You cleanly yield the first collision. No guilt.
And as soon as the other person finishes, you recover immediately — don't wait for a new gap, because it won't come:
"Okay — so what I was saying was…" — Bien, lo que estaba diciendo era…
"To finish my earlier thought…" — Para terminar la idea que tenía…
If they cut you off midway and you want to hold the floor without yielding, a firm but polite phrase works:
"Let me just finish this point." — Déjame terminar este punto. Firm, not aggressive. It's perfectly acceptable.
What to expect: saying "let me just finish this point" is going to feel bold the first time. In practice, nobody minds; it's a completely normal meeting phrase. Seniors use it without blinking. The boldness is your perception, not the listener's.
The other half of the floor: understanding what's being said
Taking the floor doesn't help if you didn't understand what was said before your turn. And here's a reality almost nobody prepares for: in a 2026 meeting you're going to hear English with non-native accents, sometimes with bad audio, and often fast. Understanding a slow, clean podcast doesn't prepare you for this. Meeting listening trains separately, with its own method.
Three steps to train it, from easiest to most real:
| Step | What to practice with | What you're training |
|---|---|---|
| 1. Clean and clear | Recorded technical talks, subtitles available | Technical vocabulary by ear |
| 2. Varied accents | Conference recordings with speakers from India, Brazil, Eastern Europe | Tolerance for non-native accents |
| 3. Real conditions | Recorded meetings from your own team, or podcasts without subtitles at 1.25x | Imperfect audio, speed, overlap |
Don't skip from step 1 to step 3. Most people only practice with clean audio and then are surprised they can't understand an Indian colleague on a cheap microphone. Accents and bad audio are trainable skills; you get your ear used to them through deliberate exposure, not all at once in a real meeting.
And when you still didn't understand something — which will happen — asking for a repeat isn't weakness. It's the central tool of the next lesson, so here we just flag it: losing a piece of information out of embarrassment to ask costs far more than the question does. How to ask for clarification without it sounding like you understood nothing is exactly what you'll work on next.
A minimal meeting script, start to finish
Put it all together in a sequence. Imagine a design meeting where you want to propose using a feature flag. Here's what the full arc looks like, with the pieces you already have:
- You signal when the speaker's tone drops: "Can I jump in here? Quick point on the rollout."
- You anchor to buy time: "So, the thing is, there are two risks I want to name."
- You disagree softly if needed: "That makes sense, but I'm worried the full rollout is risky."
- You propose an action: "So the next step would be to ship it behind a feature flag first."
- You close the agreement: "Just to confirm we're aligned: flag first, then full rollout on Friday. Does that work for everyone?"
Five sentences. None improvised — all of them fit on a card in front of you. That's a complete, competent contribution to a technical meeting, and it doesn't require any kind of general conversational fluency. It requires these formulas and an eye for the right moment.
Your practice this week
Between this lesson and the next, fold this into your practice cadence:
- Build real meeting cards. Before your next work meeting (or a simulated one), write the four-point card: your main sentence in English, two signaling phrases, three technical terms, one backup question.
- Record a five-sentence intervention following the arc above, about a technical topic of your own. Listen to it. Don't chase perfection; chase being understood and having the formulas come out naturally.
- Train listening at step 2 or 3 at least twice: a conference with a non-native-accented speaker, no subtitles, and note three sentences that gave you trouble.
- In your next real meeting, set yourself one goal: use a single signaling phrase to jump in. Just one. The goal isn't to shine, it's to break the silence with a formula. The second time will cost half as much.
This module's gate still stands: don't force the oral part if the speaking floor isn't there. But if you've made it this far forming sentences with mistakes, you already have something to work with. What was missing wasn't more English — it was the mechanics of the floor. Now you have them.
Exercises
Work through each one before checking the solution. There's no trick here: the mechanics of turn-taking are learned by recognizing them first and producing them after, so the first exercises are about recognition and the last one is about your own production.
1. Classify each phrase: does it signal, anchor, or close?
For each phrase, decide whether its function is to signal (reserve the floor before speaking), anchor (occupy the channel while you think), or close (mark that you're done or that there's agreement).
- a) "Can I jump in here?"
- b) "So, the thing is…"
- c) "Does that work for everyone?"
- d) "Bear with me for a second…"
- e) "I'd like to add something."
- f) "Just to confirm we're aligned: we're going with option B, right?"
See solution
a) Signals — asks for the floor before stating the point. b) Anchors — opens an explanation without saying anything yet. c) Closes — forces an explicit yes from the whole group. d) Anchors — asks for patience while you think. e) Signals — announces that you're about to contribute something. f) Closes — summarizes the agreement and asks for confirmation.
Why this works: the three categories correspond to three different moments of the turn — before you have it, while you're holding it, and when you deliberately let it go. If you mix a closing phrase in with an anchoring intention (for example, using "does that work for everyone?" halfway through your own explanation), you confuse the listener about whether you're done or not.
2. Rewrite this disagreement with soft packaging
Someone proposes doing the full rollout on Friday. Your raw internal reaction is: "That's wrong, a full rollout on Friday is too risky." Rewrite it applying the formula: validate first, disagree after, frame it as a doubt rather than an attack.
See solution
A version that meets the formula: "That makes sense, but I'm worried a full rollout on Friday might be risky before we test it on staging." Another equally valid one: "I might be missing something, but I think shipping the full rollout on Friday could be risky."
Why this works: neither one denies the other person or uses "wrong" — both validate first ("that makes sense" / leave the door open to being wrong) and turn the objection into a concern or a doubt, not a veto. The technical content is identical to the original; the only thing that changes is the packaging, and the packaging is what decides whether people keep listening to you next time.
3. Choose the best way to recover the floor
You're halfway through your point and someone interrupts you. You already yielded once this meeting. Which of these options holds the floor without sounding aggressive?
- A) "Excuse me, I was talking."
- B) "Let me just finish this point."
- C) You stay quiet and let the other person continue.
- D) "That's rude, let me speak."
See solution
The correct answer is B.
Why this works: "Let me just finish this point" is firm without being aggressive — it names the action (finishing your point) without accusing anyone. A) and D) point at the other person as the guilty party, which raises the meeting's tension unnecessarily. C) is yielding a second time, and this lesson's rule is clear: yield the first collision, but not the second — always yielding is what erases you from the conversation.
4. Build your own meeting card
Pick a real technical topic of your own — something you genuinely want to propose in your next team meeting. Write the four elements from the "The ace up your sleeve" section's card: (1) your main point as a complete English sentence, (2) a signaling phrase, (3) two or three technical terms you're afraid of mispronouncing, (4) a backup question.
See solution
There's no single correct answer because the topic is yours, but here's what a well-built card looks like, using as an example a proposal to add a caching layer:
- Main point: "I think we should add a caching layer before the next release, because the database is getting hit on every request."
- Signaling: "Quick point on the performance issue."
- Terms: caching layer, database, request.
- Backup question: "What's our current tolerance for added complexity this sprint?"
Why this works: every element is written as an exact sentence, not a vague bullet — that's what lets you read instead of generate English under pressure, which is the whole point of the card. If your version has complete sentences and not loose ideas, your card is ready to use as-is in a real meeting.
Summary and next step
Before moving on to the next lesson, you should be able to:
- Recognize and use at least two signaling phrases and two anchors without having to think them up from scratch.
- Disagree using the soft-packaging formula (validate, then object, framed as a doubt) without it sounding like an attack.
- Propose an action naming an owner and a deadline, and close a topic by asking for explicit confirmation from the group.
- Recover the floor once if someone interrupts you, without falling into the reflex of always yielding.
You already know how to enter a meeting, hold the floor, and close an agreement. But all of this falls apart if you didn't understand what was said before it was your turn to speak — and in a meeting with varied accents and imperfect audio, that's going to happen. The next lesson takes exactly that crack: what to do with the silent nod, and how to ask for something to be repeated without it sounding like you understood nothing. It's the other half of the same table.
Resources
- BBC Learning English — Business English — short, free lessons on work English, with audio in varied accents, useful for training this lesson's step 2 of listening.
- BBC Learning English — English at Work — series of dramatized office dialogues, with meeting, interruption, and misunderstanding situations you can use to practice recognizing signaling and closing in real context.
- Cambridge Dictionary — to check the pronunciation and exact meaning of any phrase in this lesson before using it in a real meeting.
- engVid — Business English — free video lessons from native-speaking teachers on office English, including meeting mechanics and agreement/disagreement expressions.
- Toastmasters International — Resources — articles and guides on speaking with confidence in a group, useful for the part of the lesson on holding the floor without yielding.