Running an all-hands for a global team across languages

Translate the Q&A, not just the leadership presentation, and confirm the recording keeps the translation before choosing a platform — for a global team the asynchronous audience is usually larger than the live one, and Teams and Meet both drop translated audio from recordings.

An all-hands has a specific failure mode: the parts that are easy to translate are the parts that matter least.

The presentation is the easy half

Prepared, predictable, one-directional. Brief the speakers, load a glossary of product and internal terms, rehearse once with translation running, and it will be fine.

If this is all you translate, you have translated the part that could have been a written update.

The Q&A is the half that counts

Q&A is where an all-hands stops being a broadcast. It is also where language exclusion becomes measurable, because the people who ask live questions in a second language are the confident minority — not a representative sample of your company.

Concretely:

1. Accept written questions in any language, before and during, and commit publicly to answering a set number
2. Show questions on screen in the original and translated, so the asker sees their language treated as legitimate
3. Let people ask live in their own language if your tooling handles symmetric translation
4. Publish unanswered questions with answers afterwards, translated

The fourth costs almost nothing and is the one most often skipped.

Time zones force a choice

Run it twice — expensive in executive time, and the second sitting is always flatter.

Run it once and invest in the recording — cheaper and usually better, but only works if the recording keeps the translation.

That second point is not a detail. Microsoft’s own documentation states that Teams meeting recordings only capture the original meeting audio and don’t include interpretation audio, and that translated transcripts disappear when the meeting ends. Google Meet does not translate recordings or live streams either.

For a company where most people watch the all-hands the next morning, that means the translation you arranged served the smaller audience.

Platform reality for this format

All-hands is the format native tooling handles worst:

• Teams Interpreter is unavailable in town halls and webinars, requires Microsoft 365 Copilot rather than Teams Premium, and excludes guests without a licence.
• Google Meet supports one language pair per meeting. Three offices in three languages cannot use it — an architectural limit, not a pricing one.
• Zoom translates to captions only, which for a 45-minute leadership session means your international staff are reading while everyone else listens.

Three or more languages, an asynchronous audience, and external participants puts you outside all three. Establish that during planning rather than in the week of.

Two things to stop doing

Do not translate downward only. Leadership into five languages, questions back in English, tells everyone whose language is the real one.

Do not treat the recording as an afterthought. For a global team it is the primary artefact. Decide what it will contain before you decide anything else.