# Labeling Systems

Labeling systems use consistent words and naming rules to represent categories, destinations, actions, and concepts across a product.

- Type: practice
- Domain: Experience & interface
- Level: Intermediate
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/labeling-systems/>)

## What it means

A labeling system is the coordinated set of names used to describe information and controls in an experience. It covers navigation labels, headings, link text, taxonomy terms, button names, and metadata values. Effective systems define not only individual words but also perspective, grammar, specificity, and relationships so labels work as a family.

## Why it matters

Users make rapid predictions from labels before they click or read further. Distinct, concrete terms improve information scent, reduce wrong turns, and make interfaces easier to scan. Shared labeling rules also prevent teams from calling the same thing by several names or using one label for several different concepts.

## When to use it

Use labeling-system work when designing navigation or taxonomy, consolidating products, establishing a design system, or correcting inconsistent terminology. It is especially useful when user language differs from internal jargon, similar categories compete, or localization exposes labels that rely on cultural assumptions.

## How it works

1. Inventory current labels and note duplicates, synonyms, unexplained abbreviations, and inconsistent grammatical forms.
2. Gather the words users employ in interviews, support conversations, search logs, and domain-specific tasks.
3. Define naming principles for point of view, tone, length, specificity, and the distinction between actions and destinations.
4. Write labels as a complete set, checking that neighboring choices are mutually clear rather than merely attractive in isolation.
5. Test interpretation and destination prediction, then document preferred terms and exceptions for future contributors.

## A practical example

An insurance service replaces internal menu labels such as “FNOL” and “Policy Servicing” with “Report an accident” and “Change your policy.” It standardizes buttons as verb phrases and category names as nouns. Tree tests confirm that customers can distinguish making a claim from reviewing an existing claim.

## Where it breaks

A familiar term for one audience may be obscure or misleading for another, and short labels can lose necessary context. Terminology also changes across regions, professions, and product maturity. A style guide helps consistency but should not override evidence from users or the semantic needs of accessibility and localization.

## Common mistakes

- Choosing labels in stakeholder workshops without checking user language.
- Optimizing each label separately so the full set becomes inconsistent or overlapping.
- Using vague catchalls such as “Resources,” “Solutions,” or “Other” for important content.

## Sources

1. [Better Link Labels: 4Ss for Encouraging Clicks](<https://www.nngroup.com/articles/better-link-labels/>) — Nielsen Norman Group · Research-based guidance
2. [Tree Testing: Fast, Iterative Evaluation of Menu Labels and Categories](<https://www.nngroup.com/articles/tree-testing/>) — Nielsen Norman Group · Method guidance
3. [What Is Information Architecture?](<https://www.iainstitute.org/sites/default/files/what_is_ia.pdf>) — Information Architecture Institute · Institutional overview

## Related topics

- [Navigation Design](<https://wiki.soroush.uk/topic/navigation-design/>)
- [UX Writing](<https://wiki.soroush.uk/topic/ux-writing/>)
- [Information Scent](<https://wiki.soroush.uk/topic/information-scent/>)
