mid · lesson 6 of 7

Cognitive load

Chunking, defaults, Miller’s rule.

Sidhanshu Monga·1 min·
You’ll be able to
  1. Recognise what makes an interface mentally expensive
  2. Reduce load with chunking, defaults and recognition
  3. Use "Miller's rule" correctly

Every interface asks users to think. Cognitive load is how much: holding information in mind, making decisions, working out what something means. Lower load means faster, calmer, less error-prone use.

Working memory is small

George Miller's 1956 paper "The Magical Number Seven, Plus or Minus Two" is often cited as a rule that menus should have seven items. That's a misreading: the paper was about how much people can hold in short-term memory, and later research by Nelson Cowan (2001) suggests the limit is closer to about four chunks. The practical lesson isn't a magic number. It's that people can't hold much in their heads, so the interface should hold it for them.

Chunking

Group related information into meaningful chunks: a phone number split into groups, a form split into sections, a long list grouped by date. Chunks are easier to scan and remember than flat lists.

Recognition over recall

Showing options is easier than asking people to remember them. Recent items, autocomplete, visible labels and previews let users recognise what they want instead of recalling it. This is one of Nielsen's ten usability heuristics.

Defaults and fewer decisions

Every choice costs effort. Choose good defaults, remove options that rarely matter, and use progressive disclosure for the rest. Consistency helps too: once a pattern is learned, it costs nothing to reuse.

Remove noise

Decorative elements, competing calls to action and dense text all compete for attention. Each element should earn its place on the screen.

Try it

Take the longest form or settings page in your product. Group related fields, add sensible defaults, and move anything optional behind a disclosure. Count how many decisions a typical user now has to make.

This lesson needs a hands-on exercise. The idea is sketched in issue #67. Build it and it ships here, with your name on it.
Key takeaways
01Working memory is small; don't make users hold things in it
02Recognition beats recall
03Defaults are decisions you make so users don't have to