How to Run a Meeting Across Languages

There's a moment about eighteen minutes into a lot of international calls where one person quietly stops trying. Camera on, nodding at roughly the right times. But they've stopped composing sentences, because the last four times they had one ready, the conversation had moved on.

Nobody notices. The facilitator walks away thinking it went fine — decisions made, three minutes over. And the quietest person on the call, who happens to be closest to the thing being decided, contributed nothing.

That's how a multilingual meeting fails, and almost nobody names it. No confused silence, no "sorry, can you repeat that." It just looks like some people are talkative and some aren't.

The person who stopped talking three meetings ago

Pamela Rogerson-Revell's 2008 study of international business meetings in English for Specific Purposes found that native English speakers didn't hog the talk time — airtime was reasonably shared. What she found instead was a much higher proportion of non-native speakers who were inactive: present throughout, contributing nothing.

That kills the obvious fix. The silence isn't caused by someone else filling the space. It's caused by the gap between turns.

Producing a sentence in a second language costs more working memory than producing one in your first, and so does listening — comprehension degrades as speech rate and syntactic complexity rise. In a fast meeting, someone is decoding an unfamiliar accent, holding the thread, translating their idea and hunting for a gap that isn't appearing. Then the gap arrives and closes in under a second. Do that six times and most people conclude the meeting has no room for them.

And the interpretation on the other side is: they're quiet, they must not have strong opinions. A language barrier at work gets read as a personality trait, then as a performance signal.

The tell to watch for: jot down who spoke, and for how long, across three consecutive meetings. Not to police anyone — just to see the shape. If the silent people are consistently the ones in their second language, that isn't a personality distribution. It's a design problem.

Choosing a working language, honestly

Most teams never decide this. English becomes the default because the first few hires spoke it, and then it's just the water everyone swims in.

If you're picking deliberately, the honest criterion is this: choose the language that gives the most people in the room usable comprehension, not the one most comfortable for the most senior person. Those are frequently different answers.

Then say it out loud. "We're running this in English because it's the only language everyone here shares — so I'll go slower than I naturally would." That names the arrangement instead of leaving it an unspoken hierarchy, and makes the accommodation a group norm rather than a favour.

• The cost isn't shared evenly. Whoever's in their second language spends more effort for the same participation, every meeting. Pretending otherwise is the most common mistake in cross cultural communication.
• Sometimes the right answer is to split. Two shorter discussions and a shared summary beat one conversation neither subgroup follows well.
• Some meetings need a human interpreter. Contract negotiations, disciplinary conversations, safety briefings, anything with legal weight. No facilitation and no software substitutes for that.

Most of the fix happens before anyone joins the call

This is the part people skip and the part with the best return. Written prep disproportionately helps anyone working in a second language, for a mechanical reason: reading is self-paced. A live meeting runs at the speaker's speed; a document runs at the reader's. Someone who needs an extra beat takes it, and arrives with their contribution half-composed.

There's experimental support. A CSCW study put English-native and Mandarin-native subgroups through prep conversations in their own languages before an English team meeting. Sharing machine-translated logs of those conversations beforehand improved the meeting itself — in task performance, in participants' experience, and in the depth of discussion. The prep wasn't in the shared language. Sharing it anyway still helped.

Send the agenda a full day ahead, not five minutes

Not a topic list — a real one, with the questions you need answered. "Pricing discussion" gives nobody anything to prepare. "Do we hold the enterprise tier at $29 or move to usage-based billing?" lets someone spend twenty minutes overnight forming an argument and looking up the words. Our guide on a staff meeting agenda that holds up covers the structure; for international team communication, send it earlier and plainer.

Keep a running glossary of your own jargon

Every team invents vocabulary. It's harder to infer in a second language, because the listener can't tell whether the phrase is company jargon or a word they don't know. Fifty entries in a shared doc costs an hour and pays back permanently.

Ask for written input before the meeting, not just during

"Add your thoughts to the doc by Tuesday" produces contributions from people who'd never have won a turn on the call. Then read them aloud yourself, with attribution: "Priya wrote that the migration timeline doesn't work for the Bangalore team — let's start there." Someone's idea is now at the centre without them fighting for the floor.

Running the room: pace, idioms, and who gets the floor

Most advice here starts and stops at "speak slowly and clearly." Not wrong, just not specific enough to act on.

Slow down at the joints, not everywhere. Uniformly slow speech is patronising and everyone can feel it. Pause at clause boundaries and after each complete idea instead. Two seconds. It feels endless from the inside, barely noticeable from the outside.

Idioms are the real problem, not vocabulary. Fluent second-language speakers usually have a large technical vocabulary. What ambushes them is figurative language, which can't be decoded from its parts — "behind the eight ball," "run it up the flagpole." Notice and restate: "let's park that — I mean set it aside until next week."

Give turns explicitly. "Any thoughts?" is won by whoever is fastest and most confident, which tracks fluency more than expertise. Hand the floor forward by name, with warning: "after Tom I want to hear from Lucia." Ten seconds of notice is enough to compose an opening sentence, and that sentence is usually the whole barrier.

Let silence sit. Most facilitators fill a three-second pause reflexively. In a multilingual room, three seconds is roughly when someone's sentence becomes ready. Count to five. Nothing changes participation more, and it costs nothing.

Check comprehension without singling anyone out. Never ask a specific person whether they understood — almost everyone says yes, because the alternative is announcing a deficiency in front of colleagues. Put the burden on yourself: "let me check I explained that clearly," then restate. Or make playback a group habit, rotating who does it. When one person does it, it's a spotlight, not a process step.

Run chat as a real parallel channel. Typing removes the turn-taking race and the pronunciation anxiety at once — but only if you read it. An ignored chat channel is worse than none, because it teaches people the accessible route is a dead end.

Turn captions on for everyone. Morton Ann Gernsbacher's review in Policy Insights from the Behavioral and Brain Sciences pulled together more than 100 empirical studies and found captions improve comprehension, attention and memory generally, with the benefit especially pronounced for people watching in a non-native language. Enable them by default, not on request.

The habit that's hardest to break: linguists studying English as a lingua franca describe a "let it pass" strategy — when something is unclear, people quietly let it go and hope it resolves from later context. Alan Firth documented it in 1996, and it's usually adaptive; nobody wants to halt a meeting over a half-heard preposition. But it fails badly on numbers, dates, names and commitments. Confirm those explicitly, every time: "March 14th — that's a Saturday, do we mean the 13th?"

The written record is where the meeting actually lands

For anyone who followed 80% of a meeting live, the notes are where the other 20% gets recovered. That makes the written record the highest-leverage item on this list.

A record that works states decisions as decisions ("we're going with option B"), names owners and dates, and keeps open questions separate from resolved ones. Our walkthrough on writing usable meeting minutes has the structure; the adjustment for international teams is plainness and explicit numbers.

A transcript on top of the summary is worth more than people expect. A summary tells you what was decided; a transcript lets someone search for the two minutes they lost and read them at their own pace — the self-paced advantage that makes pre-reads work. If your team spans languages, a transcript readable in someone's first language closes the last gap, which is where an AI meeting assistant with real-time translation earns its place; Laxis, for one, runs side-by-side translation across 100+ languages as people speak and carries the translated content into the summary and action items. Machine translation still stumbles on idiom, jargon and crosstalk, so treat it as a safety net, not a guarantee.

Where the tooling has actually moved is live translation, and it is worth knowing what is now possible before you plan around its absence. Laxis translates during the meeting itself across more than 100 languages, showing the translation beside the original as someone speaks, and carries that translation through into the summary and action items rather than leaving it on screen to vanish. Among AI note takers it is currently the only one that does this: the others are multilingual in the sense that they transcribe several languages, which is a different thing — Otter handles six one at a time, Fireflies transcribes over a hundred, Fathom takes thirty-eight in and translates only the summary into six. Transcribing the language someone spoke and putting a translation in front of a colleague while they are still speaking are separate problems, and most of the category has solved the first. The same translation works in the Laxis Voice Keyboard too, so you can speak Chinese and have English land in the Slack reply after the call.

Whether that changes anything for you depends on the meeting. It does not remove the need for a working language, and it does not fix a call where three people talk at once — the pacing and preparation above still do more work than any tool. What it does remove is the specific failure this whole page is about: the person who followed most of the discussion, lost the important two minutes, and said nothing.

One habit regardless of tooling: publish within a few hours, while people can still check it against what they remember. A summary that lands three days later is an archive; one that lands the same afternoon is a correction opportunity.

A checklist you can run down in ten minutes

None of this is difficult. It's just easy to forget under time pressure.

Multilingual meeting facilitator checklist

Before

• Agenda sent 24 hours ahead, with the actual questions to be decided
• Pre-reads and slides attached, not promised
• New jargon and acronyms added to the shared glossary
• Written input invited in advance, with a named deadline
• Working language confirmed — and a check on whether anyone needs an interpreter

During

• Captions on, for everyone, from minute zero
• Recording and transcription running, announced at the start
• The language choice named out loud in the first two minutes
• Idioms restated plainly when you catch yourself using one
• Turns handed out by name, with a beat of warning
• A five-count before filling any silence
• Chat monitored and read aloud, not just left running
• Numbers, dates and names confirmed explicitly, every time
• Comprehension checked by restating your own point, never by asking if someone followed

After

• Written record out the same day: decisions, owners, dates, open questions
• Transcript available and searchable, translated where useful
• Corrections invited explicitly — "reply if I got anything wrong"
• Anyone who was silent asked directly, one-to-one, for their view

Print it, pin it by your monitor, stop reading it once it's automatic.

What each change actually buys you

If you only have energy for three, it helps to know which do the heavy lifting.

How to tell whether any of this is working

A multilingual meeting can feel fine to everyone who was comfortable in it, so vibes are the wrong instrument. Four things to watch.

Participation spread — not total airtime, spread. How many distinct people said something substantive, and did that number move? If eight people consistently means five speaking and three not, name the three and find out why, privately. Transcripts make this easy to check honestly, since you're reading what happened rather than remembering it.

Rework rate. How often does a decision get reopened because someone didn't realise it had been made? That's the clearest symptom of a gap nobody flagged, and it should fall as your record improves.

The shape of follow-up questions. A healthy amount of "just to confirm, are we doing X by Friday?" is a good sign. But if one person needs basic clarification after every call, the live meeting isn't reaching them.

What people say when you ask them alone. Nobody tells you the meeting is too fast during the meeting. Ask something specific in a one-to-one instead: "on Tuesday's call, was there anywhere I went too fast?" That chair sees a different meeting — when you can't follow colleagues in meetings covers the tactics that work from inside it.

Give people something to re-read

Laxis records, transcribes and translates meetings across Zoom, Google Meet and Teams, with 300 free minutes a month.

Try Laxis free

Frequently asked questions

How do you run a meeting when not everyone speaks the same language?

Name one working language out loud, send the agenda and pre-reads a day ahead, slow down slightly, avoid idioms, and hand out turns by name so quieter people get a guaranteed slot. Then publish a written record with decisions and owners. Prep and the record matter more than anything live.

How do you choose a working language for an international team?

Pick the language that gives the most people in the room usable comprehension, not the one most comfortable for the most senior person, and say the choice out loud. If two subgroups each work better in their own language, split the discussion rather than forcing one conversation nobody follows.

Why do quiet participants stay quiet in multilingual meetings?

Usually because turn-taking is too fast, not because they have nothing to say. Composing a sentence in a second language takes longer, and by the time it's ready the topic has moved. Research on international business meetings found high rates of silent non-native speakers even where airtime was shared.

Should you turn on live captions in a multilingual meeting?

Yes, by default. Reviews of captioning research find same-language captions improve comprehension, attention and memory generally, with a larger benefit for people working in a second language. Turn them on for everyone rather than asking who needs them, so nobody has to identify themselves as struggling.

How do you check that people understood without singling anyone out?

Put the burden on yourself, not on them. Say "let me check I explained that clearly" and restate the point, or make playback a standing habit by asking someone to give the decision in their own words. Never ask one person whether they understood; almost everyone says yes.

Is machine translation good enough to replace an interpreter?

Not for high-stakes conversations. Live translation and captions handle routine standups, project reviews and status calls well, but machine translation still trips on idiom, in-house jargon and crosstalk. For contract negotiations, disciplinary matters, safety briefings or anything legally binding, hire a qualified human interpreter.

How do you tell whether your multilingual meetings are improving?

Track how many distinct people spoke and how evenly, count how often a decision gets re-litigated because someone missed it, and watch whether follow-up questions drop over time. Ask individually in one-to-ones too. A room that reports feeling fine while three people never speak is not fine.

The quiet person is usually the expensive one

There's a version of this article that frames all of the above as a kindness — be considerate, make space. True, and also the reason nothing changes, because kindness is the first thing dropped when the quarter is bad.

The sharper argument is that the person who went quiet is frequently the person closest to the work. They're on the ground in the market you're expanding into, or they built the thing you're deciding to change. The reason they're working in their second language is usually that they're the one who moved toward you. Losing their input isn't a shame — it's the most expensive thing happening on that call, every week, in a meeting everyone agreed went fine.