VOCABULARY / ENTRY
Cognitive Load
cognitive-load
Cognitive load is the total mental effort a task places on working memory. Intrinsic load comes from the complexity inherent to the task itself; extraneous load comes from how the interface presents that task. Design can mainly reduce the extraneous part.
Recognizing it
- Context needed across steps is carried by the interface rather than the user's memory
- Visual and verbal presentation stays consistent and restrained, cutting processing unrelated to understanding the task
- Unnecessary clutter and choices are removed before the task itself is simplified
Concept boundary
Cognitive load is a general concept of mental effort, not a synonym for recognition rather than recall — the latter is one concrete mechanism for lowering load (specifically the memory-retrieval part), not the concept itself. This entry also does not treat "7±2" as a design rule for menu length or similar option counts: that number describes short-term memory's capacity for unrelated recalled items, while menus and similar choices rely on recognition rather than recall, so the number cannot be applied directly as a cap on option count.
When to consider it
- A task requires the user to remember earlier input or state across multiple steps
- The interface has decorative typography, redundant links, or inconsistent wording unrelated to understanding the task
- Assessing why a flow feels effortful even though each individual step looks simple
When to be cautious
- Reducing cognitive load to "fewer options is always better," cutting features without distinguishing intrinsic from extraneous load
- Citing "7±2" as a hard cap on the number of menu items or list entries
- Judging a design's load by intuition alone instead of verifying it with task performance
- Hiding information the current task genuinely needs in the name of looking simple, and asking users to recall it instead
Tradeoff
Reducing extraneous load usually means the interface must carry more state and display cost — retaining input history, redisplaying information, or providing defaults. That takes interface space and development effort, but frees the user's mental resources for the task itself.
Conditional rules · Editorial advice
Related entries
Making options visible so people recognize rather than recall is one concrete mechanism for lowering this part of extraneous load — it is not cognitive load itself.
Inconsistent naming and styling force users to repeatedly judge whether something refers to the same thing, which is a removable source of extraneous load; consistency reduces that judgment burden at the source.
Revealing secondary information on demand can reduce the extraneous load of presenting everything at once, without cutting the task itself.
Sources and what they support
Cognitive load is the amount of mental resources required to operate a system; it splits into unavoidable intrinsic load (absorbing new information, tracking one's own goals) and extraneous load that should be minimized (visual clutter that doesn't help understand content); recommends reducing visual clutter, building on existing mental models, and offloading tasks by displaying information or providing defaults instead of relying on user memory.
Retrieved: 2026-09-15 · Archived 2026-09-10Working memory has limited capacity, like an egg carton with few slots; users forget information mid-task not from carelessness but because the interface demands more mental resources than the brain can supply; interfaces should provide external memory (comparison tables, shopping carts, note-taking features) so users can explicitly save and retrieve task information instead of relying entirely on internal recall.
Retrieved: 2026-09-15 · Archived 2026-09-06Short-term memory holds only about 7 chunks of information and these fade within about 20 seconds — but this is the source of a common misconception: limited short-term memory does not mean menus should be limited to 7 items either, because users don't need to memorize the full menu list; menus rely on recognition, not recall.
Retrieved: 2026-09-15 · Archived 2026-09-10Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.
Type extensions and implementation notes
This entry has no interactive specimen yet; the illustration is an editorial sketch. Product use still requires verifying which information genuinely needs continuous display by the interface, which load is an unavoidable part of the task itself, and whether any simplification was validated with real task performance rather than intuition.
{
"evidenceType": "A design interpretation of cognitive-psychology working-memory research and usability literature",
"limit": "This entry does not measure the cognitive load of any specific interface, nor does it prescribe a universal cap on the number of options, words, or steps; capacity figures such as \"7±2\" describe recall tasks and cannot be translated directly into a count limit for interface design."
}Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.