Great Localization Starts Long Before Anyone Starts Translating – Localization Process
One thing my easiest localization projects have in common is that they usually begin long before anyone starts translating.
That may sound surprising. But many of the biggest localization challenges have very little to do with language. They're about preparation. When terminology is unclear, when screenshots are missing, when nobody's quite sure who the audience is, then the translation becomes much harder than it needs to be. No amount of linguistic skill fully compensates for it.
Before Anyone Translates
Before I start working on a document, I usually want to know:
Who is this for?
What are they trying to achieve?
Where will this text appear?
Is there a glossary?
Is there a style guide?
Are there screenshots?
Is there previous content I should match?
Those questions often save more time than any CAT tool ever could. A translator working without answers to them isn't really translating yet; they're guessing and hoping the guesses hold up during review.
During the Localization Process
Good localization isn't a one-way process. The best projects involve questions, conversation, feedback, clarification, and a back-and-forth, not a handoff.
Sometimes one answer from the client saves dozens of unnecessary edits later. A quick clarification on tone, or on what a specific term refers to in context, can prevent an entire batch of content from needing a second pass.
Before Publication
Is the translation finished? Great. Now I want to know:
Does it fit the interface?
Does the button fit?
Does the SEO still work?
Does the terminology stay consistent?
Does the Swedish feel natural?
That's where QA becomes much more than proofreading. It's the point where language, design, and product experience all have to hold together at once — not just each in isolation.
Why Screenshots Matter More Than People Expect
One thing years of software localization have taught me is how valuable screenshots are. A single UI string can often be translated in several perfectly correct ways. But without seeing where it actually appears, choosing the best option becomes much harder than it should be.
Sometimes one screenshot answers five translator questions before they're even asked.
Questions Worth Answering Before Localization Starts
Who is the audience?
What is the purpose of this content?
Is there a glossary?
Is there a style guide?
Are screenshots available?
Who reviews terminology?
Are SEO requirements defined?
Is there enough context to judge what fits, not just what's technically accurate?
Final Thought
During my years of working with Swedish localization, I’ve realized that successful localization projects rarely depend on finding better translators. More often, they depend on giving translators the information they need to make good decisions.
The better the preparation, the better the outcome — every time.
I'm Tess Whitty. I've spent more than 20 years localizing content and product experiences for the Swedish market — translation, UX writing, and SEO, all treated as parts of the same job rather than separate steps.
Comments