Cognitive load is the total mental effort it takes to use an interface. It splits into three types: intrinsic (the task's built-in difficulty), extraneous (effort your design adds for no reason), and germane (effort that helps users learn the interface).
Use cases
Load stays invisible until it's too high, then people stall, miss things, and abandon the task. Every unnecessary decision, unclear label, or bit of clutter spends a resource users have very little of.
The overstuffed form: A four-field refill form buried under a promo banner, an auto-popup chat, three nav menus, and a "related resources" sidebar. The task is easy; the page makes it feel hard.
Recall over recognition: An app makes users remember a code from a previous screen instead of showing it. Every "what was that again?" taxes working memory and slows them down.
Choice paralysis: A pricing page with twelve plans and no clear default. More options means a longer, heavier decision, and often no decision at all.
How it's used in practice
Kill extraneous load first: Strip clutter, redundant steps, and decoration that carries no meaning. That's the load you added and can take back.
Chunk and reveal gradually: Break complex flows into steps and use progressive disclosure so users face one manageable piece at a time.
Favor recognition over recall: Show options, labels, and defaults instead of making people remember. The screen should carry the memory, not the user.
Build a clear visual hierarchy: Size, contrast, and white space guide the eye so users don't have to hunt for what matters.
Stay consistent: Reusing patterns lets users lean on habits instead of relearning your interface on every screen.
🪄
Pro-tip: Not all load is bad. Intrinsic load is the real task users came to do, and germane load is the effort that builds their mental model of your product. Strip those and you gut the experience. Aim your cutting at extraneous load only: the effort your design added that helps nobody.
Challenges & limitations
Hard to see and measure: Load is felt, not shown. Without testing, teams argue about "clean" designs on taste, not evidence.
It varies by user: A novice and an expert carry very different loads on the same screen. What feels light to your team can crush a first-timer
