Miller's Law
Working memory holds a small number of chunks, so the design lever is what counts as a chunk, not the raw item count.
Definition
George Miller's 1956 paper reported that the span of immediate memory is limited to roughly seven chunks, plus or minus two, and that people expand effective capacity by grouping information into larger meaningful chunks rather than by holding more items.
Established research. Originates in published research and has been replicated. The effect is real. Its size in your product still needs measuring.
On this plate
Reach for this when
- Users must carry information across a step or screen boundary.
- Displaying long numeric strings or identifiers.
- Structuring dense forms, tables or settings.
Common mistakes
- Using the number seven as a design constraint.
- Grouping without labelling, which adds structure but no meaning.
- Forcing recall when the information could simply stay on screen.
- Quoting seven plus or minus two as a limit on menu items, which is not what the paper measured.
What is genuinely useful here
The durable insight is chunking. A ten-digit phone number is at the limit of memory as ten items and comfortably inside it as three chunks. The same restructuring works on interfaces: an eighteen-field form is unmanageable as a flat list and reasonable as five labelled groups.
The second insight is that working memory only binds on information the user must carry across a boundary. Anything visible on screen is not in working memory, it is in the environment. Interfaces reduce memory load mostly by keeping things visible, not by shortening lists.
Design moves that follow from chunking
- Format long numbers into groups: card numbers in fours, phone numbers by country convention, IBANs in fours.
- Group form fields into labelled fieldsets that map to real-world concepts, such as delivery address and payment.
- Keep the summary of a multi-step flow visible so the user never has to remember what they entered two steps ago.
- Show the query in a search results header, since the user should not have to recall what they typed.
- Split dense tables into logical column groups with a header spanning each group.
Applying it honestly
Do
- Reduce what has to be remembered across screens.
- Chunk by meaning, so the group has a name a user would recognise.
- Persist entered data when the user navigates back.
Do not
- Cap navigation or list length at seven for its own sake.
- Cite the paper as evidence for a specific item count.
- Assume chunking helps when the groups are arbitrary. An unlabelled group of four is not a chunk.
Chunking, applied to real inputs
The useful half of Miller is chunking. These are the groupings people already hold, which is why matching them reduces error.
| Input | Chunked as | Why |
|---|---|---|
| Card number | Four groups of four | Matches the printing on the card itself |
| One-time code | Three and three, or a boxed field per digit | Read from a message and held in memory across apps |
| Phone number | Local convention, not a global format | People recall their own number in their own rhythm |
| Long reference or IBAN | Groups of four, with the grouping preserved on copy | Checked character by character against another screen |
| Settings page | Five to seven per labelled section | Sections are scanned, not read, and the label is the chunk |
In practice
- i.
Card number entry
CheckoutAuto-formatting a card number into groups of four as the user types lets them verify against the physical card in four glances instead of sixteen, and reduces transposition errors.
- ii.
Grouped settings
Application settingsSixty settings under six named groups is navigable. The same sixty in one alphabetical list is not, even though the item count is identical.
- iii.
The code that arrived as one block
Cross-app memoryA six-digit code shown unchunked in a message and entered into a single unformatted field asks the reader to carry six items across an app switch. The same code as two groups of three costs two.
Commonly confused with
Close neighbours that get substituted for each other. The difference is stated first, then the condition that picks one over the other.
Hick's Law
LawDecision time rises with the number and complexity of the options presented.
Key difference
Hick's Law is about how long a choice takes when options increase. Miller's Law is about how much can be held in working memory, and is routinely misquoted as a limit on how many items a menu may hold.
Use Miller's Law when
- The reader has to carry something from one screen to the next.
- You are deciding how to chunk a code, number or instruction.
- The problem is recall, not selection.
Use Hick's Law when
- You are reasoning about how long a choice takes to make.
- The problem is an overloaded menu, filter set or pricing page.
- The fix is grouping, defaulting or staging the options.
Local chart
LAW·004 · Region I · Grid B2
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
- [1]
The magical number seven, plus or minus two
G. A. Miller, Psychological Review, 1956
- [2]
The magical number 4 in short-term memory
N. Cowan, Behavioral and Brain Sciences, 2001
Reassessment placing the capacity limit closer to four chunks.
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applies when you are designing
Why this works
The reasoning this entry rests on.
- Cognitive LoadPSY·001 · Psychology
- Decision FatiguePSY·010 · Psychology
Applied through
Where this shows up as a concrete interface decision.
- Information ArchitectureRES·015 · Research method
- ProximityFND·004 · UI foundation
- Visual HierarchyFND·001 · UI foundation
Check your work
Review passes that test whether this was done properly.
- Form UX ChecklistCHK·001 · Checklist
Short definition
The one-paragraph version, for when that is all you need.
- ChunkingTERM·008 · Term
- Cognitive LoadTERM·007 · Term
Related concept
Connected closely enough to change how you apply this.
- Recognition Over RecallHEUR·006 · Heuristic
- Serial Position EffectLAW·008 · Law
- Progressive DisclosurePRIN·003 · Principle