Dr. Wallace's Favorite Mental Models

Miller's Law

Your working memory can only hold about four to seven meaningful "chunks" at once. Group information well, and people can handle far more than they could item by item.

Cognitive Psychology Communication & UX George A. Miller, 1956

130-Second Overview

In 1956, psychologist George A. Miller published a paper that became one of the most cited in cognitive psychology: "The Magical Number Seven, Plus or Minus Two." His finding, in plain terms: people can hold roughly seven items in short-term memory at once, give or take two. Try to hand someone ten unrelated facts in a row and most of them will fall out before they can use any of them.

The twist that makes this useful isn't the number itself. It's what Miller called chunking. Memory isn't limited by how many individual facts you present. It's limited by how many meaningful groups you present. Group ten digits into three or four chunks, and suddenly all ten fit. This is why phone numbers are written as 555-0183 and not 5550183, and why a good presentation has three main points instead of eleven.

Core claim
Working memory holds about 4 to 7 chunks at a time, not 4 to 7 individual facts.
The lever
Chunking: group related items so they count as one unit instead of several.
Where it shows up
Menus, forms, onboarding, slide decks, phone numbers, checklists, teaching.
One-line test
If someone has to remember your list to act on it, could they repeat it back in five seconds?

2Mental Model Compass

This model is about the capacity limit of short-term memory and how chunking works around it. It is easy to confuse with two neighboring models, so the Compass routes you to the right one.

✓ Reach for Miller's Law when...

  • You're deciding how many items to put in a list, menu, or step sequence that someone has to hold in mind (not just scan once).
  • You're designing something people will recall later without looking it up: a phone script, a safety checklist, a mnemonic.
  • You want to know how to group information, not just how much to show.
Choosing between how many options to show someone who's deciding in the moment? That's Hick's Law (decision time rises with the number of choices). Designing a lesson or a complex interface where the issue is total cognitive effort, not just item count? That's Cognitive Load Theory. Miller's Law sits between them: it's specifically about the ceiling on what short-term memory can hold, and the chunking technique that raises that ceiling.

3Build the Idea, Step by Step

Click through the sequence below. Each step adds one layer, and the third one includes a live memory check so you can feel the effect rather than just read about it.

Step 1 — The original finding▸

Miller reviewed experiments on two different tasks: judging a stimulus along one dimension (like pitch) and recalling a list of items in order. Both tasks topped out around the same number: roughly seven, plus or minus two. He thought the overlap was interesting enough to name, but he was explicit that the number "seven" was not some magic constant of the mind. It was a rough empirical pattern, not a law of nature in the strict sense.

Step 2 — The real insight: chunks, not items▸

Here's the part people miss. Miller found that memory span barely changes whether each item is a single bit (yes/no) or something richer, like a whole word. What matters is the number of chunks, where a chunk is the largest meaningful unit the person already recognizes. A chess grandmaster sees a cluster of twelve pieces as "a known opening" — one chunk. A beginner sees twelve separate pieces. Same board, very different memory loads.

That means you can expand what someone can hold in mind without asking their brain to do anything new: you just repackage the information into fewer, bigger units.

Step 3 — Try it yourself: chunked vs. unchunked recall▸

You'll see a string of 10 digits for 4 seconds. Half the time it's shown as one unbroken string; half the time it's grouped into chunks. Then it disappears and you type what you remember. Run it a few times with each mode and compare how it feels.

Click a button above to start
Step 4 — Why this matters for later revisions of the number▸

Later researchers refined Miller's number. Nelson Cowan's 2001 review argued that when you strip out chunking and rehearsal tricks, raw working memory capacity is closer to four chunks for most adults. Other work found the span varies by material: around seven for digits, closer to five or six for unrelated words, and less for complex items. None of this overturns Miller's core point. If anything it strengthens it: the ceiling is tight, often closer to four than seven, which makes chunking even more valuable in practice, not less.

4Examples Across Domains

Telecom
Phone numbers. A 10-digit number is split into area code, prefix, and line number (555-123-4567) instead of one long string. Three or four chunks instead of ten digits.
Software / UX
Settings menus. A flat list of 25 preferences overwhelms. Grouped into 5 to 7 labeled sections (Account, Notifications, Privacy, Billing...), users scan and recall where things live.
Aviation
Pre-flight checklists. Pilots don't memorize 40 discrete checks. Checklists are chunked into phases (power-up, taxi, pre-takeoff), each a small, recallable unit even under stress.
Presentations
The "rule of three." Audiences retain a talk built around three main points far better than one with eleven scattered ones, even if the eleven-point version technically contains more information.
Retail
Store layout. Grocery stores group related items into aisles (baking, dairy, snacks) so shoppers can hold "where things are" as a handful of categories instead of hundreds of item locations.
Education
Vocabulary and mnemonics. Acronyms like ROY G. BIV compress seven colors into one recallable chunk. Teachers group new vocabulary into thematic clusters instead of alphabetical lists for the same reason.

5Common Mistakes

Treating "seven" as a hard rule. Miller's own point was that the number is approximate and task-dependent. Designing to exactly seven items regardless of context misreads the paper.
Confusing "fewer items on screen" with chunking. Chunking is about grouping and meaning, not just deletion. Cutting a 20-item menu to 7 items by removing content is different from organizing those 20 items into 5 labeled groups of 4.
Ignoring expertise. What counts as "one chunk" depends on the person's prior knowledge. A jargon-heavy chunk is still one chunk to an expert and seven overwhelming pieces to a novice.
Applying it to information that's always visible. If the user can simply look at a reference sheet or screen instead of holding it in memory, the chunk limit barely matters. The model is about recall, not recognition.
Using it to justify oversimplification. Chunking compresses presentation, not substance. Cutting real nuance to hit a round number trades clarity for memorability at the wrong price.

6When Not to Use It

When information will always be displayed for reference (a lookup table, a persistent dashboard) rather than recalled from memory.
When the bottleneck is decision speed among visible options, not memory capacity. Reach for Hick's Law instead.
When the task is about overall instructional difficulty and schema-building over time, not short-term item count. Reach for Cognitive Load Theory instead.
When chunking would hide dependencies between items that genuinely need to be seen together and separately (for example, regulatory disclosures where grouping could obscure a required individual notice).

7Related Models

1Worked Application: Fixing an Overloaded Onboarding Flow

The problem: An AI analytics product asks new users to configure 16 settings on one screen before they can see their first dashboard: data source, refresh rate, timezone, currency, default chart type, team roles, 4 notification toggles, 3 integration keys, export format, and 2 permission flags. Completion rate on this screen is 34%. Support tickets mention "didn't know where to start" and "forgot to come back and finish."

  1. Diagnose the symptom correctly. The problem looks like a UI clutter issue, but the actual failure is memory, not layout: users can't hold "16 unrelated things I need to handle" in mind long enough to act on all of them in one sitting.
  2. Count the true items, not the fields. 16 individual fields is well past the 4-7 chunk ceiling. Even generous estimates put this at double or triple the workable limit.
  3. Find the natural chunks already hiding in the list. Data source + refresh rate + timezone + currency = "Data basics." Default chart type = "Display preference." Team roles + 4 notification toggles = "Team & alerts." 3 integration keys = "Connections." Export format + 2 permission flags = "Governance." That's 16 fields collapsing into 5 meaningful groups.
  4. Name each chunk so it reads as one unit. A group labeled "Data basics" is remembered as one thing. The same four fields with no label are remembered as four things.
  5. Sequence the chunks, don't flatten them back together. Present one chunk per screen or one expandable section at a time, rather than 5 labeled boxes stacked on a single long page — stacking them back together partially undoes the benefit.
  6. Defer non-essential chunks. "Connections" and "Governance" aren't needed to see the first dashboard. Move them to a post-onboarding checklist the user can return to, reducing the immediate memory load to 3 chunks instead of 5.
  7. Test recall, not just completion. Ask a few users 30 seconds after finishing: "What did you just set up?" If they can name the chunks (Data basics, Display, Team & alerts) rather than a blur of fields, the regrouping worked.
  8. Ship and measure. Track completion rate on the first dashboard view, and track whether users return to finish the deferred chunks within a week, which validates that deferring didn't just mean "never."

Projected effect, based on how comparable onboarding redesigns typically move: completion on the first-dashboard step improves meaningfully once the real decision count per screen drops under roughly 5, even though the total information collected across the whole flow doesn't shrink at all.

2Try It Yourself

Paste a list you're currently asking someone to remember or choose from (a menu, a form, a set of instructions, talking points). Get back a tailored prompt you can hand to yourself or to an AI assistant to chunk it properly.

Your tailored prompt will appear here.
Copied!

1Save as Skill

Below is a portable, model-agnostic description of Miller's Law written so you (or an AI assistant) can apply it consistently to future work: menus, forms, slide decks, documentation, checklists, anything with a list someone has to hold in mind.

Copied!

2Apply to My Problem

Describe what you're designing, writing, or organizing. This generates a ready-to-use prompt that applies Miller's Law directly to your situation.

Your tailored "Apply to My Problem" prompt will appear here.
Copied!