UX Laws · Foundation

Jakob's Law

People bring expectations learned from other products.

conventionsmental modelsnavigationlearnability

5 minute field note

Helps create

Lower learning effort

Overview

Make the interface carry more of the effort.

Use familiar conventions for common tasks, then spend novelty where it creates meaningful value.

Human impact

Why it matters

People bring expectations learned from other products. 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 lower learning effort without removing meaningful choice or control.

Design hypothesis

If we apply Jakob's Law to the decision point, people should reach lower learning effort with less avoidable friction.

Mechanism

How it works

01

Notice where the task currently asks people to conventions or mental models without enough support.

02

Use familiar conventions for common tasks, then spend novelty where it creates meaningful value.

03

Make the smallest change that should improve lower learning effort, then compare the task before and after.

Try the principle

Same capability, clearer presentation

Start your first project

Use a template or begin with a blank workspace.

Why it helps: the common path is clear while alternatives remain available.

Decision guide

When to use it

Choosing navigation and form conventions
Naming common account or commerce actions
Deciding whether a novel interaction is worth teaching

Apply it

Practical checklist

1

Use familiar names for familiar tasks.

2

Keep standard controls behaving in expected ways.

3

Explain unavoidable differences before they cause errors.

4

Test new patterns with people who did not design them.

Watch for

Common mistakes

Copying a competitor pattern without understanding its context.

Using novelty to decorate a routine task.

Assuming industry familiarity is universal familiarity.

Accessibility considerations

Preserve expected keyboard and assistive-technology behavior.

Use established semantics even when the visual treatment is new.

Evidence plan

How to test it

Compare the decision, not the decoration.

Prototype the current and proposed decision point with the same content. Give representative people the same goal and compare time, errors, confidence and explanation quality.

Observe

Where choice, attention or memory effort changes and whether people still understand the consequences.

Decide

Use the version that supports lower learning effort while preserving informed choice.

Use with judgment

Limits and trade-offs

Jakob's Law is a decision lens, not a universal prescription. Context, frequency, expertise and consequence can change the right implementation.

Optimising only for lower learning effort 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

People bring expectations learned from other products.

Use familiar names for familiar tasks.

Use the version that supports lower learning effort while preserving informed choice.

Apply the library

Score your interface in about three minutes.

Run free scorecard