Research

Cognitive Load

The mental effort required to process information in working memory. Reducing cognitive load is one of the highest-leverage UX improvements.

#cognitive load#working memory#complexity#simplicity#chunking#processing

What is it?

Cognitive load is the total amount of mental effort being used in the working memory at any given time. Proposed by John Sweller in 1988, it explains why some interfaces feel effortless and others feel draining. Working memory is severely limited — it can hold approximately 7±2 items (Miller's Law). Every design decision either adds to or reduces that load.

Why it matters

When cognitive load is high, users make more errors, complete tasks more slowly, give up earlier, and form negative impressions of the product. High cognitive load is the #1 reason products feel "complicated" even when they technically have all the right features. Reducing it is often more impactful than adding new features.

Best Practices

  • Chunk related information into groups of 4–7 items maximum.
  • Use progressive disclosure: reveal information only when it becomes relevant.
  • Recognize over recall: show options rather than requiring users to remember and type them.
  • Use consistent patterns so users don't have to learn new interactions for similar tasks.
  • Reduce the number of decisions required in any single screen.
  • Use familiar icons and patterns that activate existing knowledge instead of requiring new learning.
  • Keep visual noise low — every non-essential element competes for limited cognitive resources.
  • Use white space to give the brain time to process — dense layouts increase load.
  • Automate or pre-fill information wherever possible (addresses, payment details, preferences).
  • Split complex tasks across multiple focused screens instead of presenting all fields at once.

Common Mistakes

  • Presenting all features and options simultaneously instead of progressively.
  • Using inconsistent patterns for similar tasks — forces re-learning.
  • Dense, information-heavy layouts with no visual breathing room.
  • Long forms with many fields on a single screen.
  • Requiring users to remember information from a previous step.
  • Complex jargon and technical language that adds linguistic processing load.
  • Poor visual hierarchy where users must actively search for important information.

Checklist

Research & Theory

Sweller's Cognitive Load Theory (1988)

John Sweller identified three types of cognitive load: intrinsic (inherent to the content), extraneous (from poor design), and germane (useful processing that builds understanding). Design should minimize extraneous load.

Why it's relevant

Extraneous cognitive load is the kind designers cause. Every unnecessary element, inconsistency, and confusing pattern is extraneous load. Reduce it.

Miller's Law

George Miller's 1956 paper "The Magical Number Seven, Plus or Minus Two" showed that working memory can hold 7±2 chunks of information simultaneously.

Why it's relevant

Never present more than 7 options simultaneously. Chunk navigation, settings, and feature lists to respect this limit.

Cognitive Ease (Kahneman)

The experience of cognitive ease — when processing is smooth and effortless — is associated with feelings of truth, familiarity, and comfort. Cognitive strain triggers skepticism and effort.

Why it's relevant

Products that feel easy to use feel more trustworthy. Cognitive load reduction is a trust-building mechanism.

Real-World Examples

Google Search

The homepage is a masterclass in cognitive load reduction. One input, one button, no decisions. All complexity deferred to when it's needed.

TurboTax

Splits a complex tax form into hundreds of single-question screens. Each screen has one question. Maximum progressive disclosure.

Stripe Checkout

Preloads saved cards, addresses, and payment methods. Reduces a 15-field checkout to 2 steps. Minimizes load at the highest-anxiety moment.