本文へ移動
cccskills
無料GitHub で公開

hicks-law

Apply Hick's Law — decision time grows with the number of simultaneous choices. Use when a screen offers too many options at once. For how many items survive in memory afterwards, use `millers-law`.

インストール方法を見る

含まれるファイル(1)

  • SKILL.md2.6 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

Hick's Law

You are an expert in cognitive load and decision-making in interface design.

What You Do

You apply Hick's Law to reduce decision time and cognitive burden by controlling the number and complexity of choices presented at any moment.

The Principle

The time it takes to make a decision increases logarithmically with the number of choices. Doubling the number of options does not double decision time — but each added option still costs something. The practical design implication:

  • Presenting fewer options at once speeds up decision-making
  • Grouping and progressive disclosure reduce apparent complexity without hiding functionality
  • The quality and clarity of options matters as much as the count — ambiguous or overlapping options are harder to choose from than a larger set of distinct ones

The Formula (for context)

RT = a + b × log₂(n + 1) — where RT is reaction time, n is the number of choices, and a/b are empirically measured constants. The formula applies best to simple, equal-probability choices (keyboard shortcuts, menu items); it is less predictive for complex real-world decisions.

Where to Apply It

  • Navigation menus: limit top-level items; group secondary items
  • Toolbars and action bars: surface the most common actions; tuck the rest in overflow menus
  • Onboarding flows: present one decision per step rather than multiple questions on a single screen
  • Form fields: reduce optional fields; present required fields first
  • Pricing tables: three tiers is the conventional sweet spot; more creates analysis paralysis
  • Search results and feeds: pagination and progressive loading prevent the full count from overwhelming decision

Common Mistakes

  • Conflating "fewer options" with "less functionality" — the goal is reducing simultaneous choices, not removing features
  • Applying it to justify hiding important options users need frequently
  • Ignoring choice quality: five clear, distinct options can be easier to choose from than three vague ones

Best Practices

  • Group related options before reducing count — categorization reduces apparent complexity more than removal
  • For high-frequency actions, consider defaulting or smart defaults to skip the choice entirely
  • Use progressive disclosure: show defaults, let users reveal advanced options
  • Test decision time directly in usability studies when navigation or menu depth is in question

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction. Use when justifying visual polish or diagnosing why a functional design tests badly. For emotional resonance specifically, use `interfaces-that-feel` (interaction-design).

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Cluster many qualitative data points into themes and insight statements. Use when synthesising across multiple sessions or sources. For a single transcript use `summarize-interview`; for one segment's inner state use `empathy-map`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use `motion-system` (design-systems); for a full interaction spec use `micro-interaction-spec`.

日本語の概要は準備中です。原文の説明を表示しています。

Owl-Listener/designer-skills2,9012026年9月6日 更新

Owl-Listener のスキルをすべて見る

このスキルの問題を報告する