Return to All Blogs
21 Laws of UX Every Designer Should Know (2026)
The 21 laws of UX every designer should know in 2026. Real examples, how each law applies to modern products, and why these principles still define great design.
The Short Answer
The 21 laws of UX are a set of psychological principles and cognitive science findings that explain how humans perceive, process, and interact with digital interfaces. From Hick's Law (more choices slow decisions) to the Peak-End Rule (people remember the best and last moments most), these laws have shaped product design for decades. In 2026, they are more relevant than ever. AI-generated interfaces can build anything in minutes, but building something that actually feels right to use still requires understanding how the human mind works. According to Nielsen Norman Group's 2025 UX research, 74% of users abandon a product due to poor usability, not missing features. These 21 laws are the foundation of usability.
Why UX Laws Still Matter in the AI Era
With AI tools generating entire interfaces from a description, it is tempting to think UX principles are less important. If the AI knows best practices, why do designers need to understand them?
The answer is that AI tools generate interfaces based on patterns. They replicate what they have seen. They do not reason about the specific cognitive load of your specific user doing your specific task for the first time. That is still a human judgment, and it requires understanding why certain design decisions work, not just what they look like.
Figma Make, Dualite, and other AI tools generate starting points. A designer or product person who understands UX laws can look at the generated output and immediately identify where the cognitive friction is, where the visual hierarchy breaks down, and where the flow works against how users think.
These 21 laws are the conceptual toolkit that separates a designer who can evaluate AI output from one who can only accept or reject it.
The 21 Laws of UX Explained
1. Hick's Law
The time it takes to make a decision increases with the number and complexity of choices.
Named after William Edmund Hick and Ray Hyman, this law has one of the clearest practical implications in UX: fewer choices mean faster decisions. Every time you add an item to a navigation menu, a filter to a sidebar, or an option to a settings page, you are increasing the cognitive load on every user who encounters it.
Practical application: when a pricing page has three plans, users decide quickly. When it has seven plans with complex feature matrices, conversion drops. Simplify choice architecture wherever possible.
2. Fitts's Law
The time to acquire a target is a function of the distance to and size of the target.
Larger targets that are closer to the user's starting position are easier to click or tap. This is why primary action buttons are large, why mobile tap targets should be at least 44px, and why destructive actions (delete, cancel) are often smaller and placed away from primary actions.
Practical application: put the most important interactive element in the most physically accessible position. On mobile, primary actions belong at the bottom of the screen where thumbs reach naturally. On desktop, put important navigation where the cursor naturally rests.
3. Miller's Law
The average person can hold 7 (plus or minus 2) items in working memory.
George Miller's 1956 research established that human short-term memory is limited to roughly 7 chunks of information at a time. This is why phone numbers are chunked into groups, why navigation menus with more than 7 items feel overwhelming, and why onboarding flows should reveal information progressively rather than all at once.
Practical application: chunk information into groups of 5 to 9. If you have 12 navigation items, group them into 4 categories of 3. The categories reduce the cognitive load even though the total information is the same.
4. Jakob's Law
Users spend most of their time on other sites, and they prefer your site to work the same way as all the sites they already know.
Jakob Nielsen articulated this insight to push back against the instinct to make every product feel unique. Users carry mental models from every product they have ever used. When your product matches those models, learning is instant. When it defies them, every interaction requires conscious effort.
Practical application: before innovating on a familiar pattern, ask whether the innovation solves a real problem or just differentiates for its own sake. The hamburger menu is standard. Putting primary navigation at the bottom right of a desktop screen is not. The first helps users; the second hurts them.
5. Law of Proximity
Objects that are near each other are perceived as a group.
From Gestalt psychology, this law explains how visual layout communicates structure without explicit labels. Form fields grouped closely together are perceived as a single unit. Action buttons near the content they affect are understood as related. Spacing is not just aesthetic; it is information.
Practical application: use whitespace deliberately. Items that belong together should have less space between them than items in separate groups. A label that is equidistant between two fields is ambiguous. A label close to its field is clear.
6. Law of Similarity
Elements that look similar are perceived as being related.
Color, shape, size, and texture that are consistent across elements signal that those elements have the same function. All your primary buttons look the same for this reason. All your secondary actions look different from primary actions for the same reason.
Practical application: maintain consistent visual treatment for elements with the same role. If blue buttons mean primary action, do not use blue for decorative elements. If bold text means important information, do not use bold for stylistic reasons.
7. Law of Common Region
Elements within the same bounded region are perceived as belonging together.
Cards, panels, and containers create perceived groupings. This is why content in a card feels like it belongs together even without explicit labels. The boundary does the organizing work.
Practical application: use cards and containers to create visual groupings rather than relying solely on spacing. A border or background color change creates a stronger grouping signal than whitespace alone, especially on information-dense screens.
8. Law of Uniform Connectedness
Elements that are visually connected are perceived as more related than elements that are not.
Lines, arrows, and shared backgrounds create the strongest grouping signal of all. This is why wizard steps are connected by a progress line, why related data points in a chart share a color, and why timeline elements use a vertical connector.
Practical application: when you need to show that two elements are deeply related (steps in a process, parent-child relationships, cause and effect), connect them visually. Proximity alone is sometimes not enough.
9. Aesthetic-Usability Effect
Users perceive aesthetically pleasing designs as easier to use.
Norika Kurosu and Kaori Kashimura demonstrated in 1995 that users rated beautiful ATM interfaces as more usable, even when actual usability was equal. Attractive design creates a halo effect. Users are more forgiving of friction in beautiful products than in ugly ones, and they are more willing to try to understand something that looks polished.
Practical application: visual design is not decoration. It is a usability signal. A poorly designed interface signals that the underlying product is also poorly made. A polished interface builds confidence before the user has done anything.
10. Von Restorff Effect (Isolation Effect)
When multiple similar objects are present, the one that differs from the rest is most likely to be remembered.
This is why call-to-action buttons are a different color from the rest of the interface. It is why notification badges draw the eye. It is why the recommended pricing tier is highlighted differently from the others. Differentiation creates memorability and attention.
Practical application: use visual contrast deliberately. Every element in your interface cannot be highlighted. If everything is emphasized, nothing is. Reserve visual differentiation for the one thing you most want users to notice.
11. Peak-End Rule
People judge an experience largely based on how they felt at its most intense point and at its end, not on the sum of every moment.
Daniel Kahneman's research established that we do not average our experiences. We remember peaks and endings. A checkout flow with a single frustrating step will be remembered as frustrating even if 90% of it was smooth. A product onboarding that ends with a celebratory moment will be remembered more positively than one that ends on a form.
Practical application: design the emotional high points and the ending of every key flow. Where is the moment of delight in your onboarding? What does the user see when they complete their first meaningful action? These moments disproportionately determine how people remember your product.
12. Serial Position Effect
Users are most likely to remember the first and last items in a series.
The primacy effect (remembering the first item) and recency effect (remembering the last item) mean that content placement in a list, a navigation menu, or a pricing page significantly affects what users retain. The middle is where things go to be forgotten.
Practical application: put the most important navigation items first and last, not in the middle. Put your best testimonials at the beginning and end of a testimonials section. In a menu, critical items belong at the extremes.
13. Zeigarnik Effect
People remember uncompleted or interrupted tasks better than completed ones.
Bluma Zeigarnik found that waiters remembered orders better while the order was pending than after it was delivered. In UX, this is why progress bars, completion percentages, and "finish your profile" prompts are effective. Incompleteness creates cognitive tension that motivates action.
Practical application: show progress. Show what is incomplete. LinkedIn's profile completion meter, Duolingo's streak counter, and onboarding checklists all leverage the Zeigarnik effect to motivate continued engagement.
14. Doherty Threshold
Productivity soars and attention increases when a computer and its users interact at a pace under 400 milliseconds.
Walter Doherty and Ahrvind Thadani established that 400ms is the threshold under which users perceive a system as responsive. Above that, users begin to feel the system is slow, attention wanders, and frustration builds. Core Web Vitals and performance budgets in modern web development are direct applications of this principle.
Practical application: every interaction that takes more than 400ms needs a loading indicator or skeleton state. Not because the loading itself is ideal, but because visible progress maintains the perception of responsiveness.
15. Tesler's Law (Law of Conservation of Complexity)
Every application has an inherent amount of complexity that cannot be reduced, only moved.
Larry Tesler argued that complexity does not disappear when you simplify a user interface. It moves to the system, to documentation, or to edge cases. Good design moves complexity to the developer side. Bad design moves it to the user side. When you simplify a UI, you often increase backend complexity. That is the correct trade-off.
Practical application: when simplifying an interface, ask where the complexity is going. If removing a setting from the user means your backend now handles it automatically, that is good design. If removing a setting means users have to find a workaround, you have only hidden the problem.
16. Postel's Law (Robustness Principle)
Be conservative in what you send, liberal in what you accept.
Originally written for network protocols, this principle applies beautifully to UX. Be generous in what you accept from users (varied inputs, different formats, typos) and precise in what you present to them (clean, correct, well-formatted output). A form that accepts a phone number with or without hyphens, with or without country code, is more usable than one that rejects all but one exact format.
Practical application: validate inputs tolerantly. Accept date formats in multiple styles. Accept phone numbers with and without spaces. Parse addresses generously. Show clean, consistent output regardless of input variation.
17. Law of Pragnanz (Law of Good Form)
People will perceive and interpret ambiguous or complex images as the simplest form possible.
Humans resolve visual ambiguity toward the simplest interpretation. This is why logos made of simple geometric shapes are more recognizable than complex ones. It is why complex icons with too much detail are harder to recognize than simplified versions.
Practical application: favor simplicity in visual communication. A complex icon that requires explanation has failed. A simple icon that conveys its meaning instantly has succeeded. Apply this to icons, illustrations, diagrams, and data visualizations.
18. Law of Symmetry and Order
The eye is drawn to symmetry, regularity, and order, which are perceived as more stable and trustworthy.
Symmetrical layouts feel calm and authoritative. Asymmetric layouts feel dynamic and modern. Neither is universally correct, but both carry associations that affect how users feel about a product's credibility. Financial products tend toward symmetry for this reason. Creative tools tend toward asymmetry.
Practical application: match your layout style to your product's trust requirements. A banking app should feel more ordered and symmetrical than a creative platform. The visual language communicates trustworthiness before the user reads a word.
19. Parkinson's Law
Work expands to fill the time available for its completion.
Applied to UX, this means users will spend the time you give them on any task. Long forms get slowly filled and often abandoned. Short forms get completed quickly. Time limits on tasks (like session timeouts) create urgency. Progress indicators that show elapsed time accelerate completion.
Practical application: make forms as short as possible. Ask only what you need. Every additional field reduces completion rate. For multi-step processes, show how many steps remain so users can see the end.
20. Law of Continuity
Elements arranged on a line or curve are perceived as more related than elements not on that path.
The eye follows lines and curves naturally. Navigation bars, progress indicators, and sliders all exploit continuity. When content flows in a clear visual direction, users follow it. When it does not, users get lost.
Practical application: use alignment to create visual flow. Text that aligns to a left edge creates a strong reading line. Content arranged along a diagonal creates a sense of direction and momentum. Discontinuity in alignment creates friction.
21. Goal-Gradient Effect
As people approach a goal, they increase their effort and motivation.
Researched by Clark Leonard Hull, this effect explains why people speed up when they can see the finish line. Progress bars that fill up as users complete steps create this effect. Showing "3 steps left" creates more motivation than showing "3 steps completed out of 6" even though the information is identical, because the former makes the end visible.
Practical application: make progress visible and emphasize proximity to completion rather than distance from the start. "Almost there" converts better than "halfway there" even when they mean the same thing.
How These Laws Apply to AI-Built Products in 2026
AI tools like Dualite build interfaces from descriptions. The quality of the result depends partly on the quality of the description, and a designer who understands UX laws can write much better prompts.
Instead of "build a checkout flow," a designer who knows UX laws writes: "build a checkout flow with no more than 3 steps, a progress indicator showing remaining steps rather than completed ones, primary action buttons at minimum 44px touch targets placed in the lower right for right-handed mobile users, and a summary panel that stays visible throughout."
Every one of those specifications maps to a UX law. The AI tool executes the specification. The designer brings the understanding of why.
A Quick Reference Table
Law | Core Principle | Primary Application |
|---|---|---|
Hick's Law | More choices = slower decisions | Navigation, pricing, settings |
Fitts's Law | Bigger and closer = easier to click | Button size and placement |
Miller's Law | 7±2 items in working memory | Information chunking |
Jakob's Law | Users expect familiar patterns | Navigation, interaction models |
Law of Proximity | Near elements seem related | Form layout, content grouping |
Law of Similarity | Similar-looking = same function | Button styles, iconography |
Von Restorff Effect | Different = remembered | CTA buttons, key info |
Peak-End Rule | Peaks and endings define memory | Onboarding, checkout endings |
Aesthetic-Usability Effect | Beautiful = perceived as easier | Visual polish |
Zeigarnik Effect | Incompleteness drives action | Progress, streaks, checklists |
Doherty Threshold | Under 400ms feels instant | Performance, loading states |
Goal-Gradient Effect | Visible finish line accelerates effort | Progress indicators |
Source: UX laws research compilation, June 2026
Conclusion
These 21 laws are not rules to follow blindly. They are lenses to see through when evaluating design decisions. When a design feels wrong but you cannot articulate why, one of these laws usually explains it. When a design pattern works unusually well, one of these laws usually explains that too. Understanding them does not constrain creativity. It focuses it.
The best products in 2026, whether built by hand or generated by AI, succeed because the people building them understand how humans think. These laws are a map of human cognition. Use them.
Frequently Asked Questions
1. What are the most important UX laws for beginners to know first?
Start with Hick's Law, Fitts's Law, Jakob's Law, and the Peak-End Rule. These four cover the highest-impact decisions in most product designs: how many choices to offer, how to size and place interactive elements, whether to follow or break conventions, and how to make experiences memorable.
2. Do UX laws apply to mobile design differently than desktop?
Yes, primarily through Fitts's Law. On mobile, touch targets need to be larger (at least 44x44px) and thumb-reachable. Navigation belongs at the bottom of the screen, not the top. Miller's Law also applies more aggressively on mobile because screen space is limited, so chunking is even more important.
3. What is Hick's Law in simple terms?
Hick's Law says that the more options you give someone, the longer it takes them to decide. Double the number of options and you roughly double the decision time. This is why simple menus, focused landing pages, and streamlined checkout flows convert better than complex, feature-heavy ones.
4. What is the Peak-End Rule and why does it matter for product design?
The Peak-End Rule is the finding that people judge an experience based on its most intense moment and its ending, not on the average of all moments. For product design, this means designing the emotional climax and the ending of key flows intentionally. A good onboarding that ends with a celebration will be remembered more positively than a technically better onboarding that ends with a blank state.
5. How do UX laws apply to AI-generated interfaces in 2026?
AI tools generate interfaces based on patterns from existing designs. They do not reason about cognitive load or user psychology for your specific context. Designers who understand UX laws can write better AI prompts and evaluate generated output more critically. The laws provide the criteria for judging whether AI output is actually usable, not just visually acceptable.
6. Is Jakob's Law an argument against design innovation?
No. Jakob's Law is an argument against innovation for its own sake. When you break a familiar pattern, you are spending the user's trust. If the innovation creates genuine value that exceeds the cost of relearning, break the pattern. If it only makes your product feel different without improving the experience, follow the convention. Innovation should be deliberate, not reflexive.
7. What is the difference between the Law of Proximity and the Law of Common Region?
Proximity uses space to group elements. Common Region uses a visible boundary (border, background color, card) to group elements. Common Region creates a stronger grouping signal, but uses more visual weight. Use proximity for subtle groupings and common region for explicit groupings that need to be unmistakable.
8. How does the Aesthetic-Usability Effect affect user trust?
A visually polished interface signals that the product was made carefully. Users extend that quality signal to the rest of the product before they have tested it. They are more patient with friction, more willing to give the benefit of the doubt, and less likely to interpret errors as intentional deception. This is why early investment in visual quality pays disproportionate returns in user trust.
9. Can you apply too many UX laws at once?
Yes. Trying to optimize for all 21 laws simultaneously leads to paralysis and often produces conflicting results. The better approach is to identify the one or two laws most relevant to the specific design problem you are solving and apply those deliberately. Most design problems are dominated by one or two underlying cognitive issues.
10. Are there UX laws specific to AI-powered product features?
The existing laws apply to AI features but with some emphasis shifts. The Doherty Threshold becomes critical because AI responses can take 1 to 5 seconds. Loading states and progressive disclosure of AI output are not optional. The Aesthetic-Usability Effect matters more because users are already skeptical of AI output. And Jakob's Law is particularly important because users have existing mental models of what AI assistants should do from ChatGPT, Siri, and Alexa.
Related: Top 8 Figma AI Tools in 2026 - Figma Design to Code: Step-by-Step Guide - No-Code vs Low-Code vs AI App Builders
