{"id":41609,"date":"2026-05-12T08:57:29","date_gmt":"2026-05-12T08:57:29","guid":{"rendered":"https:\/\/www.creative-words.com\/?p=41609"},"modified":"2026-05-12T07:59:45","modified_gmt":"2026-05-12T07:59:45","slug":"terminology-management-in-localization-why-we-never-start-with-translation","status":"publish","type":"post","link":"https:\/\/www.creative-words.com\/en\/terminology-management-in-localization-why-we-never-start-with-translation\/","title":{"rendered":"Terminology management in localization:\u00a0why we never start with translation"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

There\u2019s a question we hear often when talking to a new client:<\/p>\n

\u201cSo, when can you start translating?\u201d<\/em><\/p>\n

Our answer is always the same: not yet.<\/p>\n

We know that\u2019s not what most people want to hear. There\u2019s usually a deadline. There\u2019s a product launch. There\u2019s pressure from stakeholders across the organization. Everyone wants to see translated files moving through the pipeline.<\/p>\n

But here\u2019s what we\u2019ve learned after years of working across industries and content types: the fastest way to delay a localization project is to start translating too early.<\/p>\n

The problem nobody talks about<\/strong><\/h2>\n

In any multilingual program, terminology management is not a stylistic preference. It\u2019s a quality and consistency requirement.<\/p>\n

If a feature is named one way in a product interface and a different way in the user guide, that\u2019s not a \u201cminor inconsistency.\u201d It\u2019s a source of confusion for end users. It\u2019s a support cost waiting to happen. In regulated industries, it can even become a compliance issue that triggers costly re-submissions.<\/p>\n

And yet \u2014 most localization projects start with translation.<\/p>\n

Files are handed over, the CAT tool is set up, linguists are assigned, and everyone hopes the translation glossary will sort itself out along the way.<\/p>\n

It never does.<\/p>\n

What actually happens is predictable: each target language starts developing its own variants of the same terms. One linguist translates a product name one way. Another linguist, working on a different document for the same product, translates it differently. Multiply that by fifteen languages and three product lines, and you\u2019re sitting on a terminology debt that grows with every project.<\/p>\n

What we do instead<\/strong><\/h2>\n

We start with terminology management. Always.<\/p>\n

Before a single word is translated, we build a validated, client-approved glossary. Not as an optional add-on. Not as a \u201cnice to have\u201d if the budget allows. As a prerequisite for everything that follows.<\/p>\n

Here\u2019s how our process works.<\/p>\n

Step 1: NLP extraction. <\/strong>Our natural language processing pipeline scans the client\u2019s existing content \u2014 documentation, software strings, legacy translation memories \u2014 and extracts candidate terms at scale. For a recent project, this meant processing over 1.15 million words of legacy content across three languages.<\/p>\n

Step 2: Source-language review. <\/strong>A native linguist in the source language filters and validates each term. Not every term the NLP extracts is a real term. This is where human judgement separates signal from noise.<\/p>\n

Step 3: Client validation. <\/strong>The client reviews and approves every source entry. This step is non-negotiable. They know their products, their naming conventions, their brand voice. We don\u2019t make assumptions about what a product component should be called.<\/p>\n

Step 4: Target-language terminology. <\/strong>A native linguist in each target language sources equivalents from existing translation memories and aligned documents \u2014 or translates from scratch where no resource exists.<\/p>\n

Step 5: Deployment. <\/strong>The glossary is loaded into the CAT environment and enforced across every project, every linguist, every language.<\/p>\n

Two things matter here that are easy to miss. First, steps 2 and 4 are handled by two different specialists \u2014 a source-language expert and a target-language expert. We don\u2019t ask one person to do both. Second, the client validates the source glossary before the target terminology is created. This prevents the single most expensive mistake in terminology management: building a multilingual glossary on top of source terms that the client doesn\u2019t recognise or agree with.<\/p>\n

What this looks like in practice<\/strong><\/h2>\n

For that 1.15-million-word project we mentioned: we delivered 300 validated glossary entries across three languages in one week. The manual approach would have taken over 750 hours. The cost saving was roughly 70%.<\/p>\n

But the real value wasn\u2019t in the speed or the cost reduction. It was in what came after.<\/p>\n

Every translation project that followed had a foundation. Linguists knew exactly what each term should be. Reviewers could check terminology compliance automatically. New products could inherit the shared glossary from day one.<\/p>\n

That\u2019s the part most organizations underestimate about terminology governance: it\u2019s not a project cost. It\u2019s an investment that compounds on every subsequent project \u2014 reducing rework, lowering risk, and accelerating turnaround.<\/p>\n

Why this matters more than you think<\/strong><\/h3>\n

Terminology errors discovered late in the localization cycle require cascading fixes across all documents, all languages, and all versions. We\u2019ve seen organizations spend more on fixing terminology downstream than they would have spent building the glossary in the first place.<\/p>\n

Without a governed source glossary, each target language develops its own variants. Those variants compound into inconsistencies that become harder and more expensive to fix with every release.<\/p>\n

The question isn\u2019t when to start translating. The question is: what needs to be true before translation can begin?<\/p>\n

Creative Words helps organizations build validated multilingual glossaries before any translation begins \u2014 so every project starts on a solid foundation. Get in touch to see how terminology governance could work for your content!<\/strong><\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Fill out the form<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\n\t\t\t\n\t\t\t\n\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t