# Avoid Cognitive Overhead: Spend Less Effort on the Interface

> Learn how to design screens so people spend their limited thinking power on their goal, not on decoding the screen.

**In short:** Cognitive overhead is mental effort spent decoding the interface, and good design cuts it so people use their limited thinking power on their goal.

From "UI/UX basics", a free course by Venkat R. Murty: https://designervenkat.online/learn/ui-ux/avoid-cognitive-overhead

## What you will learn

Every screen asks something of the person using it. It asks them to read, to find the right button, to remember a detail from earlier, and to choose. Some of that work helps the person reach their goal. Some of it gets in the way. Designers call the second kind cognitive overhead.

This lesson shows you how to spot that extra work and remove it. You will see why mental effort is limited, where overhead usually comes from, and how a checkout page can be made lighter. Two short quiz scenarios at the end let you test the idea on new screens.

- **Cognitive overhead:** Extra thinking a screen forces on a user that the user's goal does not need.
- **Cognitive load:** The total mental effort a person spends to understand and use a system.
- **Working memory:** The small space in your mind where you hold and handle information for a short time.
- **Recognition:** Seeing a cue on the screen and knowing what it is.
- **Recall:** Pulling something from memory with no help from the screen.
- **Jargon:** Specialist words that only people inside a field understand.
- **Convention:** A pattern people already expect, such as a menu bar across the top of a page.
- **Heuristic:** A rule of thumb for judging a design. It is a guide, not a law.

## Why is mental effort limited?

Cognitive load is the mental effort a person spends to understand an interface and work out what to do next. The idea comes from cognitive psychology, the study of how people think and remember. Researchers there found that working memory is surprisingly limited. Psychologist George Miller's landmark 1956 study is the classic reference for that limit, though later research challenges his roughly seven-item figure and puts the central capacity at about four chunks.

Working memory is the bottleneck. When a screen uses part of it, less is left for the task. The Nielsen Norman Group, a well-known UX research firm, informally calls this limited pool brainpower. Whatever the interface uses up is no longer available for the job the user came to do. That is why every extra element, term or step on a screen competes with the user's real goal.

### What are the three kinds of load?

Researchers commonly sort cognitive load into three kinds, though the third kind, germane load, was added to the theory later and remains debated. Your job as a designer is to keep the useful kinds and cut the rest.

- **Intrinsic load:** The effort that comes from the task itself. Some of it is fine, because people come to a site to get something done.
- **Extraneous load:** The effort the design adds. It eats attention and gives nothing back. This is the kind to cut.
- **Germane load:** The useful effort of learning something new, such as understanding how a new feature works.

> **Tip:** Ask of each element on a screen: does this help the task, or does it only add something to figure out? Only the second kind is overhead.

## Where does overhead come from?

Overhead usually comes from a few repeated mistakes. Watch for these when you review a screen.

- **Visual clutter:** Too many options, pictures and messages compete for attention. People then struggle to know where to look first.
- **Jargon and unclear icons:** Technical terms and symbols that only insiders know make people stop and decode. Use the words your user already uses.
- **Inconsistent patterns:** If a menu or button works differently from screen to screen, people must relearn the rules each time.
- **Forced memory:** If a detail from an earlier screen must be remembered to finish a later one, the user is doing a job the screen should do for them.
- **Unnecessary steps and fields:** Every field or step the task does not need is extra work, and one more place where someone might quit.

## What are five ways to cut overhead?

The fixes below follow one simple rule: keep what the user needs, show it where they need it, and make the rest easy to ignore.

1. **Remove or defer what is not essential:** Keep only the content the task needs. Strip out ads, decorative motion and extra messages. If something is useful but not urgent, move it to a later screen or to a help link.
2. **Use familiar conventions:** Use patterns people already know, such as a menu bar. Familiar layouts are quick to read, so people do not have to stop and work them out.
3. **Show information where it is needed:** Put the cue next to the place where the user acts. A form can show the required format beside the box, instead of asking people to remember the rule.
4. **Group related items:** Use spacing, borders or background colour to put related things together. People then read a group as one unit instead of many separate pieces.
5. **Use plain language:** Write labels, errors and messages in words the user knows. Say what happened and what to do next, and leave out system terms.

The next two sub-topics explain the two fixes that people most often get wrong.

### Why choose recognition over recall?

Recognition means seeing a cue and knowing what it is. Recall means pulling the same thing from memory with no help. Recognition is easier. Jakob Nielsen, a usability researcher, listed recognition rather than recall as one of his ten usability heuristics. Recognition is easier than recall, which helps cut memory load on a screen.

> **Tip:** Test a screen by asking: if the user looks away, would they have to remember a name, a code or a setting from another page to continue? If yes, move that detail onto the current page.

### Why use plain language?

Plain words are part of the same fix. Your user's language is the one that counts, not the language of the system behind the screen. Use everyday terms first. If a technical term must stay, explain it right next to it.

## Worked example: a checkout page

A checkout is a good test. The shopper has already decided to buy, so every extra hurdle is a chance to quit. Checkouts that pile on upsells, unexplained fees and long forms with no progress indicator are a familiar problem. The comparison below uses a made-up cluttered page that combines these problems, next to a streamlined version modelled on Shopify's checkout.

### The cluttered version

The cluttered page does three things at once. It asks the shopper to create an account before paying. It shows promotional banners beside the form. It puts every field into one long form. The shopper must decide about the account, ignore the banners and keep track of their place in a long scroll. Each of these adds overhead, and none of it helps the shopper buy the item.

### The streamlined version

1. **Break the flow into clear steps:** A common checkout splits the task into three steps: contact details, shipping and payment. A step indicator at the top, such as Contact, Shipping and Payment, tells the shopper where they are.
2. **Keep the order summary in view:** The shopper never has to remember what is in the basket.
3. **Ask only for what the order needs:** Every field that is not needed is removed.
4. **Explain optional fields in place:** The shopper can decide without leaving the page.
5. **Remove distracting links:** Take out links and banners that lead away from the purchase.

A fair note: splitting a checkout into steps is not automatically better. The right layout depends on the purchase.

> **Tip:** When you review a checkout, ask: what must the shopper remember when they reach the payment step? Every item on that list is a candidate for a fix.

## Check your understanding

Try these two short scenarios. Each one needs the idea, not just a memory of the text above.

**Quick check:** A budgeting app's transfer screen has eight fields, two promotional banners, and the technical term 'ACH initiation' with no explanation. Users keep abandoning it. Which change would reduce cognitive overhead, and why?

A. Add a third promotional banner that explains the transfer rules, so users understand the process before they start.
B. Remove both banners, ask only for the fields the transfer needs, and replace the term with plain words and a short explanation beside it.
C. Keep all eight fields and change the button colour, so the form looks more polished.
D. Move the eight fields to a second screen without changing anything else, so each screen looks lighter.

**Answer:** B. The banners compete for attention, so removing them cuts clutter. Asking only for needed fields removes steps the user must work through. Plain words replace a term most users cannot decode. Adding content or changing looks does not remove any of the work, and splitting the fields across screens keeps the same work in place.

**Quick check:** On a travel booking app, the user picks a flight on screen one. On screen three, they must type the flight number again, because it is no longer shown. What change best reduces cognitive overhead?

A. Ask the user to write the flight number on paper before they start booking.
B. Show the chosen flight and its number on the screen where the user enters details, so they can see it instead of recalling it.
C. Add a help article about flight numbers that users can search when they get stuck.
D. Add a short animation when the user moves from screen one to screen three.

**Answer:** B. Recognition is easier than recall. Showing the flight on the current screen gives a visible cue, so the user does not have to carry a detail across screens. A help article still makes the user do extra work, and an animation does not change what must be remembered.

## Key takeaways

Mental effort is scarce. Every label, term, step and field on a screen either helps the person finish or uses up some of their limited attention. Your job is to keep the first kind and remove the second.

Check each screen with three questions. What is not essential? What must the user remember from somewhere else? Which words or patterns make them stop? Fix those first, then test the screen with a real person.

> **Tip:** Use these fixes as a checklist, not as a rule to strip every element. Some effort belongs to the task itself, and the goal is to leave that effort in place.

## Sources

- [Equinet Academy: Cognitive Load in UX, How to Design Simpler Experiences](https://www.equinetacademy.com/blog/cognitive-load-in-ux-how-to-design-simpler-experiences/)
- [Inside UX Design: Cognitive Load, Why Less Is Often More in Interface Design](https://www.insideuxdesign.com/en/blog/cognitive-load-why-less-is-often-more-in-interface-design)
- [Master CAWEB: Designing for Cognitive Load](https://mastercaweb.unistra.fr/en/actualites/ux-ui-design-en/designing-for-cognitive-load/)
- [Orbix Studio: What Is Cognitive Load in UX Design? 7 Ways to Reduce It](https://www.orbix.studio/blogs/cognitive-load-in-ux-design)
- [4 Principles for Designing User Interfaces That Reduce Cognitive Load (adaptation of a Nielsen Norman Group article)](https://medium.com/@mfaridshad/4-principles-for-designing-user-interfaces-that-reduce-cognitive-load-cae6048c5dff)
- [uxcel: 10 Usability Heuristics by Jakob Nielsen](https://uxcel.com/lessons/usability-heuristics-270)
- [The Decision Lab: Nielsen's Heuristics](https://thedecisionlab.com/reference-guide/design/nielsens-heuristics)
- [UX UI Principles: Recognition Rather Than Recall Heuristic](https://uxuiprinciples.com/en/principles/recognition-rather-than-recall)
- [UX Design Collective: Jakob Nielsen's sixth usability heuristic](https://uxdesign.cc/jakob-nielsens-sixth-usability-heuristic-for-user-interface-design-ac88e7d58ec?gi=9ebe43ead08a)
- [Wikipedia: Heuristic evaluation](https://en.wikipedia.org/wiki/Heuristic_evaluation)
- [Shopify: Checkout Pages, Examples and Best Practices](https://www.shopify.com/enterprise/blog/checkout-pages)
- [Shopify Developers: checkout.liquid layout](https://shopify.dev/themes/architecture/layouts/checkout-liquid)
- [Oneonic: Shopify Checkout Design Guide](https://oneonic.com/shopify-checkout-design-guide/)
- [Shopify: How To Improve the Checkout Experience in 11 Steps](https://www.shopify.com/enterprise/blog/44326851-designing-the-new-customer-experience-what-happens-after-checkout)
