The glossary must cover interface, docs, and support

What it is

Cross-channel termbase governance makes one set of product-concept records usable by the interface, documentation, help search, support, notifications, and approved marketing touchpoints. It is not a word list copied between teams. Each concept and term has an owner, version, status, and channel context so that when users carry a name from the interface into search or support, the other touchpoint can resolve the same concept.

Why it happens

Terminology drift often follows organizational boundaries: product, documentation, and support teams write in different systems, cadences, and local objectives. Their individually reasonable choices accumulate into breaks in the user journey. A shared concept ID connects an interface's preferred label, a full name in documentation, user wording recognized by support, and search aliases without requiring literal identity. Version and effective scope tell each channel what may ship now; ownership resolves new concepts, conflicts, and deprecations. Without those fields, a glossary is a static table that cannot establish freshness or applicability.

Studying it

Sample by task journey. Start with one interface object and trace its concept ID and terms through help search, procedural documentation, support macros, and notifications. Record misses, false matches, manual paraphrases, and version mismatches; interview content producers to distinguish integration gaps, unclear ownership, and rules that cannot express the needed context. Treat user-coined labels in support data as candidate aliases or evidence for a rename, not as preferred terms merely because they occur often.

Where it stops holding

Channels share concepts and rules, not necessarily one surface form. Support may repeat a user's wording before bridging to the canonical name; marketing may use a metaphor that does not collide with a feature name; mandated text may retain a required term. Each exception should still resolve to a concept ID. A termbase governs term records, not translated sentences. TM stores historical translation segments and is not normative. A style guide governs voice, syntax, punctuation, and formatting. Source-language control before translation and the acceptance of localized linguistic assets have their own workflows; this leaf concerns joint consumption and maintenance across product channels.

Applying it

• Make the termbase a controlled data source. Each entry includes at least concept ID, definition, term, state, channel or audience context, owner, version, effective time, provenance, and search aliases, with a change history.
• Define an integration and synchronization owner for the UI design system, documentation platform, help search, and support macros. Name a human verifier in the release checklist where automation is unavailable.
• Record the termbase version used by each deliverable. Block affected content when a channel is stale, ownership is missing, or rules conflict instead of defaulting to an author's remembered wording.
• Audit across channels with concepts as rows and touchpoints as columns, checking preferred terms, controlled variants, search recall, and version. Route new user wording from support into review rather than changing the termbase directly.

Related

• Same group: T1.04.1 Use exactly one term per concept across the product · T1.04.3 Term changes require global replacement and migration notes
• Adjacent: S1.07.3 Terminology must first be consistent in the source language · S4.05.3 Termbases and style guides provide acceptance criteria
• Search terms: cross-channel termbase · terminology owner · term context