> ## Documentation Index > Fetch the complete documentation index at: https://meta.niceshare.site/llms.txt > Use this file to discover all available pages before exploring further. # Jakob's Law > Jakob's Law says users spend most time on other sites and expect yours to work the same. Learn origin, UX tactics, evidence, and when to innovate. **Category**: Laws
**Type**: Usability / Internet user-experience heuristic
**Origin**: Jakob Nielsen, Nielsen Norman Group, “End of Web Design” (2000)
**Also known as**: Jakob's Law of the Internet User Experience **Quick Answer** — **Jakob's Law** states that **users spend most of their time on other sites**, so they prefer yours to **work the same way** as sites they already know. Jakob Nielsen named it in **2000**; it is about transferring **mental models**, not forbidding innovation. Default to conventions; break them only when the gain is proven and the learning cost is paid. ## What is Jakob's Law? **Jakob's Law** is a usability heuristic of Internet experience: because people practice on many other products, they arrive with **expectations**—and they judge your interface against those habits, not against a blank slate. > Users spend most of their time on other sites. This means that users prefer your site to work the same way as all the other sites they already know. Think of renting a car in a new city: you still expect the steering wheel, pedals, and turn signals in roughly the same places. A “creative” layout may look distinctive in photos, yet it taxes every trip. On the web and in apps, shopping carts, top-left logos, search fields, and blue-ish links play the same role—shared vocabulary that frees attention for the task. The law sits beside [Fitts's Law](/laws/fittss-law) (pointing cost) and [Hick's Law](/laws/hicks-law) (choice load): familiarity reduces both search and decision friction. It also resonates with [status-quo bias](/effects/status-quo-bias)—people stick with what already works—without claiming that every convention is optimal forever. ### Jakob's Law in 3 Depths * **Beginner**: If your app invents a new place for “Settings” or “Cart,” people will hunt longer than on familiar apps. * **Practitioner**: Inventory industry patterns for primary tasks; match them unless research shows a better path and onboarding can teach it. * **Advanced**: Treat convention as a **transfer of training** asset; spend novelty budget on the product’s unique value, not on reinventing chrome. ## Origin **Jakob Nielsen** formulated **Jakob's Law of the Internet User Experience** in the Nielsen Norman Group Alertbox **“End of Web Design”** published **22 July 2000**. He argued that sites should tone down unique visual language, labels, workflows, and architecture because users live mostly **elsewhere** on the web. Examples he cited as already standardized included **Yahoo** and **Amazon** patterns, the **shopping cart** metaphor and icon, and **blue text links**. The same essay nested the law among other forces—mobile constraints, multi-device continuity, and syndicated/outsourced features—that push toward shared conventions. Nielsen later restated the idea in NN/g video explainers and essays (including later writing under his UX Tigers brand), keeping the core sentence stable: time on other sites drives preference for sameness. Laws of UX and similar catalogs popularized the short name **Jakob’s Law** for design education. ## Key Points Jakob's Law is a **default**, not a ban on better ideas. Most practice happens on competitors, OS shells, and adjacent products. Your first session is rarely their first interface of the day—so they transfer labels, icon positions, and flow order automatically. Standard chrome (logo home, cart top-right on many commerce sites, hamburger menus on mobile) lets people spend working memory on content and goals. Deviating multiplies [Hick's](/laws/hicks-law)-style search across unfamiliar options. Distinctiveness belongs in product capability, content, and brand expression that do not break core wayfinding. Novelty in navigation is expensive; novelty in the job-to-be-done can be worth it. If you must violate a pattern, measure task success, time, and errors against a conventional baseline—and teach the new path. [Postel's Law](/laws/postels-law) is a cousin in systems: be liberal in accepting user habits, conservative in inventing private dialects. ## Applications Use Jakob's Law whenever a design review starts with “nobody else does it this way—so we win.” Keep cart access, price proximity, and multi-step checkout in expected regions; A/B only after the baseline matches category conventions. Align save/publish, search, and settings with OS and suite norms so cross-tool workers transfer skill; document deliberate exceptions. Prefer plain labels (“Search,” “Contact,” “Pay”) over clever metaphors; citizens hop between agencies and will not relearn each portal. When building a side project or class app, clone a familiar pattern first, then change one variable at a time so testers can describe what broke. ## Case Study A concrete NN/g finding shows the cost of ignoring a near-universal web convention. In research on **logo placement**, **centered logos** produced a roughly **six-fold** rise in people who **failed to reach the homepage in a single click**: about **4%** failed with **left-aligned** logos versus about **24%** with **centered** ones (reported in NN/g’s centered-logo work and later cited by Nielsen when illustrating Jakob's Law). The left-corner logo-as-home pattern is a classic “other sites” habit; centering may look stylish, yet it collides with transfer of training. Boundary note: cultural reading order, mobile headers, and brand-only marketing pages can shift the optimum—measure your audience rather than treating 4% vs 24% as a universal constant for every layout. ## Boundaries and Failure Modes **Boundary 1: Conventions decay and differ by domain**\ What “everyone knows” on desktop e-commerce may not hold for industrial tools, games, or emerging platforms. Sample the **actual** competitive set users live in. **Boundary 2: Familiar is not always ethical or accessible**\ Dark patterns can be familiar. Jakob's Law does not excuse traps; pair convention with accessibility and honest choice architecture. **Common misuse**: Weaponizing the law to **kill research**—“Amazon does X, so we must.” Copying leaders without task analysis freezes mediocrity and ignores users who never used that leader. Use convention as a prior, not a substitute for evidence. ## Common Misconceptions These traps turn a transfer heuristic into either total sameness or total uniqueness theater. No. It prioritizes familiar **interaction models**. Brand, content, and differentiated features can still be unique where users gain value. No. The original framing is Internet UX, but the same transfer logic applies to mobile apps, desktop software, and multi-device services that users already practiced elsewhere. No. Popularity encodes past training, not permanent optimum. When evidence shows a better path and you can teach it, measured deviation is legitimate. ## Related Concepts Nearby pages connect familiarity, pointing, choice, and system interfaces. Distance and target size shape pointing time—pair with familiar placement. More unstructured options slow choice; conventions reduce effective search. Be liberal in what you accept—including users’ existing habits. Users depend on observed behavior—including accidental “conventions.” Working complex systems grow from simple ones—start from known patterns. People stick with the familiar; design with that inertia, do not only fight it. ## One-Line Takeaway Design as if your users already trained on everyone else’s product—because they did—then spend novelty where the job, not the chrome, needs it.