Memory

Recognition vs. Recall

Why showing beats asking

Key Insight

Recognition ("Is this what I want?") requires far less cognitive effort than recall ("What was that called?")-interfaces should minimize the need to remember information by making options visible.

Key Points

•Recognition uses cues from the environment to trigger memory; recall requires generating information from scratch
•Recognition is faster and more reliable-multiple-choice is easier than fill-in-the-blank
•Menus, toolbars, and suggestion lists leverage recognition by showing available options
•Command-line interfaces require recall; graphical interfaces enable recognition
•Recently used items, search suggestions, and autocomplete all reduce recall demands
•Icons paired with labels work better than icons alone because they provide multiple recognition cues
•[FIGURE 8.4 - ATM recall problem] Shows: ATM interface requiring users to recall account numbers or transaction codes without visible options. Teaches: Requiring recall creates cognitive burden and errors; showing options enables recognition. Reproduce as: Comparison of recall-based vs recognition-based input.

Guidelines

✓Show available options rather than requiring users to remember them (menus over command entry)
✓Provide search suggestions and autocomplete to turn recall into recognition
✓Display recently used items and history to support memory
✓Use consistent labeling so users recognize patterns across the interface
✓Pair icons with text labels-icons alone often require recall of their meaning
✓Show examples and placeholder text to help users recognize expected input formats

Want to learn this interactively?

Experience hands-on experiments and test your understanding.

Start Learning

🔥

Practice this topic

Active recall - strengthens long-term retention

Recognition vs. Recall

Key Points

Guidelines

Related Topics