Skip to content
UX Atlas
Plate HEUR·006 · HeuristicGrid B2 · Rev. 2026-08-14

Recognition Over Recall

Recognising something on screen is far easier than remembering it, so keep the information visible.

HeuristicExpert heuristicFoundational

Definition

Nielsen's sixth heuristic. Minimise the user's memory load by making objects, actions and options visible. The user should not have to remember information from one part of the interface to another.

Expert heuristic. A review criterion developed by practitioners. Useful and widely taught, but evaluated by judgement rather than measurement.

On this plate
  1. 1Definition
  2. 2The memory research behind it
  3. 3Recall demands worth removing
  4. 4Recall demands hiding in ordinary interfaces
  5. 5In practice
  6. 6Local chart
  7. 7Sources
  8. 8Continue from here

Reach for this when

  • Designing search, filtering and comparison.
  • Building any multi-step flow.
  • Reviewing icon-only interfaces.
  • A step asks the reader to remember something from an earlier screen.

Common mistakes

  • Interpreting it as 'show everything', which creates its own load.
  • Tooltips as the only label, which fail on touch.
  • Autocomplete that suggests from the wrong data set.

The memory research behind it

Recognition memory outperforms free recall by a wide margin, a finding consistent across decades of experimental psychology. Recognition supplies retrieval cues; recall requires generating them. This is the one Nielsen heuristic with the strongest research grounding underneath it.

Practically, it means every time an interface asks 'what was it called' or 'what did you enter earlier', it has imposed a cost it could have absorbed.

Recall demands worth removing

  • Requiring an exact command name where a searchable palette would do.
  • Clearing the search query from the results page.
  • Losing form data on validation error or on back navigation.
  • Showing a code in an email that must be typed elsewhere, when a link would work.
  • Icon-only toolbars with no labels and no tooltips.
  • Asking users to compare items across pages instead of side by side.

Do

  • Show recently used and recently viewed items.
  • Keep the query, filters and selection visible in results.
  • Autocomplete from data you already hold.
  • Show the format requirement before the user types, not after they fail.
  • Let comparison happen in one view.

Do not

  • Rely on icon-only controls for anything infrequent.
  • Hide the user's own input behind a step boundary.
  • Require memorisation of identifiers your system generated.

Recall demands hiding in ordinary interfaces

Each one asks the reader to hold something in memory that the system already knows.

  • A confirmation screen that does not repeat what is being confirmed.
  • An error that names a field which has scrolled out of view.
  • A code sent in one app and typed into another, with no autofill.
  • Filters applied somewhere off screen, with no visible summary.
  • A comparison that requires opening two tabs.
  • Keyboard shortcuts documented only in a help page.

In practice

  1. i.

    Command palettes over memorised shortcuts

    Professional tools

    A searchable palette turns a recall task into a recognition task while still exposing the shortcut for people who want to learn it. Both populations are served by one control.

  2. ii.

    Persistent query and filters

    Search and catalogue

    Keeping the query and active filters visible above results prevents the most common recall failure in search interfaces, and makes refinement rather than restart the natural next action.

  3. iii.

    Confirm what, exactly

    The dialogue that forgot

    Are you sure you want to delete this? asks the reader to remember which row they clicked. Naming the item in the dialogue turns a memory test into a reading task, and stops the wrong deletions.

Local chart

HEUR·006 · Region I · Grid B2

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Cognitive LoadPSY·001 · WHY THIS WORKSAutocomplete and TypeaheadPAT·003 · APPLIED THROUGHCommand PalettePAT·018 · APPLIED THROUGHSearchPAT·002 · APPLIED THROUGHIconographyFND·050 · APPLIED THROUGHForm UX ChecklistCHK·001 · CHECK YOUR WORKCommand PaletteTERM·053 · SHORT DEFINITIONHick's LawLAW·001 · RELATED CONCEPTJakob's LawLAW·003 · RELATED CONCEPTMiller's LawLAW·004 · RELATED CONCEPTPower Law of PracticeLAW·015 · RELATED CONCEPTDiscoverabilityPRIN·005 · RELATED CONCEPT

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

    10 Usability Heuristics for User Interface Design

    J. Nielsen, Nielsen Norman Group, 1994, revised 2020

  2. [2]

    Recognition memory for words, sentences, and pictures

    R. N. Shepard, Journal of Verbal Learning and Verbal Behavior, 1967

    Classic demonstration of the size of the recognition advantage.

Continue from here

Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.

Applies when you are designing

A Search ExperienceAuthentication

Why this works

The reasoning this entry rests on.

Applied through

Where this shows up as a concrete interface decision.

Check your work

Review passes that test whether this was done properly.

Short definition

The one-paragraph version, for when that is all you need.

Related concept

Connected closely enough to change how you apply this.