Memory & attention

Cognitive Load

Cognitive load is the amount of mental effort needed to understand and use an interface; when it exceeds what people can handle, they slow down, make mistakes or give up.

Core · User Behaviour & Decision System2 research sources
Share
A mind's capacity gauge pushed into the red by stacked blocks of information — an illustration of Cognitive Load.

See it in action

The same screen without and with Cognitive Load. Watch both sides play out, then compare the outcome.

Everything at onceCheckoutFull nameAddress line 1Address line 2CityPINGSTIN (optional)Card numberExpiry / CVVMental effortFeels like work — many abandon

Eight fields, mixed topics and jargon at once: the effort shows up as hesitation and abandonment.

One focused stepDeliveryStep 1 of 3NameAsha RaoAddress (we'll fill the rest)12 MG Road, Bengaluru 560001ContinueMental effort

One topic per step, smart defaults and plain words keep effort low and momentum high.

What to watch: the effort meter — same information collected, very different mental cost.

Do

Remove, defer or automate anything not essential, and ask for one kind of thing at a time.

Don’t

Strip out information people need — reducing load means less noise, not less help.

Key takeaways

  • Remove extraneous load: decoration, jargon and choices that don't help the task.
  • Spread unavoidable complexity across steps instead of front-loading it.
  • Rely on recognition (visible options) rather than recall (remembering what to type).

Quick facts

Also known as
—
Described by
John Sweller
Year
1988
Category
Memory & attention

Cognitive Load explained

Cognitive load is the total amount of mental effort required to use an interface. Every label to read, decision to make, item to remember and visual element to filter out draws on the same limited pool of attention and working memory.

Psychologists distinguish intrinsic load (the inherent difficulty of the task), extraneous load (effort caused by how the information is presented) and germane load (effort that builds understanding). Designers cannot remove the intrinsic difficulty of filing taxes, but they can remove a great deal of extraneous load.

When load exceeds capacity, people slow down, make mistakes, miss important information or give up. That is why reducing unnecessary load is one of the most reliable ways to improve activation and conversion.

Where it comes from

Cognitive Load Theory was developed by educational psychologist John Sweller in the late 1980s, building on research into the limits of working memory. It distinguishes intrinsic load (the task itself), extraneous load (how it's presented) and germane load (effort that builds understanding).

How it shows up in apps

Overloaded onboarding is one of the most common reasons new users never reach their first moment of value. Every extra field, unexplained term or competing call-to-action adds extraneous load right when motivation is most fragile.

Cognitive Load examples

A banking app's first screen asks for income, goals, risk tolerance and notification preferences at once. Moving all but one question to later, in context, lets users reach their dashboard and start using the product.

  • Forms that ask only what is needed

    Removing optional fields, using smart defaults and auto-detecting city from postcode reduces the effort of a sign-up form and increases completion.

  • Dashboard overload

    An analytics home screen with 20 equal-weight charts forces users to work out what matters. Leading with three key metrics and moving the rest to detail views makes insights obvious.

  • Recognition instead of recall

    Showing recently used files, saved addresses and previous searches lets people recognise options instead of remembering them, cutting load on repeat tasks.

How to apply Cognitive Load

  1. Remove anything that does not help users complete the current task: extra fields, decorative clutter and redundant options.
  2. Use familiar patterns and conventions so people do not have to learn new interactions.
  3. Show information when it is needed (progressive disclosure) rather than everything at once.
  4. Prefer recognition over recall: display options, history and context instead of asking users to remember them.
  5. Write short, plain-language labels and instructions, and offload calculations and comparisons to the system.

Want Cognitive Load checked in your own product? Our mobile app ux audit evaluates it alongside the other principles that shape how users decide, onboard and stay.

Common mistakes

  • Oversimplifying by hiding essential information, which forces users to search for it and adds load elsewhere.
  • Assuming that because the team understands a screen, new users will too; experts underestimate load for novices.
  • Adding tooltips and help text to explain a complex design instead of simplifying the design itself.

How to measure it

Track task completion rates, time on task and error rates, and ask a single ease question after key tasks. The NASA-TLX questionnaire measures perceived workload in research settings. In analytics, rage clicks, repeated back navigation and drop-off on dense screens are strong signs of overload.

Frequently asked questions

What is Cognitive Load?

Cognitive load is the amount of mental effort needed to understand and use an interface; when it exceeds what people can handle, they slow down, make mistakes or give up.

Where does Cognitive Load come from?

Cognitive Load Theory was developed by educational psychologist John Sweller in the late 1980s, building on research into the limits of working memory. It distinguishes intrinsic load (the task itself), extraneous load (how it's presented) and germane load (effort that builds understanding).

How does Cognitive Load apply to app design?

Overloaded onboarding is one of the most common reasons new users never reach their first moment of value. Every extra field, unexplained term or competing call-to-action adds extraneous load right when motivation is most fragile.

What are the three types of cognitive load?

Intrinsic load comes from the inherent complexity of the task, extraneous load from how information is presented, and germane load from the effort of building understanding. UX design mostly reduces extraneous load.

How do you reduce cognitive load in an app?

Remove unnecessary elements, use familiar patterns, break tasks into steps, show information only when relevant, use clear language and let the system remember and calculate for the user.

How do you measure Cognitive Load in a product?

Track task completion rates, time on task and error rates, and ask a single ease question after key tasks. The NASA-TLX questionnaire measures perceived workload in research settings. In analytics, rage clicks, repeated back navigation and drop-off on dense screens are strong signs of overload.

Sources

  1. Sweller, J. (1988). Cognitive load during problem solving: Effects on learning. Cognitive Science, 12(2). Find on Google Scholar ↗
  2. Sweller, J., van Merriënboer, J. J. G. & Paas, F. (1998). Cognitive architecture and instructional design. Educational Psychology Review, 10(3). Find on Google Scholar ↗

View all 60 laws of UX

Keep exploring

Cognitive Load in practice

Keep exploring

Certifications that test it

Pass it on

Teach this to your team

Share it before your next design review — a shared vocabulary makes product decisions faster.

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free certification

Can you apply Cognitive Load under pressure?

Test it in 18 real product scenarios in the free Product Design Science test. Score 70% and earn a founder-signed certificate anyone can verify.

  • Credential ID
  • QR verification
  • LinkedIn-ready
Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 74 pages

Get Laws of UX by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy

Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free. No card, no paywall — just your email.
Free PDF · 90 pages

Get 100+ Paywalls, Decoded by email

Choose your edition

You’ll also get occasional UX psychology tips. Unsubscribe anytime. Privacy policy