Hick's Law states that the time required to make a decision increases logarithmically with the number of options available. Formulated by psychologists William Edmund Hick and Ray Hyman in the early 1950s, it was derived from controlled reaction-time experiments and describes a robust relationship between choice count and decision latency. In interface design it is invoked to explain why menus with fifty items, product grids with no filtering, and pricing pages with a dozen plans slow people down and increase abandonment.
The logarithmic form of the relationship is frequently misread. Because decision time grows with the logarithm of the number of options rather than linearly, doubling the options does not double the time; the marginal cost of each additional option decreases as the list grows. This means the largest gains come from reducing small sets, and that cutting a list from forty items to thirty-five accomplishes very little. It also means the law alone does not justify the aggressive minimalism it is often cited to support.
The law's original conditions also matter. Hick's experiments involved simple, equally probable stimuli with practiced responses, which is quite unlike choosing between broadband packages or comparing running shoes. Real product decisions involve options that differ in relevance, familiarity, and complexity, and where the person is also evaluating attributes rather than simply reacting. Structure often matters more than count: a well-organized list of fifty products grouped into six meaningful categories is easier to navigate than fifteen presented as an undifferentiated block.
The practical lesson is therefore about the cost of unstructured choice rather than about choice itself. Reducing options helps when the options are genuinely redundant. Where variety is the value the business offers, the answer is not to remove it but to make it navigable: filtering, sorting, faceted search, sensible grouping, comparison tools, recommended defaults, and progressive narrowing all reduce the effective number of options a person must evaluate at any single moment without removing anything from the catalogue.
Defaults deserve particular attention, because they eliminate a decision entirely for the substantial share of people who accept them. A recommended plan, a pre-selected shipping method, a default configuration, or a highlighted best-seller converts a comparison task into a confirmation task. This is powerful enough to require care: a default chosen to serve the business rather than the customer is effective in the short term and damaging when customers realize what happened.
The law is also frequently misapplied to navigation in a way that makes findability worse. Reducing a menu from eight items to five does not reduce the amount of content on the site; it moves items into deeper levels, where they take more clicks to reach and are less likely to be discovered at all. Research on navigation depth generally finds that broader, shallower structures outperform narrow, deep ones for findability, which runs directly counter to the instinct to shorten menus. The productive interpretation is to reduce genuinely redundant options while keeping the structure broad enough that important destinations remain within reach, and to test the resulting hierarchy with tree testing rather than assuming that a shorter menu is a better one.
In commercial work, the useful application is diagnostic rather than prescriptive. Long, flat navigation, category pages without filters, plan comparisons with too many undifferentiated tiers, and forms offering many similar choices are all common findings in a UX audit, and the remedy is usually structural. Where the underlying issue is that the catalogue or product range itself has grown without organizing logic, the work belongs to product design and information architecture rather than to page-level optimization, because no amount of layout change can compensate for a structure that does not match how customers think about the choice.