One concept gets one label across the site

What it is

The same thing must be called the same name in navigation, buttons, breadcrumbs, page titles, and empty states. One label per concept is not a tone guideline. It is a one-to-one map between a concept and a string: once people have learned that “Bills” points at that class of object, the next page must not greet them with “Invoice centre,” “Payables,” or “Finance Docs.” Several labels for one concept are read as several features; one label for several concepts is read as the same feature appearing everywhere.

This is label discipline inside the site. Where user vocabulary comes from, and whether two neighbouring labels are easy to tell apart, are separate problems.

Why it happens

People file an object under a label: this word = this kind of thing, to be recognized again on a new page. A near-synonym fails to hit that file, so the system is taken to be offering an adjacent but different capability, and people go looking for the difference—even when the backend is one table. Recognition is cheaper than recall only while the cue is stable. Change the cue, recognition fails, and learning starts over.

Cross-page inconsistency also breaks path memory. Breadcrumb “Account,” sidebar “Personal centre,” title “Me” cannot corroborate each other, and sense of place has to be propped up by visual layout alone.

Studying it

Build a concept–label table; do not spot-check whether copy “sounds nice.”

• Paradigms: pick core objects (orders, messages, bills), harvest every visible string that points at them; then run a recognition test: after learning word A, is word B still treated as the same object.
• Independent variables: number of label variants for one concept, and where variants appear (nav vs body vs notification).
• Dependent variables: rate of being misread as a different feature, cross-page recognition time, extra steps taken to “find the other name.”
• Methodological note: near-synonyms substitute in linguistics and do not substitute on an interface—participants assume the UI will not change words for no reason. Do not replace a behavioural “treated as the same feature” measure with a “means the same” rating. Automated copy scans find variants; deciding whether they truly point at one concept still needs a person.

Where it stops holding

Where contracts and legal pages must use statutory wording, the official name may appear on the page, but the navigation entrance should keep the lookup label and join the two on arrival (“Bills, i.e. VAT invoices”). Different languages and locales have different user vocabularies—that is localization, not intra-site drift; one-concept-one-label still holds inside a language region. A rebrand may show both names briefly, with a retirement date for the old word, or the dual label becomes permanent.

Applying it

• Lock a preferred label for each core object in an interface glossary, shared by nav, buttons, titles, and notices.
• Before release, full-text search for near-synonym variants (bill / invoice / payable). Each hit is either changed back to the preferred word or shown to name a different concept.
• Do not swap synonyms on neighbouring controls to “avoid repetition.” Repetition is the cue recognition needs, not a copy defect.
• Verify by letting someone learn the label on the first page, then identify the same object on later pages with nav names covered. A miss or a hesitation means the word changed mid-journey.

Related

• Within the group: G1.04.1 Labels must use the user’s words, not internal jargon · G1.04.3 Distinctiveness of labels affects choice more than precision
• Adjacent: G1.08 Terminology consistency · G1.10 Controlled vocabularies and synonyms · T1.04 Terminology consistency and glossaries
• Search terms: one label per concept · label consistency · controlled vocabulary