UXFU.com Master the craft.
Glossary / Psychology

Hick's Law

Blue Belt ~6 min read
Animation illustrating Hick's Law

Hick’s Law in UX is the principle that the time it takes a user to make a decision increases as the number of choices grows – decision time scales logarithmically with the number of options, which means doubling the choices consistently slows users down and increases the risk that they won’t choose at all.

Why It Matters

Every interface presents choices. Navigation menus, filter panels, form dropdowns, product listings, settings screens – all of them ask users to select from a set of options. Hick’s Law gives designers a principled reason to be ruthless about what goes on those lists.

The cost of too many choices isn’t just speed. Barry Schwartz’s “paradox of choice” research showed that excessive options lead to decision paralysis, lower satisfaction with the eventual choice, and higher regret afterward. Users confronted with 50 filter options don’t carefully weigh each one – they often give up and leave, or make a random selection they later second-guess.

For designers, Hick’s Law is a useful pushback against the “just add it” impulse. Every time a stakeholder asks to add another item to a navigation menu, another tier to a pricing page, or another field to a settings panel, the cognitive cost is real. The law doesn’t say fewer is always better – it says every addition has a measurable cost that should be justified.

How It Works

The relationship is logarithmic: decision time grows as the number of equally probable choices increases, but each additional option adds less time than the previous one. You don’t need the formula in daily design work, but the underlying insight matters – the first few choices you add to a list slow users down significantly, while later additions have diminishing (but never zero) impact.

Chunking reduces perceived complexity. A navigation with 12 items feels overwhelming. The same 12 items organized into 3 groups of 4 feel manageable – users first choose a category, then a specific item. The total number of options hasn’t changed, but the decision at each step is smaller. This is the structural logic behind information architecture.

Familiarity bypasses Hick’s Law. Expert users with a deeply learned mental model don’t deliberate the way first-time users do. A keyboard shortcut requires no choice at all. A power user’s muscle memory routes around conscious decision-making. Hick’s Law applies most strongly to novel choices, not practiced ones.

Defaults are a form of choice reduction. Pre-selecting the most common option, or hiding advanced settings behind an expandable section, reduces the effective number of choices for the majority of users. Progressive disclosure is the structural pattern that makes this work systematically.

When Hick’s Law Doesn’t Apply

Not every long list is a Hick’s Law problem. A search results page with 100 items isn’t asking users to choose between 100 things simultaneously – it’s a browsable list with scannable attributes. Users apply their own filters (price, brand, appearance) to reduce the effective choice set.

Similarly, a well-organized settings panel with 30 clearly labeled options in logical categories doesn’t violate Hick’s Law in a damaging way – the categorization does the chunking work. The problem arises when options are undifferentiated, unlabeled, or presented as a flat list without structure.

Expert users are another exception. A command palette like the one in VS Code or Figma presents hundreds of options, but experienced users navigate it near-instantly because they know what they’re looking for. The “choice” is effectively already made before the palette opens.

Real-World Example

Netflix’s category browsing system is a direct application of Hick’s Law thinking. Rather than presenting all 15,000+ titles as a single browsable list, Netflix organizes content into rows by genre, mood, and personalized recommendation clusters. At any given moment, a user is choosing between 10–20 items in a row – not 15,000.

The design tradeoff is visible in how Netflix handles filtering. Too much explicit filtering (genre + year + language + rating simultaneously) can itself become a Hick’s Law problem – users get lost in filter configuration rather than content discovery. Netflix’s solution is to do the filtering work algorithmically, presenting pre-filtered rows rather than asking users to construct their own queries. The complexity is absorbed by the system, not offloaded to the user.

How to Apply

  1. Audit navigation items before adding more. For every new navigation item proposed, ask what it replaces or what grouping it belongs to. Navigation menus that grow without structure become decision bottlenecks that slow every user on every visit.
  2. Use progressive disclosure for complex forms. Show the minimum number of fields required for the primary task. Reveal additional options only when users indicate they need them. See progressive disclosure for the full pattern.
  3. Set sensible defaults. The decision a user doesn’t have to make is always faster than the one they do. Pre-select the most common option and let users change it, rather than forcing an explicit selection every time.
  4. Chunk long lists into meaningful groups. Before reducing the number of options, try categorizing them. Three groups of five feel cognitively like choosing from five, not fifteen.
  5. Reduce choices at decision-critical moments. Checkout flows, onboarding steps, and error recovery screens should present the fewest meaningful choices possible. These are the moments where friction has the highest cost.

Common Mistakes

Applying Hick’s Law to browsable lists. Not every long list requires reduction. The principle applies to discrete decision points, not exploratory browsing contexts where length is expected and users have their own filtering strategies.

Removing options without understanding user needs. Simplifying by deleting options rather than organizing them can remove functionality that a meaningful minority of users depend on. The answer is often structure, not subtraction – progressive disclosure hides rather than removes.

Conflating number of options with complexity. A picker with three poorly labeled options is harder to use than one with ten well-described ones. Choice count matters, but labeling, organization, and option quality matter just as much.

Further Reading

Test Your Knowledge

Flash Quiz

Which of these best defines Hick's Law in user experience design?