Recommended resources
The freely available resources this lesson will direct you to.
Hello! Welcome to the third lesson in our module on the two systems of thinking.
In our previous lessons, we distinguished between the fast, intuitive System 1 and the slow, deliberate System 2. We then learned to identify which system is likely engaged during various user interactions. You practiced deconstructing an interface to see this dynamic in action.
Today, we will connect these concepts to a crucial principle in user experience: cognitive load. Our learning outcome is to explain how cognitive load influences a user's reliance on System 1 versus System 2 thinking in a digital interface. We'll explore what cognitive load is, how it acts as a "switch" between the two systems, and what this means for your work as a product designer.
1. What is Cognitive Load?
You've likely encountered the famous UX mantra, "Don't Make Me Think," popularized by Steve Krug. Cognitive load is the psychological theory that explains why that principle is so important. It refers to the amount of mental effort or working memory required to process information and complete a task.
To get a formal definition from a UX perspective, let's watch a short video.
Why Cognitive Load Matters for UX Designers
This video from the Mastering UX channel, 'Why Cognitive Load Matters for UX Designers,' provides a clear definition of cognitive load and explains its importance in our field.
Please watch from 01:49 to 03:42. Pay attention to the definition of cognitive load based on John Sweller's theory of limited working memory and the reasons it's so critical for UX, such as its impact on user retention and efficiency.
As the video explains, our working memory is finite. When the amount of information or the complexity of a task exceeds this capacity, we experience high cognitive load. This can lead to frustration, errors, and ultimately, task abandonment—outcomes we strive to avoid in product design.
2. The Link: Cognitive Load as the System Switch
Here is the central idea for today's lesson: Cognitive load is the mechanism that determines whether we use System 1 or System 2.
- Low Cognitive Load: When a task is simple, familiar, or well-presented, it imposes a low cognitive load. Our brain can handle it easily using the automatic, low-effort System 1. This is the state of "flow" or "intuitive use" we aim for in many interactions, like scrolling a feed or clicking a clear call-to-action.
- High Cognitive Load: When a task is complex, unfamiliar, or poorly designed, it imposes a high cognitive load. System 1 can't handle it and is forced to call for help. This engages the effortful, energy-intensive System 2.
The article we looked at in our last lesson makes this connection explicit.
Applying System 1 & 2 Thinking for Better UX
Let's revisit the article 'Applying System 1 & 2 Thinking for Better UX' by Austin Acevedo. It directly links the two-systems theory to the concept of cognitive load.
Please read the first three paragraphs of the section 'How do I apply it?'. Focus on how the author frames cognitive load as the amount of mental effort required, and how keeping users in System 1 is the key to reducing it.
When an interface is confusing, cluttered, or violates established patterns (what the article calls "mental models"), it increases cognitive load. The user has to stop and think, consciously activating System 2 to figure things out.
3. When System 2 Gets Overwhelmed
System 2 is powerful, but it's also a limited resource. What happens when the cognitive load is not just high, but too high? System 2's capacity for focused attention can be completely consumed, leading us to miss things that are happening right in front of us.
The famous "invisible gorilla" experiment is a classic demonstration of this.
Mastering Both Your Brains | System 1 vs System 2
The video 'Mastering Both Your Brains' uses the gorilla experiment to show how engaging System 2 on a demanding task can make us blind to other stimuli.
Watch the segment from 32:11 to 34:49. The core task—counting basketball passes—is a System 2 activity. Notice how this high-load task makes it incredibly difficult to notice the unexpected (and obvious) gorilla.
This phenomenon, known as "inattentional blindness," is a direct consequence of System 2's limited bandwidth. When you force a user to perform a high-load task (like deciphering a confusing form), you are not just making it difficult—you are also making it likely they will miss other important information on the screen, like instructions, error messages, or even the "cancel" button.
4. Designing to Manage Cognitive Load
As a product designer, your goal is to manage cognitive load. This doesn't always mean eliminating it, but rather controlling it to create the most effective experience.
A. Designing for System 1: Reducing Unnecessary Load
For most user tasks, the goal is to minimize cognitive load to keep the user in the effortless state of System 1. A separate article, "Designing for Decision Making," offers excellent, actionable principles for this.
Designing for Decision Making: The Psychology of Choice
This article provides a fantastic checklist of design strategies aimed at simplifying decision-making by reducing cognitive load.
Read the section 'Designing for Simplified Decision Making.' Pay particular attention to the principles of 'Limiting Options,' 'Progressive Disclosure,' and 'Visual Hierarchy and Layout.' Think about how you've used these in your own work at Strategyzer or Perlego.
By applying these principles—curating choices, revealing information in steps, and guiding the eye—you reduce the mental work required. This allows the user to proceed smoothly and intuitively, relying on the fast, pattern-matching abilities of System 1.
B. Designing for System 2: Supporting Necessary Load
However, some tasks are inherently complex and require the focused attention of System 2. Think of configuring privacy settings, comparing complex subscription plans, or using a sophisticated analytics tool. In these cases, trying to oversimplify can be counterproductive or even dangerous.
The goal here is not to eliminate cognitive load, but to support the user's System 2 thinking.
Applying System 1 & 2 Thinking for Better UX
Let's return one last time to 'Applying System 1 & 2 Thinking for Better UX' to explore this crucial nuance.
Please read the section titled 'Optimizing for System 2 Thinking.' Note the strategies suggested, such as breaking tasks into smaller chunks, showing progress, and presenting relevant information at the right time. This is about making effortful tasks manageable, not making them mindless.
This is a key insight for designing professional tools. When a user needs to make a critical or complex decision, the interface should act as a helpful assistant to their System 2, providing clarity, structure, and the right information, rather than trying to force the task into a System 1 framework where errors are more likely.
Conclusion
Today we've bridged the gap between the two systems of thinking and the practical realities of UX design through the concept of cognitive load.
Key Takeaways:
- Cognitive load is the mental effort required to use an interface, drawing on our limited working memory.
- It acts as a switch: low cognitive load keeps users in the fast, intuitive System 1, while high cognitive load forces an engagement of the slow, effortful System 2.
- Excessive cognitive load overwhelms System 2, leading to errors, inattentional blindness, and task abandonment.
- As designers, we manage this by reducing unnecessary load for simple tasks (using principles like progressive disclosure) and supporting necessary load for complex tasks (by chunking information and showing progress).
In our next and final lesson for this module, we will put everything together. You will analyze a complete user flow from start to finish, identifying exactly where and why a user might switch from System 1 to System 2, and evaluating how well the design manages the user's cognitive load at each step.