Design for finite cognitive capacity.
Do not demand sustained attention, memory, or decision-making beyond what is strictly necessary for the task.
Contents 1. Human Cognition & Behavior 2. Cognitive Load
How much mental effort interaction demands.
First, ask yourself
“Does your system make users think unnecessarily during interactions?”
Mission statement
Ensure users can think efficiently by minimizing unnecessary mental effort.
Key heuristics Cognitive Load
- Interaction must operate within finite cognitive limits.
- Systems must assume users are already mentally occupied.
- Cognition must be directed toward user goals, not system mechanics.
- The system must remember whenever it reasonably can.
- Critical state must be perceptible without mental reconstruction.
- Correct action must not depend on guesswork.
- Predictability must convert reasoning into automated response.
- Tasks must not be fragmented or fatigued by unnecessary micro-decisions.
- Automation must reduce effort without increasing supervision.
- Design must account for cumulative cognitive cost.
Executive brief
The system must minimize users’ cognitive load by doing the work they do not need to think about.
Core questions Cognitive Load
“What mental effort could the system handle but currently falls on the user?”
“Who is doing the work? The user or the system?”
Focus areas
Responsibility-first
“What cognitive work is unnecessarily offloaded to the user?”
“Where is the system failing to carry its share of thinking?”
Decision-aware
“What must users remember, interpret, compare, or decide?”
“What decisions exist only because the interface forces them?”
Efficiency-aware
“Could mental effort be reduced with better design or automation?”
“Are repeated or tedious tasks unnecessarily taxing users?”
AI-aware
“What thinking persists despite automation?”
“Is AI actually helping, or just showing intelligence without acting?”
UX directives Cognitive Load
Assume users are already cognitively occupied.
Design with cognitive courtesy as a baseline responsibility.
Minimize interface thinking.
Ensure users think about their work and goals, not about how the system operates.
Require the system to remember on users’ behalf.
Do not make users recall what the system can present for recognition.
Make state visible to reduce mental bookkeeping.
Do not hide information to avoid errors or uncertainty.
Eliminate interpretive burden.
Do not require guessing scope, state, or consequences in order to proceed correctly.
Use consistency to convert reasoning into habit.
Make system behavior predictable to replace conscious reasoning with habitual response.
Reduce decision density.
Keep users from making frequent or unnecessary micro-decisions within a single task flow.
Ensure automation removes work rather than adds supervision.
Do not introduce automation that requires constant monitoring, correction, or verification.
Design for sustained use.
Treat small inefficiencies as compounding costs that accumulate into fatigue over time.
Executive summary
- Cognitive Load is the cost imposed on finite human cognitive resources.
- It must be minimized so users think about their goals, not about how the system works.
- Human cognitive capacity is easily exhausted.
- The system is responsible for minimizing unnecessary mental effort.
- Decision density and hidden conditions must be reduced to prevent cumulative fatigue.
- Cognitive Load succeeds when interaction feels effortless.
Success indicators
- The task can be completed without unnecessary thinking about the interface.
- Information is visible so users do not need to rely on memory.
- System state and next steps are easy to understand.
- Decisions within the task are few and meaningful.
- Automation reduces work instead of adding supervision.
One-line summary
Before users can think about their goals, they must not be forced to think about the interface.