# Cognitive load is three things, not one

> Most design principles treat cognitive load as a single dial to turn down. It isn't. CLT has three sources that behave differently — and reducing the wrong one makes a screen worse.

Source: https://www.thedesignagent.ai/field-notes/cognitive-load-is-three-things · Concepts · 2026-05-06

Most design principles treat cognitive load as a single dial. More complexity equals bad; less equals good. Reduce elements, simplify the layout, cut the features. This framing is both true and useless — true because load matters, useless because it treats all load as the same thing.

Cognitive Load Theory distinguishes three sources of mental effort. They don't just differ in name. They differ in cause, in whether they're worth reducing, and in what actually helps. Confuse them and you'll strip a screen of the friction it needed while leaving the friction it didn't.

## Intrinsic load: the task itself

Intrinsic load is the cognitive work the task inherently requires. Reviewing twenty reorder recommendations is intrinsically complex — there are twenty decisions to make, each with a confidence signal, a quantity, and a reasoning thread. No layout change eliminates that complexity. The job has twenty decisions; the user has to make twenty decisions.

This matters because intrinsic load is often mistaken for a design problem. Agents and designers reach for simplification when the task is actually just hard. The right response to high intrinsic load isn't to hide information — it's to structure it so the user can work through it without losing their place. Sequence, grouping, and chunking reduce the effort of navigating a complex task. They don't reduce the task.

## Extraneous load: friction the interface adds

Extraneous load is the cognitive cost of the interface itself — the effort that has no relationship to the job. A modal that interrupts a batch workflow adds extraneous load. A table that requires four clicks to get to the action adds extraneous load. A confirmation dialog for a low-stakes action that takes three seconds to undo adds extraneous load.

This is the load worth eliminating. It contributes nothing and costs focus. In high-throughput jobs — warehouse operators, support queues, anything with a batch cadence — extraneous load is fatal. It compounds across repetitions. Twenty interruptions per hundred rows isn't a minor friction; it's an hour of lost throughput per shift.

> **Pattern:** extraneous load is the only load worth eliminating unconditionally. Intrinsic load is the job; germane load builds the mental model. Extraneous load is just overhead.

## Germane load: the load that builds understanding

Germane load is the cognitive effort that produces something. Learning a workflow, building a mental model of how prices relate to inventory, understanding what a confidence score means — these require effort, but the effort is the point. Spent once, it pays off in speed every time after.

This is the load designers most commonly destroy by accident. Onboarding flows that over-explain every step, empty states that narrate exactly what to do, tooltips that activate on hover — these feel helpful but prevent the user from developing the model that would actually make them fast. Good germane load investment upfront produces expert users. Good intentions with bad execution produce users who are always dependent on the scaffolding.

## How agents misread the signal

Agents optimize for visible complexity. A screen with twenty rows, inline actions, a confidence column, and a reasoning toggle looks heavy. An agent flagged on "simplicity" will collapse the reasoning into a click, move the actions behind a modal, and add tabs to reduce visible row count. The screen is now simpler-looking and worse. The intrinsic load (twenty decisions) hasn't changed. The extraneous load has increased. The germane load for learning the pattern has been replaced with re-scaffolding via modals.

The misread happens because agents — like most tooling — can see layout complexity but can't see load type. They can count elements. They can't distinguish intrinsic from extraneous.

## How TheDesignAgent scores it

The `/ux` lens scores four dimensions. Three of them map directly to this framework: `intrinsic_load`, `extraneous_load`, `germane_load`. A low score on `extraneous_load` means the interface is adding overhead the job doesn't require. A low score on `germane_load` means the interface is either preventing model-building or front-loading expertise it should be developing.

These scores don't average into a single "load" number. A screen can score well on intrinsic and germane while failing hard on extraneous — that's the modal reflex pattern. A screen can score well on all three while failing on `jtbd_alignment` — the job is wrong even if the load is managed well.

The distinction is what makes the score actionable. "Reduce cognitive load" is too vague to patch against. "Collapse the modal — it's adding extraneous load on a batch workflow" is a patch.
