How to Open and Run a Meeting in English at Work
ESL English learning: Master the key phrases for opening, chairing, and managing tech meetings in English — from sprint reviews to stakeholder calls.
Pronunciation Guide for Meeting Phrases
Some common meeting phrases can trip up non-native speakers. Here's a quick guide to pronouncing key terms correctly so you sound confident when facilitating.
agenda /əˈdʒen.də/
a-GEN-da
Saying 'a-JEN-da' with hard 'J' instead of soft 'dʒ'
schedule /ˈskedʒ.uːl/ (US) or /ˈʃedʒ.uːl/ (UK)
SKED-yool or SHED-yool
Mixing US and UK pronunciations inconsistently
item /ˈaɪ.təm/
AI-tem
Saying 'ee-tem' instead of 'ai-tem'
facilitate /fəˈsɪl.ɪ.teɪt/
fa-SIL-i-tate
Stressing the wrong syllable: 'FA-cil-i-tate'
timebox /ˈtaɪm.bɒks/
TIME-box
Running the words together without clear separation
Opening the Meeting: Starting Strong
Whether you're kicking off a sprint planning session or a cross-functional design review, how you open a meeting sets the tone. In tech, we value efficiency — so your opening should be clear, welcoming, and purposeful.
The opening phase has three parts: starting the meeting, introducing attendees (especially new team members or guests), and presenting the goals and agenda.
| Situation | Formal Phrase | Informal/Slack Alternative |
|---|---|---|
| Starting the meeting | Let's get started. Thank you all for being here. | Alright, let's dive in! Thanks for jumping on. |
| Introducing someone new | I'd like to introduce our new backend engineer, Alex Chen. | Quick intro — Alex just joined the platform team! |
| Stating the goal | Our aim today is to finalize the RFC for the payments service. | We're here to nail down the payments RFC. |
| Presenting the agenda | As you can see on the agenda, we'll cover three items today. | Here's the plan: three things on the list today. |
Culture Tip: The 2-Minute Rule
In tech meetings, spending more than 2 minutes on the opening can feel wasteful. Get to the point quickly — your colleagues will appreciate it. Save the longer introductions for all-hands or external stakeholder calls.
Introducing New Team Members and Stakeholders
When someone new joins a call — whether it's a new hire, a guest from another team, or an external stakeholder — a brief introduction helps everyone understand who they are and why they're there.
For internal team meetings, keep introductions short. For cross-functional or external meetings, add context about the person's role and what they'll contribute.
- Before we start, I'd like to introduce Sarah from the security team. She's here to review our authentication approach.
- We have a new face today — this is Marcus, our new DevOps engineer. Marcus, want to say a quick hello?
- Could everyone briefly introduce themselves for our guests from the partner team?
- I'll let everyone go around quickly — just your name and team.
| ❌ Awkward Introduction | ✅ Natural Introduction |
|---|---|
| This is John. He does backend stuff. | This is John Chen, one of our senior backend engineers. He's leading the API migration. |
| We have new people. | We have a few guests joining us today from the data platform team. |
| Everyone say who you are. | Let's do a quick round of intros — name and role is fine. |
Presenting the Agenda and Setting Time Limits
A clear agenda keeps meetings focused. In tech, where calendar time is precious, stating the agenda upfront and timeboxing each item prevents scope creep.
When presenting the agenda, also invite additions — but be strategic. In a standup or sprint review, additions might derail the flow. In a planning meeting, inviting input shows collaboration.
| Meeting Phase | Key Phrases | Tech Context |
|---|---|---|
| Presenting agenda | Here's what we'll cover today... / The agenda has three items. | Sprint review: demo, metrics, blockers |
| Adding items | Is there anything else we should discuss? / Any additions to the agenda? | Use sparingly in standups; more open in planning |
| Setting time limits | We have 30 minutes, so let's keep each demo to 5 minutes. / Let's timebox this to 10 minutes. | Agile timeboxing is standard practice |
| Defining roles | Who's taking notes today? / Maria, can you capture action items? | Rotating note-taker is common in tech teams |
Grammar Note: Future Forms for Agendas
Use 'we'll' (we will) for planned agenda items: 'We'll start with the demo, then move to blockers.' Use 'we're going to' for decisions already made: 'We're going to skip the metrics discussion today since we covered it yesterday.'
Multiple choice
Choose the best answer.
Which phrase best invites additions to an agenda without losing control of the meeting?
Moving Between Agenda Items Smoothly
One of the most important skills for chairing a meeting is transitioning between topics. Done well, it keeps momentum. Done poorly, conversations drag or end abruptly.
Use transitional phrases to signal when one topic is complete and the next is starting. This is especially important in remote meetings where visual cues are limited.
- That covers the deployment timeline. Let's move on to the testing strategy.
- If no one has anything to add on the API changes, we can move to the next item.
- We've discussed the frontend blockers — now let's look at the backend dependencies.
- Great discussion on the metrics. Moving on to item three: the Q3 roadmap.
| ❌ Abrupt Transition | ✅ Smooth Transition |
|---|---|
| OK, next. | Alright, that wraps up the deployment discussion. Let's move to testing. |
| We're done with that. | I think we've covered that well. Any final thoughts before we move on? |
| Stop talking about that. | Let's park that discussion and come back to it if we have time. |
Complete the sentence
Type the missing word or phrase.
Complete the transition phrase: 'That about ______ the first item. Let's move on to the next point.'
Keeping the Meeting On Track and On Time
Tech meetings often run over because discussions go deep into technical details. As the facilitator, you need diplomatic phrases to redirect conversations without shutting people down.
The key is acknowledging the value of the discussion while gently moving it elsewhere — either to a later time, a separate channel, or a follow-up meeting.
| Situation | Diplomatic Phrase | Why It Works |
|---|---|---|
| Topic going off-agenda | That's a great point — can we capture it for a follow-up? | Validates the contribution while deferring it |
| Running out of time | We're running short on time. Let's table this and continue in Slack. | Clear reason + concrete next step |
| Deep-dive derailing the meeting | This deserves more time than we have. Can we schedule a separate session? | Shows respect for the complexity |
| Someone dominating discussion | Thanks for that perspective. Let's hear from others as well. | Polite redirect without criticism |
Vocabulary: 'Table' vs 'Park'
In American English, 'table' means to postpone a discussion ('Let's table this for now'). In British English, 'table' can mean to bring something up for discussion — the opposite! Use 'park' for clarity: 'Let's park this and come back to it later.' Both audiences will understand.
- We're running behind schedule, so let's skip item four and pick it up next week.
- I'm afraid we're almost out of time. Let's capture action items and wrap up.
- We'll come to that in a minute — let's finish the current item first.
- This is important, but it's taking us off-track. Can we add it to the parking lot?
Multiple choice
Choose the best answer.
A colleague starts discussing a bug that's unrelated to the sprint review. What's the most diplomatic response?
Managing the Speaking Order
In remote meetings especially, managing who speaks and when prevents chaos. Good facilitators actively invite contributions from quieter team members and recognize when someone is trying to speak.
Tech teams often include people from different cultural backgrounds with different communication styles. Some wait to be invited; others jump in freely. A good chair balances both.
- Let's go around the table so everyone gets a chance to share their update.
- Priya, I noticed you've been working on the caching layer. What's your take on this?
- James, you look like you want to add something. Go ahead.
- I'd like to hear from the folks who haven't spoken yet. Any thoughts on the timeline?
| ❌ Excluding Language | ✅ Inclusive Language |
|---|---|
| Anyone have anything to say? | I'd like to hear from the QA team on this. Wei, what do you think? |
| You've been quiet — what's wrong? | Li, I know you've been deep in this code. Any insights to share? |
| Let the experts talk. | Let's hear different perspectives. Fresh eyes often catch things we miss. |
Culture Tip: Inviting vs. Waiting
In some cultures, people wait to be invited to speak. In others, people jump in when they have something to say. If you're facilitating a diverse team, explicitly invite contributions: 'Yuki, I'd love to hear your perspective on this.' This creates space for everyone without putting anyone on the spot.
Common Mistakes: What We Hear at Work vs. Better English
Even fluent speakers make mistakes when facilitating meetings under pressure. Here are common errors we hear in tech workplaces and better alternatives.
| ❌ Heard at Work | ✅ Better English |
|---|---|
| Let's start the meeting. So, the agenda is... | Let's get started. Here's what we'll cover today... |
| We don't have time. Next topic. | We're running short on time. Let's move to the next item. |
| John, you talk now. | John, would you like to share your thoughts on this? |
| This meeting will discuss the API. | In this meeting, we'll discuss the API changes. |
| I want to present the new developer. | I'd like to introduce our new developer, Sarah. |
| The time is finishing. | We're almost out of time. / Time is running short. |
Rewrite for work
Find and correct the error: 'I want to present the new team member who joined in last week.'




