Vittorio Vittori

Design System Architect / Senior UX Designer

Recognition Rather than Recall

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.

User-Centered Design
Cognitive load

Contextual Cues

The interface provides visual or textual cues that remind users what to do next.

Step-by-step wizards with the current step highlighted

Show progress and next steps Rely on user memory of the process Guide users with inline prompts Assume users know the next step Use empty states to explain actions Leave empty screens unexplained

Pre-Filled Information

The system remembers and shows previously entered or relevant information to reduce memory load.

off on
Pre-fill fields when data is known Force users to re-enter known information Show recently used or relevant values Make users remember past selections Allow users to edit pre-filled data Lock 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

Use clear and familiar navigation labels Rely on hidden or memorized navigation paths Provide breadcrumbs for orientation Force users to remember where they are Keep navigation patterns consistent Change navigation behavior across screens

Recognition Over Commands

Interaction favors selection and recognition over memorizing commands or syntax.

Autocomplete search

Offer selectable options instead of commands Require users to remember syntax Expose actions through buttons and menus Hide core actions behind shortcuts only Use descriptive labels for actions Rely 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

Batch Actions Edit Move to group Deactivate
Make possible actions visible Hide actions behind unexplained gestures Show disabled options with reasons Remove actions without feedback Surface actions at the point of need Expect users to remember available features
Recognition Rather than Recall