Web Design Lab Guide

TL;DR: Hick’s Law states that decision time increases logarithmically with the number of options. Every additional choice adds cognitive load and delays user action. Smart designers reduce options, use progressive disclosure, and apply intelligent defaults to speed decisions and boost conversions. This guide shows exactly how.

The Restaurant Menu Problem

You’ve experienced this. You open a menu with 200 items spanning 12 pages. Chinese, Italian, Mexican, American—everything’s there.

And you freeze.

Ten minutes later, you’re still deciding. The abundance that should make choosing easier has made it harder. You end up ordering something familiar and safe, ignoring 95% of the options.

Or you just leave.

That’s Hick’s Law in action. And it’s killing conversions on your website right now.

What is Hick’s Law?

Hick’s Law (also called the Hick-Hyman Law) describes the relationship between the number of choices and the time required to make a decision.

The formula:

RT = a + b log₂(n)

Where:
RT = Reaction Time
a = baseline decision time (constant)
b = empirically derived constant
n = number of equally probable choices

Don’t worry about the math. Here’s what matters: Decision time doesn’t increase linearly with options—it increases logarithmically.

Double the choices? You more than double the decision time.

Psychologists William Edmund Hick and Ray Hyman discovered this in the 1950s through reaction time experiments. Participants had to press buttons corresponding to lights. With 2 lights, decisions were fast. With 10 lights, decisions slowed dramatically—but not proportionally.

The relationship followed a predictable logarithmic curve. This pattern holds across contexts: button pressing, menu selection, website navigation, checkout processes.

Why This Happens: The Psychology Behind the Math

Our brains didn’t evolve to compare 47 similar options. They evolved to make binary or ternary decisions: Fight or flee? This cave or that one? Eat this or not?

When faced with multiple options, your brain must:

Encode each option visually
Comprehend what each option means
Compare each option against every other option
Evaluate trade-offs between features
Predict outcomes of each choice
Commit to a decision

That’s exhausting. And it gets exponentially more exhausting with each additional option.

Working memory limitations compound the problem. We can hold roughly 7±2 items in working memory at once (Miller’s Law). Exceed that, and our brains start dropping information or refusing to process more.

With too many choices, users experience decision paralysis—the inability to commit to any option. The mental cost of choosing exceeds the perceived benefit, so they defer the decision indefinitely.

Or they just click back.

The Research: How Bad Is It Really?

The Jam Study (2000)

Psychologists Sheena Iyengar and Mark Lepper set up jam tasting booths at a grocery store:

Large selection: 24 jam varieties displayed
Small selection: 6 jam varieties displayed

Results shocked researchers:

Large selection (24 jams):

60% of shoppers stopped to sample
Only 3% made a purchase

Small selection (6 jams):

40% of shoppers stopped to sample
30% made a purchase

The small selection converted 10 times better despite attracting fewer initial browsers.

More choice didn’t increase sales. It killed them.

The 401(k) Study (2004)

Researchers analyzed retirement plan enrollment across 647 companies:

Plans with 2 options: 75% participation rate
Plans with 10+ options: 60% participation rate
Plans with 59 options: 35% participation rate

People literally sabotaged their financial futures because choosing felt too hard.

Netflix’s Button Test (2016)

Netflix tested button labels on their TV app:

“Play” (1 option concept)
“Play / More Info” (2 option concepts)
“Play / My List / More Info” (3 option concepts)

The single “Play” button increased engagement by 18% over the three-option version. Users wanted to watch shows, not decide how to engage with metadata.

Real-World Applications: Where Hick’s Law Matters Most

1. Navigation Menus: The 7-Item Rule

Bad navigation (17 items):

<nav class="overwhelming-menu">
  <a href="/home">Home</a>
  <a href="/about">About</a>
  <a href="/team">Team</a>
  <a href="/careers">Careers</a>
  <a href="/products">Products</a>
  <a href="/services">Services</a>
  <a href="/solutions">Solutions</a>
  <a href="/pricing">Pricing</a>
  <a href="/customers">Customers</a>
  <a href="/partners">Partners</a>
  <a href="/resources">Resources</a>
  <a href="/blog">Blog</a>
  <a href="/news">News</a>
  <a href="/events">Events</a>
  <a href="/support">Support</a>
  <a href="/faq">FAQ</a>
  <a href="/contact">Contact</a>
</nav>

Users scan this menu, get overwhelmed, and use the search bar instead. Or leave.

Good navigation (7 items):

<nav class="clear-menu">
  <a href="/products">Products</a>
  <a href="/solutions">Solutions</a>
  <a href="/pricing">Pricing</a>
  <a href="/resources">Resources</a>
  <a href="/about">Company</a>
  <a href="/support">Support</a>
  <a href="/contact">Contact</a>
</nav>

Seven items. Clear categories. Subcategories hidden until needed (progressive disclosure).

Real example: Apple’s main navigation has exactly 7 items: Mac, iPad, iPhone, Watch, TV, Music, Support. Dozens of products, but the top-level navigation respects cognitive limits.

2. E-commerce Filtering: Progressive Disclosure

Don’t show all 47 filter options at once. Reveal them progressively.

Bad approach:

<div class="all-filters-visible">
  <h3>Filters</h3>
  
  <div>Brand (23 options)</div>
  <div>Price Range (8 options)</div>
  <div>Color (16 options)</div>
  <div>Size (12 options)</div>
  <div>Material (9 options)</div>
  <div>Style (14 options)</div>
  <div>Rating (5 options)</div>
  <div>Availability (3 options)</div>
  <!-- 90+ total filter options visible -->
</div>

Good approach:

<div class="progressive-filters">
  <h3>Refine Your Search</h3>
  
  <!-- Start with most impactful filters -->
  <div class="filter-primary">
    <label>Category</label>
    <select>
      <option>Men's Shoes</option>
      <option>Women's Shoes</option>
      <option>Kids' Shoes</option>
    </select>
  </div>
  
  <div class="filter-primary">
    <label>Size</label>
    <select>
      <option>Select size</option>
      <!-- Only show sizes available in selected category -->
    </select>
  </div>
  
  <!-- Secondary filters collapsed by default -->
  <details class="filter-secondary">
    <summary>More Filters (8)</summary>
    <div class="filter-expanded">
      <!-- Additional filters revealed on demand -->
    </div>
  </details>
  
  <button class="clear-filters">Clear All</button>
</div>

Amazon masters this. They show 3-4 primary filters prominently, with additional filters hidden behind expandable sections. Users see manageable choices first, then drill down if needed.

3. Pricing Pages: The Three-Option Sweet Spot

Bad pricing (7 tiers):

<div class="too-many-plans">
  <div class="plan">Micro - $9/mo</div>
  <div class="plan">Starter - $19/mo</div>
  <div class="plan">Basic - $29/mo</div>
  <div class="plan">Standard - $49/mo</div>
  <div class="plan">Professional - $79/mo</div>
  <div class="plan">Business - $149/mo</div>
  <div class="plan">Enterprise - Custom</div>
</div>

Users spend minutes comparing similar tiers, get confused about differences, and often leave without choosing.

Good pricing (3 tiers):

<div class="clear-pricing">
  <div class="plan">
    <h3>Starter</h3>
    <p class="price">$19/month</p>
    <p class="description">For individuals and small teams</p>
    <ul>
      <li>Up to 5 users</li>
      <li>10 GB storage</li>
      <li>Email support</li>
    </ul>
  </div>
  
  <div class="plan featured">
    <span class="badge">Most Popular</span>
    <h3>Professional</h3>
    <p class="price">$49/month</p>
    <p class="description">For growing businesses</p>
    <ul>
      <li>Up to 20 users</li>
      <li>100 GB storage</li>
      <li>Priority support</li>
      <li>Advanced analytics</li>
      <li>API access</li>
    </ul>
  </div>
  
  <div class="plan">
    <h3>Enterprise</h3>
    <p class="price">Custom</p>
    <p class="description">For large organizations</p>
    <ul>
      <li>Unlimited users</li>
      <li>Unlimited storage</li>
      <li>Dedicated support</li>
      <li>Custom integrations</li>
      <li>SLA guarantee</li>
    </ul>
  </div>
</div>

Three clear tiers with obvious differentiation. Most users gravitate to the middle option (the “featured” tier, which you strategically want them to choose).

Real example: Basecamp simplified from 5 pricing tiers to 2 (Personal and Business). Conversion rate increased because the decision became binary instead of comparative.

4. Forms: One Question at a Time

Long forms trigger Hick’s Law by forcing users to evaluate all fields simultaneously.

Bad form (everything at once):

<form class="overwhelming-form">
  <input type="text" placeholder="First Name">
  <input type="text" placeholder="Last Name">
  <input type="email" placeholder="Email">
  <input type="tel" placeholder="Phone">
  <input type="text" placeholder="Company">
  <input type="text" placeholder="Job Title">
  <select><option>Industry</option></select>
  <select><option>Company Size</option></select>
  <select><option>Budget Range</option></select>
  <textarea placeholder="Tell us about your needs"></textarea>
  <input type="checkbox"> Subscribe to newsletter
  <input type="checkbox"> Accept terms
  <button>Submit</button>
</form>

Users see 12 fields and mentally calculate the time cost. Many abandon before starting.

Good form (progressive revelation):

<form class="stepped-form">
  <!-- Step 1: Basic info only -->
  <div class="form-step active">
    <h3>Let's start with your name</h3>
    <input type="text" placeholder="First Name" autofocus>
    <input type="text" placeholder="Last Name">
    <button>Next</button>
    <p class="progress">Step 1 of 3</p>
  </div>
  
  <!-- Step 2: Contact info -->
  <div class="form-step hidden">
    <h3>How can we reach you?</h3>
    <input type="email" placeholder="Email">
    <input type="tel" placeholder="Phone (optional)">
    <button>Next</button>
    <p class="progress">Step 2 of 3</p>
  </div>
  
  <!-- Step 3: Context -->
  <div class="form-step hidden">
    <h3>Tell us about your needs</h3>
    <textarea placeholder="What brings you here?"></textarea>
    <button>Get Started</button>
    <p class="progress">Step 3 of 3</p>
  </div>
</form>

Each step presents 1-2 simple decisions. Users commit to small actions progressively rather than facing the entire cognitive load upfront.

Result: Multi-step forms typically see 20-40% higher completion rates than equivalent single-page forms, despite requiring more clicks.

5. CTAs: One Primary Action Per Page

Every page should have one dominant call-to-action. Not three. Not five. One.

Bad CTA strategy:

<div class="competing-ctas">
  <button class="cta">Start Free Trial</button>
  <button class="cta">Schedule Demo</button>
  <button class="cta">Download Whitepaper</button>
  <button class="cta">Contact Sales</button>
  <button class="cta">View Pricing</button>
</div>

Five equally prominent CTAs create decision paralysis. Users don’t know which action you want them to take, so they take none.

Good CTA strategy:

<div class="clear-cta-hierarchy">
  <button class="cta-primary">Start Free Trial</button>
  
  <div class="cta-secondary">
    <a href="/demo">Schedule a demo</a>
    <span class="separator">or</span>
    <a href="/pricing">View pricing</a>
  </div>
</div>

One primary action (visually dominant). Secondary options available but clearly subordinate.

Real example: Slack’s homepage has one massive “TRY FOR FREE” button. Everything else is secondary. No confusion about what they want you to do.

Advanced Technique: Intelligent Defaults

You can’t always reduce options. Sometimes users need choice. The solution? Make the default choice do the heavy lifting.

Example: Software Installation

Bad (forces decision):

<div class="install-options">
  <h3>Choose Installation Type</h3>
  <label>
    <input type="radio" name="install">
    Minimal (500 MB)
  </label>
  <label>
    <input type="radio" name="install">
    Standard (2 GB)
  </label>
  <label>
    <input type="radio" name="install">
    Complete (5 GB)
  </label>
  <label>
    <input type="radio" name="install">
    Custom (specify components)
  </label>
</div>

No default selected. Users must research what each option means.

Good (smart default):

<div class="install-smart-default">
  <h3>Install Photoshop</h3>
  <label class="default-option">
    <input type="radio" name="install" checked>
    <strong>Recommended:</strong> Standard installation
    <span class="description">Includes most commonly used features (2 GB)</span>
  </label>
  
  <details>
    <summary>Advanced options</summary>
    <label>
      <input type="radio" name="install">
      Minimal (500 MB) - Core features only
    </label>
    <label>
      <input type="radio" name="install">
      Complete (5 GB) - Everything
    </label>
    <label>
      <input type="radio" name="install">
      Custom - Choose specific components
    </label>
  </details>
</div>

Most users accept the default and move on. Advanced users can still access other options, but they’re not forced to make a decision they’re not equipped to make.

Research finding: Approximately 95% of users stick with default options in most contexts. A good default eliminates decisions for the vast majority.

Categorization: When You Must Offer Many Options

Sometimes you can’t reduce the absolute number of options. E-commerce sites with 10,000 products can’t show just 5.

The solution: Categorization reduces effective choice count.

Instead of:

10,000 products shown at once

Use:

8 categories (user chooses 1)
12 subcategories per category (user chooses 1)
100 products per subcategory (filtered down)

Users never face 10,000 simultaneous choices. They make a series of small choices (8 → 12 → 100), each manageable.

Example: Restaurant Menu Categories

Bad menu structure:

130 items in alphabetical order:
- Appetizer 1
- Appetizer 2
- Burger 1
- Dessert 1
- Dessert 2
- Entree 1
...

Users must scan 130 items linearly.

Good menu structure:

6 categories (choose 1):
├─ Appetizers (8 items)
├─ Salads (6 items)
├─ Burgers (10 items)
├─ Entrees (15 items)
├─ Sides (8 items)
└─ Desserts (7 items)

Users first choose category (6 options), then item within category (6-15 options). Total cognitive load is dramatically lower despite identical product count.

Key principle: Hick’s Law applies to simultaneously evaluated choices. Sequential decisions don’t compound the same way.

Search as an Escape Valve

Even with perfect categorization, some users know exactly what they want. Give them a search bar.

<div class="nav-with-search">
  <nav>
    <!-- Traditional navigation for browsers -->
    <a href="/products">Products</a>
    <a href="/solutions">Solutions</a>
    <a href="/pricing">Pricing</a>
  </nav>
  
  <input 
    type="search" 
    placeholder="Search for anything"
    class="quick-escape"
  >
</div>

Search bypasses all navigation decisions. Users with clear intent get direct access; browsers still have structured navigation.

Amazon puts search front and center because they know users often arrive with specific intent. Why force them through category navigation?

Mobile Considerations: Hick’s Law on Small Screens

On mobile, Hick’s Law hits harder. Limited screen space means fewer options visible simultaneously, which helps. But thumb zones, tap targets, and scrolling add interaction costs.

Mobile Navigation: The Hamburger Debate

Three-item visible menu:

<nav class="mobile-minimal">
  <a href="/">Home</a>
  <a href="/products">Products</a>
  <a href="/contact">Contact</a>
</nav>

Three choices. Clear. But forces architects to prioritize ruthlessly.

Hamburger menu (☰):

<button class="hamburger-menu">☰ Menu</button>

<nav class="hidden-menu">
  <!-- 10+ items hidden until clicked -->
  <a href="/products">Products</a>
  <a href="/solutions">Solutions</a>
  <a href="/pricing">Pricing</a>
  <a href="/about">About</a>
  <a href="/blog">Blog</a>
  <a href="/support">Support</a>
  <a href="/contact">Contact</a>
</nav>

Hides complexity behind one button. Reduces initial choices to 1 (open menu or don’t), but then presents many options at once.

Best practice: Hybrid approach. Show 3-4 critical paths visibly; hide less critical options in hamburger menu.

<nav class="mobile-hybrid">
  <!-- Critical paths visible -->
  <a href="/products">Products</a>
  <a href="/pricing">Pricing</a>
  <button class="cta-mobile">Try Free</button>
  
  <!-- Everything else hidden -->
  <button class="more-menu">⋯ More</button>
</nav>

Users get quick access to primary actions without opening menus. Secondary options available but not cluttering the interface.

Measuring Hick’s Law Impact

How do you know if choice overload is hurting conversions?

Metrics to Track

Decision time:

// Track time between page load and CTA click
const pageLoadTime = performance.now();

document.querySelector('.cta').addEventListener('click', () => {
  const decisionTime = performance.now() - pageLoadTime;
  analytics.track('decision_time', { 
    duration: decisionTime,
    options_count: document.querySelectorAll('.option').length
  });
});

Long decision times suggest users are struggling to choose.

Abandonment rate: Track users who view options but don’t convert. High view-to-conversion drop-off indicates choice paralysis.

Click patterns: Heatmaps reveal whether users are clicking frantically between options (comparison paralysis) or clicking decisively (clear choice).

A/B test results: Test reduced choice versions against current implementation:

const variants = {
  control: { options: 12 },
  variant_a: { options: 6 },
  variant_b: { options: 3 }
};

// Track which converts better

Common Mistakes & How to Fix Them

Mistake 1: Confusing “More Options = Better”

Symptom: You keep adding options because “different users want different things.”

Fix: Most users want the same 2-3 things. Serve the majority first, hide edge cases.

Mistake 2: Equal Visual Weight for All Options

Symptom: All buttons look identical. No visual hierarchy signals importance.

/* Bad: Everything equally prominent */
.all-buttons {
  background: #0066cc;
  padding: 12px 24px;
  font-size: 16px;
  font-weight: 600;
}

/* Good: Clear hierarchy */
.cta-primary {
  background: #ff4500;
  padding: 16px 32px;
  font-size: 18px;
  font-weight: 700;
  box-shadow: 0 4px 6px rgba(0, 0, 0, 0.1);
}

.cta-secondary {
  background: transparent;
  padding: 12px 24px;
  font-size: 14px;
  font-weight: 500;
  border: 1px solid #ddd;
}

Fix: Make the most important option dramatically more prominent.

Mistake 3: Hidden Complexity Explosion

Symptom: Users click a category and get hit with 47 sub-options.

<!-- Bad: Overwhelming subcategories -->
<details>
  <summary>Products</summary>
  <div class="mega-menu">
    <!-- 47 product links suddenly appear -->
  </div>
</details>

Fix: Even within categories, limit options to 5-9. Use further subcategorization if needed.

Mistake 4: Ignoring Context

Symptom: You apply “reduce options” universally without considering user intent.

Reality: Emergency contexts require different approaches.

<!-- Good: Context-appropriate choices -->

<!-- High-stakes decision: Show all critical options -->
<div class="medical-emergency">
  <h2>What type of emergency?</h2>
  <button>Heart Attack</button>
  <button>Stroke</button>
  <button>Severe Bleeding</button>
  <button>Breathing Problem</button>
  <button>Poisoning</button>
  <!-- All options visible - speed matters more than paralysis -->
</div>

<!-- Low-stakes decision: Reduce options aggressively -->
<div class="newsletter-frequency">
  <h3>How often should we email you?</h3>
  <label>
    <input type="radio" name="freq" checked>
    Weekly digest (recommended)
  </label>
  <details>
    <summary>Other options</summary>
    <label><input type="radio" name="freq"> Daily</label>
    <label><input type="radio" name="freq"> Monthly</label>
  </details>
</div>

Fix: Match choice architecture to decision importance and user emotional state.

When to Violate Hick’s Law (Yes, Sometimes)

Hick’s Law isn’t absolute. Sometimes more options work better:

1. Expert Users

Power users want comprehensive options immediately available. They’re not making decisions—they’re executing known actions.

<!-- Good for experts: All tools visible -->
<div class="photoshop-toolbar">
  <!-- 30+ tools visible for instant access -->
  <!-- Experts know what they want -->
</div>

Solution: Offer “Advanced Mode” that reveals more options for power users while keeping simplified default for newcomers.

2. Comparison Shopping

When users explicitly want to compare options, hiding choices frustrates them.

<!-- Good for comparison: Side-by-side specs -->
<table class="comparison-table">
  <tr>
    <th>Feature</th>
    <th>Basic</th>
    <th>Pro</th>
    <th>Enterprise</th>
  </tr>
  <!-- Detailed comparison across all tiers -->
</table>

Users arrived specifically to compare. Give them comparison tools.

3. Creative Exploration

Some contexts reward browsing and discovery. Design portfolios, art galleries, recipe sites—users want serendipity, not efficiency.

<!-- Good for exploration: Rich visual browsing -->
<div class="portfolio-grid">
  <!-- 50+ projects displayed as thumbnails -->
  <!-- Users enjoy browsing, not deciding -->
</div>

Key difference: Exploration vs. Decision. Hick’s Law applies to decisions, not browsing.

Practical Implementation Checklist

Ready to reduce choice overload? Follow this checklist:

Navigation Audit:

[ ] Primary navigation has 7 or fewer items
[ ] Subcategories limited to 5-9 items each
[ ] One clear primary CTA per page
[ ] Search bar available for direct access

Forms:

[ ] Multi-step forms for 8+ fields
[ ] Each step asks 1-3 questions maximum
[ ] Progress indicator shows completion
[ ] Smart defaults selected where possible

Product Pages:

[ ] 3-5 primary product tiers
[ ] Clear visual hierarchy (featured option obvious)
[ ] Detailed comparisons hidden behind “Compare” link
[ ] Filters use progressive disclosure

CTAs:

[ ] One primary CTA (visually dominant)
[ ] Secondary options clearly subordinate
[ ] No more than 3 total action options
[ ] Mobile view maintains hierarchy

Decision Points:

[ ] Every major decision presents 3-7 options max
[ ] Options categorized if count exceeds 9
[ ] Defaults selected when appropriate
[ ] “Recommended” option highlighted

Tools & Resources

Heatmapping (to identify choice paralysis):

Hotjar
Crazy Egg
Microsoft Clarity

A/B Testing (to measure impact):

Google Optimize
Optimizely
VWO

User Testing (to observe decision-making):

UserTesting.com
Lookback
Maze

Analytics (to track decision time):

// Track time-to-decision
window.addEventListener('load', () => {
  const startTime = Date.now();
  
  document.querySelectorAll('.decision-point button').forEach(button => {
    button.addEventListener('click', () => {
      const decisionTime = Date.now() - startTime;
      gtag('event', 'decision_made', {
        'decision_time_seconds': Math.round(decisionTime / 1000),
        'option_chosen': button.textContent,
        'options_available': document.querySelectorAll('.decision-point button').length
      });
    });
  });
});

Real-World Case Studies

Case Study 1: Procter & Gamble’s Head & Shoulders

Before: 26 varieties of Head & Shoulders shampoo

Problem: Sales declining despite brand strength

Change: Reduced to 15 varieties

Result: 10% increase in sales

Fewer options made choosing easier. Customers were relieved, not disappointed.

Case Study 2: Golden Cat Corporation

Before: 10 varieties of cat litter

Change: Reduced to 6 varieties

Result: 87% sales increase

The paradox: offering less made them sell more.

Case Study 3: A Major Bank’s Credit Cards

Before: 55 different credit card options

Problem: Low application completion rates

Change: Reduced displayed options to 6 primary cards, with “See all cards” link for browsers

Result: 23% increase in completed applications

Most users chose from the 6 featured cards. Power users still found niche options via “See all.”

The Future: AI-Driven Choice Reduction

Coming soon: AI systems that personalize option sets based on user behavior, demographics, and predicted preferences.

Instead of showing everyone 30 options, show:

New users: 3 recommended options
Returning users: Last selected option + 2 alternatives
Power users: Full option set

Same product, different presentations based on user sophistication.

Ethical consideration: Transparency matters. Users should know why they’re seeing certain options and have access to full selection if desired.

Conclusion: Less Is More (Really)

Hick’s Law isn’t about dumbing down interfaces. It’s about respecting cognitive limits and removing unnecessary friction.

Every additional option you present:

Increases decision time logarithmically
Raises abandonment risk
Decreases user satisfaction
Reduces conversion rates

The solution isn’t always “fewer options”—it’s smarter choice architecture:

Progressive disclosure: Reveal options as needed
Smart defaults: Do the thinking for most users
Clear hierarchy: Make the best choice obvious
Categorization: Break large sets into manageable chunks
Search: Provide escape valve for intent-driven users

Key takeaways:

Decision time increases logarithmically with choices—not linearly
Limit primary options to 3-7 for best results
Use progressive disclosure to handle necessary complexity
One dominant CTA per page—no exceptions
Smart defaults eliminate 95% of decisions for most users
Test, measure, iterate—your users will tell you what works

Start today: Find your most complex decision point and simplify it. Measure before and after. You’ll be shocked how much improvement comes from simply removing options nobody wanted anyway.

Your users don’t want infinite choice. They want to accomplish their goals with minimum cognitive effort.

Give them fewer, better options. They’ll thank you with conversions.

Frequently Asked Questions

Q: What if users complain about lack of options?

They rarely do. In most cases, complaints come from internal stakeholders (“But what about users who want X?”). Real users are usually relieved by simplicity. A/B test to confirm.

Q: How do I decide which options to remove?

Use data: analytics show which options are actually chosen. Keep the top 70-80% of selections, hide or remove the rest. The Pareto Principle applies: 20% of options account for 80% of usage.

Q: Doesn’t this reduce user agency and control?

Not if you maintain access to full options via “Advanced” or “Show more” sections. You’re not removing choice—you’re removing cognitive load from the default experience while keeping advanced options accessible.

Q: What about power users who want all options immediately?

Provide a setting: “Simple view” (default) vs “Advanced view.” Let sophisticated users opt into complexity while protecting novices from it.

Q: Does Hick’s Law apply to physical products too?

Yes. The jam study, cat litter study, and numerous retail examples prove it works offline too. The psychology is identical.

Q: How do I convince stakeholders to remove options?

Run an A/B test. Data beats opinions. Show that the reduced-choice version converts better, and stakeholders will come around.

Q: Is there ever a case for more than 7 navigation items?

In mega-sites (Amazon, Wikipedia), yes. But even there, options are heavily categorized. The top-level navigation still respects the 7±2 rule.