Consistency and Standards / User-Centered Design

Behavioral Consistency

Similar actions produce similar outcomes, regardless of where they occur in the interface.

Click on three dots menu

Ensure the same interaction leads to the same result everywhere

Change outcomes for the same action depending on the screen

Align gestures, clicks, and shortcuts across features

Introduce special-case behaviors without clear reason

Test interactions across the entire product, not in isolation

Assume users will relearn behavior in different sections

External Standards

The interface follows established platform, industry, and web conventions, reducing the learning curve.

Follow OS and platform-specific guidelines

Redefine common patterns without strong justification

Use familiar symbols and interaction models

Assume novelty is more important than usability

Respect accessibility and web standards

Break conventions for purely aesthetic reasons

Internal Consistency

The system behaves the same way in similar situations, so users can rely on patterns they have already learned.

Apply the same rules to similar components

Create hidden exceptions to established behavior

Centralize logic for shared interactions

Let different teams define behavior independently

Document patterns and enforce them

Rely on memory instead of guidelines

Pattern Reuse

Established solutions are reused instead of reinvented, strengthening familiarity and efficiency.

Some reusable web components

Reuse proven UI patterns

Design new components for already-solved problems

Maintain a shared component library

Fork components without clear necessity

Optimize patterns through iteration

Reset design decisions with each feature

System Integrity

The interface feels like a single, coherent system rather than a collection of disconnected parts.

Separated components which compose complex components

Design features as parts of a whole

Treat each section as a standalone product

Ensure transitions feel natural and connected

Mix conflicting interaction paradigms

Align design, content, and behavior

Allow visual or functional drift over time

Terminology Consistency

Words and labels are used consistently to avoid confusion and misinterpretation.

off

on

Use one term for one concept

Introduce synonyms for the same action

Maintain a shared glossary

Change labels without updating all occurrences

Validate terminology with users

Favor internal jargon over user language

Visual Consistency

Visual styles are applied uniformly, reinforcing recognition and predictability.

Apply the same visual rules across the interface

Introduce ad-hoc styles for individual screens

Use design tokens and style guides

Let visual inconsistencies accumulate over time

Ensure visuals reinforce function

Use decoration that conflicts with established meaning

Consistency and Standards