Chunking: Stop Making Visitors Remember the Interface
Group information around meaning so people can recognize context instead of holding the interface in memory.
Start with the moment where the interface asks too much.
A verification flow shows instructions, moves to the next screen, and then asks for an identifier, a formatting rule, and a code. The person goes back, loses the code, and starts over. The failure is not memory. The interface discarded useful context and then blamed the visitor for not carrying it.
Interfaces should organize information around meaning and task while keeping necessary context visible. Chunking is not a license to cite “seven plus or minus two” as a universal design limit.
Show the failure and the correction.
The lab uses controlled markup instead of raster text so the lesson stays legible, accessible, and easy to revise.
- Context disappearsRecall becomes part of the task.
- Cards multiplyThe interface looks cleaner but remains mentally heavy.
- Numbers are treated as decorationErrors and re-reading increase.
- Meaningful groups appearThe user recognizes instead of memorizes.
Carry context forward
Show summaries, selected values, and instructions where they are needed.
Make the useful path easier.
Remember, recognize, retrieve
For every required piece of information, ask whether the person must remember it, can recognize it on screen, or can retrieve it without losing work.
Labels make chunks real
A box is not a chunk unless the grouping has a meaningful label or task reason. Decorative cards can increase scanning work.
Use Miller carefully
Miller’s paper is often flattened into a universal item limit. The practical lesson is not “always make lists of seven”; it is to respect limited memory and use meaningful grouping.
Turn critique into a usable rule.
Remove
Memory handoff
The interface asks the user to carry details between steps instead of carrying them forward.
Decorative fragmentation
One coherent task is split into too many cards, each with its own heading and border.
Unlabeled complexity
Settings are grouped by layout convenience rather than task meaning.
Build
Carry context forward
Show summaries, selected values, and instructions where they are needed.
Group by task
Chunk details by what the person is trying to do, not by internal data structure.
Keep retrieval safe
Let people open needed information without losing input or place.
Use it on a real page.
Walk through the task from start to finish.
List every fact required later.
Mark whether each fact is remembered, recognized, or retrievable.
Trigger back/forward and error paths.
Check whether valid work and context survive.
- Use the memory-demand list and screenshots of context carry-forward.
- Important context stays visible or retrievable without reset.
- The user must memorize details that the interface already knows.
The rule should help the person making the next decision.
Business owner
Do not mistake fewer visible words for lower cognitive load.
Designer
Name the concept behind each group before drawing a container.
Developer
Preserve summaries and state across steps, especially in forms and account flows.
Reviewer
List every fact the user must remember from another part of the interface.
Too many groups can fragment one task. Chunking should reduce conceptual load, not turn every sentence into a separate panel.
Check the page, then answer the doubt.
- Groups have meaningful labels.
- Needed context travels through steps.
- Long identifiers are formatted for recognition.
- Summaries preserve decisions.
- Cards do not fragment a single task.
- Back, error, and retry paths preserve state.
- Is Miller’s 7±2 rule still valid for interface design?
- Do not use it as a quota. Use it as a reminder that memory is limited and grouping must be meaningful.
- Can an interface have too many groups?
- Yes. If grouping breaks one coherent task into scattered fragments, it adds load instead of reducing it.
- How does chunking reduce cognitive load?
- It lets people recognize meaningful units and keep context visible instead of remembering separate pieces.
Standards and research links support the factual parts of the rule. They do not replace original judgment on the page.
Use the rule on the page that matters.
Use this when the reader is ready to inspect their own page before asking for a rebuild.
Get the conversion checklist