Recognition rather than recall

A product should reduce what people have to remember by keeping objects, actions and options visible, so they can recognize what they need instead of recalling it from memory.

Last reviewed

On this page

The law

A product should reduce what people have to remember by keeping objects, actions and options visible.

Recognizing something you see is much easier than recalling it from memory with no cue. Every time a product asks people to remember a code, a command or a value from another screen, it spends their limited working memory.

Where it comes from

This is the sixth of Jakob Nielsen's ten usability heuristics, published in their current form in 1994. Nielsen Norman Group's article on recognition and recall explains the memory research behind it and how it applies to menus, forms and navigation.

Psychologists have long found that recognition outperforms recall: people asked to pick a word from a list do far better than people asked to produce it. Graphical interfaces were built partly on this finding, replacing typed commands people had to remember with menus they could scan.

What it means for an interface

  • Show options instead of asking for them. Menus, suggestions and recent items let people pick rather than remember.
  • Carry information forward. If people need a value from an earlier step, such as an order number, show it where it is needed.
  • Keep context on screen. Labels that stay visible while typing, and summaries of earlier choices, remove the need to remember them.
  • Offer history. Recent searches, recently viewed items and saved filters turn repeat tasks into recognition.

Examples

Search with recent queries. A search box that shows recent queries when focused lets people repeat a search with one tap instead of retyping it.

Placeholder labels. A form that uses placeholder text as the only label makes people remember what each field was for once they start typing. A visible label keeps it in view.

Checkout summaries. A final checkout step that repeats the address, delivery option and items lets people confirm by recognition instead of recalling what they chose three steps ago.

Where it is misapplied

  • Showing everything. Recognition does not mean displaying every option at once. Too many visible options slow people down; prioritize.
  • Hiding everything behind icons. An unlabeled icon must be recalled; a labelled one can be recognized.
  • Ignoring experts. Power users often prefer recall, such as typed commands, because it is faster once learned. Offer both.
  • Stale history. Recent items that are no longer relevant clutter the view instead of helping.

Checklist

  • People never need to copy information from one screen to use on another.
  • Form labels remain visible while people type.
  • Important actions are visible or one obvious step away, not hidden behind memorized gestures.
  • Recent and frequent items are offered for repeat tasks.
  • Icons that are not universally recognized carry a text label.

Sources

  1. Nielsen Norman Group. Memory Recognition and Recall in User Interfaces.
  2. Nielsen, J. (1994). Enhancing the explanatory power of usability heuristics. Proceedings of CHI '94, 152–158. ACM.