UX Design

21 Laws of UX explained with real product examples

Neha Thakkar

Experience Designer

Explained in simple english, all the 21 laws of UX, with real examples from apps like Amazon, Netflix, Duolingo, and Google, so you can design more intuitive products.

A plain-English, example-first guide to the Laws of UX, the psychological principles behind why some products feel effortless and others feel like a fight, illustrated with apps and products you already use every day.

Who this is for: UX and product designers, UI designers, product managers, founders, students, and anyone who wants to understand why good design works. How to use it: Read it once to get the mental models, then keep it open as a checklist the next time you design a screen.

What are the Laws of UX?

The Laws of UX are a collection of principles and heuristics, drawn mostly from psychology, that designers use to build interfaces people find intuitive. They aren't "laws" in the legal or scientific sense. They're well-observed patterns of human behavior: how we perceive, decide, remember, and get frustrated.

The collection was popularized by designer Jon Yablonski, whose book Laws of UX gathered 21 principles into a single, memorable framework across four categories: heuristics, Gestalt principles, cognitive biases, and broader design principles. But the ideas themselves come from decades of research in cognitive psychology, human-computer interaction, and Gestalt theory. This guide covers all 21.

Here's the key insight that makes the Laws of UX so powerful: users don't read your interface, they experience it through a brain that has hard limits and predictable shortcuts. People have limited working memory. They hate too many choices. They judge things in milliseconds. They remember peaks and endings, not averages. When your design works with these tendencies, it feels effortless. When it fights them, it feels broken, even if every button technically works.

This guide walks through each major UX law, explains the psychology in plain language, and, most importantly, shows you real examples from products you use every day so each principle actually sticks. Let's dive in.

Why the Laws of UX matter and why memorizing them isn't the point

Before the list, one warning: the goal isn't to memorize twenty laws and recite them in interviews. The goal is to internalize the underlying truth, that design is applied psychology, so that good decisions become intuitive.

Knowing the Laws of UX helps you in three concrete ways:

They give you a shared language to explain and defend design decisions ("we're reducing choices here because of Hick's Law") instead of relying on "it just feels right." They help you diagnose problems faster, when a flow underperforms, the laws point you toward why. And they help you design proactively, anticipating how humans will actually behave rather than how you wish they would.

With that framing, let's go law by law. For each, you'll get what it is, the psychology behind it, and real product examples.

Part 1: Laws about decision-making and cognitive load

1. Hick's Law, more choices means slower decisions

What it says: The time it takes to make a decision increases with the number and complexity of choices available. More options equals more hesitation.

The psychology: Every additional option adds cognitive processing time. Faced with too many choices, people don't just slow down, they often freeze or abandon the task entirely (the "paradox of choice").

Real examples:

• Google's homepage is the textbook case. A single search box on a blank page. Google could have crammed it with links, ads, and widgets (as Yahoo and other portals once did), but the minimal interface makes the one important decision, "what do I want to search?", instant.
• Netflix manages a catalog of thousands of titles but never shows you all of them. It curates rows ("Because you watched…", "Top 10") to shrink the decision down to a handful of relevant options at a time.
• Apple's checkout and setup flows break complex configuration into one decision per screen, rather than overwhelming you with every option at once.

How to apply it: Break complex tasks into steps. Highlight recommended options. Use progressive disclosure to hide advanced settings until needed. But don't oversimplify to the point of hiding things people need, which brings us to Tesler's Law later.

2. Miller's Law, the magical number seven (give or take)

What it says: The average person can hold only about 7 (±2) items in their working memory at once.

The psychology: Working memory is tiny and fragile. Overload it and people lose track, make errors, and feel stressed. The trick is chunking, grouping information into meaningful units.

Real examples:

• Phone numbers are the classic chunking example: (555) 867-5309 is far easier to remember than 5558675309, because it's grouped into three chunks.
• Navigation menus on well-designed sites keep top-level items to a handful. Compare a clean primary nav (Apple, Stripe) to a sprawling mega-menu that makes you scan endlessly.
• Stripe and modern banking apps chunk long card numbers into groups of four as you type, reducing errors and cognitive load.

How to apply it: Chunk content into digestible groups. Don't treat "7" as a hard rule, treat it as a reminder that working memory is limited. Group form fields, break long numbers, and structure content with clear sections.

3. Tesler's Law, the conservation of complexity

What it says: Every process has an inherent amount of complexity that cannot be removed, only shifted. The question is who absorbs it, the user or the designer/system.

The psychology: Complexity doesn't vanish when you hide it. If you make the interface simpler by pushing complexity onto the user, they suffer. Good design absorbs complexity into the system so the user doesn't have to.

Real examples:

• Gmail automatically parses dates, addresses, and flight details from emails so you don't have to manually create calendar events. The complexity is real, Google's system absorbs it.
• Apple Pay / one-tap checkout absorbs the complexity of entering card details, billing addresses, and security codes. The user experiences one tap; the system handles the mess.
• Google Search interprets typos, synonyms, and intent ("did you mean…?") so users can type sloppily. The system eats the complexity.

How to apply it: Identify irreducible complexity, then decide deliberately where it lives. Whenever possible, let the system do the hard work (smart defaults, autofill, inference) rather than dumping it on the user.

4. Occam's Razor, the simplest solution wins

What it says: Among competing solutions that solve the problem equally well, the simplest one is best. Don't add elements that aren't necessary.

Real examples:

• The original iPhone removed the physical keyboard and stylus that every competitor had, betting that a simpler interface would win. It did.
• Google's homepage (again) embodies this, nothing on screen that isn't essential to the core task.
• Medium's writing editor strips away toolbars and clutter so writers focus purely on words.

How to apply it: For every element, ask "does this need to be here?" Remove decorative complexity. Simplicity isn't about doing less, it's about removing everything that isn't pulling its weight.

5. Pareto Principle, roughly 80% of effects come from 20% of causes

What it says: For many systems, about 80% of the outcomes come from about 20% of the inputs. In UX, a small subset of features drives the vast majority of usage and value.

The psychology: Effort and attention are finite. If most of the value lives in a handful of features and flows, that's where design and optimization effort should concentrate, not spread thin across everything equally.

Real examples:

• Instagram built its entire early product around the ~20% of features people actually used (photos, filters, feed) and stripped away the rest from the app it evolved from (Burbn), which was cluttered with check-ins and features few people touched.
• Microsoft famously found that fixing the top ~20% of reported bugs eliminated around 80% of crashes and errors, an application of the principle to prioritization.
• Google Search's interface optimizes relentlessly for the one action ~everyone does (searching), rather than equally weighting rarely-used features.

How to apply it: Identify the vital few features and flows that deliver most of your product's value, and invest disproportionately in making them excellent. Don't polish rarely-used corners at the expense of the critical path. Use analytics to find your 20%.

Part 2: Laws about interaction and usability

6. Fitts's Law, size and distance determine how easy targets are to hit

What it says: The time to acquire a target is a function of the distance to it and its size. Bigger, closer targets are faster and easier to click or tap.

The psychology: This is about motor control. Small, far-away targets require more precision and time; large, near ones are effortless.

Real examples:

• Mobile "thumb zones": Well-designed apps like Instagram and Spotify place primary actions (post, play, like) within easy thumb reach at the bottom of the screen, not in far corners.
• The macOS menu bar sits at the very top edge of the screen, an "infinitely tall" target, because you can slam your cursor to the edge without overshooting.
• Big CTAs: Amazon's "Buy Now" and "Add to Cart" buttons are large, high-contrast, and impossible to miss. Compare that to a tiny, cramped "unsubscribe" link, that's Fitts's Law working against you on purpose.

How to apply it: Make important buttons large and place them where users' fingers or cursors already are. Use screen edges and corners strategically. Keep destructive or rarely-used actions smaller and out of the primary path.

7. Jakob's Law, users expect your site to work like the others they know

What it says: Users spend most of their time on other products. So they expect yours to work the same way as all the ones they already know.

The psychology: People transfer expectations from familiar experiences. Meeting those expectations reduces the learning curve; violating them creates friction, even if your "innovative" pattern is objectively clever.

Real examples:

• The shopping cart icon in the top-right corner, the logo linking home, the hamburger menu on mobile, these are conventions users expect on every e-commerce site (Amazon, Shopify stores, ASOS). Move them and you confuse people.
• Video players (YouTube, Netflix, Vimeo) all put play/pause on the left, fullscreen on the right, and a scrubber along the bottom. Users don't want to relearn this per app.
• Form patterns: email field, password field, "forgot password?" link, users expect this exact arrangement, and reordering it slows everyone down.

How to apply it: Use established patterns unless you have a strong, tested reason not to. Innovate on value, not on where the cart icon lives. Familiarity is a feature.

8. Postel's Law (the Robustness Principle), be liberal in what you accept

What it says: Be conservative in what you send, be liberal in what you accept. Design systems that tolerate a wide range of user input while giving clear, reliable output.

Real examples:

• Phone/date fields that accept any format: The best forms let you type "(555) 867-5309" or "5558675309" or "555.867.5309" and quietly normalize it. Bad forms reject you for a stray space.
• Google Search accepts typos, partial queries, natural language, and still returns useful results.
• Airbnb / booking search accepts flexible date and location input and interprets intent rather than demanding a rigid format.

How to apply it: Accept input in whatever format users naturally provide, then clean it up behind the scenes. Never punish a user for a formatting choice a machine can easily fix.

9. Doherty Threshold, keep responses under 400 milliseconds

What it says: Productivity soars when a computer and user interact at a pace (under ~400ms) that neither has to wait for the other. Anything slower breaks the sense of flow.

The psychology: Delays over ~400ms make interactions feel sluggish and pull users out of a state of flow. Fast feedback keeps them engaged and confident.

Real examples:

• Instant search suggestions (Google, YouTube) appear as you type, keeping you in flow.
• Optimistic UI: Instagram shows your "like" instantly, before the server confirms it. Slack shows your message as sent immediately. The perceived speed keeps interaction seamless.
• Skeleton screens and progress indicators: Facebook, LinkedIn, and YouTube show skeleton placeholders while content loads, so the wait feels shorter and the app feels responsive.

How to apply it: Optimize real performance, but also manage perceived performance with instant feedback, optimistic updates, skeleton screens, and progress bars. Never leave a user staring at nothing.

Part 3: Laws about perception and visual grouping (Gestalt principles)

The Gestalt principles are a core part of the Laws of UX, they explain how our brains automatically organize visual information into patterns.

10. Law of Proximity, things close together are perceived as related

What it says: Objects near each other are perceived as a group.

Real examples:

• Form labels placed close to their input fields (rather than floating far away) are instantly understood as belonging together, a constant issue in poorly spaced forms.
• Pricing cards (Notion, Spotify, any SaaS pricing page) group each plan's features tightly together and add space between plans, so you read them as distinct bundles.
• Instagram's profile stats (posts, followers, following) are grouped tightly to read as one unit.

How to apply it: Use whitespace deliberately. Group related items; separate unrelated ones. Spacing is not decoration, it's meaning.

11. Law of Common Region, borders and containers create groups

What it says: Elements within the same bounded region (a box, card, or background) are perceived as grouped, even if they're spaced apart.

Real examples:

• Card-based UIs everywhere, Pinterest, Trello, Google Material cards, use containers to bundle related content and actions.
• Notification groups on iOS and Android stack by app inside a shared container.
• Facebook posts each sit in their own card, so comments, reactions, and content read as one self-contained unit.

How to apply it: Use cards, backgrounds, and borders to signal grouping, especially when you can't rely on proximity alone.

12. Law of Similarity, similar-looking things are perceived as related

What it says: Elements that share visual characteristics (color, shape, size) are perceived as related or having the same function.

Real examples:

• All links in one color: Consistent link styling teaches users "blue underlined text = clickable" across a whole site.
• Consistent button styles: Stripe and Material Design make all primary actions look the same, so users instantly recognize "this is the main action."
• Instagram's grid of uniform square thumbnails reads as one cohesive gallery.

How to apply it: Make things that behave the same look the same, and things that behave differently look different. Consistency is a usability tool, not just an aesthetic one.

13. Law of Prägnanz (Law of Simplicity), we see complex shapes in the simplest form

What it says: People perceive and interpret ambiguous or complex images in the simplest form possible, because it takes the least cognitive effort.

Real examples:

• Logos rely on this: the Apple logo, Nike swoosh, and Twitter/X bird were all simple shapes the brain grasps instantly and remembers.
• Icon design across iOS and Android reduces complex concepts (settings = gear, share = arrow) to minimal, universally recognizable forms.

How to apply it: Favor clean, simple visual forms. Reduce icons and illustrations to their essential shapes. The brain rewards simplicity with faster recognition.

14. Law of Uniform Connectedness, connected elements are perceived as a group

What it says: Elements that are visually connected (by lines, arrows, or a shared color region) are perceived as more related than elements with no connection.

Real examples:

• Progress steppers (checkout flows on Amazon, ASOS) connect steps with a line to show they're part of one sequence.
• Onboarding flows and flowcharts use connecting lines to show relationships and sequence.
• Grouped toolbar buttons joined into a single segmented control (iOS) read as one related set.

How to apply it: Use lines, connectors, and shared containers to show relationships and sequence explicitly.

Part 4: Laws about memory and the emotional arc

15. Peak-End Rule, we judge experiences by their peak and their end

What it says: People judge an experience largely based on how they felt at its most intense point (the peak) and at its end, not the average of every moment.

The psychology: Memory is selective. A mostly-fine experience with a terrible ending is remembered as bad; a mostly-average one with a delightful peak and ending is remembered fondly.

Real examples:

• Duolingo's celebratory end-of-lesson animations and confetti create a positive "end" that keeps you coming back, even if the lesson itself was hard.
• Uber's arrival experience and clean receipt end the ride on a smooth note; the peak (seeing your driver approach in real time) reduces anxiety.
• Apple's unboxing experience is engineered peak delight, the product reveal is a designed emotional high point.
• Mailchimp's famous "high five" after you send a campaign turns a nerve-wracking moment (hitting send to thousands) into a peak of relief and celebration.

How to apply it: Identify the emotional peaks and the ending of your user journey and invest in making them delightful. Pay special attention to endings, the last screen, the confirmation, the goodbye.

16. Zeigarnik Effect, we remember unfinished tasks

What it says: People remember uncompleted or interrupted tasks better than completed ones. Open loops nag at us.

Real examples:

• Progress bars and completion meters: LinkedIn's "Profile strength" meter and Duolingo's streaks exploit our discomfort with incompleteness to drive us to finish.
• Onboarding checklists: Slack, Notion, and Asana show "getting started" checklists with unchecked items that pull you toward completion.
• Netflix's "Continue Watching" row leverages the open loop of a half-finished show.

How to apply it: Use progress indicators and checklists to motivate completion, but ethically, don't manufacture fake incompleteness just to nag users.

17. Serial Position Effect, we remember the first and last items best

What it says: Users best remember the first (primacy) and last (recency) items in a series, and forget the middle.

Real examples:

• Navigation menus put the most important items first and last: Apple and most apps place "Home" first and key actions (profile, cart) at the end.
• Mobile tab bars (Instagram, Twitter/X) place the most-used destinations at the two ends, home on the far left, profile on the far right.

How to apply it: Place your most important navigation and actions at the beginning and end of lists and menus, not buried in the middle.

18. Von Restorff Effect (Isolation Effect), the different one gets remembered

What it says: When multiple similar objects are present, the one that differs from the rest is most likely to be noticed and remembered.

Real examples:

• Highlighted pricing plans: Nearly every SaaS pricing page (Notion, Spotify, Slack) visually emphasizes the "recommended" or "most popular" tier with a different color or badge, so your eye lands there.
• Primary vs secondary buttons: A bold, filled "Sign Up" button next to a plain "Learn More" link uses contrast to guide the eye to the desired action.
• Sale tags and badges ("New", "-50%") on e-commerce sites (Amazon, ASOS) pop against uniform product grids.

How to apply it: Make the single most important element visually distinct, through color, size, or contrast. But use it sparingly: if everything is highlighted, nothing is.

Part 5: Laws about motivation and behavior

19. Goal-Gradient Effect, motivation increases as we approach the goal

What it says: The closer people are to a goal, the more motivated they are to complete it, and the harder they push.

Real examples:

• Starbucks / loyalty apps: Rewards programs show how close you are to a free item ("2 stars until your reward"), accelerating purchases near the finish line. A famous study found people bought coffee faster when their loyalty card appeared closer to complete, even with the same number of stamps needed.
• Duolingo and fitness apps show streaks and daily goal rings (Apple Watch) that pull you to "close the ring."
• Profile completion and checkout progress: Showing "80% complete" motivates users to finish onboarding or a purchase.

How to apply it: Show progress visibly, and consider giving users a head start (an "endowed progress" effect, e.g., a loyalty card that starts at 2/10 instead of 0/8) to boost motivation.

20. Parkinson's Law, work expands to fill the time available

What it says: Any task will take as long as the time allotted to it. In UX, users appreciate when a task takes less time than expected.

Real examples:

• Autofill and one-click checkout (Amazon 1-Click, Apple Pay, Google autofill) dramatically shorten tasks users expect to take longer, creating delight.
• Pre-filled forms and smart defaults (address lookup from a postcode, saved payment methods) collapse minutes of work into seconds.

How to apply it: Reduce the time and effort a task actually takes with automation, autofill, and smart defaults. Beating the user's time expectation feels like a gift.

21. Aesthetic-Usability Effect, beautiful design is perceived as more usable

What it says: Users perceive aesthetically pleasing design as more usable, and they're more forgiving of minor usability issues when a product looks good.

The psychology: Attractiveness triggers a positive emotional response that makes users more tolerant and more likely to believe the product works well, sometimes even masking real usability problems in testing.

Real examples:

• Apple products are the archetype: polished aesthetics create a perception of quality and ease that carries the whole experience.
• Airbnb and Notion use beautiful photography, clean typography, and generous whitespace so the product feels trustworthy and simple, which increases patience and engagement.
• Stripe's famously elegant documentation makes a genuinely complex task (integrating payments) feel approachable.

How to apply it: Invest in visual craft, it's not superficial, it measurably affects perceived usability and trust. But a caution: because beauty can hide usability problems in testing, always validate with real task-based usability testing, not just "do you like how it looks?" (See our guide to UX research methods for how to run that testing properly.)

Using the Laws of UX responsibly: principles, not dark patterns

Here's the ethical fork in the road. Many of these laws, the Zeigarnik Effect, Goal-Gradient, Von Restorff, describe how to influence behavior. Used well, they help people accomplish their own goals with less friction. Used manipulatively, they become dark patterns: fake scarcity, guilt-tripping "no thanks, I hate saving money" buttons, endless streaks engineered to exploit anxiety, or highlighted options that serve the business at the user's expense.

The test is simple: are you using the principle to help the user get what they want, or to trick them into what you want? The Laws of UX are ethically neutral tools. Your intent is what makes them good design or manipulation. Great designers use them to remove friction and add delight, not to extract behavior against a user's interest.

Common mistakes when applying the Laws of UX

Treating them as rigid rules. They're heuristics, not commandments. Miller's "7±2" doesn't mean menus must have exactly seven items. Context and testing always win over dogma.

Applying one law in isolation. The laws interact and sometimes conflict. Hick's Law says reduce choices; Tesler's Law warns against oversimplifying to the point of hiding needed complexity. Good design balances them.

Using laws to justify decisions after the fact. Don't reverse-engineer a "Hick's Law" rationale for a choice you already made. Use the laws to inform design and then validate with real users.

Confusing persuasion with manipulation. As above, the line between a helpful nudge and a dark pattern is intent and user benefit.

Skipping research. The laws describe general human tendencies, but your users in your context may behave differently. Laws guide; testing confirms. (Pair these principles with real UX research methods and the right UI/UX design tools to put them into practice.)

Key takeaways

• The Laws of UX are psychological principles that explain why some interfaces feel effortless and others feel like friction. They turn "it just feels right" into something you can explain, defend, and repeat.
• They cluster around a few human truths: we have limited attention and memory (Hick's, Miller's, Tesler's), we rely on familiarity and motor ease (Jakob's, Fitts's), we perceive in groups (the Gestalt laws), we remember peaks, endings, and unfinished business (Peak-End, Zeigarnik, Serial Position), and we're driven by progress and beauty (Goal-Gradient, Aesthetic-Usability).
• The best way to learn them is through real products, once you see Hick's Law in Google's homepage or the Peak-End Rule in Duolingo's confetti, you'll never unsee it.
• Use them ethically, to reduce friction and serve users' goals, not to manipulate.
• And remember: laws are heuristics, not laws of physics. They inform great design, but user research and testing have the final word.

Master the psychology, and the pixels get a lot easier. The best interfaces aren't the ones with the most features or the flashiest visuals, they're the ones designed around how human beings actually think, decide, and feel.