UX Design Laws and Principles Every Designer Should Know

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 nine you'll use constantly.

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. 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.

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?

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. 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.