Laws of UX
Chunking
Breaking information into small, meaningful groups makes it faster to scan, understand, and remember.
Where it comes from
The concept comes from George Miller's foundational 1956 work on memory, which showed that the mind handles information far better when individual items are grouped into larger meaningful units — 'chunks'. The term has since become a staple of both cognitive psychology and interface design.
Why it matters for your website
The brain processes information in discrete, manageable chunks — not as continuous streams. Chunking (drawing on Miller's foundational 1956 research) says that grouping related items into visually distinct units reduces cognitive load and dramatically speeds up scanning. The practical implication is structural: any time content exceeds four to five items, grouping, sectioning, and visual hierarchy aren't just aesthetic choices — they're the difference between content that can be processed and content that overwhelms.
A chunk is a unit of meaning, not just a visual cluster. The reason a grouped phone number, a sectioned form, or a categorised menu feels easier is that each group collapses into a single thing the mind can handle, rather than a string of separate items it has to track one by one.
On a page, chunking is what lets you present a lot without overwhelming. The content isn't reduced — it's organised so the visitor meets it a few groups at a time. Without that structure, even modest amounts of information read as a wall, and walls get skipped.
Wrong vs right
A long article published as one unbroken column of text with no subheadings, so the reader faces an undifferentiated wall.
The same article broken into sections with descriptive subheadings and short paragraphs, scannable in chunks.
A checkout that asks for fifteen fields in one flat list, with no grouping of shipping, billing, and payment.
The same fields chunked into labelled groups, so each step feels small and self-contained.
A navigation menu listing twenty items in a single run.
The items grouped under four or five clear category headings, so the menu can be scanned in two quick passes.
Understanding Chunking
Chunking is the practice of grouping individual pieces of information into small, meaningful units so the mind can process them more easily. It works because working memory handles a few chunks far more comfortably than many loose items — and a well-formed chunk counts as roughly one item, regardless of how much it contains. Reading a card number as four groups of four is the canonical example: identical information, dramatically easier to handle.
In interface terms, chunking is mostly a structural discipline. Subheadings, sections, cards, labelled groups, and visual hierarchy all break a mass of content into digestible units. The practical trigger is simple: whenever a set runs beyond about four or five items, grouping stops being decorative and starts being the thing that makes the content usable at all.
The key is that chunks should be meaningful, not arbitrary. Grouping by genuine relationships — topic, function, sequence — is what lets the user predict where to look and hold the structure in mind; grouping at random just adds visual noise. Chunking sits at the centre of a cluster of related ideas including Miller's Law, working memory, and scannability.
How Kweri checks it
Chunking is one of the more checkable structural principles, and Kweri assesses it directly: it looks at whether long runs of content — text, fields, options, links — are broken into grouped units with headings and sections, or presented as one undifferentiated block. It can reliably flag unchunked walls of content that are likely to overwhelm. What it can't fully judge is whether your chosen groupings are *meaningful* to your audience, so it pairs the structural check with a prompt to make sure the chunks reflect real relationships.
FAQ
What is chunking in UX design?
Chunking is grouping related pieces of information into small, meaningful units so they're easier to scan, understand, and remember. Examples include sectioning a form, formatting a long number into groups, and breaking text with subheadings.
Why does chunking make content easier to process?
Because working memory holds only a few units at once, and a chunk counts as roughly one unit no matter how much it contains. Grouping items lets people handle far more total information without overload.
When should I chunk content?
Whenever a set of items runs beyond about four or five, grouping starts to pay off. Long lists, multi-field forms, large menus, and unbroken text all benefit from being divided into labelled, meaningful chunks.
What makes a good chunk?
Meaning. Chunks should group items by a genuine relationship — topic, function, or sequence — so users can predict what's where. Arbitrary grouping adds visual structure without the comprehension benefit.
How is chunking related to Miller's Law?
Chunking is the technique; Miller's Law is the reason it works. Miller showed working memory is limited to a few items, and that grouping into chunks effectively expands how much can be handled at once.
Related principles
Working memory holds only a handful of items — chunk information to ease the load.
The brain has a limited processing budget — demand too much and performance collapses.
The brain's temporary active store holds only 4–7 chunks for 20–30 seconds — information users have to remember across steps will be forgotten unless the system carries it for them.
People scan web pages rather than read them — structure content so scanners still get the point.
Attribution & sources
Identified by George A. Miller (1956). Catalogued from Laws of UX (Jon Yablonski).
Rooted in Miller's 1956 memory research; popularised for designers by Jon Yablonski's Laws of UX.
See Chunking on your own site
Run a free Kweri audit — a plain-English review of your site’s speed, accessibility, SEO and design, ranked by what to fix first. No login, no jargon.
Run a free audit →