Strategy ⚡ Low

Hick's Law

More choices = more time to decide. The time it takes to make a decision increases logarithmically with the number of options. Every option you add is cognitive debt the user must repay.

Navigation Onboarding Checkout Forms Pricing

01 — TL;DR

Two sentences.

Hick's Law states that the time required to make a decision increases as the number of choices grows — specifically, as a logarithmic function: RT = a + b log₂(n), where n is the number of equally probable alternatives. In practice: every option you add to a screen is asking the user to spend mental energy they might not have.

The formula in plain English

Doubling your choices doesn't double decision time — it adds a fixed increment. Going from 1 to 2 choices adds roughly the same amount of time as going from 4 to 8. This is why simplification has diminishing returns at the extreme end, but the first few cuts make the biggest difference.

02 — When to Use

Apply this when…

→ You're designing any navigation system — global nav, sidebar, tab bars, bottom nav

→ A form has more than 5–7 fields and completion rates are lower than expected

→ You're designing a pricing page with more than 3 plans

→ An onboarding flow shows too many options upfront and users are dropping off before activation

→ A checkout flow has multiple competing CTAs or decision points on the same screen

→ A stakeholder wants to add "just one more option" to an already full screen

When NOT to apply it

Hick's Law applies to discrete choices from a closed set. It doesn't apply to search, open-text input, or expert-mode interfaces where users have strong mental models and speed is the goal. Power users with high familiarity are less affected — the law is most potent for new users and infrequent decisions.

03 — How It Works

The mechanism

William Edmund Hick and Ray Hyman published separate papers in 1952 and 1953 establishing that reaction time scales logarithmically with the number of stimulus-response pairings. The key insight is that each additional choice requires the user to eliminate alternatives — a process that takes cognitive work proportional to the information content of the choice.

Audit your choice sets

List every decision point on the screen. For each one, count the number of options. Any count above 7 (Miller's Law threshold) is a candidate for reduction.

Categorise, don't eliminate

You don't always need to remove options — you can group them. A nav with 12 items becomes manageable as 4 categories of 3 items each. The decision space is the same; the cognitive load is smaller because the user makes two sequential small decisions instead of one large one.

Use progressive disclosure

Move secondary options behind a "More" pattern, a settings panel, or an expandable section. Surface only the options that matter most to the majority of users at the primary level.

Add visual hierarchy

Even without reducing count, you can reduce perceived complexity through hierarchy. A primary action at high contrast with secondaries visually de-emphasised effectively creates a 1+n structure. The "1" is the obvious choice; the "n" exist but don't demand attention.

Test with real users

Time-to-click is a measurable proxy for decision time. Run a first-click test or session recording analysis before and after a simplification. The data usually confirms what Hick predicts.

04 — Real Example

Netflix and the paradox of choice

Netflix's internal research found that their recommendation algorithm was showing users too many categories on the homepage. When they reduced the number of visible content rows from 76 to a curated set of 6–10, they measured a significant improvement in time-to-play — the key activation metric for their product.

The counterintuitive finding: users who saw fewer categories watched more content, not less, because they spent less time in the paralysed browsing state and more time actually watching. The abundance of choice was actively harming engagement.

E-Commerce · Checkout · 2023

Payment method overload

A European e-commerce client had 11 payment methods displayed on their checkout screen — every option their payment provider supported. A/B testing with a simplified view showing 4 methods (Card, PayPal, Apple Pay, "More options →") reduced checkout abandonment by 18% and increased conversion. The products were identical. The decision architecture was the only variable.

+18% conversion

05 — In the Wild

Test yourself & see real examples

No examples yet — be the first.

Spotted Hick's Law in the wild? A real product using it well — or ignoring it entirely? Submit a screenshot and annotate what you see. Every approved example gets attributed to you.

✓ Reviewed before publishing ✓ Your name on every example you submit ✓ Violation or fix — both welcome

Seen Hick's Law violated in a real product? Help grow the evidence base.

06 — Common Mistakes

Where teams go wrong

✗ Confusing reduction with removal. "Simplifying" by hiding options in a hamburger menu doesn't reduce the choice set — it just makes it harder to find. Reduction means fewer actual options, not hidden options.

✗ Applying it to expert interfaces. A keyboard shortcut panel for a code editor, a settings page for power users, an admin dashboard — these are contexts where users have high familiarity and Hick's Law is less relevant. Reducing options in expert UIs often frustrates more than it helps.

✗ Using it to justify bad IA. "We can only have 5 nav items because of Hick's Law" is often used to avoid the harder work of good information architecture. Hick's Law is about decision paralysis; IA is about findability. The right question is: can users find what they're looking for, not: can they decide between the items you've shown them.

✗ Ignoring familiarity effects. For repeat users performing familiar tasks, the cost of additional options drops significantly because they've built a mental model. Over-simplifying for power users based on Hick's Law applied to new users can damage retention.

✗ Not testing the hypothesis. "We removed 3 nav items so performance should improve" is a prediction, not a result. Always measure: first-click accuracy, time-to-click, task completion rate. The law predicts the direction of the effect, not its magnitude.

07 — Variations & Related Principles

Connected ideas

Hick's Law sits in a cluster of principles governing cognitive load and decision-making. Understanding its neighbours tells you when to apply it and when a different principle is more relevant.

The most important pairing is Cognitive Load Theory — Hick's Law is a specific application of the broader CLT framework. If CLT is the general case (working memory is finite), Hick's Law is the specific case (choice count consumes working memory predictably). Use both together when auditing any decision-heavy interface.

08 — 10-Min Exercise

Run it right now

⏱ 10 minutes · Solo or team · No prep

The Choice Audit

Open a product you're currently working on — or a competitor's product. Navigate to the most complex screen.

1. Count every discrete choice a user must make on that screen. Include navigation items, buttons, form fields, toggles, and links. Write the number down.

2. For each choice, ask: "What percentage of users actually need this option on this screen, at this point in their journey?" Mark anything below 20% as a candidate for progressive disclosure.

3. Sketch a simplified version that moves the low-use options to a secondary level (a "More" section, a settings page, a contextual tooltip). Count the remaining top-level choices.

4. Share it with one other person and ask them to complete a task without instructions. Time how long it takes on each version.

10 minutes