i

Recognition over Recall

STR·09 · 9 of 11

Show people their options; don't make them remember the incantation.

documented A named, findable source says this. Why: Nielsen heuristic, and the recognition-over-recall memory result predates it.

The same task, built twice

Both panes below are real interfaces. They respond, they can be got wrong, and each is timed from your first move in it. The times are not a study — two panes, one reader, no controls. They are here to make a difference you can feel into a number you can see, and nothing is recorded or sent anywhere.

Your task

Make the selected text bold and centred.

Recall—

The quick brown fox.

The commands are real and the syntax is consistent. You still have to know them, or find the manual, or remember from last time — none of which is on the screen in front of you.

Recognition—

The quick brown fox.

The same two operations, visible, labelled and reversible. You did not remember anything; you recognised it.

What to watch The left pane is faster once you know it, which is why command lines survive. The claim is not that recall is useless — it is that an interface which offers only recall has no way in.

The principle

OriginNielsen heuristic #6, standing on well-established memory research: recognition is reliably easier than recall.
EvidenceThe GUI's whole victory over the command line, replayed today in command palettes — which win precisely by turning recall (remember the command) into recognition (type two letters, see the options).
Limits & misuseFor experts, recall is faster — keyboard shortcuts exist because recognition has a reading tax. The principle sets the default for the newcomer, not the ceiling for the practiced; interfaces that never let you graduate to recall are politely condescending forever.