Internal consistency is judged by whether the same meaning always uses the same expression

What it is

Internal consistency does not mean every screen looks identical. Within one product, a meaning should always map to the same name, icon, control type, interaction result, and feedback; “customer,” “contact,” and “approver” should not drift across pages. The unit of judgment is the meaning-to-expression mapping, not pixels alone.

Why it happens

Users build a concept dictionary from a few encounters: this word points to this object, this icon points to this action, this button saves or executes immediately. Repeated mapping lets them transfer an interpretation to a new page. Synonym switches force them to ask whether a new object has appeared or an old one has been renamed, and visual differences can be misread as changed permissions, states, or consequences. Consistency therefore reduces interpretive variance, not merely visual clutter.

Studying it

Build a meaning-expression matrix, then run cross-task interpretation tests: ask users to name the same icon across modules, distinguish near-synonyms, predict button outcomes, or classify objects. Measure synonym confusion, wrong predictions, first-use time, help queries, and transfer across pages. Vary the number of expression variants, contextual explanation, and control feedback; aggregate by meaning and count mapping conflicts.

Where it stops holding

Consistency cannot override task difference. Actions with the same appearance but different consequences need strong differentiation, and platforms or input methods may require different control forms. Over-unification can flatten a complex domain into wrong categories—for example, calling draft, staging, and publication all “save.” Determine the relations among objects and actions first, then decide which expressions must match.

Applying it

• Maintain a vocabulary for core objects and actions: standard name, banned synonyms, icon, object type, primary action, and consequence level.
• Use the standard object name on every page; when an abbreviation is necessary, bind it to the full concept at first appearance.
• When reviewing buttons and menus, ask: is this expression already used elsewhere? Is the result the same? Does the difference represent a real semantic difference?

Related

• Same group: B2.23.2 Consistency maintained by shared components and a unified vocabulary survives; consistency maintained by documentation erodes over time · B2.23.3 Every locally optimal difference accumulates into overall inconsistency · B2.23.4 The benefits of internal consistency grow with product scale and frequency of use
• Nearby: B2.10 Consistency · T1 Interface Vocabulary
• Search terms: internal consistency · terminology consistency · conceptual model