Writing Translation-Ready Employee Comms Campaigns
Overview
This guide is intended for administrators who have configured Multilingual Support with On-the-fly translation and are ready to leverage dynamic translation for employee communication campaigns. Learn more by reading OTF Employee Comms.
Authors of campaigns must follow these guidelines in order to minimize incorrect translations that may happen from English to various languages. Fundamentally, language translation is a challenge even for expert human translators so even state-of-the-art translation models aren't able to perform as intended, at times.
Guidelines
- Proofread. Use proper grammar, including subject-verb agreement and proper verb tense. Check your spelling.
- Poor English will produce poor translations.
- Use clear and concise language, and provide context in order to avoid ambiguity.
- Don’t use too many modifying adjectives. Excessively complex sentences are hard.
- Use active voice; some languages require this and you don’t want the machine translation to have to guess who or what does the action.
- ❌ Invoices must be submitted by August 1.
- ✅ You must submit your invoices by August 1.
- ✅ Managers must submit invoices by August 1.
- Never leave off direct objects. This may be grammatically impossible in the translation.
- ❌ It is encouraged to update by Friday.
- ✅ You are encouraged to update your operating system by Friday.
- Unintended ambiguity can create translation errors
- ❌ “User selected to resolve the issue” - “selected” here could mean “The user [who was] selected” or “The user [had] selected”
- ✅ The user chose to resolve the issue.
- The denser your phrases are, the higher the chances that the machine translation will misinterpret them - to an English speaker the intended meaning may be clear, but a machine can be misled.
- ❌ record past time off
- ✅ Record my time off from a recent absence
- ✅ A record of the time off I have taken in the past
- ✅ A record of my team’s time off from some time period in the past
- ✅ Stop recording times from the past
- Minimize idiomatic language.
- Especially avoid partial idioms
- ❌ “It’s been ages!”
- ✅ It’s been a long time since you sent me a message.
- Expect that extended metaphors will not translate well. At best, the extended metaphor will be lost; at worst, non-English speaking employees will be confused about how they missed the announcement that their company is now engaging in aerospace engineering.
- ❌ As we embark on this exhilarating journey through H2, remember that every one of us plays an integral role in launching this rocket. From our engineers and product developers to our sales and marketing teams, each contribution adds to the momentum that propels us forward. Let's harness the energy of our collective ambition, fuel our passion with purpose, and navigate the challenges ahead with resilience and determination. The countdown has begun, and the horizon is brimming with possibilities. Together, we are more than just a team; we are pioneers on a mission to redefine what's possible.
- Especially avoid partial idioms
- Provide context for possibly niche terminology.
- ❌ We have an important update on RTO.
- ✅ We have an important update to our RTO (Return to Office) policy.
- ✅ We have an important update to our Recovery Time Objective (RTO) policy.
- Use consistent terminology
- Ex: If you use “employee” or “team member,” always use the same term.
- Avoid slang and other creative use of words
- Be careful of corporate jargon. Because these terms are so widely used in corporate settings, it’s easy to forget that they are metaphorical and may not translate well. For example, the translations of “needle mover,” “drill down,” “churn” might invoke images of injections, carpentry, and butter.
- Custom terminology has the risk of being untranslatable - for example, at Moveworks, employees are called “Movesters”, and there aren’t any equivalents in other languages.
- Jokes involving plays on words won’t translate.
- Check for cultural sensitivity
- Short greetings that feel fun and friendly in English often cause translation mistakes (usually because they are translated literally) - “Hey there!” can get translated as “Hey - Over there!”
- Formality may be interpreted differently across locales - e.g. informal English is friendly, but in translation it may cause offense in a business setting.
- Norms around how to refer to people in the workplace vary across cultures.
- Your carefully-chosen emoji may mean something completely different in another culture.
Updated 3 months ago