Developer English guide
How to Lead a Meeting in English: Phrases for Tech Leads
October 21, 2026
Surviving a standup as an attendee and running a meeting are two different skills. This is the second one: opening on time, keeping a group on track, and closing with a clear outcome, in English.
Key Takeaways
- Leading a meeting in English is a different skill than attending one. You need phrases for opening, redirecting, inviting input, assigning action items, and closing.
- A tangent does not need to be shut down rudely. 'Let's take that offline and come back to the agenda' works every time.
- If someone has not spoken in ten minutes, invite them in directly by name. Silence does not mean agreement.
- Every action item needs an owner and a deadline said out loud, not just written in the notes afterward.
- Closing with a one-sentence summary of decisions and next steps is what makes a meeting feel like it had a point.
Running the room is a different job than sitting in it
Dirigir la reunión es un trabajo distinto a solo asistir
If you already know how to get through a daily standup as an attendee, this is the other side of that skill. At some point in your career, usually once you move into a tech lead or senior role, you stop just reporting your own status and start running the meeting: a sprint planning session, a retro, a design review, a 1-on-1 with someone on your team.
That means you become responsible for things nobody ever taught you in an English class: opening on time, keeping a group of people focused, making sure the quiet person gets a turn, and closing with something more useful than 'okay, I think we're done.'
This guide gives you the exact phrases for each of those moments.
Three jobs, in every meeting you lead
Tres tareas, en cada reunión que diriges
A meeting you are running has three phases, and most of what goes wrong in English happens because a lead skips straight from 'before' to 'during' without a plan for either.
Before
Set a clear agenda and a time box for each topic before anyone joins.
During
Keep the discussion on track and make sure everyone who should speak gets a turn.
After
Close with a one-sentence summary, confirm the action items, and send a recap.
The exact phrases for every moment
Las frases exactas para cada momento
These cover the moments that actually come up in a meeting you are leading, not generic small talk. Memorize the ones for opening, redirecting, and closing first, since you will use those every single time.
Opening the meeting
“Thanks everyone for joining. Today we have three things on the agenda: X, Y, and Z. Let's start with X.”
Setting a time box
“Let's spend ten minutes on this one so we have time for the rest of the agenda.”
Redirecting a tangent
“That's a good point, but it's a separate conversation. Let's take it offline and get back to the agenda.”
Parking a topic for later
“Let's park that one. We'll come back to it at the end if we have time.”
Inviting a quieter person to speak
“I haven't heard from you yet, [name]. What's your take on this?”
Managing someone who talks too much
“Let me pause you there so we can hear from a few other people too.”
Assigning an action item
“[Name], can you own this one? Let's say by [date].”
Confirming an action item out loud
“So to confirm: [name] will do X by [date], and I'll follow up on Y.”
Closing the meeting
“Let's wrap up here. To summarize: we decided X, [name] owns Y, and I'll send a recap in the channel.”
Handling disagreement without it turning into a standoff
Manejar un desacuerdo sin que se convierta en un enfrentamiento
Technical disagreements are normal and healthy. What derails a meeting in English is not the disagreement itself, it's running out of neutral phrasing and defaulting to a flat 'no, that's wrong,' which reads as more aggressive in English than most non-native speakers intend.
Three phrases buy you time to respond carefully instead of reactively: 'I see it differently, and here's why,' 'I want to make sure I understand your concern before we respond to it,' and 'Can we agree on what problem we're solving before we argue about the solution?' That last one in particular defuses a surprising number of arguments, because half the time two people disagreeing loudly are actually solving for two different things.
Frequently asked questions
How do I politely interrupt someone who is talking too much in a meeting?
Use a short, neutral phrase that redirects rather than criticizes: 'Let me pause you there so we can hear from a few other people too,' or 'That's a great point, let's come back to it if we have time.' Say it right after they finish a sentence, not mid-word, and move straight to the next person by name.
What do I say if nobody answers my question in a meeting?
Silence in a video call usually means people are unsure who should answer, not that they disagree. Name someone directly: 'Maria, what do you think?' If it's a harder question, give people a few seconds of silence first by saying 'Take a moment, no rush,' since many people need a beat to switch from listening to speaking in a second language too.
How do I close a meeting that doesn't have a clear outcome yet?
Say so directly instead of letting it trail off: 'We didn't land on a final decision, so let's regroup with [names] by [date] and finalize it then.' A clear next step is a valid outcome. What you want to avoid is ending with 'okay, I think we're good' when nobody actually agreed on anything.
Is it rude to say 'let's take this offline'?
No, it's one of the most common and accepted phrases in English-speaking tech meetings. It signals that the topic matters, just not to the whole group right now. It reads as organized, not dismissive, as long as you actually follow up afterward instead of using it to avoid the conversation entirely.
Related articles
Ready to practice your English at work?
Lingua-e has interactive exercises built around real developer conversations: standups, code reviews, retrospectives, and more. Practice until it comes naturally.
Try Lingua-e for free
Written by
Roxana LafuenteLingua-e's founder
Roxana Lafuente is a software engineer with 8+ years of experience. At the beginning of her career, even though she had already passed the First Certificate in English, she still froze every time she had to speak up in the daily standup. That was a gap nobody was fixing. After 2,000+ standups, she figured out what actually builds fluency: practice that looks like your real work. She built Lingua-e so other developers wouldn't have to take the long road to feel confident working in an international development environment.