What Cognitive Load Theory Actually Says
John Sweller introduced cognitive load theory in a 1988 paper in Cognitive Science, building on a well-established fact about working memory: it holds only a small number of new items at once - see Miller's Law - before problem-solving performance degrades. Sweller's contribution was splitting the demand placed on that limited capacity into three distinct types, only one of which a designer can actually control.
The Three Types of Load
- Intrinsic load: The complexity inherent to the task itself. Filing taxes is intrinsically complex - no amount of interface polish removes that; good design can only sequence and contextualise it.
- Extraneous load: Overhead created by how the task is presented - confusing labels, inconsistent patterns, unnecessary steps. This is the one type of load design controls directly, and the one Sweller's original research focused on reducing in instructional materials.
- Germane load: The effort spent building a working mental model of the system. This is productive load - it's what happens when a user learns your product - and it should be protected, not stripped out along with the extraneous load.
Signs of High Extraneous Load
- Users re-read the same label more than once before acting.
- Error rates spike at a step that isn't inherently difficult.
- Usability sessions surface confusion out loud ("wait, which one do I click?").
- Support tickets cluster on one feature rather than spreading evenly.
- Task time runs well past what the task's actual difficulty would predict.
Reducing Extraneous Load Without Cutting Function
- Progressive disclosure: Show what the current step needs; defer advanced options until they're asked for.
- Recognition over recall: Persistent labels, icons paired with text, and visible context remove the need to remember something from a previous screen.
- Chunking: Group related fields and information spatially - the same principle behind Miller's 7±2.
- Defaults: Pre-fill the most common answer. Every blank required field is a small decision users have to make.
- Consistency: Reuse one interaction pattern for one type of action so the learning cost is paid once, not on every screen.
Key Takeaways
- Cognitive load theory, from Sweller's 1988 paper, splits mental effort into intrinsic, extraneous, and germane load.
- Only extraneous load is the designer's to fix - intrinsic load has to be managed, not disguised.
- Germane load (learning the system) is desirable; don't optimise it away along with the noise.
- Progressive disclosure, chunking, and consistent patterns are the direct levers for cutting extraneous load.
