Abbreviations need a nearby expansion point

What it is

A user who doesn't recognize an abbreviation doesn't need a glossary parked somewhere else — they need a proximate expansion: a hover, a tap-to-expand, or a spelled-out form at first occurrence, placed right next to the abbreviation itself rather than requiring a trip to another screen. The same explanation, moved to a different location, is a completely different cost to the user.

Why it happens

Looking something up in a separate glossary requires interrupting the current task, remembering the term to look up, navigating away, finding it, and navigating back to relocate where you left off — that whole sequence is a context-switch cost, not merely a reading cost. Placing the expansion right next to the abbreviation compresses that cost down to a single hover or tap; the user's gaze doesn't even need to leave its resting point. Both approaches convey identical information, but the cost differs by an order of magnitude, and the entire difference comes from the physical distance between the term and its explanation, and whether a navigation step is required.

Where it stops holding

Not every abbreviation needs expanding: when the target audience is more familiar with the abbreviation than with its spelled-out form (URL, API in a developer-facing interface), forcing an expansion is pure noise and should be skipped. Hover-based expansion doesn't exist on touch devices without a pointer — it needs an equivalent tap-or-long-press trigger rather than a straight port of the desktop hover assumption.

Applying it

• For any abbreviation a meaningful share of the target audience won't recognize, spell it out at first occurrence per screen, or attach a hover/tap expansion layer — don't require navigating to a standalone glossary page.
• On touch devices, substitute long-press or tap for hover so the same proximate-expansion capability remains reachable.
• Skip expansion for abbreviations the target audience is generally more familiar with than the spelled-out form (high-frequency industry shorthand for an expert audience), to avoid adding visual noise for experts.
• Verification: run an abbreviation audit across the interface, marking each one as "needs expansion for this audience" or not, then spot-check whether those that need it actually have a proximate expansion point in the live interface — surfacing the gap between abbreviations that need expansion and ones that have none.

Related

• Same group: A11.05.1 The gap between users' words and the system's words · A11.05.2 Jargon fails at cross-discipline interface boundaries · A11.05.5 Domain experts tolerate higher information density
• Adjacent: A11.04.1 Novices rely on recognition, experts on recall
• Search terms: tooltip · first-use expansion · progressive disclosure