Your user's brain is not a calm, focused place. It's a battlefield. Notifications are firing. Slack is pinging. Their phone is vibrating. They have 7 tabs open. And somewhere in the middle of all that noise, they're trying to use your product.

If your design assumes a focused, rational user, it's already failed.

Cognitive load is the total amount of mental effort being used in working memory at any given moment. When your interface demands more than the user has available, they don't try harder — they leave.

Working memory: the bottleneck you can't ignore

Humans can hold roughly 4-7 items in working memory at once. That's it. Every field in your form, every option in your dropdown, every piece of information you ask users to carry from one screen to the next — it all consumes that tiny, precious resource.

Most interfaces fail not because they're confusing, but because they're exhausting. They ask the brain to track too many things simultaneously, and the brain — being the efficient machine it is — opts out.

The three types of cognitive load

Intrinsic load (the unavoidable)

Some tasks are inherently complex. Filing taxes. Configuring a server. Learning a new language. You can't eliminate intrinsic load, but you can avoid adding to it. Don't make hard things harder.

Extraneous load (the enemy)

This is the mental effort your design creates unnecessarily. Cluttered layouts. Inconsistent patterns. Vague labels. Information that should be together but is spread across screens. Extraneous load is design debt, and your users pay the interest.

Germane load (the good kind)

This is the mental effort devoted to actually understanding and learning. When you reduce extraneous load, you free up capacity for germane load — which means users can actually engage with your product instead of fighting it.

Designing for the distracted brain

Chunk information. Break complex flows into smaller, digestible steps. A multi-step form feels lighter than a single-page form, even if the total number of fields is identical. The brain prefers small, completable units.

Recognise over recall. Don't ask users to remember information from a previous step. Show it to them. Menus are easier than command lines. Icons alongside labels are easier than icons alone. Every time you make someone remember something, you're spending their cognitive budget.

Reduce decisions. Hick's Law tells us that decision time increases with the number of choices. If your navigation has 12 items, users aren't empowered — they're overwhelmed. Group. Prioritise. Hide secondary options behind progressive disclosure.

Provide clear feedback. Uncertainty is cognitively expensive. When users don't know if an action succeeded, their brain spins cycles wondering. A simple confirmation, a loading state, a success message — these aren't niceties. They're cognitive off-ramps.

The best interface isn't the one with the fewest elements. It's the one that demands the least from the user's working memory at any given moment.

The bottom line

Cognitive load isn't abstract theory — it's the difference between a product people tolerate and a product people love. Every element you add, every piece of text you write, every step in a flow — ask yourself: Is this worth the mental energy it costs?

If the answer isn't an immediate yes, cut it. Your users' brains will thank you.