How to run meetings with a multilingual team
Decide the working language explicitly rather than letting it default to whoever is loudest, put anything decision-critical in writing, and translate the discussion rather than only the presentation — most exclusion happens in the parts nobody plans.
Teams usually manage the formal parts of a multilingual meeting well and lose people in the informal parts, which is where the actual work happens.
Name the working language, out loud
Most multilingual teams have never explicitly decided what language meetings run in. It defaults to whatever the most senior or most talkative people speak, and everyone else adapts silently.
Deciding it explicitly costs one conversation and changes the dynamic, because it converts an unspoken hierarchy into a stated convention that can then be supported — with translation, with written materials, with a norm about pace.
Write down anything that has to be right
The reliable pattern in multilingual teams is: discussion spoken, decisions written.
Someone types the decision, the owner and the date into the shared doc during the meeting, and it is read back before the meeting ends. This takes ninety seconds and eliminates most of the “I thought we agreed something different” that gets blamed on language and is usually just ambiguity.
It also gives second-language speakers a text they can re-read at their own pace, which is a much lower barrier than asking for clarification in front of everyone.
Translate the discussion, not just the presentation
The common half-measure is translating a prepared presentation and leaving the discussion in the working language. That covers the part that could have been an email and leaves out the part that matters.
If you are going to translate, translate the debate.
Change how you handle turns
A few conventions that consistently help:
- Pause between speakers. Two seconds. It gives translation time to land and gives second-language speakers time to formulate.
- Ask for input by name rather than opening the floor. “Anyone have thoughts?” reliably selects for confidence in the working language.
- Use the chat as a first-class channel. People who will not interrupt in a second language will type.
- Repeat questions before answering them. In a call with mixed audio quality and accents, half the room often did not catch the question.
What your tooling will and will not do
- Google Meet supports one language pair per meeting, English-anchored, with a 90-minute cap. Fine for a two-language team, structurally impossible for three.
- Teams Interpreter covers 10 languages and requires Microsoft 365 Copilot — not Teams Premium, which is roughly a third of the cost people assume. It excludes external guests and unlicensed participants, and does not work in ad hoc meetings.
- Zoom gives translated captions, not audio.
There is a real case where the native tooling is the right answer: two languages, one of them English, everyone internal and licensed, under 90 minutes. If that describes you, use what you already pay for.
What not to do
Do not translate performatively. Adding translation to a meeting where everyone is comfortable in the shared language, because it seems inclusive, adds latency and helps nobody. Ask the people it is for.
Do not translate only downward. If leadership is translated into five languages and questions must come back in English, the meeting has told everyone what it thinks of their languages.