Hick's Law: Why Fewer Choices Help Users Decide Faster

The 70-year-old psychology finding behind every calm menu, simple checkout, and confident tap.

You need a flight from Dhaka to Cox's Bazar. You open a travel app and the screen hits you all at once: 27 filters. Airlines, stops, baggage, meals, departure windows, fare classes. You have not seen a single flight yet, and your brain is already tired.

Now picture the same app: three flight cards with the essentials, and one quiet "Filters" button. You pick a flight in under a minute.

Both screens book the exact same flight. The difference is how many decisions each screen demands, and when. That difference has a name behind it. It is called Hick's Law.

---

The Lamp Experiment That Started It All

In 1952, British psychologist William Edmund Hick arranged ten lamps in a circle, each paired with a key the subject pressed with a different finger. A lamp lit up at random, and Hick measured how long the response took as he changed the number of lamps in play. American psychologist Ray Hyman extended the work in 1953 with named lights and found the same pattern: reaction time grows with the number of alternatives, but not in a straight line. The relationship is logarithmic, commonly written as RT = a + b · log2(n), where RT is reaction time and n is the number of choices.

The shape of that curve is what matters. The penalty is steepest for the first few extra options, then it flattens: 3 options to 12 slows people far more than 30 to 40. So the biggest wins come from simplifying screens that already look simple.

Three Things Hick's Law Does Not Mean

The law is widely quoted and just as widely misused, so three corrections are worth making.

First, it is not a mandate to delete options. The Nielsen Norman Group's guidance on long menus says it directly: long menus work well when items are grouped, labelled clearly, and revealed progressively. Organising usually beats amputating.

Second, it does not govern searching. Finding a name in an alphabetical list takes linear time, since you scan item by item, so the logarithmic relationship does not apply. For findability problems, invest in better search, sorting, and filtering instead of cutting items.

Third, it punishes undecided users most. The person who pays the full price is the browser, the comparer, the first timer, and that is exactly the person you most need to convert.

Four Practical Ways to Apply It

1. Chunk and categorise

When options cannot be removed, group them into labelled categories so users eliminate whole groups at once. Retailers do this with departments: each click roughly halves the remaining choices.

2. Reveal complexity gradually

Show the essentials first and expose advanced controls only when asked for. This is progressive disclosure: Hick's Law applied over time instead of space.

3. Recommend one clear option

Smart defaults and a visible "Most popular" badge let the majority decide in one glance. Design the fast path for the many and keep the full set one step away for the few.

4. Break big tasks into smaller steps

One decision per screen beats twelve on one screen. A checkout asking for email, then payment, then delivery across three calm screens converts better than one overwhelming form.

Technique	When to use it	Real example
Chunk and categorise	Many options, all needed	Grouped navigation menus; retail departments
Progressive disclosure	Advanced options few users need	"Filters" button instead of 27 visible filters
Recommended option	One choice suits most users	Default plan, "Most popular" badge
Task breakdown	Long process, many decisions	Multi-step checkout; Slack onboarding

A Real Test: Two Flight Screens

Return to the two flight screens from the opening. The 27-filter version demands 27 micro decisions before the user has seen a single flight. The three-card version demands exactly one: which flight looks right.

The goal is not fewer options. The goal is fewer decisions at the same moment. Power stays available while pressure stays low.

Mistakes Designers Keep Making

The most common is treating the law as a deletion mandate. Teams cut menus by raw count and hide settings users need. If research shows nobody uses an option, remove it; otherwise group it, sequence it, or disclose it progressively. Another error is applying the law to search problems, where the fix is better ordering, not fewer items.

Frequently Asked Questions

How many options is too many? Is there a magic number?

No. The law describes a relationship, not a limit. Five confusingly similar options can be harder than ten clearly distinct ones, because complexity counts alongside quantity. Instead of chasing a number, test with real users and watch where hesitation appears.

What if my users genuinely need all the options visible?

Keep them visible, but organise them. Group into categories, add clear labels, and use visual hierarchy so the eye lands on the most likely choices first. The law does not forbid abundance; it forbids demanding that users process all of it simultaneously.

Key Takeaways

---

Conclusion

Seventy years after Hick's lamps, the lesson is concrete. Do not ask how many options you can delete. Ask how many decisions the user must make at this exact moment, and whether each one earns its place there.

---

References and Further Reading

• Hick's Law, Laws of UX
• Hick's Law: Designing Long Menu Lists, Nielsen Norman Group (video)
• Hick's Law, Interaction Design Foundation
• Hick's law, Wikipedia