UX Design · Lesson 12 / 13
Laws of UX
The psychology behind interfaces: Fitts's, Hick's, Jakob's and Miller's laws, Tesler's law, the Doherty threshold, the peak–end rule, cognitive load and more — with practical design implications.
5 min read · 5 quiz questions
Why psychology matters in UX
People don't use interfaces as rational machines. Perception, attention and memory are limited, and we rely on shortcuts and habits. A set of principles from psychology — often collected as the "laws of UX" — explains many patterns you see in good design.
They are not physical laws. They are well-supported tendencies. Use them to explain and guide design decisions, and always check them against real user behaviour.
Fitts's law
The time to reach a target depends on the distance to it and its size. Close, large targets are fast to hit; far, small ones are slow and error-prone. Paul Fitts described this in 1954 studying physical movement, and it applies to mouse pointers and fingers alike.
- Make primary buttons large enough and give them generous touch areas.
- Place related actions close to where the user's attention already is (e.g. "Save" near the form, not at the top of the page).
- Screen edges and corners are easy to hit with a mouse because the pointer stops there — operating-system menus use this.
- Keep destructive actions away from frequent ones to avoid accidental taps.
Hick's law (Hick–Hyman law)
The time it takes to make a decision increases with the number and complexity of choices. More options mean slower decisions — and sometimes no decision at all.
- Reduce choices where possible: fewer plans, fewer menu items, fewer form fields.
- Group and categorise long lists so people decide in smaller steps.
- Highlight a recommended option ("Most popular").
- Use progressive disclosure: show basic options first, advanced ones on request.
- Break complex tasks into steps (onboarding wizards, checkout steps).
Common mistake: Applying Hick's law blindly. Hiding things too aggressively makes them hard to find. The goal is to reduce unnecessary choices at the moment of decision, not to remove useful options.
Jakob's law
Users spend most of their time on other sites and apps, so they prefer yours to work the same way as the ones they already know. Named after Jakob Nielsen.
- Follow established conventions: logo top-left (top-right in RTL) linking home, search with a magnifying glass, cart icon in the header, underlined links.
- Use platform patterns on mobile (tab bars, swipe back on iOS).
- When redesigning, give users time to adapt — or let them keep the old version briefly.
- Innovate where it creates real value, not on basic controls.
Miller's law and chunking
In 1956, psychologist George Miller observed that people can hold roughly 7 (plus or minus 2) items in short-term memory. Later research suggests the real number is often smaller, around 4 "chunks".
The practical lesson is about chunking: grouping information into meaningful units makes it easier to process and remember.
Hard: 4111111111111111
Easier: 4111 1111 1111 1111
Hard: +212612345678
Easier: +212 6 12 34 56 78Common mistake: Using Miller's law to argue that menus must have "no more than 7 items". Menus are visible — people don't need to memorise them. The law is about memory, not about how many options can be on screen.
Tesler's law (conservation of complexity)
Every system has a certain amount of complexity that cannot be removed — only moved. Larry Tesler argued it's better for the system (and its designers and developers) to absorb complexity than to push it onto users.
- Auto-detect the card type from the number instead of asking.
- Fill in the city from the postal code.
- Use smart defaults so most people never need to change settings.
Doherty threshold
Productivity soars when a computer and its users interact at a pace (under about 400ms) that ensures neither has to wait on the other. Fast responses keep people in flow.
- Give instant visual feedback on every action, even if the work takes longer.
- Use skeleton screens and optimistic UI (show the result immediately, sync in the background).
- Show progress indicators for anything that takes more than about a second.
More principles worth knowing
| Principle | What it says | Design implication |
|---|---|---|
| Peak–end rule | Experiences are judged mainly by their peak moment and their end | Design delightful success states and graceful endings |
| Aesthetic–usability effect | Attractive designs are often perceived as easier to use | Visual quality builds trust and patience — but can hide real problems in testing |
| Von Restorff (isolation) effect | The item that differs is remembered | Make the primary action visually distinct — and only one |
| Serial position effect | First and last items in a list are remembered best | Put key items at the start and end of navigation |
| Zeigarnik effect | Unfinished tasks are remembered better than finished ones | Progress bars and checklists motivate completion |
| Goal-gradient effect | Motivation increases as people get closer to a goal | Show progress; give a head start ("2 of 5 done") |
| Postel's law | Be liberal in what you accept, conservative in what you send | Accept phone numbers with or without spaces; format output consistently |
| Occam's razor | Prefer the simplest solution that works | Remove elements until removing more would hurt |
Cognitive load
Cognitive load is the mental effort needed to use an interface. Intrinsic load comes from the task itself (filing taxes is complex). Extraneous load comes from the design (confusing layout, unclear labels). Your job is to minimise extraneous load so people can spend their attention on the task.
Do
- Use familiar patterns and clear labels.
- Show one primary task per screen.
- Remove visual clutter and decoration that carries no meaning.
- Offload work: defaults, autofill, reminders.
Don't
- Make people remember information between screens.
- Use novel interactions for basic tasks.
- Present every option at once.
- Write long, dense instructions.
Key takeaways
- Fitts's law: make important targets large and close.
- Hick's law: fewer, grouped choices lead to faster decisions.
- Jakob's law: follow conventions users know from other products.
- Miller's law is about chunking information for memory — not a limit on menu items.
- Absorb complexity in the system (Tesler), respond fast (Doherty), and design the peaks and endings.
Exercise
Spot the laws in the wild
- Open three apps you use daily.
- Find one example of each: Fitts's, Hick's and Jakob's law being applied well.
- Find one place where a law is violated and it causes friction.
- Redesign that one place with a quick sketch.
- Explain your change in one sentence using the law's name.
Test yourself
Laws of UX quiz
5 questions. Score 70% or more to complete the lesson.
