Cognitive Load

Cognitive load is the mental effort needed to understand information and carry out a task. In UX, this includes interpreting the interface, remembering details and comparing options while pursuing a goal.

La Oveja Negra /

Cognitive Load

Useful information also takes effort to process. Comparing two products involves understanding differences; an interface should preserve mental resources for that decision.

Problems arise when the system adds work that does not help: ambiguous instructions, hidden details or information people must memorise before switching screens.

What it means

Cognitive load is not equivalent to the number of visible elements. An empty screen can require more interpretation than a structured comparison. There is no universal option limit suitable for every task.

Origin of the concept

Cognitive load theory developed in educational research on problem solving and learning. A 1988 Cognitive Science paper examined that relationship. Interface design uses the concept as a framework for investigating the mental effort of a task; it does not automatically make a complex screen problematic or provide a universal difficulty score.

Application in UX

Keep context visible, use understandable labels and group related information. Support recognising an option rather than recalling a detail shown earlier.

Separate the task’s inherent complexity from work added by the interface. Completing an application may require precise information, but contradictory instructions or changing formats introduce avoidable effort. Preserve entered details when people correct errors and explain each requirement close to the field where it applies.

Application in ecommerce

Total price, availability and delivery conditions should remain available when comparing alternatives. Hiding them does not necessarily simplify shopping: it can move the work into the shopper's memory.

During navigation, filters with understandable labels reduce unnecessary interpretation. At checkout, showing costs and delivery conditions beside the summary supports decisions without reconstructing earlier screens. Evaluation should consider hesitation, repeated lookups and errors; element counts or conversion figures alone do not explain mental effort.

Practical example

Imagine two laptops with different weights and battery lives. A table using matching rows supports comparison without switching between product pages. The hypothesis would be to check whether repeated lookups and errors decrease, rather than assume a conversion improvement.

Common mistakes

Hiding necessary information to achieve a cleaner screen can increase cognitive load. Introducing internal business categories that shoppers do not understand is another problem. Removing options is not always the same as making decisions easier: an excessively limited selection may force people to search elsewhere or prevent a useful comparison.

Related concepts

Explore in the Journal

Explore the topic

Sources