A glossary is a decision system

A useful terminology entry answers more than “what does this word mean?”. It records the preferred term, definition, forbidden or deprecated variants, context, grammatical notes and owner.

Start with high-friction concepts

Do not attempt to inventory every noun. Begin with terms that cause support questions, inconsistent UI labels, translation problems or review disputes.

Separate concept from label

One concept may have several historical names. Model the concept once, choose the preferred label and record aliases. This is especially important for localization.

Put terminology into the workflow

Use the same source for writing guidance, translation and automated linting where practical. A glossary nobody sees during authoring becomes an archive, not a control system.

Give terms owners and review dates

Products change. Definitions should have responsible owners and be reviewed when the underlying behavior changes. Terminology quality is maintenance, not a one-time cleanup.

Applied example

Apply “Terms and definitions: building a terminology system” to one real page rather than discussing the rule in isolation. Choose a page with enough complexity to expose failure: headings, a table, a note, an example, a term that appears several times, and at least one action the reader must perform. Review the page once as an author and once as a reader who does not know the internal product vocabulary.

Record defects in observable terms:

  • Which structure carries meaning that is not available in plain text?
  • Which term changes meaning or spelling across the page?
  • Which instruction depends on context that is never stated?
  • Which rule would be difficult to check consistently in review?

A standard is useful when it helps two editors make roughly the same decision on the same content. If the rule sounds correct but cannot be demonstrated on a representative page, refine the rule, add an example, or narrow its scope before treating it as policy.

Quick editorial checklist

  • A glossary is a decision system. A useful terminology entry answers more than “what does this word mean?”.
  • Start with high-friction concepts. Do not attempt to inventory every noun.
  • Separate concept from label. One concept may have several historical names.
  • Put terminology into the workflow. Use the same source for writing guidance, translation and automated linting where practical.