What is cognitive load in interface design?

It is the amount of mental effort an interface demands. Some of that effort is intrinsic to the task, and some is added by how information is presented; good design reduces the added effort.

Is a less dense interface always better?

No. The right density depends on the task. Monitoring and comparison can benefit from higher density, while focused decisions benefit from less on screen.

Why prefer recognition over recall?

Working memory is limited, so requiring users to remember information across screens is costly. Keeping the needed information visible lets them recognize rather than recall it.

← All articles

December 18, 20256 min readcognitive-load, ux, interface-design, usability

Cognitive Load and Interface Density: An Evidence-Based Approach

By Maksym Bardakh · Co-founder & President

In short

Cognitive load is the mental effort a task requires, and interface density is one of the strongest levers over it. The goal is not the sparsest possible screen but the right density for the task: reduce effort that comes from the interface itself, while preserving the information the user genuinely needs to make a decision.

Three kinds of load

Cognitive load theory distinguishes the effort intrinsic to a task from the effort imposed by how information is presented and the effort that goes toward building understanding. The practical reading for interface design is that some load is unavoidable because the task is genuinely complex, and some load is added by the interface and can be removed.

Good design targets the second kind. When a user struggles because a screen is cluttered, inconsistent, or ambiguous, that is effort spent on the interface rather than on the task. Removing it makes the user more capable without making the task itself easier or harder.

Density is a tool, not a vice

A common oversimplification is that less on screen is always better. In reality, density is task-dependent. An expert monitoring many values at once is served by a dense display that puts everything in view, whereas a person making a single fraught decision is served by a sparse screen that removes distraction. The mistake is applying one rule to both.

For comparison and monitoring tasks, higher density can reduce load by keeping relevant data visible together.
For decision and focus tasks, lower density reduces load by removing competing demands on attention.
Hiding information the user needs does not reduce load; it converts visual effort into memory effort.

Working memory is the constraint

Working memory holds only a small amount of information at once, and exceeding it is where interfaces fail. Asking a user to remember a value from one screen to use on another, or to hold several steps in mind while navigating, spends a resource that is in short supply.

A reliable heuristic: keep the information needed for a decision visible at the moment of the decision. Recognition is far cheaper than recall, so showing options beats requiring the user to remember them.

Reduce the load you added

The most actionable version of this work is to find and remove self-inflicted load. Inconsistent patterns force the user to relearn the same action in different places. Unclear labels make the user guess at meaning. Visual noise competes with the content that matters. None of this is intrinsic to the task; all of it is added by the design.

In Flowo we apply this by showing the user only what the current step requires and deferring everything else, so that the screen carries the load for the user instead of demanding the user carry it. The aim throughout is to spend the user’s limited attention on their goal rather than on the interface.

Key takeaways

Cognitive load includes effort intrinsic to the task and effort added by the interface; design targets the latter.
Optimal interface density depends on the task, not on a universal preference for less.
Dense displays help comparison and monitoring; sparse displays help focused decisions.
Keep information needed for a decision visible, since recognition is cheaper than recall.
Most fixable load comes from inconsistency, unclear labels, and visual noise.

Frequently asked questions

What is cognitive load in interface design?: It is the amount of mental effort an interface demands. Some of that effort is intrinsic to the task, and some is added by how information is presented; good design reduces the added effort.
Is a less dense interface always better?: No. The right density depends on the task. Monitoring and comparison can benefit from higher density, while focused decisions benefit from less on screen.
Why prefer recognition over recall?: Working memory is limited, so requiring users to remember information across screens is costly. Keeping the needed information visible lets them recognize rather than recall it.

References

Nielsen Norman Group

About the author

Maksym Bardakh

Co-founder & President

Maksym is a software engineer and product strategist focused on executive-function and behavioral system design. At BBMM he leads product direction across Flowo, TextPack, and Pillow, working at the intersection of human cognition and durable interface design.