The mental effort required to use an interface or process information. High cognitive load leads to errors and frustration. UX designers reduce cognitive load through clear visual hierarchy, progressive disclosure, and chunking related information together.
Common contexts
- Splitting a 12-field onboarding form into three focused steps to reduce completion abandonment
- Removing decorative icons from a dense settings panel to let the labels carry the cognitive weight
- Chunking a long legal agreement into labeled sections so users can scan and locate relevant clauses
Use when
Actively audit for cognitive load whenever a screen contains more than five or six distinct decisions or information types — complexity tends to accumulate invisibly through feature additions. If users are making errors or abandoning flows, cognitive load is almost always a contributing factor worth measuring before redesigning anything.
Avoid when
Reducing cognitive load at all costs can oversimplify interfaces for expert users who need density and control — stripping a power tool of its depth in the name of simplicity often just relocates the cognitive effort to additional steps rather than eliminating it. Understand which users you're designing for before cutting.
Cognitive load isn't only about how much information is on screen — it's about how much the user has to hold in working memory because the interface won't hold it for them.
Real-world examples
- Google's homepage reduces cognitive load to near zero by presenting a single search bar on an empty white canvas, eliminating competing stimuli.
- Apple's checkout flow pre-fills shipping and payment details from Apple Pay, removing the need for users to recall and type information under task pressure.
- Duolingo breaks language lessons into micro-tasks of under two minutes, chunking content to match users' working-memory capacity and prevent overload.