Skip to content
cccskills
FreePublished on GitHub

millers-law

Organize forms, menus, and workflows into meaningful groups that are easier to scan, understand, and remember. Apply chunking, which combines related information into manageable units, using headings, spacing, and clear divisions.

OriginalShow the original description

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`.

Run score Not tested

See how to install

Good for

  • Dividing a long form into clear sections
  • Grouping menu items by category
  • Organizing onboarding into named phases
  • Making tables and feature lists easier to scan

Files included (1)

  • SKILL.md2.7 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

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

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

a-b-test-design

FreeSummary

Plan A/B experiments to measure the effect of a design change. Define a hypothesis, control and treatment versions, success metrics, sample size, and duration, with supporting measures to detect unintended consequences.

  • Planning a comparison between current and proposed designs
  • Defining success metrics for a change
  • Estimating sample size and test duration
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Assess an existing interface against WCAG 2.2 accessibility guidelines. Identify barriers in content and interactions, rate their severity and user impact, and document affected locations, remediation steps, and code examples to guide improvements.

  • Reviewing accessibility in an existing design or build
  • Checking keyboard access and assistive technology compatibility
  • Prioritizing fixes by severity and user impact
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Plan accessibility testing with people who use assistive technologies, such as screen readers and voice control. Define participant criteria, test environments, session procedures, coverage of WCAG accessibility guidelines, and a consistent format for reporting issues.

  • Planning test sessions with assistive technology users
  • Defining participant recruitment criteria
  • Mapping key user flows to test environments
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Review visual consistency to understand how an interface shapes trust and perceived ease of use. Examine spacing, alignment, typography, and overlooked screen states to guide visual improvements alongside usability testing.

  • Investigating poor feedback on a functional interface
  • Checking visual consistency before launch
  • Reviewing error, empty, and loading states
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

affinity-diagram

FreeSummary

Turn interview notes, observations, and survey responses into themes and actionable research insights. Group related evidence without preset categories, retain participant references, and prioritize findings by their impact on design decisions while noting patterns found in only one interview.

  • Synthesize findings across multiple interviews
  • Organize observation notes and survey responses
  • Prioritize research insights for design decisions
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

Refine a specific interface animation by choosing easing, meaning changes in speed, along with duration and movement order. Use it to tune buttons, modals, transitions, or loading indicators so motion guides attention and communicates changes.

  • Tune how a modal enters and exits
  • Adjust button and toggle animations
  • Coordinate the order of related movements
Owl-Listener/designer-skills3.1KUpdated Sep 6, 2026

See all skills by Owl-Listener

Report a problem with this skill