VOCABULARY / ENTRY
Recognition Rather Than Recall
recognition
Make objects, actions, and options visible so people need to retrieve less operating information from memory.
Choose a note category
Recall version: you need to know the category code. Shown for comparison; it should not be the only entry point for unfamiliar users.
Recognizing it
- Explicit option names
- Cues near the relevant task
- No requirement to memorize internal codes
Concept boundary
This does not mean showing every option at once. Visibility still needs suitable grouping, search, or disclosure.
When to consider it
- People are unfamiliar with commands, category codes, or action names
- Tasks span steps and earlier information is easily forgotten
When to be cautious
- Showing many low-relevance options at once and making scanning harder
- Assuming experienced people never benefit from command shortcuts
Tradeoff
It reduces reliance on memory but takes display space and adds scanning effort.
Conditional rules · Editorial advice
Related entries
Balances visibility with the amount of information shown.
Visible cues can be one inclusive-design strategy.
Sources and what they support
Recognition uses cues; recall retrieves information from memory. Visible interface information can reduce memory demands.
Retrieved: 2026-09-15Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.
Type extensions and implementation notes
Capability tags describe this specimen only; verify the implementation again in a real product.
{
"evidenceType": "A usability heuristic and explanation of memory mechanisms",
"limit": "Does not establish that every selection list is faster than text input."
}Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.