Marcus Andrey Study
Ler em português Library

UX Foundations · Step 3 · 4 min read

How people think

A few facts about human attention and memory explain most usability problems. Mental models, cognitive load, recognition versus recall, Hick's and Fitts's laws, and why "seven, plus or minus two" is usually misused, with what each one means for a screen.

A shape-sorter box: each block only fits its own hole, as a design only fits when it matches what people expect. Four holes, one for each lesson: how people think, interviews, usability tests and heuristics. Point at a hole and its block drops in. Illustration: Marcus Andrey, drawn with Hairline (MIT, Lucas Marques).

People don't read interfaces; they guess, based on what they already know. They have a few seconds of attention, a small working memory and a lifetime of habits from other products. You can't change any of that. Good design works with it: it shows what people expect where they expect it, asks them to remember as little as possible, and makes the next step easy to hit.

What you'll be able to do after reading:

  • Explain mental models and why they matter more than your design
  • Spot cognitive load and reduce it
  • Prefer recognition over recall in your designs
  • Use Hick's and Fitts's laws, and avoid the "7 ± 2" myth

1. Mental models

"A mental model is what the user believes about the system" (NN/g, Chan, Mental Models, 2024). Not what the system is, but what people believe it is, formed by every similar product they've used. When your design matches that belief, it feels obvious; when it doesn't, it feels broken, even if it's logical.

This is why conventions matter. Jakob's Law, as Laws of UX puts it: users spend most of their time on other sites, so they expect yours to work the same way (Laws of UX, Jakob's Law).

A lift panel with two identical EG buttons side by side, an OG button lit in red, and key switches with tiny labels.
Two buttons both say EG: which one takes you out? When labels don't match what people expect, every choice costs thought, and some people press the wrong one. Photo: Karen Mardahl, cropped, Wikimedia Commons, CC BY-SA 2.0.

2. Cognitive load and memory

1Attention is short

People scan; they rarely read everything.

Put the key thing first
2Memory is small

Working memory holds only a few chunks.

Group; don't make them remember
3Habits are strong

People expect what other products taught them.

Follow conventions
4Effort adds up

Every extra choice and label costs a little.

Remove what doesn't help
Four limits of the human mind that most usability problems come from. Diagram: Marcus Andrey, CC BY 4.0.
  • Cognitive load is the mental effort an interface demands. Some is needed to do the task; the rest is waste: clutter, unclear labels, things to remember (NN/g, Whitenton, Minimize Cognitive Load, 2013).
  • Recognition beats recall: "Recalling items from scratch is harder than recognizing the correct option in a list of choices" (NN/g, Budiu, Memory Recognition and Recall, 2024). Show options, recent items and examples instead of asking people to remember.
  • The "7 ± 2" myth: George Miller's 1956 paper was about short-term memory in experiments, not about how many items a menu may have. Laws of UX warns: "Don't use the "magical number seven" to justify unnecessary design limitations" (Laws of UX, Miller's Law). Later research suggests working memory holds closer to four chunks (Cowan, 2001). Group information; don't count it.

3. Hick's law and Fitts's law

  • Hick's law (Hick, 1952; Hyman, 1953): the more options people have, the longer they take to decide (Laws of UX, Hick's Law). It applies to simple choices; it doesn't mean "fewer options are always better" when people know what they want. Use it to reduce options at key moments, and to highlight a recommended one.
  • Fitts's law (Fitts, 1954): the time to hit a target depends on its size and distance. Bigger, closer targets are faster and safer to hit (NN/g, Budiu, Fitts's Law and Its Applications in UX, 2022). That's why primary buttons are large and destructive ones are kept away from common actions.

4. Common mistakes

  • Designing for your own mental model, because you built the system.
  • Breaking a convention without a strong reason.
  • Asking people to remember codes, steps or rules from one screen to the next.
  • Quoting "7 ± 2" to limit a menu.
  • Small, crowded tap targets on phones.

5. Vocabulary

Term Meaning
Mental model What a person believes about how a system works
Convention A design pattern people already know from other products
Cognitive load The mental effort an interface demands
Recognition vs recall Picking from what you see vs remembering from scratch
Hick's law More choices, slower decisions
Fitts's law Bigger, closer targets are faster to hit

6. Try it (no tools needed)

  1. Pick a screen you use often (a ticket machine, a settings page).
  2. Find one place where it asks you to remember something, and redesign it on paper so you recognise instead.
  3. Find the most important button. Is it the biggest and easiest to reach? Sketch a version where it is.

Reflection questions: Where did a product surprise you because it broke your mental model? Was the new way actually better?


7. If you already practise

  • In critiques, name the principle: "this asks for recall", "this target is far from the thumb". It turns taste into reasons.
  • Test with people new to the product to see their mental models; experts have already adapted to your quirks.
  • Jon Yablonski's Laws of UX (O'Reilly, 2nd edition 2024) collects these principles with design examples.

Checklist

Learn more

Books, courses and videos to go deeper

Short user interviews · Heuristic evaluation · What UX design is (and isn't) · Users, tasks and context · Expert-user efficiency

Saved only on this device.

↑ ↓ to move · Enter to open · Esc to close