B3.06.1Recognition over Recalldesignresearch

Objects, actions, and options should be visible

Aliases: visible options · recognition memory · menu design

What it is

Recognition over recall means users more easily identify a target among visible objects, actions, and options than reconstruct an exact name, command, or path from memory. The interface should show comparable candidates at the decision point unless users have explicitly asked for less clutter.

Why it happens

Recognition uses external cues to activate existing knowledge; recall must rebuild labels, spelling, and order from unprompted memory. Working memory is limited and decays across time and screens. Visible options support comparison, correction, and discovery: seeing “Export CSV/PDF/Excel” reveals capability, while a bare input lets users only guess whether a command exists.

Studying it

Compare visible menus, partial prompts, and empty-input conditions on task performance: locate time, first correct selection, command discovery, abandonment, and help seeking. Card sorting can elicit users’ candidate names; logs can reveal empty searches, spelling errors, and repeated navigation. Expert interfaces still need testing for whether infrequent functions remain recognizable.

Where it stops holding

Showing everything causes overload and clutter, and complex enterprise systems cannot keep every action visible. Progressive disclosure, search, and command palettes are legitimate when they have discoverable entries, examples, and categories. Visible is not the same as understandable; icons still need text, state, and feedback.

Applying it

  • At action points, show primary objects, common options, and next steps; give secondary functions explicit entries rather than memory-only commands.
  • In empty states, filters, and search, show available fields, popular queries, or example syntax.
  • For long lists, provide grouping, filtering, and recent use instead of requiring exact item names.
  • Test whether first-time users can state system capabilities from visible options, and record steps possible only through prompting.

Related

  • Same group: B3.06.2 Users should not have to remember information across screens · B3.06.3 Instructions should be available where and when needed
  • Nearby: A6.05 Recognition over recall · B2.13 Layering and Progressive Disclosure
  • Search terms: recognition over recall · menu design · discoverability

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/B3.06.1