A dense but well-structured interface can beat a sparse but chaotic one

What it is

Low information density — not much on the screen — does not mean low load. A screen that's tightly packed but clearly grouped and hierarchically organized can carry less actual load than one that looks spacious but has vague grouping, leaving the user to work out the relationships between elements on their own. What sets load isn't how much information sits on a screen, but whether that information has already been organized into a structure the user can perceive directly, versus one they have to piece together themselves.

Why it happens

A dense but well-organized interface keeps load manageable because clear grouping, alignment, and hierarchy let the perceptual system treat what would otherwise be many separate data points as a handful of chunks — the number of units that actually need to be held in mind and processed one at a time is much smaller than the raw element count suggests. A sparse but chaotic interface works the opposite way: even with few visible elements, if grouping is vague and there's no visual sense of what belongs with what, the user can't pre-package the information perceptually and has to identify each piece separately, working out in their head which items belong together — this act of "finding the structure yourself" consumes cognitive resources on its own, raising load largely independent of the raw element count. The pattern becomes sharper when information is split even further apart — say, content meant to be viewed together ends up on different screens or pages — because the user then has to find the structure themselves and hold the earlier content in working memory with the previous screen out of sight, retrieving it later to make a judgment once the next screen appears, which draws further on working memory's limited capacity and retention time.

Studying it

A common approach organizes the same information content into two presentations — "densely packed with clear grouping" and "sparsely spaced with vague grouping" — and has participants complete a task requiring comparison or integrated judgment across information points, comparing completion time and error rate between the two.

Common independent variables: clarity of grouping within a single screen, density of information presentation. Common dependent variables: completion time and error rate on cross-information comparison tasks, subjective load ratings.

This comparison is often used in HCI to check whether a redesign that "looks cleaner" actually reduces load, or merely shifts the load from visual presentation onto the user's own effort to organize structure.

Methodological note: the key is not counting elements or measuring whitespace area, but whether task performance drops due to muddled grouping; judging "this version looks tidier" by eye alone easily leads to the wrong conclusion.

Where it stops holding

• The load advantage of a dense-but-organized interface has a ceiling: once the number of chunks on a single screen exceeds what a user can hold at once, density itself becomes a source of load again — content can't be packed onto one screen without limit.
• If a task doesn't require comparison across elements (each information point is processed independently), the extra load from sparse layout is much smaller; this entry addresses the case where integrated or comparative judgment is required.
• This entry addresses the interaction between density and structural organization; it does not address how many screens content should be split across or how to handle context that has already disappeared across screens — that mechanism is closer to a working-memory-capacity question.

Applying it

• For tasks requiring comparison or judgment across multiple information points, prioritize organizing related information within a single visible area, using clear grouping and hierarchy — even if that makes a screen look "denser" — rather than forcing whitespace that leaves the user to work out the relationships themselves.
• When reviewing a redesign that "looks cleaner," check whether the simplification compressed element count or compressed grouping structure. If grouping structure was weakened (relying on spacing alone instead of explicit containers or headings), load may rise even as element count falls.
• Verification: have users complete a cross-information comparison task on both versions and record completion time, error rate, and subjective load ratings. If the sparser version performs worse, the "whitespace" didn't buy lower load — it just relocated the burden.

Related

• Same group: A9.05.1 Element count is not cognitive load · A9.05.3 Hiding structure behind a simplified appearance raises load · A9.05.4 Objective structural complexity and subjective perceived complexity don't always track together, and can vary independently · A9.05.5 Visual complexity metrics correlate weakly with actual cognitive load · A9.05.6 Inconsistency across screens compounds complexity beyond the simple sum of each screen's own complexity · A9.05.7 A more aesthetically pleasing interface is often misjudged as easier to use, masking real differences in load
• Nearby: A6.02 Working memory capacity (including A6.02.3, requiring users to remember content across pages is a design flaw)
• Search terms: chunking · information density · perceptual grouping · working memory