UX Laws · Foundation
Hick's Law
More competing choices generally increase decision effort.
5 minute field note
Helps create
Faster decisions
Overview
Make the interface carry more of the effort.
Help people decide by clarifying priority, grouping related choices and revealing complexity when it becomes useful.
Human impact
Why it matters
More competing choices generally increase decision effort. When the interface does not account for this, people spend effort interpreting the product instead of completing the task. Applied with context, the principle supports faster decisions without removing meaningful choice or control.
Design hypothesis
If we apply Hick's Law to the decision point, people should reach faster decisions with less avoidable friction.
Mechanism
How it works
Notice where the task currently asks people to choices or navigation without enough support.
Help people decide by clarifying priority, grouping related choices and revealing complexity when it becomes useful.
Make the smallest change that should improve faster decisions, then compare the task before and after.
Interactive experiment
How do option count and grouping change decision effort?
Find “Team permissions”
Start the timer, then select the requested destination.
Workspace
Data
Account
Appearance
Turn the experiment into a decision
What happened
A visible primary path and meaningful groups reduce scanning compared with an undifferentiated list.
Why it happened
People can recognise a category and priority before comparing every individual option.
Where to apply it
Navigation, pricing, command menus, onboarding choices and dense settings.
How to validate it
Compare time to first correct choice, wrong selections and confidence using the same task and labels.
Decision guide
When to use it
Apply it
Practical checklist
Give the decision area one clear primary action.
Group alternatives under labels people already understand.
Show secondary choices only when their context is available.
Keep necessary choices visible and honestly comparable.
Watch for
Common mistakes
Hiding useful options inside an unlabeled overflow menu.
Splitting a simple decision into unnecessary screens.
Reducing option count while leaving labels ambiguous.
Accessibility considerations
Keep progressively disclosed controls keyboard reachable.
Communicate expanded and selected states programmatically.
Evidence plan
How to test it
Compare the decision, not the decoration.
Prototype the current and proposed decision point with the same content. Give representative people the same goal and compare time, errors, confidence and explanation quality.
Observe
Where choice, attention or memory effort changes and whether people still understand the consequences.
Decide
Use the version that supports faster decisions while preserving informed choice.
Use with judgment
Limits and trade-offs
Hick's Law is a decision lens, not a universal prescription. Context, frequency, expertise and consequence can change the right implementation.
Optimising only for faster decisions can create new costs elsewhere. Recheck access, comprehension, user control and business constraints together.
A polished prototype can still fail in real use. Validate consequential decisions with representative people and realistic content.
Design responsibly
Better outcomes must also be honest outcomes.
Use the principle to reduce avoidable effort, not to pressure people into a choice.
Keep price, risk, consent and irreversible consequences visible before commitment.
Record what evidence supports the decision and what remains an assumption.
Evidence
Sources and interpretation
Design principles are lenses, not automatic answers. Apply them in context and validate consequential decisions with users and accessibility testing.
Keep close
Key takeaways
More competing choices generally increase decision effort.
Give the decision area one clear primary action.
Use the version that supports faster decisions while preserving informed choice.