Made with 🧠 and πŸ«€ by Youssef Bouksim

Back to library
🧩

Miller's Law

The average person can hold only 7 (plus or minus 2) items in working memory at once. Go beyond that limit and things start to fall through the cracks.

5 min readUX Β· Product Β· AI

In 1956, psychologist George Miller published a landmark paper titled β€œThe Magical Number Seven, Plus or Minus Two.” He had noticed something consistent across dozens of experiments: when people were asked to hold items in short-term memory β€” numbers, letters, words, tones β€” performance reliably fell off a cliff at around seven items. Below seven, recall was near-perfect. Above it, things disappeared.

The implication for design is straightforward and unavoidable: every time you present more than seven things at once without grouping or structure, you are asking users to hold more than working memory can reliably contain. Some of it will drop. The question is which part β€” and in a form, a navigation, or an AI response, that's rarely the part you'd choose.

✦ Key takeaways
βœ“
The limit is on chunks, not items. Miller's insight was that grouping items into meaningful chunks effectively expands capacity. A phone number formatted as 555-867-5309 is three chunks; the same digits as 5558675309 are ten items. Same information, radically different cognitive cost.
βœ“
Seven is a ceiling, not a target. More recent research suggests the practical limit is closer to four chunks. Using seven as your limit is already pushing it β€” for complex tasks or anxious users, four is a safer number to design around.
βœ“
Structure converts items into chunks. A list of fourteen bullet points is fourteen items. The same fourteen points organised under three headings becomes three chunks with sub-items β€” well within working memory's capacity.

The experiment behind the number

Miller ran participants through a series of tasks involving sequences of digits, letters, and words presented at speed. He wasn't studying how much people could memorise β€” he was studying something more precise: the channel capacity of human short-term cognition. At what point does information simply not get processed?

The answer, replicated across many conditions, was consistently around seven. But Miller's more important observation was that this limit applied to chunks of information, not to raw data. A trained musician can hold a complex chord in working memory as a single chunk. A novice holds each note separately. The capacity is the same β€” what differs is the chunking ability of the person and, crucially for designers, how the interface structures the information before it reaches the user.

7 Β± 2 chunks
Working memory holds roughly 7 items (range: 5–9).
Recent research (Cowan, 2001) suggests 4 chunks is more realistic for complex tasks.

The key insight: the limit is on chunks, not raw items. Structure determines chunk size.
β€œThe span of absolute judgement and the span of immediate memory impose severe limitations on the amount of information we can receive, process, and remember.”
β€” George Miller, 1956

Credit card numbers β€” chunking as standard practice

The 16-digit credit card number is one of the oldest and most universal chunking problems in interface design. As a flat string of digits, it requires users to hold all 16 in working memory to spot an error, verify what they've entered, or match it against their physical card. As four groups of four, it requires holding four chunks β€” well within Miller's limit β€” and aligns with how the number is physically printed on the card.

Every major payment processor, bank, and e-commerce platform chunks card numbers into four groups. This isn't a visual preference β€” it's a direct application of Miller's Law that reduces transcription errors and lets users visually verify their entry at a glance.

Before β€” 16 digits, no grouping
9:41
Add card
Card number
1234567890123456
Expiry
CVC
Cardholder name
Secured by 256-bit encryption

16 raw digits in one field. No structure to verify against.

After β€” 4 groups of 4 digits
9:41
Add card
Card number
1234567890123456
Expiry
CVC
Cardholder name
Secured by 256-bit encryption

4 chunks of 4 digits. Matches the physical card. Errors jump out instantly.

The chunked version does something the flat version cannot: it lets users verify each group of four independently against their physical card. Instead of a single 16-item memory task, the verification becomes four 4-item tasks β€” each well within working memory's reliable range. Error rates drop, and so does the anxiety of entering a number that controls access to money.


Navigation β€” when every section gets its own tab

Navigation bars are where Miller's Law violations accumulate quietly over time. A product launches with five sections. A new team adds two more. A feature request brings another. Three years later, the nav bar has eleven items and every one of them is labelled as primary navigation β€” which means none of them are.

Eleven options in a navigation bar are eleven items held in working memory simultaneously just to orient to a page. Five primary options with the remainder grouped under a β€œMore” or section menu reduces that to five β€” plus the knowledge that more exists. Users can find what they need faster because the cognitive map of the navigation is simpler.

Before β€” 11 items, all equal weight
yourapp.com/dashboard
Appname
Dashboard
Analytics
Reports
Customers
Products
Orders
Campaigns
Integrations
Billing
Settings
Help
Dashboard
Welcome back β€” here's what's happening
Revenue
$48,200
this month
Orders
1,506
this month
Customers
24,821
total

Every section gets its own tab. Users must scan all 11 to find what they need.

After β€” 5 primary + grouped overflow
yourapp.com/dashboard
Appname
Dashboard
Analytics
Customers
Orders
Products
More
Dashboard
Welcome back β€” here's what's happening
Revenue
$48,200
this month
Orders
1,506
this month
Customers
24,821
total

5 primary items plus a β€œMore” dropdown. Same sections, simpler cognitive map.

The sections haven't disappeared from the good navigation β€” Reports, Campaigns, Integrations, Billing, Settings, and Help are all still accessible under β€œMore.” The difference is that the primary navigation now represents a single chunk of five items rather than eleven individual items. Users build a mental model of the product faster and navigate more confidently because the structure respects working memory's limits.


AI responses β€” structure is not decoration, it's chunking

One of the most consistent cognitive load failures in AI-generated content is the flat bullet list. When a model responds with fourteen bullets in a single undifferentiated list, it is presenting fourteen items to working memory simultaneously. Users must scan the entire list before they can begin to identify what's relevant, group related items mentally, and retain what they've read.

The same information organised under three labelled headings becomes three chunks. Each section is a group with a clear label β€” the label itself tells users whether they need to read the items beneath it before they start reading them.

Before β€” 14 flat bullets
9:41
AI Assistant
How do I improve my app's user retention?
Here are some ways to improve user retention:
  • β€’Send personalised push notifications
  • β€’Add a daily streak mechanic
  • β€’Improve onboarding flow
  • β€’Reduce time to first value
  • β€’Add progress indicators
  • β€’Create a loyalty rewards programme
  • β€’Use re-engagement email campaigns
  • β€’Identify and fix drop-off points in analytics
  • β€’Add social features or community
  • β€’Offer personalised content recommendations
  • β€’Make the app faster and more reliable
  • β€’Introduce premium features via trial
  • β€’Allow offline access to key features
  • β€’Collect and act on NPS feedback
Follow up...

14 items, no structure. Working memory fills before you reach the end.

After β€” 3 labelled sections
9:41
AI Assistant
How do I improve my app's user retention?
Here are 14 strategies, grouped by where in the journey they apply:
Onboarding
  • β€’Improve onboarding flow
  • β€’Reduce time to first value
  • β€’Add progress indicators
  • β€’Introduce premium features via trial
Engagement
  • β€’Send personalised push notifications
  • β€’Add a daily streak mechanic
  • β€’Create a loyalty rewards programme
  • β€’Add social features or community
  • β€’Offer personalised content recommendations
Recovery & quality
  • β€’Use re-engagement email campaigns
  • β€’Identify and fix drop-off points
  • β€’Make the app faster and more reliable
  • β€’Allow offline access to key features
  • β€’Collect and act on NPS feedback
Follow up...

3 sections of 4–5 items. The label tells you whether to read the group. Same 14 points β€” completely different cognitive cost.

This is why prompting an AI to β€œorganise your response into sections” consistently produces more usable output than asking for a list. The model contains the same information either way. The structure determines whether working memory can process it. Good AI interfaces are beginning to apply this automatically β€” recognising response length and complexity, and grouping output into labelled sections before presenting it. This is Miller's Law applied at the level of content generation, not just interface layout.


Applying this to your work

Miller's Law offers a clear diagnostic question for any interface: how many separate items is the user holding in working memory at this moment? If the answer is more than five to seven, the design is doing cognitive work that it should be doing for the user. Grouping, chunking, progressive disclosure, and visual hierarchy all have the same effect: they reduce the number of things the brain must hold simultaneously, freeing capacity for the task itself.

βœ“ Apply it like this
β†’Chunk numerical inputs -- card numbers, phone numbers, sort codes, account numbers -- into groups of 3-4 digits.
β†’Limit primary navigation to 5 items. Everything beyond that belongs in a grouped secondary menu, not on the top bar.
β†’Structure long AI responses and content into labelled sections of 4-5 items rather than flat lists of 12+.
β†’When you can't reduce the number of items, group them -- three groups of four is always easier than twelve individual items.
βœ— Common mistakes
β†’Single-field inputs for long numerical strings -- raw 16-digit card numbers, phone numbers without formatting, IBAN codes.
β†’Navigation bars that accumulate items over time with no pruning -- every new feature gets its own tab until the bar has 11 entries.
β†’Flat bullet lists in AI responses -- presenting 14 points without structure forces users to do the grouping mentally while reading.
β†’Treating seven as a comfortable target rather than a hard ceiling -- for cognitively demanding tasks, four is the safer number.