Slack kept Workspace-Management in German, but replaced an English pony with a sweet in Spanish.
Both choices appear in localization manager Anca Greve’s 2018 account of localizing Slack. The team also wanted its Japanese copy to feel like a helpful colleague, without excessive politeness. One brand had different rules for terminology, playful messages and the relationship with its reader.
Should your brand keep English too? Only when you have a reason for that particular term, audience and language. Slack’s example gives you a decision to make, not a rule to copy. Before translating your next document, separate the elements that must remain exact, the concepts that need a consistent local name, and the wording that can change to do its job.
Keeping English is a decision, not a default
Greve explained the German choice by pointing to English words already used in everyday German. That does not establish that your customers know an unfamiliar English feature name. Nor does it make every English word in a source document a protected brand asset.
Ask why a term should stay. Is it an official product name? Does it need to match a label the reader will see? Or is it simply familiar to the team that wrote the original?
The last answer deserves scrutiny. A sales team can use an internal abbreviation for years while a new customer has never encountered it. Write down the concept and the reader’s task before deciding whether the letters themselves matter.
Start with the meaning, not just the spelling. The English word bank can refer to a financial institution or the edge of a river; each needs its own definition. Torsten Machert’s terminology model separates the concept, preferred terms, deprecated terms and equivalents in other languages. Use that distinction to check whether your glossary identifies the intended concept or merely pairs isolated words.
Your glossary and your voice guide have different jobs
Collect the expressions your team uses repeatedly in a shared glossary, as copywriter Alex Cattoni recommends. Then decide which part of that familiarity should travel: the exact phrase, an approved local equivalent, or its purpose? A familiar expression is useful only when the person translating it knows what makes it matter.
A product term may need the same local name throughout a proposal. A friendly closing may need different words. Putting both in a single “always translate this as that” list hides the distinction.
Separate copy that helps someone navigate or order from copy that expresses personality. Brand designer Arek Dvornechuck distinguishes these functional and expressive roles. Turn that distinction into a specific instruction for the passage: how serious, formal, respectful or enthusiastic should it be? A confirmation message and a campaign headline may need different answers.
A tone brief describes the writing choices a translator needs to make. It does not establish that a glossary or a particular tone will increase sales.
Give permission to adapt, with a boundary
Slack’s Spanish sweet preserved a playful reward after the reader had cleared their unread messages. Keeping the pony was not the only way to preserve that function. This was a documented choice for Slack’s copy in 2018; it does not tell us how every Spanish-speaking audience would respond today.
Mailchimp’s writing-for-translation guidance adds a useful restraint. It gives translation-specific rules precedence over its general style guidance and asks writers to consider whether an informal register fits the particular language. It also recommends using one term consistently for the same thing. An informal English brand voice is therefore an input to a local decision, not enough to settle it.
For a commercial document, define the freedom explicitly. You might allow a metaphor to change while requiring the offer, qualification and next step to stay intact. A reassuring rewrite must not turn a possibility into a guarantee.
Make three decisions before the document leaves your team
The following is our suggested handoff method. It is a synthesis of the cases above, not a test we ran on Slack or a result from Reasoning Translator.
| Decision | What to supply | What to check |
|---|---|---|
| Retain an exact element | The official spelling, where it applies and why it must match. | The element is intact in the places covered by that rule. |
| Standardize a concept | A definition, the target language and variant, an approved equivalent and an example. | The same concept has a consistent name; a different sense has not been forced into it. |
| Adapt a phrase | Its purpose, the relationship with the reader, permitted changes and facts that must stay. | The new wording performs the intended job without changing the promise. |
Keep a separate decision for each relevant language and variant. A Portuguese rule should say whether it covers Portugal or Brazil. An English example should say whether it is intended for a British or American audience. A customer’s country and the language of their readers are separate pieces of information.
For each uncertain entry, name the person on your team who can approve it. Mark an unresolved choice as unresolved. A blank equivalent is more useful than a confident guess that everyone mistakes for an approved term.
Check the rule on a small passage
Here is an invented English example to make the method concrete: “Your export is ready. Download the file.” Suppose the team wants a more playful version. “Ta-da!” adds personality, but on its own it removes the status and the action. A translation brief can permit a playful opening while requiring both of those pieces of information to remain.
Before applying a rule to a whole document, choose a passage where the distinction matters. Put the original beside the translation, along with the approved term and the instruction. Check meaning and tone separately. Does the reader still know what happened and what to do? Does the wording suit the agreed relationship? Resolve a disagreement by improving the rule or its example, then use that decision for the remaining text.
Reading only the target can reveal awkward wording. It cannot establish that the original offer or qualification survived. Keep the original available for that comparison, and arrange the appropriate language review when your team needs it.
Bring the rules to the translation
For brand voice translation, “make it sound natural” becomes a more useful instruction when it comes with settled terms, the reader’s situation and a clear boundary for adaptation. Our worked translation brief can help you organize those inputs.
Reasoning Translator supports providing context, audience, tone and terminology when translating from an original. Use those inputs to explain what may change and what must remain before generating the next version. The method above still needs a check against the source; it is not a guarantee that every term or cultural choice will be right.
Slack’s public account describes its own historical process. The terminology and writing recommendations offer ways to prepare a translation; they do not measure our product’s quality or the revenue effect of these decisions. Decide which parts of your voice are fixed, and give the rest enough direction to work in another language.
