Skip to main content

Cognitive Load

A UX concept for understanding the mental effort required to use information, interfaces, and service journeys.

Reference entry content

Concept facts

Cognitive load is the mental effort required to understand information, make decisions, remember details, and complete an interaction.

Also known as
Mental effort, mental workload, interface complexity.
Used in
Content design, form design, navigation review, onboarding, dashboards, and decision-heavy service flows.
Interpret with
Task success, time on task, errors, accessibility, information architecture, and user context.

Plain-language explanation

Cognitive load increases when users must hold too much information in memory, decode unfamiliar language, make unclear choices, or recover from avoidable confusion.

Reducing cognitive load does not mean removing all complexity. It means presenting complexity in a way people can understand and act on.

Why it matters

High cognitive load can make digital services harder for people with limited time, stress, low digital confidence, unfamiliar language, assistive technology needs, or high-stakes decisions.

Use contexts

  • Long or conditional forms.
  • Eligibility and application journeys.
  • Navigation and content-heavy portals.
  • Transaction confirmation and review screens.

Application guidance

Use clear labels, progressive disclosure, meaningful grouping, useful defaults, plain language, and strong feedback. Test whether people can understand what to do without holding too much in memory.

Practical example

A rural identity verification system asks local officers to compare paper records, biometric capture status, address history, and household relationship data before approving a case.

The interface shows all data fields on one dense screen without grouping or decision support. Officers can complete the task, but the high cognitive load increases the chance of overlooking mismatched records, especially during peak service hours.

Interpretive boundaries

  • Cognitive load should not be used as a vague synonym for “bad design.”
  • Some complexity belongs to the domain and must be explained, not hidden.
  • Cognitive load cannot always be reduced without simplifying the underlying domain structure.
  • Cognitive-load claims need careful source support.
  • Accessibility, language, literacy, and stress can change how effort is experienced.

Applied at Userhub

Cognitive load is relevant when Userhub reviews whether complex digital-service journeys are understandable and manageable for real users.

Sources and references

  • Sweller, J. (1988). Cognitive load during problem solving: Effects on learning. Cognitive Science, 12(2), 257-285. https://doi.org/10.1207/s15516709cog1202_4
  • Miller, G. A. (1956). The magical number seven, plus or minus two: Some limits on our capacity for processing information. Psychological Review, 63(2), 81-97. https://doi.org/10.1037/h0043158
  • Card, S. K., Moran, T. P., & Newell, A. (1983). The Psychology of Human-Computer Interaction. Lawrence Erlbaum Associates.
  • Paas, F., Tuovinen, J. E., Tabbers, H., & Van Gerven, P. W. (2003). Cognitive load measurement as a means to advance cognitive ergonomics. Theoretical Issues in Ergonomics Science, 4(1-2), 63-71. https://doi.org/10.1080/14639220210159513

Cite this entry

APA

Userhub. (2026). Cognitive Load. UX Reference. https://userhub.com.bd/reference/cognitive-load/