What is cognitive load in UX?

The three kinds of mental effort

Psychologists usually split cognitive load into three parts. Intrinsic load is the difficulty built into the task itself: filing a tax return is harder than ordering a pizza, whatever the design looks like.

Extraneous load is the effort your design adds for no good reason, such as a cluttered layout, jargon or inconsistent buttons. This is the part designers can actually remove. Germane load is the useful effort of learning and making sense of something new, and you generally want to support it rather than eliminate it.

In practice, you cannot make a complicated task simple, but you can stop making it harder than it is.

Why it matters more than it seems

People rarely complain about mental effort. They just leave, make mistakes or put the task off until tomorrow. High load shows up as abandoned forms, support tickets that ask basic questions and users who say a product is "overwhelming" without being able to say why.

It also hits some people harder: someone tired, distracted, new to the topic or using a second language has less spare capacity. Designing for low load is therefore also a quiet form of inclusion.

Practical ways to lower it

• Show less at once. Break a long form into steps, and only reveal advanced options when someone asks for them.
• Lean on recognition instead of recall. A dropdown of past addresses beats asking people to retype one.
• Keep patterns consistent so that people learn a thing once.
• Use plain words and put the most important action in an obvious place.
• Limit choices where you can. Ten equal buttons make people stall.
• Give clear feedback so users never have to wonder whether something worked.

Notice that most of these are subtraction, not addition.

Mistakes that raise the load

The common one is mistaking minimal for easy. A stripped-down screen with mystery icons may look calm, but it forces users to guess. Another is the "seven plus or minus two" rule being quoted as a law for menu sizes. It describes a classic finding about short-term memory, and applying it as a hard cap on items in a menu misreads it.

Teams also forget that load stacks. A single confusing label is fine; five small frictions in a row are exhausting.

How to spot it in your own product

Watch people use it. Pauses, rereading, hovering without clicking and sighs are all signs of strain. A think-aloud test makes this visible quickly. Task completion time and error rates give you numbers, and a short post-task question like "how easy was that?" adds a rough self-reported measure.

There is no single cognitive load meter you can read off a dashboard, so treat it as something you triangulate.