UX laws
The research findings behind everyday design decisions, stated plainly, with the original sources and what each one means for a real product. The shelf also holds Nielsen's ten usability heuristics, in the same shape. Every law follows the same workbook shape: the law in one sentence, where it comes from, what it means for an interface, examples, where it is misapplied, a checklist to run against your own screens, and related laws and patterns.
Laws
- Jakob's Law
Users spend most of their time on other sites, so they expect yours to work the way those sites already do, and every departure from that habit costs them effort.
- Hick's Law
The time it takes to choose between options grows with the number of options, roughly with the logarithm of that number rather than in step with it.
- Fitts's Law
The time it takes to point at a target grows with the distance to the target and shrinks as the target gets bigger, so near, large targets are the fastest to hit.
- Miller's Law
People can hold only a small number of meaningful chunks in short-term memory at once, about seven in Miller's 1956 estimate and closer to four in later work.
- The Doherty Threshold
People stay engaged and get more done when a computer responds in under about 400 milliseconds, so that neither the person nor the system has to wait for the other.
- Law of Proximity
Things that sit close to each other are seen as belonging together, so the spacing in a layout tells people which elements form a group before they read a single word.
- Peak-End Rule
People judge a past experience mostly by how it felt at its most intense moment and at its end, not by the sum or the average of every moment in it.
- Serial position effect
People remember the first and the last items in a sequence better than the items in the middle.
- Tesler's Law
Every task carries a share of complexity that cannot be designed away, so the real choice is whether the product absorbs it or hands it to the person using it.
- Postel's Law
Accept what people give you in as many reasonable forms as you can, and be strict, consistent and predictable about what you give back.
- Zeigarnik Effect
People remember a task that was started and then interrupted more readily than one they were allowed to finish.
- Von Restorff Effect
When several similar things are presented together, the one that stands out from the rest is the one people are most likely to notice and remember.
- Aesthetic-Usability Effect
People tend to rate a good-looking interface as easier to use than a plain one, and are more forgiving of its small problems.
- Goal-Gradient Effect
People put in more effort, and move faster, the closer they believe they are to reaching a goal.
- Parkinson's Law
Work expands to fill the time available for it, so a task given more time than it needs tends to take all of it.
- Law of Common Region
Elements placed inside the same clearly bounded area, such as a card, a panel or a shaded box, are seen as one group.
- Law of Similarity
Elements that look alike in colour, shape, size or style are seen as belonging together, even when they are not next to each other.
- Law of Prägnanz
People see a complex or ambiguous image in the simplest form it allows, because the simple reading takes the least effort to process.
- Law of Uniform Connectedness
Elements joined by a line or sitting on one continuous surface are seen as more strongly related than elements that are only close together or look alike.
- Paradox of the Active User
People start using software straight away instead of reading instructions, even when a little learning first would save them time overall.
Heuristics
- Visibility of system status
A product should always let people know what it is doing and what just happened, through clear feedback that arrives quickly enough to be useful.
- Match between the system and the real world
A product should speak the language of the people who use it and present information in the order and form they already know from the world outside the screen.
- User control and freedom
People take wrong turns, so a product should give them a clearly marked way to undo, go back or leave without having to go through a long process.
- Consistency and standards
The same word, icon or action should mean the same thing everywhere in a product, and the product should follow the conventions people already know from their platform and industry.
- Error prevention
A design that stops a mistake from happening in the first place is better than any message explaining the mistake after it has happened.
- Recognition rather than recall
A product should reduce what people have to remember by keeping objects, actions and options visible, so they can recognize what they need instead of recalling it from memory.
- Flexibility and efficiency of use
A product should serve newcomers and experts at once, offering shortcuts and customization that speed up frequent users without getting in the way of people who are still learning.
- Aesthetic and minimalist design
An interface should show only what matters for the task at hand, because every extra element competes for attention with the information people actually need.
- Help users recognize, diagnose, and recover from errors
When something goes wrong, the product should say so in plain language, explain what the problem is and offer a concrete way to fix it.
- Help and documentation
A product should ideally be usable without help, but when people need it, help should be easy to find, focused on their task and written as concrete steps.