Labels must use the user’s words, not internal jargon

What it is

Words on navigation have to be the words people use when they look, not department names, product codenames, or statute abbreviations. User vocabulary is lookup language; internal jargon is production language. Writing “HR shared-services centre” on the nav hides “request time off” behind a name nobody will click. A label’s job is to preview what follows, and the preview must be in the receiver’s lexicon, not the sender’s.

Internal terms are not always wrong. They are precise in expert tools and legal source text. What is wrong is using them as the first-layer words of a finding entrance.

Why it happens

Information scent is a statistical link between a word and hidden content. User words have co-occurred with the target in the person’s experience (“expenses,” “invoice,” “time off”), so they preview. Internal terms co-occur only in staff manuals and system fields (“SSC,” “spend control,” “OA workflow”) and are scentless strings to the untrained. The decision to click happens before a definition can be read, so first-layer labels get no chance to “explain, then choose.”

Jargon does a second kind of damage: it signals that only people who already know the word are the intended users, and drives everyone else to search or away. If search also indexes internal field names, both paths fail together.

Studying it

Align two lexicons: words people spontaneously produce in tasks, and labels the system currently uses.

• Paradigms: free listing (“what would you click to find time off”), query logs, self-naming in open card sorts; then align those with current nav labels. Reverse card sorts: show a label, ask what sits behind it.
• Independent variables: label source (high-frequency user words / department names / product codes), presence of a parenthetical gloss.
• Dependent variables: label–target match rate, first-click accuracy, rate of interpreting the label as some other content.
• Methodological note: staff are not a source of user vocabulary. “We all know what SSC means” in a focus group does not generalize. Successful queries in logs may already be post-learning of internal words; stratify new users. Bilingual products have two user vocabularies; translating internal jargon is not enough.

Where it stops holding

In professional software the users already hold that terminology (clinicians, pilots, lawyers); the specialist words are the user vocabulary, and everyday substitutes lose scent. When a legally required official name must appear, it can be the on-page title while the entrance label stays a lookup word, joined to the official name after arrival. A brand name works as a label only when people already use that brand as a lookup key; otherwise it is still an internal code.

Applying it

• Pull first-layer label candidates from spoken tasks and search terms. Do not lift names from the org chart.
• Reverse-test each candidate: give only the word, ask what a click would reveal. On a wrong answer, change the word; do not patch it with a help sentence.
• Internal terms may appear in body copy after arrival, in filter fields, or in an expert mode—not in the first layer of global navigation.
• Verify by giving a first-time user their own task words and watching the nav. If those words match no label, the layer is still internal language.

Related

• Within the group: G1.04.2 One concept gets one label across the site · 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: user vocabulary · labeling system · information scent