Use the same words and graphics for the same meaning
Aliases: terminology consistency · graphic consistency · concept mapping
What it is
The first test of consistency and standards is a stable mapping: one object, state, or action uses the same word, icon, control form, and feedback everywhere. Conversely, the same word or graphic should not carry two meanings that require different responses.
Why it happens
Users learn a word-graphic-result triple from the first successful action and transfer it to later pages. Stable mapping lets recognition replace recall and allows screen readers, search, help, and automation to share one concept. Synonym switches or overloaded icons force re-interpretation at every occurrence, and errors occur precisely where users believe they already know the meaning.
Studying it
Build a meaning-expression matrix and extract every label, icon, control type, message, and result across modules. Use cross-page interpretation tasks to measure agreement in users’ descriptions, prediction accuracy, confusion matrices, and help queries; check whether one meaning has variants or one expression has different consequences.
Where it stops holding
Consistency is not mechanical sameness. Platforms, input methods, and consequences may require different controls; brand styling may vary while the interaction contract must not drift. A professional domain may have two near-synonyms for different workflows; define and exemplify them rather than collapsing them into a wrong category.
Applying it
- Maintain vocabulary, icon, and action tables specifying standard expressions and banned variants for each meaning.
- Pair every graphic with text, and declare result, permission, and irreversibility for critical actions.
- Check whether search, routes, components, and copy read the same concept key.
- Test whether users can explain same-named objects and actions with one consistent sentence across pages.