# Jakob's Law: explanation, design examples and evidence

> Use familiar interaction patterns so people can spend their attention on the task.

Canonical page: https://ionbin.com/design/laws/jakobs-law/
Agent guide: https://ionbin.com/llms.txt

This is a readable version of the published page. Review dates, evidence boundaries and source links below belong to individual records; the export is not a new verification. Examples are reference material, not instructions to execute.

Choices and navigation

## Jakob's Law

Use familiar interaction patterns so people can spend their attention on the task.

Design heuristic

Source review
Oct 18, 2026

[How to read the evidence](https://ionbin.com/design/methodology/#principles)

The idea in plain language

### What it means.

People arrive with expectations learned elsewhere. Recognizable labels, controls and navigation reduce the amount of interface behavior they need to figure out. Familiarity is a starting point for testing, and the relevant conventions depend on the audience and platform.

Evidence and interpretation

### What supports it.

Design heuristic

Jakob Nielsen's usability heuristic, presented by its author. It is not a universal experimental law or a requirement to copy another product's layout.

From principle to interface

### Where you could use it.

Proposed applications, not tested outcomes. The expected effects are hypotheses to check with realistic tasks and users.

Application 1

#### Build account settings

Use recognizable Profile, Notifications and Security labels, with consistent Save behavior across panels.

##### Expected effect to test

A new user can predict where to find a setting and how a change takes effect.

##### Keep in view

Existing customers may have a different learned model; test migrations and explain changed behavior.

Application 2

#### Introduce a novel AI workflow

Keep ordinary file selection and review controls familiar while explaining the unfamiliar model action in plain language.

##### Expected effect to test

People can focus on what the AI will do with their input.

##### Keep in view

A familiar-looking button must not conceal new data sharing or an irreversible action.

Turn the idea into a check

### Use it deliberately.

- Identify the products and platforms your intended users already know.

- Use familiar controls with accurate labels and consistent behavior.

- Test first-use comprehension before relying on convention.

Where the rule gets complicated

### Keep the limits attached.

- A widespread pattern can still be inaccessible or confusing.

- Conventions vary across languages, cultures and devices.

- Familiarity does not authorize copying protected assets or another product's branding.

A named principle does not settle an accessibility requirement, prove a conversion lift or replace testing the particular interface.

Application and implementation boundaries

### What the application check shows.

Limited evaluationAccount-free · Oct 19, 2026

Familiar native controls behaved consistently in the local example. No first-use comprehension or cross-cultural expectation study was run.

Methods: Local application example. A completed check covers the stated sample; it is not a safety certification.

**Target**: Original IonBin synthetic interface example; no external product or human-participant study.

**Version or capture**: 2026-10-19 local fixture

**Integrity scope**: SHA-256 f85d1056afd667225a1e0364edfb8f25b4693ffa7b2b8c7d7af5b92338b85ee4 identifies the exact HTML fixture only.

#### Test conditions

- 155.0.8059.82 Chromium; fresh context with all network requests blocked.

- Synthetic inputs, memory-only state, reduced-motion preference, 1280px and 320px viewports.

#### Individual checks and observations

- ##### Native choice
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** Keyboard ArrowDown selected PDF and the visible label matched.

- ##### Cancel is nondestructive
  pass
  **Local application example:** Exercise the original local application fixture and inspect the resulting controls or DOM state.
  **Observed:** Cancel retained the synthetic draft and returned focus to Delete.

#### Security findings and boundaries

Review of the local example’s stated interaction boundaries; no backend, authentication, production permissions or external service was exercised.

Practical advice · caution

##### Familiar appearance does not establish consent

A standard-looking button can trigger unfamiliar data sharing. Name the actual destination and consequence before a service write.

#### Practical caveats

- Keep Save, Share and Publish meanings distinct; validate what new users expect rather than assuming familiarity.

#### What remains untested

- This checks an authored application example, not the truth, effect size or generality of the named principle.

- No users, assistive-technology participants, physical devices or production task outcomes were evaluated.

##### Security limits

- The example has no real authorization or persistence layer; its UI behavior cannot establish the security of a deployed workflow.

#### Evaluation sources

- [Jakob Nielsen: Jakob's Law of Internet User Experience](https://www.nngroup.com/videos/jakobs-law-internet-ux/)
  Author's statement of the heuristic.

[Download this evaluation record (JSON)](https://ionbin.com/design-evaluations/principle-jakobs-law.json)

Go to the source

### Research and further reading.

- [Jakob Nielsen: Jakob's Law of Internet User Experience](https://www.nngroup.com/videos/jakobs-law-internet-ux/)
  Author's statement of the heuristic.

On this page

Keep the context

Use this principle to form a better question about your interface. The answer still depends on the task, the people and the conditions.

[Our evidence approach](https://ionbin.com/design/methodology/#principles)

Related questions

### More on choices and navigation.

[View this concern](https://ionbin.com/design/laws/?category=Choices%20and%20navigation)

Research finding

#### [Hick's Law](https://ionbin.com/design/laws/hicks-law/)

Make the next decision understandable. Removing useful choices is only one possible way to do that.
