<?xml version="1.0" encoding="utf-8"?>

Recognition rather than recall

Recognition rather than recall Bad Practice
Recognition rather than recall Best Practice

The system should help users recognize things instead of forcing them to strain their memory and recall items. For example, when users are asked to type their birth date, they know it by heart and see no difficulties in doing so. When you ask them to provide the card number and its CVV, it’s more challenging data for users to recall. Some websites and applications offer to remember a card number for further purchases. However, CVV is confidential data, and users need to make extra efforts to get this number (take out a card from their wallet or find a note where they've written it down).

Users' ability to retrieve information from memory depends on how often they see and use it and the context surrounding it. Ideally, interfaces should promote recognition and apply certain design practices to make information and interface functions visible and easily accessible.

This can be done through:

  • Search history and recently viewed content: Netflix’s home page displays unfinished movies or TV series to help users get back to what they’ve started.
  • Tips and tutorials: If you want to introduce a new function, tips may help users remember this information and recognize it the next time they visit this page.[1]
Improve your UX & Product skills with interactive courses that actually work