Translation and new markets 7 min

Multilingual team: working without a shared language

A multilingual team works well when it picks a shared language for written decisions, lets everyone read and speak in their own language through translated captions and message translation, writes simple sentences with a shared glossary, and keeps bilingual colleagues or interpreters for the conversations that commit the company.

Contents10
  1. 01Reading, listening, speaking: very different levels
  2. 02What meeting tools do in 2026
  3. 03Choosing a working language, and what stays in each person’s language
  4. 04Writing to be understood, and translated
  5. 05Meetings that leave nobody out
  6. 06Documentation in several languages
  7. 07What tools do not replace
  8. 08When the multilingual team also serves customers
  9. 09Where to start
  10. 10Frequently asked questions

A subsidiary opened in Germany, a team acquired in Spain, a developer hired in Portugal, a production partner in Asia: a 50-person company can end up with colleagues who share no language, or who share a very uneven English. Meetings get longer, emails are reread three times, and some people stay silent because they are not sure they will say it right.

Translation tools have improved a lot, and they help. But a multilingual team works first thanks to a few simple rules on the working language, writing and meetings. This article goes through them. It complements our other articles on translation and new markets, which focus on customers: this one looks inside the company.

In short

  • The problem is not vocabulary, it is the misunderstanding nobody sees.

  • Many people read a foreign language better than they speak it: writing is often the best common ground.

  • Teams and Google Meet can now translate a meeting, as captions or as voice, with limits on languages and licences.

  • A shared language for written decisions, a shared glossary and systematic minutes do more than any tool.

  • Conversations that commit the company (negotiation, appraisal, safety) keep a bilingual person or an interpreter.

Reading, listening, speaking: very different levels

In a multilingual team, people often assume everyone “speaks English”. Measurements show a more nuanced reality, and above all an uneven one depending on the skill. The EF English proficiency ranking illustrates it for France:

English proficiency in France by skill, EF EPI 2025 score

Reading555
Listening524
Writing500
Speaking456
Source: EF English Proficiency Index 2025, France fact sheet

This ranking is based on people who chose to take the test: it shows a trend, not an exact portrait of your team. But the gap between reading and speaking shows up in many teams. Practical consequence: a written decision, read at one’s own pace, gets through better than a decision made orally at the end of a meeting, when those who were following with effort have already dropped off.

What meeting tools do in 2026

The two big office suites now translate meetings, each with its own conditions.

  • Microsoft Teams shows live translated captions. According to Microsoft’s help, the feature is part of Teams Premium and Microsoft Copilot, add-on licences: if the organiser has one, all participants can use it.
  • Google Meet goes further with voice translation, available to businesses since 27 January 2026 according to the Google Workspace announcement: everyone speaks their language and the others hear a translation that keeps the speaker’s tone. At launch, one language pair per meeting, between English and Spanish, French, German, Portuguese or Italian.

These tools help a great deal in everyday meetings: a colleague can follow in their own language instead of guessing. They do not solve everything. A mistranslated trade term goes unnoticed, a joke falls flat, and a three-language meeting still exceeds some tools’ limits. And what is said in a meeting goes to a translation service: the questions of translation and GDPR apply just as they do for a document.

Choosing a working language, and what stays in each person’s language

A team needs a reference language for what everyone must understand the same way. It does not need to do everything in that language.

In the shared language

  • Decisions, minutes and priorities

  • Documentation of processes and tools

  • Tickets, requests between departments, deadlines

In each person’s language

  • Relations with local customers and suppliers

  • Personal exchanges: appraisals, feedback, difficulties

  • Safety instructions and anything that must be understood beyond doubt

For exchanges with foreign customers, the workflow described in translating customer support emails without hiring also works between colleagues: everyone writes in their language, translation bridges the gap, and what commits the company goes through someone who reads the language.

Writing to be understood, and translated

A simple text is easier to understand in a foreign language and translates better by machine. A few rules are enough:

  1. One idea per sentence, with no innuendo or irony.
  2. No idioms, and no internal acronyms left unexplained.
  3. The same words for the same things, kept in a shared glossary, like the brand glossary used to translate the website.
  4. The decision written first, the context after.
  5. Explicit dates, figures and names: “Friday the 24th” rather than “next week”.

These rules also serve the tools: a clear text gives a better machine translation, whatever the engine, and the method in DeepL, Google or an LLM helps choose the one that best understands your trade.

Meetings that leave nobody out

A multilingual meeting in four stages

  1. Before

    The agenda written and sent, so everyone can prepare in their language.

  2. During

    Captions or voice translation switched on, and a round for those who do not speak up spontaneously.

  3. At the end

    The decision restated aloud, then written in the team’s tool.

  4. After

    Short minutes in the shared language, translated for those who want them.

Stage four is the most useful. A summary generated by AI from the transcript saves time, provided someone who attended the meeting reviews it before it is sent: a summarising tool can turn a hesitation into a decision. To check whether translations hold up without rereading everything, the method of our article on translation quality applies to internal documents too.

Documentation in several languages

Procedures, onboarding for newcomers, tool rules: documentation kept in one source language, then translated and synchronised, prevents each country from having its own drifting version. A translation memory only retranslates the sentences that changed, and the principles of translating software or an app apply to the internal tools the team uses every day. Training videos are subtitled following AI subtitles and dubbing for export.

From the field

One source language, a checked translation

This website runs on that rule: French is the source language, English follows in the same change, and an automatic check refuses to publish an offer whose two versions do not have the same blocks, the same lists and the same numbers. Internal documentation in several languages benefits from the same principle: one reference version, and translations checked to say the same thing.

Legal terms and documents that commit the company, employment contracts, regulations, agreements, follow the precautions of translating a contract with AI: where it stops.

What tools do not replace

Bilingual team members are bridges: they spot a misunderstanding the translation let through, and explain what belongs to culture rather than language. Language courses keep their value, because a direct conversation, even an imperfect one, builds a relationship a tool does not. And for a negotiation, labour relations or a crisis, a professional interpreter remains the right choice: the stakes justify someone whose job it is.

When the multilingual team also serves customers

A team that speaks several languages is an asset for opening markets. Its members know what customers in their country look for, which helps redo keyword research abroad rather than translate it, localize rather than just translate prices and proof, and review product pages translated for export. It helps choose which European market to open first, understand what changes beyond language in an English-speaking market or in China and Southeast Asia, and decide which blog articles to translate first. The choice between machine and reviewed translation is detailed in translating your website with AI: automatic or reviewed?, and the budget in website translation cost.

Where to start

Write down the team’s working language and the list of what must be done in it, then turn on translated captions in your meeting tool and test them in an everyday meeting. Start a shared glossary of the twenty internal terms that raise the most questions, and introduce written minutes after every decision meeting. To equip the translation of your documents and messages with your data rules, tell us about your team and your languages.

Frequently asked questions

Should English be imposed as the working language?

Not necessarily English, but a reference language for what everyone must understand the same way: decisions, minutes, documentation. Choose the one most of the team reads best. The rest, personal exchanges and relations with local customers, can happen in each person’s language, with translation bridging the gap.

Are the translated captions in Teams or Meet enough?

For an everyday meeting, they help a lot: everyone follows in their language. They have limits: add-on licences at Microsoft, restricted language pairs at Google, trade terms sometimes poorly rendered. Complete them with a written agenda and reviewed minutes, and keep an interpreter for meetings that commit the company.

Can internal messages be translated automatically?

Yes, and it is often useful for everyday exchanges. Just check where the translated messages go and what the service does with them, as with any company data. For a safety instruction, an important decision or a sensitive exchange, have the translation reviewed by someone who masters both languages.

Are language courses still useful with these tools?

Yes. Tools translate words, not relationships: a direct conversation, even an imperfect one, builds a trust that a translation does not replace, and it helps spot cultural misunderstandings. Courses focused on the working language, especially speaking, where the gap is often widest, remain a good investment for the team.

Sources

  1. Microsoft, live captions in Teams (new tab)support.microsoft.com
  2. Google Workspace Updates, speech translation in Meet (new tab)workspaceupdates.googleblog.com
Source 1

Microsoft, live captions in Teams

Read on support.microsoft.com(new tab)
Source 2

Google Workspace Updates, speech translation in Meet

Read on workspaceupdates.googleblog.com(new tab)

Jim · founder of Brain Plus AI

Also in translation and new markets

  • Practical guide8 min

    Brand glossary: keeping translations consistent

    The same product called three different things on three pages, and readers wonder whether there are three products. A brand glossary fixes the terms that are not up for debate, before the first translation, whatever the tool or the translator.

  • Understand7 min

    Translating customer support emails without hiring

    Answering every customer in their language does not take one person per language. The support tool translates both ways, canned replies are translated once, and the messages that commit you go through someone who reads the language.

  • Understand8 min

    Translation and GDPR: where your translated texts go

    Translating a text with an online tool means sending it to a third party. When it contains personal data, the GDPR applies: knowing where the text goes, how long it stays there and whether it trains a model is part of choosing the tool.

WhatsApp