UX Design Laws and Principles: 18 Rules With Examples

UX design is sometimes treated as pure intuition - you either have an eye for it or you don't. That's not quite right. Over decades of cognitive science, psychology, and usability research, a set of principles has emerged that explains why certain design decisions work better than others. These aren't rigid commandments. They're research-backed rules of thumb that help you make better decisions faster, explain your reasoning to stakeholders, and avoid common traps.

None of them replace user research. All of them become more useful the more you practice applying them. Here are 18 you'll use constantly.

UX Design Laws at a Glance

| Law | What it says | Apply it when | |-----|--------------|----------------| | Jakob's Law | Users expect your product to work like others they already know | Designing navigation, checkout, or any familiar flow | | Hick's Law | More choices means slower decisions | Building menus, pricing pages, onboarding steps | | Fitts's Law | Larger, closer targets are faster to hit | Sizing and placing buttons and touch targets | | Miller's Law | Working memory holds roughly 7 (plus or minus 2) items | Structuring lists, forms, and navigation | | Law of Proximity | Elements placed close together are seen as related | Grouping labels, fields, and related controls | | Law of Common Region | A shared boundary groups elements, even if spaced apart | Designing cards, panels, and containers | | Peak-End Rule | Experiences are judged by their peak moment and their end | Designing confirmation, error, and offboarding screens | | Aesthetic-Usability Effect | Pleasing designs are perceived as easier to use | Prioritising visual polish alongside functionality | | Doherty Threshold | Productivity rises when response times stay under 400ms | Deciding where to invest in perceived performance | | Tesler's Law | Complexity can be moved, not removed | Deciding whether the system or the user absorbs a step | | Postel's Law | Be liberal in what you accept, strict in what you produce | Designing input validation and error handling | | Serial Position Effect | People best remember the first and last items in a list | Ordering navigation, menus, and onboarding steps | | Von Restorff Effect | An item that stands out from its peers is remembered best | Highlighting a single primary action or plan | | Zeigarnik Effect | Unfinished tasks are remembered better than finished ones | Designing progress indicators and re-engagement prompts | | Law of Pragnanz | People perceive the simplest possible interpretation of a shape | Simplifying icons, illustrations, and layouts | | Occam's Razor | The simplest solution that works is usually the right one | Choosing between a simple flow and a clever one | | Parkinson's Law | Work expands to fill the time available for it | Setting deadlines, limits, and time-boxed steps | | Goal-Gradient Effect | Motivation increases as people get closer to a goal | Designing progress bars, loyalty schemes, checkout steps |

Jakob's Law

Users spend most of their time on other websites, so they expect yours to work the same way.

Jakob Nielsen coined this one, and it's deceptively simple. When someone arrives on a new website or app, they bring a mental model built from every product they've used before. Understanding who your users are and what mental models they bring is the job of a user persona - a structured way to document that research before applying it to design decisions. Navigation at the top. Logo links home. Search in the top-right. Checkout in a basket icon. Break these conventions and you force users to learn something new - which takes effort, creates friction, and erodes trust.

Practically: before reinventing a UI pattern, ask whether the novelty serves the user or just makes the product feel distinctive. A uniquely-styled navigation might win a design award. It might also lose you conversions. When you do deviate from convention, test it - don't assume clever equals better.

If you want to understand how these principles show up in real evaluations, read our post on heuristic evaluation in UX design.

Hick's Law

The more choices you give someone, the longer it takes them to decide.

W.E. Hick (and Ray Hyman) formalised this in the 1950s: decision time increases logarithmically with the number of choices. The practical implication is that overloading users with options doesn't feel generous - it feels paralysing.

This is why good onboarding flows surface one decision at a time. It's why pricing pages often have three tiers, not seven. It's why a well-designed hamburger menu that reveals a focused list of options often outperforms an exposed navigation with fifteen links.

Practically: audit any screen where you're asking users to choose something. Can you reduce the number of options? Can you sequence choices so they appear only when relevant? Progressive disclosure - revealing complexity gradually - is Hick's Law applied as a pattern.

Fitts's Law

The time to reach a target depends on how far away it is and how small it is.

Paul Fitts published this in 1954, and it remains one of the most empirically solid principles in human-computer interaction. A large button close to the user's current position is faster to hit than a small button far away. Obvious when stated, but routinely violated in practice.

Practically: primary call-to-action buttons should be large and positioned where users are likely to be looking or pointing. On mobile, touch targets should be at least 44x44 pixels (Apple's guideline) or 48x48dp (Google's Material guidance). Destructive actions - delete, cancel, clear - should be smaller or further away, making them harder to trigger accidentally. The corners and edges of a screen are special: the pointer stops there, effectively making them infinitely large targets on a desktop.

Miller's Law

The average person can hold roughly 7 (plus or minus 2) items in working memory at once.

George Miller's 1956 paper "The Magical Number Seven" gave designers a shorthand for cognitive load. Working memory is limited - when you overwhelm it, people make errors, miss things, and disengage.

The key practical application is chunking: grouping related pieces of information so they register as a single unit rather than several separate items. A phone number written as 07700900123 is harder to process than 07700 900 123. A navigation with twelve ungrouped links is harder to scan than one where links are organised under four clear headings.

Practically: wherever you have a list, a form, or a set of options, look for natural groupings. Chunking respects working memory limits without hiding information.

The Law of Proximity (and Gestalt Principles)

Elements that are close together are perceived as related.

This is one of the Gestalt principles - a set of perceptual rules developed by German psychologists in the early twentieth century describing how humans group visual elements. Proximity is the most directly applicable to interface design: if two elements are near each other, users assume they're connected.

This is why form labels should sit directly above (or beside) their input fields, not ambiguously positioned between two fields. It's why a button placed next to a paragraph is assumed to act on that paragraph. It's why whitespace between sections is a design decision, not wasted space - it signals where one group ends and another begins.

The other Gestalt principles worth knowing are similarity (elements that look alike are grouped together), continuity (the eye follows lines and curves), closure (we complete incomplete shapes), and figure-ground (we separate objects from their backgrounds). All of them shape how users perceive layout before they consciously read a single word. You can explore how these feed into usability thinking in our post on usability in UX design.

The Law of Common Region

Elements within a clearly defined boundary are perceived as a group.

This extends Gestalt proximity. Even if elements are spread apart, placing them inside a shared container - a card, a box, a shaded region - groups them in the user's perception. It's why card-based layouts work: the card boundary creates a distinct unit.

Practically: if you want users to understand that a set of elements belongs together, the most reliable signal is a shared enclosure - a border, a background colour, or a consistent container. Don't rely on proximity alone if the grouping is genuinely critical to comprehension.

The Peak-End Rule

People judge an experience primarily by how they felt at its most intense moment and at the end, not by the average across the whole experience.

This comes from Daniel Kahneman's research on remembered utility. The implication for UX is significant: a checkout flow that is smooth throughout but ends with a confusing confirmation screen will be remembered as worse than the effort involved. Conversely, a process with some friction that ends with a moment of delight - a well-crafted success screen, a personal confirmation email, an unexpected small reward - will be remembered more positively.

Practically: pay particular attention to the end states of your flows. Success screens, error pages, confirmation emails, and offboarding moments are disproportionately important to how users remember your product. Don't rush them. Make them feel intentional.

The Aesthetic-Usability Effect

Users perceive more aesthetically pleasing designs as easier to use, even when they aren't.

This was demonstrated by Masaaki Kurosu and Kaori Kashimura in 1995 and has been replicated since. A polished, visually considered interface creates a halo effect: users assume it works better, are more forgiving of problems they encounter, and rate it more highly.

This doesn't mean aesthetics substitute for usability - they don't, and the effect erodes quickly when a beautiful interface genuinely fails to work. But it does mean visual craft is not just decoration. A well-designed product earns more patience and goodwill from users before they give up.

Practically: take visual polish seriously as a design deliverable, not a finishing touch someone else handles. Typography, spacing, colour consistency, and icon quality all signal professionalism - and that signal has measurable effects on perceived usability.

The Doherty Threshold

Productivity increases when a computer and its users interact at a pace of under 400 milliseconds each.

Walter Doherty and Ahrvind Thadani published this in 1982. When response times drop below 400ms, users enter a state of flow - the interface feels responsive, fluid, and under control. Above that threshold, users notice the wait, lose their train of thought, and disengage.

Practically: perceived performance is as important as actual performance. Skeleton screens, progress indicators, and optimistic UI updates (showing a change immediately before the server confirms it) all reduce perceived latency even when actual response times haven't changed. On the development side, this principle justifies investment in performance work: slow interfaces aren't just annoying, they reduce engagement and completion rates.

Tesler's Law

Every process has an irreducible amount of complexity - the only question is who handles it, the system or the user.

Also called the Law of Conservation of Complexity, this was articulated by Larry Tesler while working on human-computer interaction at Xerox PARC and Apple. Complexity doesn't disappear when you simplify an interface - it moves. The question a designer has to answer for every feature is: does the system absorb this complexity, or does the user?

Practically: when a checkout form asks for a card number, good UX auto-detects the card type and formats the digits as you type, rather than asking the user to format it correctly themselves. When an address field geocodes a partial entry instead of demanding a rigid format, the system is absorbing complexity the user would otherwise have to manage. Every time you're tempted to add a setting, a step, or a field, ask whether the system could handle it instead.

Postel's Law

Be liberal in what you accept, strict in what you produce.

Postel's Law comes from early internet protocol design (Jon Postel, RFC 761), but it maps directly onto form and input design. Systems that are rigid about what they accept from users create friction; systems that are sloppy about what they output create confusion.

Practically: a phone number field should accept spaces, dashes, and parentheses rather than rejecting anything that isn't eleven bare digits - normalise it after the fact. A date field should parse "5 Sep 2026", "05/09/2026", and "2026-09-05" rather than forcing one format. On the output side, be strict: what you show back to the user - confirmation numbers, formatted totals, validation messages - should be unambiguous and consistent every time.

The Serial Position Effect

People remember the first and last items in a list far better than the ones in the middle.

This comes from memory research by Hermann Ebbinghaus, later refined into the primacy effect (first items are rehearsed and moved to long-term memory) and recency effect (last items are still active in short-term memory). Middle items get the least attention and the weakest recall.

Practically: put your most important navigation items, product options, or onboarding steps at the start or the end of a list, not buried in the middle. If you have a five-step onboarding flow, the first step sets the tone and the last step is what people remember when deciding whether the whole thing felt easy. A pricing page with the plan you want customers to choose in the first or last position outperforms the same plan placed second or third.

The Von Restorff (Isolation) Effect

An item that stands out visually from its surrounding peers is more likely to be remembered.

Named after psychiatrist Hedwig von Restorff, who documented it in 1933, this is the principle behind why a single differently-coloured item in a list draws the eye and sticks in memory more than any item that looks like all the others.

Practically: this is why the recommended plan on a pricing page is usually highlighted with a different colour or a "Most popular" badge, and why a single primary call-to-action button should look visually distinct from every secondary button on the same screen. Use isolation sparingly - if everything is highlighted, nothing is, and the effect collapses.

The Zeigarnik Effect

People remember incomplete or interrupted tasks better than tasks they've already finished.

Soviet psychologist Bluma Zeigarnik observed that waiters could recall unpaid orders in detail but forgot them the moment the bill was settled. The tension of an unfinished task keeps it active in memory in a way a completed one isn't.

Practically: progress bars, "your profile is 80% complete" widgets, and step counters ("Step 2 of 4") all exploit this - the visible gap between where a user is and where they'll be done creates a pull to finish. Onboarding flows and multi-step forms that show remaining steps, rather than hiding them, tend to see higher completion, because the incompleteness itself becomes motivating rather than discouraging.

The Law of Pragnanz

People perceive and interpret ambiguous or complex shapes in the simplest form possible.

The Law of Pragnanz - German for "conciseness" - is the umbrella Gestalt principle underlying proximity, similarity, closure, and continuity. Faced with visual complexity, the human eye and brain default to the simplest, most orderly interpretation available.

Practically: icons, logos, and illustrations read faster and are remembered better when they resolve to simple, recognisable shapes rather than ornate detail. A cluttered dashboard with a dozen visual styles fighting for attention forces the brain to do work it would rather not do. Simplifying the visual language of a product - fewer shapes, more consistent forms - reduces cognitive effort even before anyone reads a word of content.

Occam's Razor

Among competing solutions that solve the problem equally well, the simplest one is usually the right one.

Occam's Razor originates in medieval philosophy (William of Ockham), not psychology, but it's a working principle for UX decision-making: don't multiply design complexity beyond what's needed to solve the user's actual problem.

Practically: when two design directions solve the same user need, and one requires more screens, more copy, or more custom interaction patterns than the other, the simpler one is usually the better bet - unless there's specific evidence the complexity earns its keep. This is a useful check against "clever" designs that solve a problem nobody had, or solve a real problem in a needlessly elaborate way.

Parkinson's Law

Work expands to fill the time available for its completion.

Cyril Northcote Parkinson coined this about bureaucracy in 1955, but it applies directly to task design. Give someone an unlimited amount of time to complete a task and the task will take longer - not because it's harder, but because there's no pressure forcing a decision.

Practically: this is why limited-time offers, countdown timers on checkout sessions, and time-boxed trial periods change user behaviour - they impose a constraint that forces action. It also applies internally: a form with no field limits and no clear end point feels more effortful than a short form with a visible finish line, even if the total amount of information requested is the same.

The Goal-Gradient Effect

Motivation to complete a task increases as people get closer to the goal.

Clark Hull's research on rats running mazes, later confirmed in human behaviour by Ran Kivetz's coffee-loyalty-card studies, found that effort and speed both increase as the finish line approaches. Early progress motivates less than late progress does.

Practically: progress bars that start pre-filled (a loyalty card that begins with two stamps already given, not zero) accelerate completion because the goal feels closer from the outset. Multi-step checkouts, onboarding wizards, and course-completion trackers all benefit from showing users how close they are to done, especially in the final stretch - that's the point where a small nudge has the most effect.

How to Apply These Without Over-Applying Them

The risk with a list like this is treating each law as a trump card to be played in design critiques. "Hick's Law says fewer choices" is not a complete argument. Context matters. A recipe website with a large ingredient list isn't violating Miller's Law - it's serving a user who came specifically for that information. A form with many fields might be unavoidable given business requirements.

Use these principles as a starting point for asking better questions. Why does this feel hard to navigate? Is Fitts's Law telling us the tap targets are too small, or is it something else? What's the peak moment in this flow, and are we designing it with the care it deserves? Our guide to the UX design process is a good companion here - it shows where each of these principles tends to matter most across the different stages of a project.

The designers who use these principles well are the ones who've internalised them enough to apply them quickly and set them aside when the evidence says something different. That kind of fluency comes from practice - real projects, real feedback, real iteration.

If you want to build that fluency alongside a structured curriculum and live instruction, look at what we cover on our beginner UX design course at UX Academy (myuxacademy.com), taught by lead instructor Natalia Veretenyk and her team. Or if you want a low-commitment starting point, our free UX/UI masterclass covers the fundamentals in a single session - no prior experience required.

You can also browse all our courses to see how we approach UX design education.