How to include non-native English speakers in meetings

Most exclusion comes from pace, idiom and turn-taking rather than vocabulary. Slow the transitions, drop the idioms, invite people by name, and treat the chat as a real channel — these cost nothing and help more than translation does.

The instinct is to reach for a translation tool. Often the barrier is not vocabulary at all — it is speed, idiom and the social mechanics of getting a turn.

Fix the speech first

Drop the idioms. Sporting metaphors, war metaphors and regional expressions are the single biggest comprehension cost in fluent-sounding English. “Let’s circle back”, “out of left field”, “boil the ocean” — every one costs a second-language listener a beat, and beats accumulate until they have lost the thread.

Slow at the transitions. You do not need to speak slowly throughout, which is patronising and ineffective. Slow down when you change topic, introduce a name, or state a number.

Expand acronyms on first use. Every meeting has attendees who have never heard three of them and will not ask.

Repeat the question before answering it. With mixed audio and mixed accents, a good share of the room did not catch it.

Fix the turn-taking

This is where most exclusion actually happens. Getting a turn in a fast conversation in your second language requires interrupting confidently — a skill that is not correlated with having something worth saying.

Invite by name. “Anna, you’ve worked on this — what do you think?” is worth more than any number of open invitations to contribute.
Pause after questions. Count to three silently. The person composing a sentence in their second language needs those three seconds; the person who always answers first does not.
Treat the chat as first-class. Read it aloud, respond to it, credit it. People who will not interrupt will type.
Do not reward speed. If the first answer always wins, you have optimised for fluency rather than judgement.

Fix the materials

Send an agenda in advance. Preparation converts a listening-comprehension problem into a reading problem, which is far easier.

Put numbers and names on screen. These are the highest-risk items to transmit by voice and the cheapest to display.

Write decisions down during the meeting, and read them back. Ninety seconds, and it removes most misunderstandings later blamed on language.

Then consider translation

Once the above is in place, live translation is worth evaluating for discussion-heavy meetings — design debates, planning, retrospectives — where real-time contribution genuinely matters.

Check the limits first:

Google Meet: one English-anchored language pair per meeting, 90-minute cap
Teams Interpreter: 10 languages, needs Microsoft 365 Copilot not Teams Premium, excludes external guests, not available in ad hoc meetings
Zoom: translated captions only

If your team is two languages with English on one side and everyone internal, the native option may be enough.

Ask, do not assume

Some people prefer to work in English and find translation intrusive. Some want captions but not translated audio. Some want the recording and transcript and do not care about the live session at all.

Ask the people concerned what would help, individually rather than in the meeting. The answers are usually more specific and cheaper than what you would have bought.