Extraneous load comes from presentation and can be designed away
Aliases: extraneous load · split-attention effect · redundancy effect
What it is
Extraneous load is the processing burden added by presentation, layout, or interaction flow — things that don't belong to the task itself: splitting information that should be viewed together across screens, unnecessary animation pulling attention away, opaque icons standing in for plain text. None of this serves understanding the task; it's cost bolted on from outside, which is exactly why it can be sharply reduced or eliminated by redesigning presentation, unlike intrinsic load. The test for whether a burden counts as extraneous: if a clearer presentation makes it drop while the task itself gets no simpler, it was extraneous.
Why it happens
The typical source is an extra processing step introduced by presentation. The best-known case is the split-attention effect: related pieces of information are separated in space or time, forcing the user to jump back and forth and integrate them mentally — that integration work is pure overhead, since the actual information required by the task hasn't changed. Another source is the redundancy effect: the same content repeated in multiple forms forces extra work reconciling which version to trust, adding load instead of reducing it. Neither burden is required by the task; both come from presentation choices, so integrating related information into one view and removing duplicate expressions eliminates them directly, without touching what the task demands.
Studying it
The main paradigm is the split-attention experiment: content and task steps stay identical, only presentation changes — one condition integrates related information in space/time, the other splits it apart and requires the user to cross-reference across screens or sections; learning outcome or task performance is then compared. Typical independent variables are whether information is integrated and whether redundant forms exist; dependent variables are completion time, error rate, and performance on later transfer tasks. In interface research this is used to check whether a given presentation scheme adds burden on its own. The methodological catch: intrinsic load (task content and step count) must be held identical across conditions, or the measured gap can't be attributed to extraneous load alone.
Where it stops holding
There's a floor to how much extraneous load can be removed: once presentation is already well integrated and redundancy is cleaned up, remaining load is mostly intrinsic, and further "simplification" stops paying off — it can even damage content that was actually necessary, such as removing all explanatory text to shorten the steps, which leaves users less able to build an understanding of the system — that text was doing work that helps understanding form, so it counts as load worth keeping rather than surplus to be cut. The same presentation also produces unequal extraneous load across users: a repeated hint that helps a novice can become pure interference for someone already fluent with the interface, so the same design carries different load depending on expertise.
Applying it
When auditing an interface, put information that belongs to the same decision into one view instead of requiring cross-screen or cross-window comparison; remove duplicate expressions of the same fact (when an icon and adjacent text say the identical thing, keep only one); cut visual decoration and motion that isn't tied to the task. A concrete audit checklist for a given interface works well: separated information sources, redundant expressions, unrelated animation, unnecessary mode switches. Verification: change only the presentation while keeping the number of task steps fixed, then compare completion time and error rate across versions; if the more integrated version is clearly faster and more accurate, the original design did carry removable extraneous load.
Related
- Same group: A9.01.1 intrinsic load comes from the task's own complexity · A9.01.3 germane load builds understanding and shouldn't be driven to zero · A9.01.4 cutting extraneous load is the primary design lever
- Nearby: A9.06 intrinsic, extraneous and germane load (shared-capacity mechanism of the three types)
- Search terms:
extraneous cognitive load·split-attention effect·redundancy effect