Cognitive Load Theory
Working memory is finite. Design around it.
Your brain can only process ~4 items at once. Reduce waste (extraneous), manage complexity (intrinsic), maximize learning (germane).
The Working Memory Bottleneck
"Working memory can hold roughly 4 (±1) items for about 20 seconds. Everything you learn must pass through this bottleneck."
John Sweller discovered that learning isn't just about attention—it's constrained by working memory capacity. Overload working memory and learning stops. Great instruction respects cognitive limits, using them efficiently.
The Three Types of Cognitive Load
Intrinsic Load
The inherent difficulty of the material itself. Complex topics have high intrinsic load regardless of presentation.
Verdict
MANAGE IT - Break complex topics into smaller chunks
Extraneous Load
Cognitive effort wasted on poor presentation, confusing layouts, irrelevant information, or bad UX.
Verdict
ELIMINATE IT - This is pure waste. Reduce ruthlessly.
Germane Load
Mental effort spent actually learning—building schemas, making connections, encoding into long-term memory.
Verdict
MAXIMIZE IT - This is productive learning effort
The Cognitive Load Equation
Intrinsic + Extraneous + Germane ≤ Working Memory
⚠️ When Overloaded
Learning stops. Confusion. Frustration. Information doesn't encode to long-term memory.
✅ When Optimized
Reduce extraneous → More room for germane → Better learning outcomes.
Developer Implication
Every bad UX decision adds extraneous load. Every confusing API, every unclear error message, every unnecessary step—it all taxes your users' finite cognitive resources. Simple is not dumbed down. Simple is respectful of cognitive limits.