Choices and navigation
Hick's Law
Make the next decision understandable. Removing useful choices is only one possible way to do that.
The idea in plain language
What it means.
Hick studied choice reaction time under controlled conditions. More uncertainty generally required more decision time. In an interface, clear labels, meaningful groups and relevant defaults can make choices easier to distinguish. A sprawling menu and a well-organized directory are different problems, even when they contain the same number of links.
Evidence and interpretation
What supports it.
Laboratory choice-reaction research. Applying it to menus is a design inference; the study does not establish a universal maximum number of navigation items or calls to action.
From principle to interface
Where you could use it.
Proposed applications, not tested outcomes. The expected effects are hypotheses to check with realistic tasks and users.
Application 1
Choose an export format
A report offers CSV for spreadsheets and PDF for sharing, with short explanations and advanced formats in a labelled disclosure.
Expected effect to test
People can identify the format that fits their next task.
Keep in view
Keep advanced formats discoverable and remember a preference only when the user can change it.
Application 2
Browse a large tool catalog
Group tools by job, then provide search and filters for platform, account requirements and cost.
Expected effect to test
A visitor can narrow the catalog using criteria they understand.
Keep in view
Test the group names. More levels can add work if the categories do not match the visitor's task.
Turn the idea into a check
Use it deliberately.
- Name the decision before simplifying the screen.
- Use distinct labels and explain consequential defaults.
- Compare task completion and wrong selections in realistic tasks.
Where the rule gets complicated
Keep the limits attached.
- There is no evidence-based four-to-seven-item rule here.
- Experts, familiar choices, unequal choice probabilities and search tasks change the situation.
- Do not hide necessary options merely to produce a shorter menu.
A named principle does not settle an accessibility requirement, prove a conversion lift or replace testing the particular interface.
Application and implementation boundaries
What the application check shows.
The example preserved keyboard selection and a labelled path to advanced options. We did not measure decision time or establish an ideal menu size.
Methods: Local application example. A completed check covers the stated sample; it is not a safety certification.
- Target
- Original IonBin synthetic interface example; no external product or human-participant study.
- Version or capture
- 2026-10-19 local fixture
- Integrity scope
- SHA-256 f85d1056afd667225a1e0364edfb8f25b4693ffa7b2b8c7d7af5b92338b85ee4 identifies the exact HTML fixture only.
Test conditions
- 155.0.8059.82 Chromium; fresh context with all network requests blocked.
- Synthetic inputs, memory-only state, reduced-motion preference, 1280px and 320px viewports.
Individual checks and observations
Native choice
passLocal application example: Exercise the original local application fixture and inspect the resulting controls or DOM state.
Observed: Keyboard ArrowDown selected PDF and the visible label matched.
Advanced disclosure
passLocal application example: Exercise the original local application fixture and inspect the resulting controls or DOM state.
Observed: The advanced JSON/XML choices remained available through a labelled disclosure.
Security findings and boundaries
Review of the local example’s stated interaction boundaries; no backend, authentication, production permissions or external service was exercised.
Practical advice · caution
Keep consequential choices discoverable
Simplifying a menu must not bury privacy, cancellation or permission controls. Test wrong selections as well as speed.
Practical caveats
- Test category names with intended users; the fixture only establishes that the controls remained operable.
What remains untested
- This checks an authored application example, not the truth, effect size or generality of the named principle.
- No users, assistive-technology participants, physical devices or production task outcomes were evaluated.
Security limits
- The example has no real authorization or persistence layer; its UI behavior cannot establish the security of a deployed workflow.
Evaluation sources
- Hick, On the Rate of Gain of Information (1952)
Original choice-reaction research; publisher abstract reviewed.
Go to the source
Research and further reading.
- Hick, On the Rate of Gain of Information (1952)
Original choice-reaction research; publisher abstract reviewed.
Related questions
More on choices and navigation.
Design heuristic
Jakob's Law
Use familiar interaction patterns so people can spend their attention on the task.