What you'll understand by the end of this lesson
- Why the brain processes and remembers grouped information far better than long undifferentiated lists
- How chunking reduces perceived complexity without removing any information
- How to apply chunking to forms, pricing tables, and multi-step processes
- How to audit a page for chunking failures
The principle in plain English
The human brain can hold roughly four to seven items in working memory at once. When it encounters more than that as an undifferentiated list, processing becomes effortful and recall degrades.
Chunking is the process of grouping individual items into meaningful clusters. Instead of remembering twelve separate pieces of information, the brain holds three groups of four — which is far easier. The total amount of information hasn't changed. The cognitive load of handling it has dropped significantly.
Psychologist George Miller described this in his 1956 paper as "the magical number seven, plus or minus two." Modern research suggests the number is closer to four, but the principle holds: grouping information into chunks dramatically expands how much the brain can process at once.
A simple example
You're given a ten-digit phone number to memorise: 07891234567.
As a single string of digits, this is almost impossible to remember reliably. But written as 07891 234 567, you now have three short chunks. You remember each chunk, and the whole number becomes manageable.
Nothing changed except the grouping. The brain's ability to handle the information changed dramatically.
Chunking long forms into sections
A checkout form that asks for name, email, phone, billing address, delivery address, card number, expiry, CVV, and discount code all on one page feels long and overwhelming — even if filling in each field takes only a few seconds.
Break the same form into three labelled steps:
- Your details (name, email, phone)
- Your address (billing and delivery)
- Payment (card number, expiry, CVV, discount)
The total number of fields hasn't changed. But each step feels short and completable. Users make micro-progress, which keeps motivation up. The perceived complexity of the task has shrunk considerably.
Multi-step forms convert better than equivalent single-page forms in most contexts — not because they're shorter, but because each step feels like a small accomplishment. The progress indicator ("Step 2 of 3") reinforces this by showing proximity to completion. Both effects come from chunking.
Chunking pricing features
SaaS pricing pages often list 15–25 features per plan. When these appear as an undifferentiated bullet list, visitors struggle to evaluate them — the list doesn't feel scannable.
Grouping the same features under category headers transforms the experience:
Collaboration
- Real-time editing
- Comment threads
- Guest access
Reporting
- Weekly digest emails
- Custom dashboards
- CSV export
The total feature count is identical. The categories allow the eye to find what it's looking for and allow the brain to process the list in segments rather than all at once.
Chunking complex processes
If a user needs to complete twelve steps to set up a new account, presenting all twelve at once is overwhelming. Grouping them into three phases of four steps changes the mental model entirely:
- Phase 1: Create your account (4 steps)
- Phase 2: Set up your workspace (4 steps)
- Phase 3: Invite your team (4 steps)
The user's goal at any point is to complete the current phase, not all twelve steps. Progress becomes visible at a granular level — finishing Phase 1 feels like an accomplishment even though the full setup isn't done.
Chunking can become chunking theatre if the groups are arbitrary. If you label five features "Collaboration" and they have nothing meaningful in common, the grouping adds visual structure but no cognitive benefit. Chunks need to be genuinely meaningful — the brain uses the category label to build a mental model, not just a visual landmark. Bad chunking is almost as confusing as no chunking.
The CRO audit
Look at your forms, pricing pages, and onboarding flows and ask:
1. Are your forms single-page or multi-step?
If a form has more than five or six fields and it's all on one page, test breaking it into labelled steps. Watch for changes in form completion rate and drop-off by step (which tells you where friction lives).
2. Are your feature lists grouped under meaningful categories?
If your pricing page lists 20 bullets per plan without subheadings, you're asking visitors to evaluate a wall of text. Add groupings that reflect what the visitor is trying to find: collaboration features, reporting features, integration features. The label does work.
3. Is your onboarding framed as phases rather than a single long task?
A progress bar that says "Step 4 of 12" is demoralising. "Step 1 of 3 — Account setup" is achievable. If your onboarding has more than five or six steps, consider whether those steps can be grouped into named phases.
A SaaS product's checkout flow has 9 fields on a single page. A CRO specialist recommends splitting it into 3 steps of 3 fields each. A developer pushes back, saying this adds more pages and friction. Who is right, and why?
You've seen how grouping information reduces cognitive load. Now — what about the format of information itself? Why do we remember pictures so much better than words, even when the words describe the same thing?