Hick's Law

The Principle

In 1952, British psychologist W.E. Hick published "On the Rate of Gain of Information" in the Quarterly Journal of Experimental Psychology. Working with Ray Hyman, he built on earlier observations and information theory to show that choice reaction time grows with the logarithm of the number of stimulus-response alternatives.

In classic experiments, participants faced lights in different positions and pressed corresponding keys. As the set of possible lights increased from 1 to 10, reaction time didn't rise linearly — it followed a logarithmic curve. More options meant more uncertainty (measured in "bits" of information), and the brain needed extra time to resolve it. This relationship holds across many simple choice tasks, though real-world factors like familiarity, practice, and stimulus discriminability moderate it.

What Hick's Law reveals beneath the surface is not just slower button-pressing, but the cognitive work of resolving uncertainty. The brain doesn't passively scan options; it actively processes probabilities, eliminates alternatives, and prepares a response. Each additional choice adds mental overhead. In modern terms, this ties into selective attention and working memory limits — the more options compete for processing, the harder it becomes to act decisively.

Why It Matters for Design & Building

The real cost of choice isn't just a few extra seconds of deliberation. It's that the mental energy you sat down to spend on the actual task gets quietly consumed by the act of choosing. Under even mild time pressure or daily fatigue, the range of options you consider degrades while you're still inside the decision. By the time you finally act, you're often working with a diminished set.

I learned this the hard way with my 6am workout habit. For months I kept a long mental menu: run outside, lift weights, yoga video, bodyweight circuit, or "just stretch and walk." Each morning the decision itself ate the limited willpower I had reserved for movement. Some days I'd spend ten minutes weighing options, feel the window closing, and end up doing nothing. The interface of my own intention had too many equally viable paths. When I simplified to one default (a 20-minute bodyweight routine) plus one easy swap (run if the weather felt right), the habit finally stuck. The constraint didn't limit me — it protected the resource I actually cared about.

For designers and builders this is the sharper lesson. Backend flexibility makes it easy to expose many options, but each one competes for the user's finite attention budget. In high-stakes or habitual flows — onboarding, daily tools, checkout — we should design systems that quickly surface or enforce the one constraint that renders most alternatives irrelevant. Progressive disclosure, smart defaults, and clear hierarchies aren't just polish; they're mechanisms for preserving user energy for the work that matters.

As someone bridging design and code, I've watched teams add toggles and filters because "users might want them." They usually do — until the moment they don't, because the cognitive tax arrives first. This becomes even more critical in AI products, where the model already introduces unpredictability. Layering choice overload on top of probabilistic outputs is a fast path to distrust and abandonment. The honest practice is humility: build interfaces that respect the brain's limits rather than testing them. Often, reducing perceived choice quietly increases real agency.

Real-World Examples

Duolingo offers a strong positive example in its onboarding. New users are not dumped into a full menu of language courses, skills, and settings. Instead, the app starts with one simple exercise after a minimal goal-setting step. Features are introduced gradually through guided practice rather than overwhelming choice. This respects Hick's Law by keeping early decisions minimal, helping users build momentum before complexity arrives.

X (formerly Twitter) applies it well in its mobile bottom navigation: a handful of core items (Home, Explore, Communities, Notifications, Messages) plus a clear compose button. The limited set allows quick orientation even for new or distracted users. Complexity lives deeper in the app rather than competing at the primary level.

On the negative side, Microsoft's Windows 8 interface struggled with choice overload. The tile-based Start screen presented a dense, sprawling array of live tiles and options without strong initial hierarchy or progressive disclosure for many users. What was intended as modern flexibility often left people scanning, hesitating, and feeling lost, contributing to slow adoption and frustration.

LINGsCARS.com shows that choice cost is not universal. Its famously cluttered homepage — flashing text, competing offers, and dense navigation — violates Hick's Law on almost every measure. Yet it works for a specific segment: highly motivated bargain hunters who arrive with strong prior commitment to finding a deal. For these users, motivation overrides the cognitive tax. For everyone else, the site feels exhausting. It quietly illustrates how strong external drivers can moderate the law's effect, even as poor architecture limits broader appeal.

Many enterprise dashboards also illustrate the downside. I've seen internal tools with 20+ filter toggles, metric cards, and sidebar options visible at once. Teams report spending noticeable time just deciding where to start or what to adjust, slowing down real work.