Cognitive Load in UI Design: Less Is Always More
Cognitive load is the total mental effort required to use your interface. Learn the three types of cognitive load and how to reduce unnecessary complexity in every screen you design.
What Is Cognitive Load?
Cognitive load is the total amount of mental effort required to use an interface at any given moment. Introduced by educational psychologist John Sweller in 1988, the theory divides cognitive demand into three types — and good UX design targets each one deliberately.
The Three Types of Cognitive Load
- Intrinsic load: The inherent complexity of the task itself. Filing taxes is intrinsically complex — a well-designed tax app cannot eliminate that complexity, but it can sequence and contextualise it well.
- Extraneous load: The unnecessary overhead created by poor design — confusing labels, cluttered layouts, inconsistent patterns. This is the designer's responsibility to eliminate.
- Germane load: The mental effort used to build schemas and understanding. This is productive — it's what happens when users learn your system. Design for it by providing clear feedback and logical structures.
Signs of High Extraneous Load
- Users pause and re-read the same label multiple times.
- Error rates spike on a specific step that isn't inherently complex.
- Users verbalise confusion ("Wait, which one do I click?") during usability tests.
- Support tickets cluster around the same feature.
- Task completion time far exceeds what the task's inherent complexity justifies.
Techniques to Reduce Cognitive Load
- Progressive disclosure: Show only what's needed for the current step. Defer advanced options.
- Recognition over recall: Labels, icons with text, and persistent context eliminate the need for users to remember information from a previous screen.
- Chunking: Group related information visually and spatially (see Miller's Law).
- Default values: Pre-fill forms with the most common answer. Every blank field is a micro-decision.
- Consistent patterns: Reuse the same interaction for the same type of action — users amortise the learning cost across the whole app.
- Reduce visual noise: Every decorative element that isn't communicating something is consuming cognitive resources.
Key Takeaways
- Extraneous load (bad design) is the designer's problem to eliminate. Intrinsic load (task complexity) must be managed, not hidden.
- Progressive disclosure, chunking, and consistent patterns are the primary tools.
- Every unnecessary element — visual or interactive — costs users cognitive resources they need for the actual task.
The three types of cognitive load: intrinsic (task complexity), extraneous (poor design overhead), and germane (learning). Designers can only control extraneous load.
