Cutting extraneous load is the primary design lever

What it is

Of the three load types, interface design can only reliably move one: extraneous load. Intrinsic load is set by the task's own complexity, which interface tweaks can't touch; germane load is the part that should be preserved, even protected — pushing it down does harm. So the design goal of "reducing cognitive load" almost always cashes out, in practice, to "find and remove the extra burden added by presentation," not a blanket push to make everything simpler — treating all three types the same and cutting whatever looks like load risks damaging germane load along with extraneous load.

Why it happens

Extraneous load is the one lever design can reliably reach because its very definition is "the part removable at the presentation layer": eliminating it requires no change to what the task demands and no change to the user's skill level — only a change to how information is organized and shown. Moving intrinsic load requires changing task scope or raising user capability, neither of which a single interface pass can accomplish; germane load shouldn't be treated as something to reduce at all. Among the three, extraneous load is the only one where design effort and load reduction have a direct, controllable causal link, which is why it gets prioritized in practice again and again.

Where it stops holding

Once extraneous load is already low and total load is dominated by the intrinsic component, further presentation-layer "polish" stops paying off — this doubles as a practical signal for when to stop iterating on visuals: if several rounds of presentation adjustments fail to reduce reported difficulty, the problem has likely moved past the extraneous layer, and effort should shift to task decomposition or user training. Another common trap is treating germane load as if it were extraneous and cutting it too — removing all guiding hints and explanatory text makes operation faster in the short run but damages the user's chance to build understanding over time, which is the easiest way to over-optimize.

Applying it

During design review, ask of every element whether the task itself requires it: if not, it's likely a removable source of extraneous load — related information scattered across screens, the same fact expressed redundantly in multiple forms, decoration or motion unrelated to the task, unnecessary mode switches. A concrete extraneous-load checklist for the interface at hand, worked through item by item, keeps this systematic. Verification: after removing each checklist item, re-measure completion time and error rate on the same batch of tasks to confirm real improvement; also check a transfer task to make sure content that helps users build understanding wasn't accidentally cut — if transfer-task performance drops, what was removed was actually germane load, not extraneous load, and should be restored.

Related

• Same group: A9.01.1 intrinsic load comes from the task's own complexity · A9.01.2 extraneous load comes from presentation and can be designed away · A9.01.3 germane load builds understanding and shouldn't be driven to zero
• Nearby: A9.06 intrinsic, extraneous and germane load (the shared-capacity mechanism behind the three types)
• Search terms: extraneous load reduction · cognitive load theory design implications