Blog

Top 10 UX Laws Everyone Should Know

Ten UX laws, each with the study or product behind it, what it claims, and where it stops holding. Use them to explain decisions, not to replace testing.

What a UX law is

A UX law is an observation about how people behave that has held up well enough to design with. It's not a law of physics. Several on this list are better described as heuristics (rules of thumb) or effects, and each has limits you should know before you lean on it. Some are older than the web: Max Wertheimer described how people group dots in 1923, and Paul Fitts measured how fast people move to a target in 1954.

The practical value is that a law gives a design decision a reason other than taste. If someone says “I prefer the button on the left,” the room argues about taste. If someone says “people look for the logo there, and one study counted how often they failed when it moved,” the team has something to check. Here are ten worth knowing, each with one real case you can look up.

1. Jakob's Law

Jakob's Law says users spend most of their time on other sites, so they prefer yours to work the way the others do. Jakob Nielsen formulated it in 2000, in an article from July that year (opens in a new tab). People arrive with those habits whatever you intended.

A 2016 Nielsen Norman Group article (opens in a new tab) reports a study in which 50 people each used one of 14 fashion-retail sites. Eight of the sites centered their logo and six kept it left-aligned. Each person picked a gift under $100, added it to the cart, then was asked to go to the site's starting page. People were 6 times as likely to fail to get there in a single click when the logo was centered. Jakob Nielsen has described a study with that six-fold gap as 4% failing with a left-aligned logo against 24% with a centered one.

2. Fitts's Law

Fitts's Law says the time it takes to reach a target depends on how far away it is and how big it is. The farther and smaller the target, the longer the movement takes. Psychologist Paul Fitts published the finding in 1954. He had people move a stylus back and forth between two plates and tap each one at its center, with plates of different widths and distances apart.

Push the pointer to the top edge of a Mac screen and it stops there, so you can't overshoot a menu item that sits against the edge. Nielsen Norman Group uses this to explain Fitts's Law (opens in a new tab): macOS puts the application menu at the very top of the screen, which turns each menu item into what the article calls an infinite target.

The edge trick has a limit. It works with a mouse or trackball, where the screen edge stops the pointer. A study by Daniel Avrahami, described in the same article, found that on touchscreens it actually takes longer to hit targets placed around the edges.

3. Hick's Law

Hick's Law says the time it takes to make a choice rises with the number of options, but slowly. Each doubling of the options adds about the same extra delay, because people sort options into groups (opens in a new tab) and drop about half of what remains at each step.

William Edmund Hick began his experiments in 1951 and published them in 1952. He arranged ten lamps in a circle around each volunteer and paired each lamp with a Morse key worked by a different finger. A random lamp lit every 5 seconds, and the volunteer pressed the matching key. Hick found that reaction time rose with the logarithm of the number of possible choices, which is that doubling pattern.

Ray Hyman extended the work in 1953, so you'll also see the Hick-Hyman law. The law is often quoted as “fewer options is always better.” It doesn't say that. It describes reaction time for equally likely choices. Studies of spoken answers to familiar items found little or no extra time as options grew. In a randomly ordered list, people read item after item, so time rises in a straight line and Hick's Law doesn't apply. In an alphabetical list, someone who knows the name can split the list and search in logarithmic time.

4. Miller's Law

Miller's Law says short-term memory holds a limited number of chunks, the units you've learned to treat as one. George Miller made the case in his 1956 paper The Magical Number Seven, Plus or Minus Two (opens in a new tab).

The paper describes a test the psychologist Sidney Smith reported in 1954. Among 20 volunteers, memory span was 9 for binary digits (zeros and ones) and 7 for octal digits (the numbers 0 to 7). Smith taught them to rename each group of three binary digits as one octal digit, so 18 binary digits became 6. Smith then drilled himself on it and could repeat back 12 octal digits, the same as 36 binary digits. With bigger groups he reached about 40.

The seven in the title has since been revised. In 2001 Nelson Cowan reviewed the evidence (opens in a new tab) and wrote that Miller meant it as a rough estimate and a rhetorical device, not a real limit. Cowan put capacity at three to five chunks, averaging about four. People also stretch it to cap menus at seven items. Miller tested what people could recall, not how long a visible menu can be.

5. The Doherty Threshold

The Doherty Threshold says people get far more done once a computer replies to each command in under a second. It comes from a 1982 report by Walter Doherty and Arvind Thadhani at IBM.

When businesses first put people in front of computers, psychologists argued that two seconds was the longest anyone should wait for a reply, and designers worked to that. The comforting thought was that the wait cost nothing, because the person was using those seconds to plan their next step anyway. Doherty and Thadhani's report (opens in a new tab) says that thought was wrong. It uses measurements Thadhani made of programmers working at terminals, which were a screen and keyboard wired to a big shared computer.

Every command a programmer typed and every answer the computer sent back made up one transaction. Thadhani counted how many transactions programmers got through in an hour. When the computer took 3 seconds to answer, they finished about 180, which is one every 20 seconds. When it answered in 0.3 seconds, they finished 371, one every 9.7 seconds. That's 106 percent more work in the same hour.

The faster answer saved far more than the 2.7 seconds cut from the computer's wait. Each transaction got about 10 seconds shorter. The rest of the saving came from the programmers themselves: the pause between getting an answer and typing the next command fell from 17 seconds to 9.4. The report's explanation is that people keep the next few steps in mind while they work, and a long wait makes them lose that plan, so they have to think it through again. You've probably felt this when a page hangs and you forget what you were about to click.

You'll often see the threshold quoted as 400 milliseconds, which is under half a second. That number doesn't show up in the copy of the report that's online, which talks about replies of under a second. Kent Beck, writing about the threshold, calls the figure (opens in a new tab) a practically motivated threshold and not a universal constant of human attention. Treat it as a useful target.

6. The Aesthetic-Usability Effect

The aesthetic-usability effect (opens in a new tab) says people judge attractive designs as easier to use.

A participant in a Nielsen Norman Group usability test shopped on the Fitbit site and ran into problems that ranged from small annoyances to serious flaws in the navigation. She finished her task, but with difficulty. Afterward she rated the site's ease of use very highly. Asked for feedback, she talked only about the look: “It's the colors they used. Looks like the ocean, it's calm. Very good photographs.”

The effect was first studied in human-computer interaction in 1995, when Masaaki Kurosu and Kaori Kashimura at the Hitachi Design Center had 252 participants rate 26 variations of an ATM interface for ease of use and for appeal. Ratings of appeal matched ratings of perceived ease of use more closely than they matched actual ease of use. The effect has a limit: a pretty design can make users forgive minor problems, but not large ones.

7. The Law of Proximity

The law of proximity says that things sitting close together look like they belong together. Max Wertheimer demonstrated it in 1923 (opens in a new tab) with a row of dots whose gaps alternated between 3 mm and 12 mm. People see pairs of dots, not an even row. He called it the Factor of Proximity and noted it isn't the only grouping factor, since similarity groups things too.

On the California EDD website, as Nielsen Norman Group described it in 2020, the Add button for listing employer information sat among the unrelated buttons for Next, Save as Draft and Cancel. It was close to buttons it had nothing to do with and far from the main area of the form, which made it hard to find. The same article on the proximity principle (opens in a new tab) adds that Previous and Next are related, so grouping those two would have helped.

8. The Peak-End Rule

The peak-end rule says people remember an experience mostly by its most intense moment and its end, not by the total. The idea traces back to a 1993 study (opens in a new tab).pdf) by Daniel Kahneman and colleagues. In it, 22 of 32 people chose to repeat a longer cold-water trial that ended slightly warmer over a shorter one.

In a randomized trial published in 2003, Donald Redelmeier, Joel Katz and Kahneman (opens in a new tab) studied 682 people having a colonoscopy. Half of them, chosen at random, had up to 3 minutes added at the end while the instrument's tip rested still, with no suction or inflation. Both groups reported nearly the same peak pain (8.1 and 8.0 on a scale of 0 to 10). But the group with the longer procedure rated its final moments as less painful (1.7 against 2.5). Over about five years, the odds that they came back for another colonoscopy were 1.41 times as high. Return rates averaged 50.4%, so the effect was real but modest.

9. The Von Restorff Effect

The von Restorff effect, also called the isolation effect, says the one item in a list that differs from the rest is the one people remember best.

Hedwig von Restorff published her memory experiments in 1933. In one of her experiments, volunteers studied a list of 19 nonsense syllables and a single number, or 19 numbers and a single syllable, with the odd item in the middle. The odd item was remembered much better than its neighbors, and the advantage was far bigger than in her first lists, which held several odd items. A history of her work (opens in a new tab) sets out these experiments in detail.

Two limits matter for design. She measured memory for items in a list, not where people look or click, so applying it to a screen goes beyond what she tested. And the effect depends on rarity: it grew when her lists held fewer odd items. Her own explanation also put weight on the plain items, which interfere with one another because they resemble each other.

10. Tesler's Law

Tesler's Law, also called the law of conservation of complexity, says every app has some complexity that can't be removed, only moved. Around 1984, the computer scientist Larry Tesler, who worked at Xerox PARC and Apple, put it this way: “Every application has an inherent amount of irreducible complexity.” (opens in a new tab) The open question is who handles it: the person using the app, the team building it, or the platform underneath.

Buy something with Amazon's 1-Click (opens in a new tab) and you don't type a shipping address or card number, because the system uses the ones you stored. The US Patent and Trademark Office issued Amazon a patent for the technique in September 1999.

1-Click answers that question in the shopper's favor. The work of typing an address and a card number doesn't vanish when it leaves the form. It moves to Amazon's system, which holds the details for you. Moving complexity isn't free, because the team that takes it on has to build and maintain it.

Using these laws

Use them in two ways. One is to explain a decision to a team with a reason people can check instead of a matter of taste. The other is to spot a likely problem early, in a design review, before it costs a round of testing.

They don't replace watching real people use your product. Each law was measured in a particular setting, and yours may differ. The laws tell you where to look. A test with a handful of users tells you whether it matters in your product, and when a law and your test disagree, trust the test and work out why.

Sources

Show all 22 sources
  1. Nielsen Norman Group: The End of Web Design (July 2000)

  2. Jakob Nielsen: Jakob's Law of the Internet User Experience

  3. Nielsen Norman Group: Centered Logos Hurt Website Navigation

  4. Nielsen Norman Group: Fitts's Law and Its Applications in UX

  5. Fitts (1954): The information capacity of the human motor system in controlling the amplitude of movement

  6. I. Scott MacKenzie: Fitts' Law (chapter)

  7. Hick (1952): On the Rate of Gain of Information

  8. Miller (1956): The Magical Number Seven, Plus or Minus Two

  9. Cowan (2001): The magical number 4 in short-term memory

  10. Doherty and Thadhani: IBM report on the economic value of rapid response time (scanned copy)

  11. Kent Beck: The Precious Eyeblink

  12. Nielsen Norman Group: The Aesthetic-Usability Effect

  13. Wertheimer (1923): Laws of Organization in Perceptual Forms

  14. Nielsen Norman Group: Proximity Principle in Visual Design

  15. Kahneman, Fredrickson, Schreiber and Redelmeier (1993): When More Pain Is Preferred to Less

  16. Redelmeier, Katz and Kahneman (2003): Memories of colonoscopy, a randomized trial

  17. Nielsen Norman Group: The Peak-End Rule

  18. Zeigarnik and von Restorff: The memory effects and the stories behind them (Memory & Cognition, 2020)

  19. Larry Tesler: The Law of Conservation of Complexity

Missing a concept?

Tell us what to write next. We’ll email you when it’s live.

Several? Separate them with commas.

Only to tell you when it’s live.

How we use your email: privacy.