Recognition Rather than Recall

Minimize the user's memory load by making elements, actions, and options visible. The user should not have to remember information from one part of the interface to another. Information required to use the design (e.g. field labels or menu items) should be visible or easily retrievable when needed.

How to achieve recognition?

Use appropriate UI controls

For example, instead of asking users to type an option, provide the list of options in the form of a dropdown, checkboxes, or radio buttons. Bonus if they are accompanied by icons and descriptions; then users can visually recognize options without even reading them.

A wonderful example is from the newsletter service provider that I use. If you want to add new subscribers, you have three options to choose from. You don't need to remember this; after seeing the modal a few times, you already know that the big left button adds a single subscriber, the middle button imports multiple subscribers, and the third button is rarely used.

Auto-suggestion and auto-completion

It often happens that you remember only part of the name of something. The most obvious example is Google. When you try to find something, even if you remember only a few letters of its name, it might be enough for Google to show you what you recalled. Sometimes you don't even need to remember the name if it's something popular.

For example, if I type "iPhone", I will also get the most popular requests, including model names.

We often remember things subconsciously. The most obvious example is always with us—our mobile phones. We arrange the applications we use in a specific order on specific screens.

Nobody remembers where exactly an app is, but as soon as we take our phone, we can instantly find it.

Changing all app icons on your friend's phone is the easiest way to demonstrate this concept.

This will

  1. Piss your friend off
  2. Make it super hard for them to find an app they use every day. They remember the location and have become accustomed to it. Now they’re swiping in circles, wondering where the hell WhatsApp went.
Key Takeaways
  • Minimize users' cognitive load by making options visible and easily recognizable
  • Use appropriate UI controls like dropdowns and checkboxes instead of text input where possible
  • Implement auto-suggestion and auto-completion to help users recognize rather than recall information
  • Maintain consistent layouts and patterns to help users build muscle memory

Further reading

Memory Recognition and Recall in User Interfaces
Detailed explanation by Raluca Budiu from NNGroup about the difference between recognition and recall
Recognition over Recall
A long read from Learning Loop about recognition vs recall.
What is Recognition vs Recall?
As usual, the Interaction Design Foundation provides a comprehensive explanation.
Next Lesson