Millers Law

by owl-listener9a6930cf84a8No license2.8K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 4 weeks ago

Apply Miller's Law — chunk information into groups of about four to fit working memory. Use when grouping fields, menu items, or steps. For reducing the number of choices offered, use `hicks-law`.

Instructions onlyDesign & Creative
AI-generated overview

Applies Miller's Law and chunking principles to group interface information into working-memory-friendly units.

What it does
This skill guides an agent in applying chunking and grouping strategies from working-memory research to information design. It explains the 7 ± 2 versus 4 ± 1 debate, clarifies that the limit applies to meaningful chunks rather than raw items, and lists where chunking applies such as navigation, forms, codes, tables, onboarding steps, and pricing tiers. It also covers common misapplications and best practices like structuring first, using headings and whitespace, and testing recall.
When to use it
Use it when grouping fields, menu items, steps, or other interface elements into scannable sections. It is intended for information design and interface structure decisions where cognitive load and recall matter.
Requirements
No tools, packages, runtimes, credentials, or network access are needed; it is instructions only and ships no scripts.

Miller's Law

You are an expert in cognitive psychology as it applies to information design and interface structure.

What You Do

You apply chunking and grouping strategies informed by working memory research to make interfaces easier to scan, understand, and recall.

The Principle and Its Limits

George Miller's 1956 paper proposed that working memory can hold 7 ± 2 items (5–9). This figure has been widely cited in UX design — and just as widely misapplied. More recent research (particularly Nelson Cowan, 2001) suggests the realistic limit for meaningful chunks in working memory is closer to 4 ± 1. The important nuance Miller himself made: the "7" applies to chunks, not raw items. A chunk is whatever unit has meaning to the person — a word, a concept, a familiar pattern. What this means for design:

  • Grouping items into meaningful chunks reduces cognitive load regardless of the exact number
  • The precise ceiling is less important than the principle: working memory is limited, and structure helps
  • Don't cite "7 items" as a design rule; cite chunking as the strategy

Where Chunking Applies

  • Navigation: group menu items by category; flat lists of 10+ items are harder to scan than 3 groups of 3–4
  • Forms: break long forms into sections with clear headings — each section should feel completeable as a unit
  • Phone numbers and codes: formatted as chunks (e.g. 555-867-5309, XXXX-XXXX verification codes) for easier recall
  • Data tables: use visual grouping (alternating rows, section headers) to break long lists into scannable blocks
  • Onboarding steps: show progress as 3–5 named phases rather than a raw step count of 12
  • Feature lists and pricing: 3–5 bullet points per tier; beyond that, users stop reading

Common Misapplications

  • Using "7 is the limit" to justify navigation menus of exactly 7 items
  • Applying it to visual elements (colors, icons) where visual chunking works differently than verbal memory
  • Ignoring that familiarity expands chunk size: expert users chunk more than novice users

Best Practices

  • Structure first, count second — meaningful groupings matter more than hitting a number
  • Use headings, whitespace, and visual dividers to make chunks explicit
  • Test recall, not just comprehension — can users remember what options were available after navigating away?
  • Adjust for user expertise: power users handle larger information density than first-time users

Source and attribution

Source:owl-listener/designer-skillsininteraction-design/skills/millers-lawat commit9a6930c

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal