Miller’s Law
Working memory is limited, and meaningful grouping changes how much information people can handle.
Seven is not a universal menu limit. The real lesson is to stop designing memory tests.
A verification code arrives on one screen and must be entered on another. Every switch between apps risks losing a digit. Showing the code above the field or supporting autofill removes a memory task that never needed to exist.
Origin
Miller's 1956 paper discussed limits across several information-processing tasks and introduced chunks. Later work, including Cowan's 2001 review, argued for a smaller capacity under restricted conditions.
Do not turn seven plus or minus two into a component rule. The original paper did not establish a universal limit for navigation or interface elements.
Keep instructions, codes, and comparison details visible at the point of use. Recognition is safer than carrying arbitrary information in memory.
Group information into units people understand. A chunk helps only when the relationship is meaningful to the person using it.
Design for different levels of expertise. An expert may recognize one familiar pattern where a newcomer still sees many separate details.
Digital systems
A visible verification code
The product supports one-time-code autofill or keeps the code visible while the field is active. The person can verify the value instead of memorizing and retyping it.
Physical signals
A written shopping list
The list moves items out of memory and into the environment. Grouping them by aisle can further reduce repeated searching inside the store.
Important details disappear between steps, leaving people to hold codes, rules, or comparisons while they complete another action.
Keep task-relevant information visible, group it meaningfully, and remove transfers that depend on short-term recall.