Usability · Foundation

Consistency and Standards

Similar things should look, sound and behave similarly.

design systemscopypatternsconventions

5 minute field note

Helps create

Predictable use

Overview

Make the interface carry more of the effort.

Use a coherent product language and respect platform conventions so people can transfer what they learn.

Human impact

Why it matters

Similar things should look, sound and behave similarly. When the interface does not account for this, people spend effort interpreting the product instead of completing the task. Applied with context, the principle supports predictable use without removing meaningful choice or control.

Design hypothesis

If we apply Consistency and Standards to the decision point, people should reach predictable use with less avoidable friction.

Mechanism

How it works

01

Notice where the task currently asks people to design systems or copy without enough support.

02

Use a coherent product language and respect platform conventions so people can transfer what they learn.

03

Make the smallest change that should improve predictable use, then compare the task before and after.

Interactive experiment

What do people notice and remember after five seconds?

4–6 minutes

Move the cards, then run the five-second recall test.

Priority 1

Revenue at risk

$12,480

Priority 2

Recommended next action

Supporting dashboard information

Priority 3

Recent activity

Supporting dashboard information

Priority 4

Product tips

Supporting dashboard information

Turn the experiment into a decision

01

What happened

A clear visual order helps people recall the primary status and next action after a brief exposure.

02

Why it happened

Position, scale, grouping and contrast direct attention before detailed reading begins.

03

Where to apply it

Dashboards, landing pages, reports, record details and operational overviews.

04

How to validate it

Show the interface for five seconds, hide it and ask what it was for, what mattered and what action came next.

Open the focused lab page

Decision guide

When to use it

Building shared components or navigation
Naming repeated actions and statuses
Adding a feature to an established product

Apply it

Practical checklist

1

Use one label for one action across the product.

2

Keep equivalent controls in equivalent positions.

3

Document component states and behavior.

4

Check new patterns against platform expectations.

Watch for

Common mistakes

Forcing visual uniformity on different tasks.

Treating a design system as a static component gallery.

Changing established language for marketing novelty.

Accessibility considerations

Keep focus, error and selected states consistent.

Preserve native control behavior where possible.

Evidence plan

How to test it

Run a short task-based usability test.

Give five representative people one realistic goal. Watch without teaching, record the first hesitation or error and ask what they expected after the task.

Observe

Completion, hesitation, recovery and whether the system response matches the person’s expectation.

Decide

Keep the change when it improves predictable use without creating a new failure elsewhere.

Use with judgment

Limits and trade-offs

Consistency and Standards is a decision lens, not a universal prescription. Context, frequency, expertise and consequence can change the right implementation.

Optimising only for predictable use can create new costs elsewhere. Recheck access, comprehension, user control and business constraints together.

A polished prototype can still fail in real use. Validate consequential decisions with representative people and realistic content.

Design responsibly

Better outcomes must also be honest outcomes.

Use the principle to reduce avoidable effort, not to pressure people into a choice.

Keep price, risk, consent and irreversible consequences visible before commitment.

Record what evidence supports the decision and what remains an assumption.

Evidence

Sources and interpretation

Design principles are lenses, not automatic answers. Apply them in context and validate consequential decisions with users and accessibility testing.

Keep close

Key takeaways

Similar things should look, sound and behave similarly.

Use one label for one action across the product.

Keep the change when it improves predictable use without creating a new failure elsewhere.

Apply the library

Score your interface in about three minutes.

Run free scorecard