In short
Cognitive load is the amount of mental effort people need to understand and use an interface, from reading content to making decisions.
What is cognitive load?
Cognitive load is the mental work a task demands from your working memory. That memory is limited: people can only hold and process a handful of things at once. Every extra option, vague label or unexpected step uses up part of that capacity.
The term comes from Cognitive Load Theory, developed by educational psychologist John Sweller in the late 1980s. In UX design, it helps to separate two kinds of load: the effort the task itself requires, and the effort that a clumsy interface adds on top. The second kind is the one you can actively reduce.
Why cognitive load matters
When a product asks for too much thinking, people make more mistakes, abandon flows or put decisions off. In a SaaS tool, that shows up as support tickets and unused features. In an online store, as abandoned checkouts. An interface that does some of the thinking for people leaves them energy for what they actually came to do: get a task done or buy something.
How to reduce cognitive load in practice
- Show less at once: Only surface what matters for the current step.
- Stick to familiar patterns: Put navigation, search and the cart where people expect them.
- Use smart defaults: Good presets take decisions off people's plate without hiding choices.
- Show, don't make them remember: Display previous inputs, active filters and progress instead of relying on memory.
- Write clearly: Specific labels and short helper text stop the guesswork.
Example
A store selling coffee machines shows twelve filters, a comparison table and two pop-ups on its category page, all at the same time. In user tests, participants scroll up and down and lose track of what they were looking for. After the redesign, there are four main filters, the rest sit behind "More filters", and the comparison only opens on request. The page feels calmer, and participants find the right machine much faster.

written by
Benedikt Geisberger
Got the theory? Let’s test your product.
We use real user tests to show you where your product gets stuck and what to improve first.