By using our site, you agree to our Cookie Policy
Accept
Share
Cognitive Load and How to Reduce It
This next article in our Behavioral Science for Digital Experience Design series focuses on the topic of Cognitive Load.
The Bandwidth Problem
We often think of our users as having unlimited attention. We imagine them sitting in a quiet room, sipping coffee, and reading every word of our interface with deep focus.
The reality is quite different. Your user is likely distracted, in a hurry, and operating with a “mental battery” that is already half-empty.
In cognitive psychology, this battery is known as working memory[1]. It is a finite resource, similar to a computer’s RAM. When a digital interface demands more processing power than the user has available, cognitive overload occurs.[2] The result is not just frustration; it is abandonment. If a user has to burn calories figuring out how to use your interface, they have no energy left to decide what to buy.
Cognitive Load Theory
Cognitive Load Theory (CLT), developed by educational psychologist John Sweller in 1988, posits that human learning and task execution are severely hampered when working memory is overwhelmed. [3]
To design effective digital products, we must understand the three types of load that compete for the user’s mental bandwidth:
- Intrinsic Load: The inherent difficulty of the task itself (e.g., calculating a mortgage rate). This cannot be eliminated, only managed.
- Extraneous Load: The unnecessary difficulty added by poor design (e.g., a confusing font, a hidden navigation menu, or visual clutter). This is “waste” and must be eliminated.
- Germane Load: The effort dedicated to actually processing and learning the information (e.g., understanding a pricing tier). This is “good” load because it leads to value.
One reason “one-click checkout” works is not magic. It relies on a learned schema: saved addresses, saved payment methods, familiar confirmation patterns. The interface reduces the amount of new thinking required in the moment.
A useful nuance: the older “7 plus or minus 2” idea is often quoted in UX, but modern research suggests working memory capacity is frequently closer to 3–5 meaningful items, depending on conditions and chunking. Treat capacity as smaller than you want it to be, and your designs get better. [4]
The Interface Design Goal:
Your job is to ruthlessly eliminate Extraneous Load so that the user has enough remaining bandwidth to handle the Intrinsic Load of the task.
How This Behavior Shows Up in Digital Interfaces
When extraneous load is high, users exhibit specific failure patterns.
The Split-Attention Effect
This occurs when users must hold information in their head while physically moving their eyes to a different part of the screen. A common example is a map legend that is visually separated from the map itself. The user has to look at the color “Red,” remember “Red means Traffic,” move their eyes to the map, and apply that label. This “juggling” act burns working memory rapidly.
Examples:
- A pricing page where plan details sit far from the feature comparison, so users bounce their eyes back and forth while trying to remember what they just read.
- A checkout that shows shipping options on one panel and the shipping address on another, forcing users to reconcile constraints mentally.
- A settings screen where “what this does” is separated from the control that does it.



If you integrate related information spatially and temporally, the task gets easier.[5]
Hick’s Law and Decision Fatigue
Hick’s Law states that the time it takes to make a decision increases logarithmically with the number of choices.[6] Interfaces that present too many equal-weight options simultaneously (e.g., a mega-menu with 50 links) paralyze the user. This is often seen in “Kitchen Sink” dashboards that try to show every metric at once, resulting in a user who looks at everything but sees nothing.[7]
“Decision fatigue” is often used loosely, but the core idea has a research trail: making repeated decisions can degrade the quality of subsequent decisions and increase avoidance.[8]
Visual Clutter (Chartjunk)
Every visual element on a screen—no matter how small—requires a micro-amount of processing power to ignore. Decorative icons, heavy grid lines, and unnecessary gradients are “cognitive taxes.” If they do not convey information, they are noise. If users spend a long time in a flow and still do not finish, it is often a sign they are trying to reason their way through resistance. They are not lazy. The interface is expensive.
Users must actively ignore these distractions, and that costs effort. Edward Tufte’s critique of “chartjunk” is essentially an argument about extraneous cognitive load in visual form.[9]
Practical Application: Designing for Mental Economy
To respect the user’s mental limits, we must design for economy. Here are four tactical ways to reduce the load.
1. Leverage Progressive Disclosure
Do not show everything at once. Show only the information necessary for the current step. This strategy was mastered by Domino’s with their “Pizza Tracker.” Instead of showing a complex logistics table, they show a simple progress bar with one status at a time (“Prep,” “Bake,” “Delivery”). By hiding the complexity, they reduced support calls because users felt informed without being overwhelmed.[1]
Design the “happy path” to be obvious and light. Put advanced options behind clear affordances:
2. Optimize for “Chunking” (Miller’s Law)
Do not show everything at once. Show only the information necessary for the current step. This strategy was mastered by Domino’s with their “Pizza Tracker.” Instead of showing a complex logistics table, they show a simple progress bar with one status at a time (“Prep,” “Bake,” “Delivery”). By hiding the complexity, they reduced support calls because users felt informed without being overwhelmed.[1]
Design the “happy path” to be obvious and light. Put advanced options behind clear affordances:
3. Recognize Over Recall
Do not show everything at once. Show only the information necessary for the current step. This strategy was mastered by Domino’s with their “Pizza Tracker.” Instead of showing a complex logistics table, they show a simple progress bar with one status at a time (“Prep,” “Bake,” “Delivery”). By hiding the complexity, they reduced support calls because users felt informed without being overwhelmed.[1]
Design the “happy path” to be obvious and light. Put advanced options behind clear affordances:
Case Study: GOV.UK’s “One Thing Per Page” Strategy
A practical method for evaluating visual hierarchy is the Squint Test, popularized by product design leader Luke Wroblewski.
To perform this audit, display the design on a screen. Step back five feet. Squint until the details blur. The goal is to see what elements remain visible when the text is illegible.
If the design is successful, the primary Call to Action and the main value proposition should be the darkest and most prominent visual blobs.
If it fails, the logo dominates the page, or the design appears as a uniform gray wash. That indicates a lack of hierarchy.
For a data-driven alternative, teams can use predictive eye-tracking tools such as Attention Insight. You can also simply apply a heavy Gaussian blur in your design software to simulate peripheral vision processing. If the primary action is not identifiable while squinting, users will likely miss it while scanning.
Conclusion
You cannot change the user’s brain, but you can change the interface.
Reducing extraneous load allows users to focus their limited mental energy on the task at hand.[1] Good design is often invisible because it requires no conscious thought to operate. If a user notices your navigation, it is likely because it is confusing them.
This article is part of a series titled “Behavioral Science for Digital Experience Design”. The goal is understanding users through psychology, communication, and empirical research. This section focuses on Cognitive Psychology with this article in particular covering the topic of Cognitive Load.
Sources
- [1] Working Memory — PubMed (1992)
- [2] The Magical Mystery Four: How is Working Memory Capacity Limited, and Why? — National Library of Medicine (2010)
- [3] Cognitive Load During Problem Solving: Effects on Learning — Cognitive Science (1988)
- [4] The Magical Number Seven, Plus or Minus Two: Some Limits on our Capacity for Processing Information — George A. Miller (1956)
- [5] The Split-Attention Effect as a Factor in the Design of Instruction — Paul Chandler and John Sweller
- [6] On the Rate of Gain of Information — W. E. Hick (1952)
- [7] Stimulus Information as a Detriment of Reaction Time — Ray Hyman (1952)
- [8] Decision Fatigue: A Conceptual Analysis — PubMed (2018)
- [9] Chartjunk — Edward Tufte (2015)
