behavioral ux
Back to library

Hick's law

Hick's law, or the Hick–Hyman law, says choice reaction time rises in proportion to the information a choice carries. It describes a practised decision between known alternatives, which is not the same thing as finding an item in a list you have never seen.

Settings
10 settings on one screen
  • Mentions
  • Password
  • Weekly report
  • Profile photo
  • Quiet hours
  • Sign-in history
  • Email digest
  • Two-factor
  • Mobile push
  • Email address
Listed in no particular order · scanned top to bottom
Without an order
Settings
10 settings on one screen
Account
  • Email address
  • Password
  • Profile photo
  • Sign-in history
  • Two-factor
Notifications
  • Email digest
  • Mentions
  • Mobile push
  • Quiet hours
  • Weekly report
Grouped by purpose · alphabetical inside each group
With an order
Live demo

The law rests on two small experiments. Hick (1952) ran the first on a single subject — the experimenter himself, who notes at least 8,000 practice reactions before the ones he reported. His mean reaction times fitted a logarithm of the number of alternatives, about 156 milliseconds per bit of choice, and the same function fitted Merkel's 1885 data at about 188 ms per bit; Hick summarised the result as a rate of gain of information of the order of five bits per second. His second experiment, in which subjects deliberately traded accuracy for speed, had two subjects.

Hyman (1953) is the replication that put the second name on the law, and it is barely larger: four male undergraduates responding by voice to lights given nonsense names. He varied the information per stimulus three ways — the number of equally likely alternatives, the relative frequencies of particular alternatives, and sequential dependencies between successive stimuli — and reaction time came out linear in bits for every subject. The slope, the one number a designer could use, ranged from 127 to 215 ms per bit across those four people. That is the provenance of the law: practised keypressing, not a time budget you can put on a screen.

The shape is the part that gets dropped on the way into design advice. Because the cost is logarithmic, doubling the number of options adds one bit and therefore adds a fixed increment — on Hyman's slopes, roughly a seventh to a fifth of a second — whether you go from two options to four or from sixteen to thirty-two. Liu, Gori, Rioul, Beaudouin-Lafon and Guiard reviewed the choice-reaction literature for CHI 2020 and concluded that Hick's law “speaks against, not for, the popular principle that ‘less is better’”, that logarithmic growth in an observed timing curve is not by itself evidence that the law is operating, and that in HCI tasks choice-reaction time can often be assumed constant. The extra option is not what is making your screen slow.

A first encounter with a menu is a search task, and search is linear. Bailly, Oulasvirta, Brumby and Howes (CHI 2014) had 21 participants select labelled items from menus of 8, 12 and 16 items under eye tracking, in unordered, alphabetical and semantic layouts, with items repeated so practice could build. Selection time rose significantly with menu length, and that rise shrank from the first block of trials to the last. Unordered menus were consistently slower than alphabetical or semantic ones, targets further down the list took longer until the layout was learned, and trials where the target was absent took longest, which is what exhaustive scanning predicts. Their model puts the conclusion plainly: with practice, performance shifts from search, which is linear in the number of items, to decision, which is logarithmic and is where the Hick–Hyman law lives. Ordering and labelling a list buys more than shortening it.

Holding the number of options fixed makes the other lesson visible. Fitts and Seeger (1953) tested 72 airmen, crossing three eight-light stimulus panels with three eight-position response panels. Every combination carried the same three bits of information, so Hick's law predicts the same time for all nine. Mean reaction time ranged from 0.39 seconds for the best-matched pair to 0.77 seconds for the worst, and errors from 3.4% to 18.8%. How the options map onto the controls moved performance by nearly a factor of two while the count never changed.

So: well replicated inside its own paradigm, badly over-applied outside it. Proctor and Schneider's 2018 review lists the standing challenges to the law — stimulus–response compatibility, practice, very large set sizes and sequential dependencies — and notes, with some irony, that it is now regarded as fundamental to the design of interfaces that did not exist when Hick ran it. None of this work measures what design advice claims for it. These are millisecond-scale results about one practised keypress; nobody here tested whether cutting options from a pricing page or a navigation bar raises conversion, and none of it is about whether people choose at all rather than how fast — that is choice overload, a separate and considerably weaker finding. Treat Hick's law as a reason to order, group and label a list well, not as evidence for deleting things from it.

When it holds

  • The user already knows which option they want and the mapping is practised. That is the stimulus–response paradigm Hick and Hyman ran, with the alternatives learned in advance and thousands of trials of practice behind the data.
  • Not on first contact with an unfamiliar list. Bailly and colleagues found selection time rising with menu length and with target position, which is serial scanning — roughly linear in the number of items, not the logarithmic curve.
  • Weaker with practice. The length effect in the menu study shrank significantly from the first block of trials to the last, and Proctor and Schneider list practice among the standing challenges to the law.
  • Dominated by the mapping, not the count. In Fitts and Seeger the same eight alternatives produced 0.39 to 0.77 seconds depending on how the display corresponded to the controls.
  • Worst when the target is not there. Absent-target trials took longest, because the user has to inspect every item before concluding it is missing.
  • It is a law about time, not about abandonment. Nothing in this literature predicts that a longer list makes people give up; that claim belongs to choice overload and is far less secure.

How to apply

  • Sort the list — alphabetically or by meaning — instead of shortening it. Ordered menus beat unordered ones consistently, and the advantage grew with length.
  • Put the likeliest target in the first few rows, because a first-time user scans from the top down and selection time rises with target position until the layout is learned.
  • Keep every item in the same position across sessions. Do not reorder a menu by recency or frequency: the length penalty only flattens with practice if the item stays where the user last found it.
  • Add search or filtering to any list where the wanted item may not exist at all. Absent targets are the most expensive case, because they force a scan of everything.
  • Lay the control out in the shape of the choice: plan tiers in price order, a location picker on a map, time slots on a clock. The same eight options cost twice as long under a poor mapping.
  • Keep the extra pricing tier and fix the comparison instead. Make tiers differ on the same attributes in the same order and mark one as recommended; an unclear comparison costs far more than the fraction of a second of reading one more column.
  • Split a long menu into labelled groups on one screen rather than paginating or nesting it. Grouping gives the eye somewhere to jump; another level adds a decision rather than removing one.

What to avoid

  • Hiding options a user needs in order to steer them down a path. Simplify, do not conceal: the EDPB's deceptive design guidelines call this “Longer than necessary” — making the protective control take more steps than the data-invasive one — and tie it to GDPR Articles 7(3), 12(1), 12(2), 21(1) and 25(1).
  • Scattering related settings across many screens. The same guidelines list “Too many options” as a deceptive pattern in its own right, engaging the fairness and transparency principle in Article 5(1)(a) and the transparent-information duty in Article 12(1), because users give up or miss a setting entirely.
  • Citing Hick's law to justify deleting choices. The law predicts a logarithmic cost per doubling, which is why the CHI 2020 review says it argues against “less is better” rather than for it.
  • Treating a slow menu as a count problem when it is a labelling problem. If people read each item twice, the words are wrong, not the number of them.
  • Quoting millisecond slopes from the 1950s as if they were your product's numbers. They came from practised keypresses by one to four laboratory subjects.

Real-world examples

Gymshark exercises screen with a Search Exercises field, tabs for Alphabetical, Body Part and Recent with Alphabetical selected, a section heading A listing Ab Crunch, Ab Roll Outs, Above the Knee Barbell Hang Power Clean, Above the Knee Barbell Hang Snatch and Above the knee Barbell Hang Power Squat, and an A to Z index rail on the right.
Gymshark offers the same exercise library under alphabetical, body part and recent orderings, with a search field above it and an A–Z rail down the side, so a long list is jumped into rather than scanned.
Zocdoc Book an appointment screen headed Available appointments. Today, May 26, Tomorrow, May 27 and Thursday, May 28 each read No available appointments. Friday, May 29 shows a three-column grid of yellow time buttons running from 8:20 AM, 8:30 AM and 8:40 AM down past 1:40 PM.
Zocdoc answers Today, May 26, Tomorrow, May 27 and Thursday, May 28 with “No available appointments” before laying Friday, May 29 out in clock order from 8:20 AM, so a missing slot is read off a line instead of hunted for.
Singapore Airlines seat map for SQ 11 from NRT to SIN on a Boeing 777-300ER in Economy. The header shows seat 42C at SGD 25.50. A colour legend reads Extra Legroom SGD 76.50, Forward Zone SGD 25.50 and Standard Seat SGD 12.80. The grid has columns A, B, C, D, E, G, H, J and K and rows 41 to 48, with unavailable seats marked by crosses, above a Done button.
Singapore Airlines draws the choice as the cabin itself, rows 41 to 48 with unavailable seats crossed out, and keys seat colour to Extra Legroom at SGD 76.50, Forward Zone at SGD 25.50 and Standard Seat at SGD 12.80, so the selected 42C reads as SGD 25.50 from where it sits.
Grab pickup screen with a Pick up at? search field over a map of Teras Kota BSD. Labelled pins include Footbridge and Lau's Coffee Lobby, and a callout reads Preferred pickup (56% of users). The sheet below shows Teras Kota BSD at 0.1km on Jl. Pahlawan Seribu No.8, then Footbridge at 0.1km and Main Lobby at 0.1km, above a green Choose this pickup button.
Grab labels the pickup points on the map where they physically stand and flags one “Preferred pickup (56% of users)”, with Footbridge and Main Lobby repeated at 0.1km in the list below, so the likeliest door is also the first one offered.
Hinge subscription screen on the HingeX tab, headed Get seen sooner and go on 3x as many dates. A horizontal row of cards shows 1 week at $34.97/wk marked New, 1 month at $16.32/wk marked Save 53%, a selected 3 months at $11.66/wk marked Save 67%, and a six-month card running off the edge. Below are Enhanced recommendations, Skip the line and Priority likes, and a button reading Get 3 months for $149.98.
Hinge lines its subscription terms up in one row with the same unit in the same slot on every card — 1 week at $34.97/wk, 1 month at $16.32/wk, 3 months at $11.66/wk — so an added tier costs a comparison rather than a conversion.
1 / 5

Measuring it

  • Primary metric: time from the list or step appearing to a selection being made, split by first-time and returning users. The two groups are doing different tasks — search and decision — and an average over both hides the effect you changed.
  • Secondary: selection accuracy. Count corrections, back-navigation and immediate re-opens of the same menu; Fitts and Seeger's error rates moved with the mapping even where times looked similar.
  • Backfire metric: searches that return nothing, and support contacts asking where something went. That is what simplification-by-deletion looks like in the data.
  • Second backfire metric: the rate of the less profitable choice — reject-all versus accept-all, downgrade versus upgrade, cancel versus keep. If your simplification moved that ratio while completion time barely changed, you concealed rather than simplified.
  • Watch the returning-user curve over several sessions. If selection time is not falling as people repeat the same choice, the layout is probably moving under them.

References

For agents

An agent-friendly guide to this principle lives at /agents/hicks-law.md.

Our MCP server and skills for all principles are coming soon.

Similar principles

Disclaimer: The theories here are just that — theories. They may not apply universally and should be considered in context. Use your own judgment and consult additional sources when applying these principles.