Cognitive Load in UX Design: Why Users Feel Tired | Guide to UX Laws

You land on a page and something just feels heavy. Too many buttons. Too much text. Five things asking for your attention at once. You are not even sure where to look. So you feel a little tired, a little annoyed, and you leave. Did you ever feel that? That heavy feeling has a name. It is cognitive load.

Cognitive load is the total mental effort a task takes. Your brain has a small tank of thinking fuel, and every choice, every word, every button burns a little of it. Burn too much, and the user gives up.

So let me give you the real thing. What cognitive load is, where the idea came from, the three types, and how to design so your users think less and do more.

This is Part 4 of my 34 part UX Laws series. One law, one deep dive, every time. Part 1 was my Complete Guide to UX Laws, all 33 in one place. If you want each new law the day it drops, subscribe below.

What cognitive load actually is

Think of your brain like a phone battery. Every task you do drains some of it. Reading, deciding, remembering, figuring out what a button does, all of it pulls from the same battery.

Cognitive load is just how much of that battery a task uses up. A clean, clear screen uses a little. A messy, confusing one uses a lot.

And here is the key. That battery is small. We talked about working memory in the last post, the tiny mental desk. Cognitive load is what happens when you pile too much onto that desk. The user cannot think straight, so they slow down, make mistakes, or quit.

So the point is simple. Your job is not to add more. Your job is to make the user spend less effort to get what they came for.

The real story, where the idea came from

In 1988, a psychologist named John Sweller studied how people learn and solve problems. He noticed something important. When you overload someone’s working memory, learning falls apart. Not because they are not smart. Because the brain simply ran out of room.

He turned this into cognitive load theory. The core idea is honest and simple. Working memory is very limited. So if you want people to actually understand and act, you have to respect that limit and stop overloading it.

It started in classrooms and textbooks. But it is the same brain sitting in front of your app. The moment your screen asks for more effort than the user has, they check out.

The three types of cognitive load

Sweller said the load comes in three kinds. This part is gold for designers, so stay with me.

First, intrinsic load. This is the effort the task itself needs. Filing your taxes is just hard. You cannot make tax rules simple. That difficulty lives in the task.

Second, extraneous load. This is the extra effort your design adds on top. Clutter, jargon, confusing labels, too many choices, steps in a weird order. None of this helps the user. It is pure waste, and it is your fault as the designer.

Third, germane load. This is the good effort, the effort the user spends actually learning your product and getting the job done.

So the trick is not to remove all effort. It is to kill the extraneous load, so the user’s small battery goes to the real task, not to fighting your design.

The one you actually control

Here is the part that matters most. You cannot change intrinsic load much. The task is the task. And you want to protect germane load, the useful effort.

But extraneous load is 100 percent on you. Every messy layout, every wall of text, every unclear icon, every extra field you did not need, that is load you added. And it is load you can delete.

“Don’t make me think.” – Steve Krug

That line is the whole job in three words. Every time the user has to stop and think about your interface instead of their task, you added extraneous load. Cut it.

What cognitive load means for your design

So the rule is simple. Lower the effort. Here is where the extra load usually hides.

Clutter. Too many things on one screen, all shouting. Each one costs battery.

Jargon. Fancy words the user has to decode. Plain words are lighter.

Too many choices. Every option is a decision, and decisions drain the tank fast.

Inconsistency. When the same thing looks different on two screens, the brain has to relearn it every time.

Bad order. Asking for things in a confusing sequence makes the user hold more in their head.

Every one of these is extraneous load. And every one is fixable.

Real examples you already use

You feel this everywhere once you know it.

A clean dashboard that shows three key numbers, versus one that dumps forty. The clean one is calm. The busy one is exhausting.

A checkout that asks only for what it needs, versus one with fifteen fields. Fewer fields, less load, more finished orders.

Plain button labels like “Start free trial,” versus vague ones like “Proceed.” You should never have to guess what a button does.

Progressive disclosure, where the app shows the basics first and hides the advanced stuff until you need it. That keeps the load low until the user asks for more.

The same layout and patterns across every screen, so the user learns it once and never has to think about it again.

How to lower cognitive load

Here is how I actually apply it in UX design.

First, cut what is not needed. Before you add anything, ask if it helps the user act. If not, it is just load. Remove it.

Also, use plain words. Write like a human. Every fancy word is effort the user has to spend decoding.

Next, reduce choices on each step. Show fewer options, guide the eye to the main action, and hide the rest until it is needed.

Then, keep it consistent. Same buttons, same patterns, same words for the same things. Consistency means the brain learns once and relaxes.

And chunk and order things well. Break big tasks into small, logical steps so the user only carries a little at a time.

The honest pros and cons

Designing for low cognitive load is powerful because it works on every single user, on every screen. Take the effort down and the whole product feels easy, fast, and trustworthy.

The trap is thinking that more equals more helpful. It does not. Adding another banner, another tip, another field, another option feels generous, but it is really just piling weight on a tired brain. Simple is not lazy. Simple is respect.

So the rule is short. Every element must earn its place, or it goes.

Why this matters for your business

If you run a product, cognitive load is a silent tax on your growth. Every bit of extra effort you put in front of a user is a chance for them to feel tired, get confused, and leave. And they will not tell you why. They just bounce.

When you cut that load, the opposite happens. The user feels the ease, keeps moving, and reaches the end. In my own revamp work, stripping out extraneous load, the clutter, the jargon, the extra fields, is one of the most reliable ways to lift conversion. Not a trick. You just stopped burning the user’s battery on your mess.

So the takeaway for founders is short. A lighter screen is not a style choice. It is a growth lever.

FAQ

Wrapping up

Cognitive load is the effort your design asks of the user. Some of that effort is the task itself, and you cannot change it. But a lot of it is extra weight you added, and that part you can delete.

So make it lighter. Cut the clutter, use plain words, offer fewer choices, and stay consistent. Do that, and your product stops draining the user and starts feeling easy.

That is cognitive load. See you in Part 5, where we get into chunking.