Recognition Rather Than Recall
Show people the information and choices they need instead of asking them to remember.
It is easier to choose from what you can see.
You see someone and know you have met before, but their name will not come. Seeing the face gives you a clue. Being asked for the name gives you less to work with. Interfaces work the same way. Visible choices make answers easier to find.
Origin
Jakob Nielsen included Recognition Rather Than Recall in his 1994 heuristics. Raluca Budiu's 2024 explanation focuses on cues. Recognition provides visible context, while recall asks people to retrieve an answer with less help.
Show relevant actions where people need them. Clear labels, visible buttons, and familiar menus are easier to use than hidden gestures or commands people must memorize.
Carry important context across screens. If someone chose a flight earlier, show that choice again when they review or pay for it.
Surface recent items, search history, and saved choices when people return. Let them recognize what they used before instead of rebuilding the path from memory.
Teach in context. A short tip beside an unfamiliar control is more useful than an opening tutorial people must remember later.
Digital systems
Amazon Recently Viewed
Amazon shows products a shopper viewed earlier. The list helps them find an item again by recognizing it, rather than recalling its exact name or repeating the search.
Physical signals
Restaurant Menu
A printed menu shows dishes and categories. Diners choose from visible options instead of remembering everything the kitchen can make. The list turns an open-ended memory task into recognition.
When actions are hidden and context disappears between screens, people must remember names, steps, and earlier choices. Every missing cue makes the task harder than it needs to be.
Keep relevant actions, labels, recent history, and prior choices visible or easy to retrieve. Let the interface carry context so the user can recognize what to do next.