Minimize 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 dialogue to another.
The interface provides visual or textual cues that remind users what to do next.
Step-by-step wizards with the current step highlighted
New account
Next step
Personal data
Previous step
Next step
Newsletter settings
Previous step
Next step
Account activation
Previous step
Next step
Login
Previous step
Next step
Done
Previous step
Show progress and next stepsRely on user memory of the processGuide users with inline promptsAssume users know the next stepUse empty states to explain actionsLeave empty screens unexplained
Pre-Filled Information
The system remembers and shows previously entered or relevant information to reduce memory load.
off
on
Mario Rossimario.rossi@example.comSave changes
Mario Rossimario.rossi@example.comSave changes
Pre-fill fields when data is knownForce users to re-enter known informationShow recently used or relevant valuesMake users remember past selectionsAllow users to edit pre-filled dataLock pre-filled fields without explanation
Recognition-Based Navigation
Navigation relies on recognition of familiar patterns and labels, not memory of paths or commands.
Tabs with content
NewsSportsWeather
News
Sports
Weather
Use clear and familiar navigation labelsRely on hidden or memorized navigation pathsProvide breadcrumbs for orientationForce users to remember where they areKeep navigation patterns consistentChange navigation behavior across screens
Recognition Over Commands
Interaction favors selection and recognition over memorizing commands or syntax.
Autocomplete search
latest searches
Design UX Vittorio Vittori Dog Parent
Offer selectable options instead of commandsRequire users to remember syntaxExpose actions through buttons and menusHide core actions behind shortcuts onlyUse descriptive labels for actionsRely on undocumented commands
Visible Options
The system makes available actions and choices visible, so users don't have to remember what is possible.
A table with user data
Mario Rossi mario.rossi@example.com Product ManagerItaly+39 333 1234567 Luigi Verdi luigi.verdi@example.com UX DesignerItaly+39 340 9876543 Giulia Crippa giulia.crippa@example.com Frontend DeveloperItaly+39 347 5551234 Joan Baez joan.baez@example.com Backend DeveloperUSA+1 (555) 123-4567 Jamie Oliver jamie.oliver@example.com Product OwnerUK+44 20 7946 0958
Batch Actions
Edit
Move to group
Deactivate
Batch Actions
Edit
Move to group
Deactivate
Make possible actions visibleHide actions behind unexplained gesturesShow disabled options with reasonsRemove actions without feedbackSurface actions at the point of needExpect users to remember available features
Related references and bibliographypotentially outdated
Articles & Posts
Harsh Gorasia — Heuristics #6: Recognition Rather Than Recall-Simplified by the examples.