Cognitive Load
Cognitive load is the amount of mental effort needed to understand and use an interface; when it exceeds what people can handle, they slow down, make mistakes or give up.
Key takeaways
- Remove extraneous load: decoration, jargon and choices that don't help the task.
- Spread unavoidable complexity across steps instead of front-loading it.
- Rely on recognition (visible options) rather than recall (remembering what to type).
Origin
Cognitive Load Theory was developed by educational psychologist John Sweller in the late 1980s, building on research into the limits of working memory. It distinguishes intrinsic load (the task itself), extraneous load (how it's presented) and germane load (effort that builds understanding).
How to apply it
- Remove anything that does not help users complete the current task: extra fields, decorative clutter and redundant options.
- Use familiar patterns and conventions so people do not have to learn new interactions.
- Show information when it is needed (progressive disclosure) rather than everything at once.
- Prefer recognition over recall: display options, history and context instead of asking users to remember them.
- Write short, plain-language labels and instructions, and offload calculations and comparisons to the system.
How Science of Apps uses this law
5 checks in every investigation rely on Cognitive Load, for example: “Do charts, scores and components have titles, legends and units so users know what they're looking at?”
Get your product investigated