Cognitive load

What it is

The concept comes from John Sweller's Cognitive Load Theory (1988), developed for education but directly applicable to UX. It distinguishes three types: intrinsic load — the inherent complexity of the task; extraneous load — mental effort added by how the interface presents the task; and germane load — effort spent building useful understanding.

Designers can't reduce intrinsic load — booking a flight requires certain decisions no matter what. But extraneous load is entirely within design's control. Cluttered layouts, jargon labels, hidden actions, inconsistent patterns, unnecessary steps — all extraneous.

Why it matters

Every metric that matters — completion rate, error rate, time on task, satisfaction, return usage — degrades as cognitive load rises. Users don't report 'high cognitive load' when they abandon a checkout; they report that it 'felt hard' or 'took forever'. The felt experience of an interface is largely a measurement of the load it imposed.

When to use it

Cognitive load applies to every design decision. It's the mechanism behind why chunking works, why progressive disclosure reduces overwhelm, why consistent patterns save effort, and why microcopy quality matters. Any decision that adds elements, adds steps, or adds ambiguity is a decision that raises extraneous load.

What it looks like in practice

A single-column form with clear labels above each field imposes less load than a two-column form with labels floating inside inputs. A dashboard with 4 clearly grouped KPIs imposes less load than 20 metrics competing for attention. A checkout that autofills known information imposes less load than one that asks users to retype their address for the third time.

The Nielsen Norman group's 20-year corpus finds cognitive load explains more usability variance than almost any other single factor.

What people get wrong

• Adding features without accounting for the load each new element imposes on every user, forever. Features have ongoing cognitive cost, not just build cost.
• Solving cognitive load with visual polish alone. Prettier interfaces can carry the same or higher load — polish sometimes hides complexity rather than reducing it.
• Treating cognitive load as a mobile-only concern. Desktop users under time pressure or on complex enterprise software face load problems too.
• Assuming your team's ability to use the product predicts a real user's. Team members have context, muscle memory and mental models real users don't have.

Learn next

Cognitive load is the framework that ties chunking, mental models, recognition-over-recall and Hick's Law together. Every audit surfaces load failures under Nielsen's aesthetic-and-minimalist heuristic (H8) and error-prevention heuristic (H5).

Reviewed 29 September 2026 · Editorial standards