UX Laws · Foundation
Miller's Law
Working memory has limited capacity and benefits from structure.
5 minute field note
Helps create
Lower memory load
Overview
Make the interface carry more of the effort.
Reduce unnecessary memory work through meaningful chunks, visible context and recognition-based choices.
Human impact
Why it matters
Working memory has limited capacity and benefits from structure. When the interface does not account for this, people spend effort interpreting the product instead of completing the task. Applied with context, the principle supports lower memory load without removing meaningful choice or control.
Design hypothesis
If we apply Miller's Law to the decision point, people should reach lower memory load with less avoidable friction.
Mechanism
How it works
Notice where the task currently asks people to working memory or chunking without enough support.
Reduce unnecessary memory work through meaningful chunks, visible context and recognition-based choices.
Make the smallest change that should improve lower memory load, then compare the task before and after.
Interactive experiment
What changes when important context remains visible?
Your workspace verification code is
7K4-P9
Turn the experiment into a decision
What happened
Keeping reference information beside the task removes the need to remember an arbitrary sequence.
Why it happened
Recognition uses visible cues while recall depends on limited working memory.
Where to apply it
Verification codes, multi-step forms, comparisons, setup instructions and complex data entry.
How to validate it
Compare completion, transcription errors and perceived effort with and without persistent context.
Decision guide
When to use it
Apply it
Practical checklist
Group information by meaning rather than arbitrary count.
Keep instructions visible while they are needed.
Show progress and previously entered information.
Prefer recognition over memorised commands.
Watch for
Common mistakes
Treating seven items as a universal interface limit.
Creating chunks that do not match the user’s task.
Hiding context in the name of visual simplicity.
Accessibility considerations
Use persistent labels and descriptive headings.
Avoid memory-dependent time limits and error recovery.
Evidence plan
How to test it
Compare the decision, not the decoration.
Prototype the current and proposed decision point with the same content. Give representative people the same goal and compare time, errors, confidence and explanation quality.
Observe
Where choice, attention or memory effort changes and whether people still understand the consequences.
Decide
Use the version that supports lower memory load while preserving informed choice.
Use with judgment
Limits and trade-offs
Miller's Law is a decision lens, not a universal prescription. Context, frequency, expertise and consequence can change the right implementation.
Optimising only for lower memory load can create new costs elsewhere. Recheck access, comprehension, user control and business constraints together.
A polished prototype can still fail in real use. Validate consequential decisions with representative people and realistic content.
Design responsibly
Better outcomes must also be honest outcomes.
Use the principle to reduce avoidable effort, not to pressure people into a choice.
Keep price, risk, consent and irreversible consequences visible before commitment.
Record what evidence supports the decision and what remains an assumption.
Evidence
Sources and interpretation
Design principles are lenses, not automatic answers. Apply them in context and validate consequential decisions with users and accessibility testing.
Keep close
Key takeaways
Working memory has limited capacity and benefits from structure.
Group information by meaning rather than arbitrary count.
Use the version that supports lower memory load while preserving informed choice.