Recognition vs Recall
Recognition (seeing an option and knowing it) requires less cognitive effort than recall (remembering from scratch).
Plain English
Recognition is easier than recall because it requires matching rather than retrieval. You can recognise a person's face but struggle to recall their name. In UI design: users should be able to recognise their options from what they can see, not have to remember commands from scratch. This is why menus are better than command lines for novices, why autocomplete reduces form friction, and why consistent iconography must be paired with text labels.
Research background
Derived from cognitive psychology research by Nielsen (Heuristic #6): 'Minimize the user's memory load by making objects, actions, and options visible.' Practical applications: always-visible navigation (no hidden menus for primary paths), persistent search history and suggestions (recognition of past inputs), visible input formatting hints, iconography with text labels, and command palettes with search (reduces recall to recognition for expert users).
UI examples
✓ Applying the principle
A dropdown showing all city options alphabetically (recognition) vs. a blank text field where users must type the exact city name (recall).
✗ Violating it
A command-line interface with no autocomplete, help text, or visible command list — requires pure recall with no recognition scaffold.
AI Prompt
Paste into Claude, Cursor, Bolt, or v0.
Design for recognition: show navigation options (never hide primary paths), use autocomplete for known data sets, pair all icons with text labels, and surface recent/common items in search results before typing.