Hick’s Law: Structure Choice Without Hiding It
Make options comparable, explainable, and reversible instead of pretending fewer choices always means better UX.
Start with the moment where the interface asks too much.
The pricing page has nine cards. Each card has a confident name, a similar feature list, a similar price rhythm, and the same button. The visitor does not need fewer products as much as they need to understand the difference. The page is asking them to compare with no comparison system.
Decision friction grows when choices multiply without meaningful structure. The design task is not blind reduction; it is helping people compare, distinguish, and proceed without guessing.
Show the failure and the correction.
The lab uses controlled markup instead of raster text so the lesson stays legible, accessible, and easy to revise.
- The visitor comparesChoice becomes reading labor.
- A recommendation appearsThe recommendation feels like pressure, not help.
- Terms are simplified awayThe decision is faster but less informed.
- Choice quality improvesConfidence improves without hiding useful choice.
Group by audience or task
Let the visitor locate themselves before comparing details.
Make the useful path easier.
Choice count is not the only issue
Similarity, consequence, reversibility, and unclear labels can make three choices harder than ten well-structured ones.
Comparable difference matters
Plan names, feature order, constraints, and evidence should let a visitor explain why one option fits and another does not.
Reduction can become concealment
Moving rare details out of the primary view is useful; hiding material terms before commitment is not.
Turn critique into a usable rule.
Remove
Equal option cards
Every choice looks recommended because the visual system avoids prioritization.
Vague plan names
Labels sound appealing but do not reveal who should choose which path.
Hidden constraints
Terms, limits, or consequences move behind a disclosure that the visitor must remember to open.
Build
Group by audience or task
Let the visitor locate themselves before comparing details.
Make differences stable
Use repeated feature order and meaningful contrasts across options.
Offer reversible confidence
Where truthful, explain whether the visitor can change path without penalty.
Use it on a real page.
Ask participants to choose between the available options.
Have them name the meaningful difference.
Ask which option they eliminated first and why.
Ask what would make them change their mind.
Check whether terms and consequences were understood.
- Use explanation accuracy and confidence notes.
- People can decide and explain the decision accurately.
- People choose quickly but cannot distinguish options or miss material terms.
The rule should help the person making the next decision.
Business owner
Do not remove meaningful options just to make the page look simple.
Designer
Design the comparison structure before designing the cards.
Developer
Preserve terms, plan data, and accessibility semantics in comparison tables or cards.
Reviewer
Ask users to explain the difference between their choice and the nearest alternative.
Experts may need many visible controls, and some decisions are inherently complex. Removing information can make a choice faster while making the outcome worse.
Check the page, then answer the doubt.
- Options are grouped by meaningful criteria.
- Differences are comparable.
- Recommendations explain who they fit.
- Material terms are visible before commitment.
- Rare choices are findable.
- Changing direction is explained when relevant.
- Is reducing choices always better?
- No. Useful choices should remain available. The page should structure them so people can compare without guessing.
- Should pricing pages recommend a plan?
- Only when the recommendation is explainable and truthful for a clear audience or use case.
- How many options should a website show?
- As many as the decision requires, with enough structure for people to understand the differences.
Standards and research links support the factual parts of the rule. They do not replace original judgment on the page.
Use the rule on the page that matters.
Use this when the reader is likely comparing redesign, UX cleanup, or launch support.
Start a project