hicks-law

Reduce visible interface choices to minimize cognitive load.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/suwandre/my-opencode-config --skill hicks-law-suwandre
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hicks-law
Source: https://github.com/suwandre/my-opencode-config/tree/main/skills/hicks-law
Command: npx skills add https://github.com/suwandre/my-opencode-config --skill hicks-law-suwandre

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Minimizes cognitive load and speeds user decisions by reducing the number of visible choices in interfaces like menus, onboarding steps, and configuration flows.

Core Features & Use Cases

  • Guides design decisions to simplify options
  • Applicable to navigation, onboarding, forms, and feature exposure
  • Helps balance choice availability with user satisfaction and conversion

Quick Start

Audit a UI flow to count visible options and apply chunking or progressive disclosure to reduce choices to a sweet spot (4-7) and measure expected decision time.

Frequently Asked Questions about hicks-law

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce cognitive load in UX design by simplifying choices?

Hick's Law states that decision time increases logarithmically with the number of choices presented. The formula RT = a + b * log2(n+1) calculates expected reaction time, guiding UX designers to limit options for faster decisions.

What is the ideal number of menu items for navigation to speed up user decisions?

To simplify onboarding flows, reduce the number of visible steps and choices by applying chunking and progressive disclosure. This minimizes cognitive load and accelerates user completion rates by utilizing Hick's Law.

Does reducing options in forms and dashboards improve conversion rates?

Reducing options in forms and dashboards improves conversion rates by balancing choice availability with user satisfaction. Simplifying feature exposure minimizes cognitive load and speeds up decision time.

When should I not use progressive disclosure to limit choices in a user interface?

You should not use progressive disclosure to limit choices when users need immediate access to all options for complex configuration. Over-simplifying feature exposure can hinder expert users who require full dashboard visibility.