Back to Glossary

Miller’s Law

Synonyms: The magical number seven, 7±2 rule, memory span limit, working memory capacity, short-term memory limit

Do not index

Definition

Miller’s Law says the average person can keep about 7 (plus or minus 2) items in working memory at once. It comes from George Miller’s 1956 paper, which opens with him admitting he’s been “persecuted by an integer.”
The part designers can use is chunking. People remember more when small bits are grouped into bigger, meaningful units. A phone number in 3 groups is easier to recall than 10 loose digits.
 

Use cases

Overload working memory and users forget things halfway through a task. They scroll back, re-read, guess, then quit. They’re also juggling 3 tabs and a Slack ping while they do it.
Examples:
  • The 7-link nav myth: A team cuts the menu to exactly 7 links “because Miller’s Law” and hides pages people need. Menus stay on screen while users scan them, so their length barely touches memory.
  • Disappearing codes: A booking code shows on one screen and gets asked for on the next. Users have to carry 6 to 8 random characters across a page change, and typos follow.
  • Unbroken card fields: Baymard saw users struggle to type 15 to 16 straight digits without a mistake. One typo means a validation error at the worst moment.
 

How it's used in practice

  • Auto-format long strings: Split card, phone, and IBAN fields into groups (4-4-4-4 for most cards, 4-6-5 for Amex).
  • Section long forms: Group fields under labels like Contact, Shipping, and Payment so users deal with one set at a time.
  • Carry details forward: Keep the order total, chosen plan, or code visible on later steps.
  • Test recall: In usability tests, ask what users picked 2 screens back. If they can’t say, the flow is too heavy.
🪄
Count only what users have to hold after it leaves the screen. A 20-link footer stays visible, so it costs almost nothing. A 6-digit code that vanishes on the next step costs all 6 digits.
 

Challenges & limitations

  • The number gets abused: “7±2” gets quoted as a hard cap for tabs, menus, and slides. Miller studied recall after brief exposure, and most UI tasks don’t work that way.
  • Chunks are personal: A developer reads “API-KEY-V2” as 1 chunk. A new user sees 9 random characters. Stress and multitasking shrink capacity too.
  • Hard to measure: No analytics tool tracks working memory. You have to read it from errors, drop-offs, and back-button use.
 

Free resources

Share this post

Get free UX resources

Get portfolio templates, list of job boards, UX step-by-step guides, and more.

Download for FREE
 
 

The best email 📮 for growing 🌱 designers

Honest notes about the work behind the work. Read in 2 minutes, weekly. Free forever.
 
 
     
    notion image
    Join 13,045 designers and get tactics, hacks, and tips.