Terminology consistency outranks terminology accuracy; synonym rotation is read as different concepts
Aliases: synonym rotation · term stability · concept boundary
What it is
After users have established understanding, stable terminology matters more than pursuing a more precise synonym in each place. If “customer,” “user,” “contact,” and “account” rotate across nearby pages, users read them as different objects, permissions, or life cycles. Terminology consistency outranks local semantic refinement.
Why it happens
Words are the main cue for concept boundaries. Users do not know the author intended a nuance; they treat change as functional change: a new list may filter different content and a new button may have different consequences. Rotation also breaks aggregation by search, filtering, help, and automation. The better path is to establish the model with one stable term, then add precise distinctions in definitions, examples, or advanced notes.
Where it stops holding
Consistency cannot protect a wrong term. If a core word is seriously ambiguous, legally risky, or exclusionary in the domain, migrate it uniformly rather than preserving it forever; migration must synchronize interface, documentation, search, and logs. Different professional contexts may genuinely need two words, but then boundaries must be defined and casual interchange banned.
Applying it
- Specify standard terms, banned synonyms, plurals, abbreviations, and localization keys for core objects.
- Review navigation, buttons, errors, logs, and help; replace undefined near-synonyms.
- When a term must change, create a migration table and aliases for the old term so API and interface do not split.
- Measure synonym-induced confusion and search failure with cross-page findability and explanation tasks.
Related
- Same group: B3.14.1 The match targets users’ world, not the designer’s or the engineering implementation’s world · B3.14.2 Metaphors necessarily break where they exceed the original object’s properties; define their boundary in advance · B3.14.4 Numbers, dates, and units should follow users’ local conventions
- Nearby: B2.23 Internal Consistency · T1 Interface Copy and Content
- Search terms:
terminology consistency·synonym rotation·controlled vocabulary