Cognitive load

Cognitive load is the amount of mental effort required to use an interface. When load exceeds capacity, users make errors, give up, or avoid the interface entirely.

What is cognitive load in UX design?

Cognitive load is the total amount of mental effort a user must exert to interact with an interface. Every decision they make, every element they must interpret, every step they must remember adds to cognitive load. When that load exceeds a user's working memory capacity, performance degrades: users make errors, slow down, or abandon the task entirely.

The concept comes from educational psychologist John Sweller's cognitive load theory. In UX design it is one of the most practical frameworks for evaluating whether an interface is asking too much of its users.

What are the types of cognitive load?

Intrinsic load is the inherent complexity of the task itself. Filing a tax return is cognitively demanding regardless of how well the interface is designed. Designers cannot eliminate intrinsic load, only avoid adding to it unnecessarily.

Extraneous load is complexity introduced by poor design. Unclear labels, inconsistent navigation, too many choices presented at once, and redundant steps all create extraneous load. This is entirely within the designer's control and reducing it is the core job of UX design.

Germane load is the mental effort that builds useful understanding. A well-structured onboarding flow that teaches users how the product works creates germane load intentionally and productively.

Why does cognitive load matter in UX?

Every element that doesn't need to exist, every label that isn't clear, every extra step in a flow is consuming mental resources that should go toward the user's actual goal. High extraneous cognitive load is the most common reason users abandon forms, misuse features, and leave products feeling confused. Reducing it directly improves completion rates, error rates, and user satisfaction.

How to reduce cognitive load in interface design

Use progressive disclosure to show only what users need at each step. Break complex tasks into smaller, focused steps. Use consistent affordances so users never have to figure out how to interact with elements. Apply Gestalt principles to create visual groupings that reduce the need to read labels. Remove any element that doesn't serve the user's current task.

Related terms

Related guides