A concept shouldn't keep changing its name
People use recurring words to orient themselves within a text. If a website refers to the same thing first as a "customer account," then as a "profile," and later as a "user area," readers have to verify each time whether the same thing is actually meant. This consumes attention and can lead to users abandoning an action. Consistent terms make connections clear and provide confidence for the next step.
Varying terms across multiple pages are particularly problematic. A person might read about an "application" on the information page, encounter a "sign-up" in the form, and then receive a confirmation of "registration." Even if internal teams use these words interchangeably, visitors might assume they refer to different processes. Clear terminology therefore ensures consistency across the information page, form, confirmation, and advisory information.
A glossary can document chosen terms and explain their meanings. However, its primary value does not lie in simply being a long list of words. It helps content teams, translators, and subject matter experts consistently refer to the same concepts. For readers, the crucial factor remains that the necessary explanation appears within the content itself. No one should have to leave a page just to understand an essential sentence.
Good terminology starts with the language of the reader
Organizations often have their own language, shaped by specialized procedures, laws, or internal areas of responsibility. Visitors are unfamiliar with this background. They search for "reporting a move," even though the responsible team refers to it as "statutory residency registration." Content that is easy to understand acknowledges the user's familiar search terms and then - if necessary - guides them to the official terminology. This keeps access open without sacrificing technical accuracy.
Observe the words people use in search queries, consultations, and follow-up questions. Recurring misunderstandings indicate where an internal term requires explanation or could be replaced. Existing correspondence and forms also provide clues: if a term appears differently on the website than in a document, the two designations should be visibly linked so readers recognize they refer to the same process.
The most common word is not always the best one. It may be ambiguous, derogatory, or technically incorrect. Therefore, evaluate meaning, context, and impact together. For topics such as disability, illness, or migration, involve the people affected, as preferred self-designations can change and vary between groups. A respectful choice cannot be based solely on search frequency or internal habit.
Technical terms are useful when they provide precision.
Clear language does not require avoiding every technical term. Some terms define a legal status, medical diagnosis, or technical function more accurately than any brief paraphrase. If readers encounter the term later in an official notice, conversation, or form, familiarity with it can actually be helpful. The crucial factor is ensuring its meaning is clear the first time it appears.
A good explanation links the technical term to its practical impact. Instead of merely providing a dictionary definition, it shows what the term means for the individual. For instance, regarding a co-payment, it is important to know the amount the person pays themselves and at what point the insurance takes over. This information is more helpful than an abstract description of the contractual principle. Examples should illustrate typical cases without presenting rare exceptions as the general rule.
Not every technical term warrants the same level of prominence. Internal acronyms, product codes, and department names are often unnecessary, as they do not help readers make decisions. If a term is relevant only for background processing, it should remain there. Technical terminology is used when it provides orientation or precision, not to make institutional processes visible in the public-facing text.
Explanations belong at the point of the first significant use.
A glossary at the end of a website can be useful, but it does not fix an incomprehensible main text. Readers need the explanation right where they need to understand a statement or make a decision. A brief parenthetical addition, a separate sentence, or a clearly labeled note may suffice at the first significant mention. The introduced term can then be used consistently throughout the rest of the text.
The form of the explanation depends on the content. A simple substitute works for familiar, everyday concepts. Complex conditions, however, require a full sentence or an example. Pop-up notes can provide supplementary information but must not be the only source of it if they are difficult to access via touchscreens, keyboards, or assistive technologies. Crucial information should always remain available as standard page content.
Avoid explanations that themselves contain new technical terms. Defining "interoperability" is of little help if the definition relies on terms like "system heterogeneity" and "interface compatibility." Instead, describe the practical interaction involved. Can data be exchanged between two programs without re-entering it? A concrete effect makes the term tangible while also demonstrating its relevance to the text.
A useful glossary is based on the actual questions readers have.
A glossary should include terms that appear frequently, are important for usage, and are not generally understood without explanation. A comprehensive collection of all an organization's terminology quickly becomes unwieldy. Readers do not go there looking for an internal encyclopedia, but rather for help with a specific term. Therefore, start with terms that recur in key user journeys or are known to prompt inquiries.
Each entry requires a clear label and an explanation written in the language of the intended audience. Supplementary synonyms can be helpful if people are searching for a different word or using an older document. An example is useful if it clarifies the application. Sources or technical notes may be important for internal purposes but should not clutter the readable explanation with administrative details.
Navigation also determines utility. An alphabetical glossary works only if readers know the exact spelling. Search functions, cross-references from common variants, and thematic access points can make it easier to find information. Nevertheless, the glossary should not become a mandatory step. Direct links from the term requiring explanation are helpful, provided the original content remains easily accessible after the reader has consulted the definition.
Consistent terminology simplifies the editorial workflow.
Editorial teams make minor decisions about wording every day, often under time pressure. Without shared guidelines, variations emerge that may seem plausible in isolation but cause confusion when viewed together. A well-maintained glossary indicates the preferred term and explains how it can be described to readers. It does not relieve editors of the need to think; rather, it prevents the same fundamental question from having to be resolved anew on every page.
Examples drawn from actual sentences are particularly helpful. An isolated term reveals little about whether it works well as a heading, a button label, or an explanation. Therefore, demonstrate how the term is used in typical content and highlight any ambiguous variations that should be avoided. These examples must serve as a guide rather than becoming rigid text blocks that get copied into inappropriate contexts.
Subject matter experts and the editorial team should clarify terminology collaboratively. The experts ensure the meaning is accurate, while the editorial team identifies points where readers might lose the thread. If the two parties merely exchange finished phrases, conflicts often remain hidden. A brief discussion about the actual action involved usually leads to a good solution more quickly: What must a person be able to know, decide, or do after encountering this word?
Multilingual content requires shared concepts, not identical words.
When translating, it is not enough to simply assign a single foreign-language equivalent to each German word. Terms carry different meanings depending on the country, administrative system, or culture. A seemingly direct equivalent may actually refer to a different service or legal implication. Translators therefore need not only the preferred term but also a clear explanation of the underlying concept and the context in which it is used.
A multilingual glossary helps ensure consistent translation of recurring names, technical terms, and key actions. It was intended to show which terms should be translated, which official names should remain unchanged, and when an explanatory phrase is preferable to a concise term. This ensures, for example, that the name of a German authority is not confused with a supposedly equivalent foreign agency, but is instead clearly described as the responsible body.
Natural language remains more important than formal word-for-word equivalence. In a given language, the same action may require a different verb depending on the sentence. A forced one-to-one translation can seem unnatural or even alter the meaning. Therefore, the glossary should ensure conceptual consistency, while qualified translators select the phrasing best suited to their readers. Clarifying ambiguous concepts often leads to improvements in the German source text as well.
Inconsistencies between the website, forms, and advisory services must be brought to light.
Terminology issues often arise not within a single text, but across different channels. The website promises a "reservation," the confirmation refers to an "order," and customer service speaks of a "job" or "assignment." While employees may understand the internal distinction, it remains unclear to customers whether costs have already been incurred. Therefore, verify key terms across web pages, messages, documents, and conversations.
Not every deviation is incorrect. A brief button label may differ from the detailed designation used in a contract. The crucial factor is that the context remains clear. If different words actually refer to different states, those differences must be explained. For instance, "paid," "submitted," and "reviewed" denote distinct steps; equating them would be just as detrimental as using an unnecessarily large number of names for the same state.
Technical systems can limit changes because field names or templates are hard-coded. In such cases, the user-friendly term should at least appear in the visible interface and, if necessary, be linked to the system term. Correcting the issue at the source pays off in the long run. Otherwise, content teams are forced to repeatedly bridge the same linguistic gap, and translations perpetuate an inconsistency that was never resolved at a functional level.
Terminology evolves alongside products, services, and society.
A glossary is not a static reference work. New services emerge, responsibilities shift, and familiar terms take on new meanings. Even respectful forms of address evolve. Review an entry if the underlying process changes, readers repeatedly ask for clarification, or the groups concerned prefer a different term. Otherwise, a rigid glossary can actually hinder the very clarity it is intended to foster.
Changes should not cause existing content to diverge unnoticed. When a preferred term is replaced, search for its key occurrences and examine the specific context. Automatic replacement can generate incorrect forms or distort historical documents. For multilingual content, translators need to know whether only the German term has changed or the concept itself.
Usage data provides additional insights. Frequent searches yielding no results, users abandoning a process after viewing an explanation, and recurring customer service inquiries can indicate missing or unsuitable terms. Direct conversations reveal how people paraphrase an explanation in their own words. Such observations are more valuable than the mere number of glossary entries, as they clarify whether the terminology is truly helpful in real-world situations.
Clear terminology links content, action, and translation.
Good terminology usually goes unnoticed by readers. They do not have to wonder if two words mean the same thing, and they encounter key terms consistently throughout the text. Unfamiliar terms are introduced in an understandable way without disrupting the flow of reading. This builds trust in the content, especially when users switch between information pages, forms, confirmations, and personal consultations.
For editorial teams, a focused glossary creates a shared linguistic foundation. Instead of simply amassing technical terms, it records key decisions alongside useful explanations and examples. This provides translators with the necessary context regarding meaning, enabling them to choose natural phrasing. At the same time, subject-matter experts can see where their precise concepts need to be explained more clearly for the general public.
Start with a few terms from a frequently used user journey and review them within the full context. Do the term, explanation, form, and message align? Do readers understand the crucial significance, and does it work in other languages as well? When these questions are answered, a glossary evolves from actual usage and improves content, rather than simply becoming another collection.