When small language errors turn into big market failures
Your product is ready. The packaging’s final. The site is live.
And then — one line in the user manual confuses buyers. Or a wrong label blocks customs. Or a call-to-action just… doesn’t convert.
We’ve seen it happen. Not because companies don’t care. But because translation looks simple — until it breaks something expensive.
Here are 7 mistakes that quietly sabotage global launches. Plus how to avoid them.
1. Not defining the content type
“Just translate this” isn’t a brief.
Is it regulatory? UI? Marketing? Each has its own standards. Without context, even good linguists guess. And guesses are dangerous when you’re dealing with dosage instructions or liability disclaimers.
What to do instead:
Tag your content. Split it into tracks: legal, technical, creative. Different goals = different teams = fewer surprises.
2. No glossary. No TM. No alignment.
Releasing your first product in six languages?
Better hope everyone translates “operating mode” the same way.
Without a glossary or TM (translation memory):
- Style becomes inconsistent
- Terms change from page to page
- Updates get messy
What to do instead:
Set terminology early. Build a small termbase, even 20 entries. It’ll save weeks (and face).
3. Treating design and translation as separate workflows
You get the design. Then you “just need it translated.”
But German text is 30% longer. Arabic reads right to left. And your dropdown menu? Now cuts off half the words.
What to do instead:
Involve linguists early. Send layout previews. Use formats that keep structure intact: SDLXLIFF, XML, HTML. And test before it’s too late.
4. Ignoring context (and UX)
Ever seen a button that says “Apply” — and you’re not sure if it means submit or put on?
Out of context, strings break. Especially:
- CTAs
- Help text
- Drop-down menus
- In-app messages
What to do instead:
Provide screenshots, flows, or user journeys. Let translators see what users see.
5. Rushing the review stage
Review gets squeezed between launch pressure and marketing deadlines. That’s when real issues slip through:
- Units get swapped (mg vs. mcg)
- Formatting breaks (especially for RTL languages)
- Legal disclaimers lose key phrases
What to do instead:
Build in review time. Use checklists. Set up linguistic QA, not just spellcheck. And never skip regulatory proofreading.
6. Using generalist vendors for specialist content
Your product might be for surgeons. Or aviation engineers. Or financial analysts.
Do your linguists know what “torque-to-yield” means?
If not, they’ll guess. Or ask Google.
And that’s how “valve seat” becomes “throne”.
What to do instead:
Work with teams that know your domain. Look for ISO 17100, subject-matter experts, and translators who’ve actually touched a device like yours.
7. Skipping localization QA in the final build
Translation’s done. Everything’s approved. But in the final UI:
- The menu overlaps
- Translated fields cut off
- One screen shows English, the next French
What to do instead:
Run an in-context QA pass. Let native speakers walk through the build. It takes hours, not days — and saves thousands in fixes.
No comment