Whether users can easily recognize instead of remember.
First, ask yourself
“Can users of your system interact correctly through recognition without relying on recall?”
Mission statement
🫡Ensure users act through recognition by making options and states visible and eliminating recall burden and ambiguity.
Key heuristics → Recognition
🚀- Action must be guided by recognition rather than recall.
- Known information must be presented directly, not recalled from memory.
- Outcome-relevant state must remain perceptible at all times.
- Choices must appear at the moment of decision.
- Consistent placement must reinforce recognition over time.
- Meaningful differences must be visually or behaviorally evident.
- Recovery paths must be visible and accessible.
- Returning users must reorient through visible cues, not memory.
- Visual economy must not remove essential cues.
- Visible cues must be favored over memory to keep interfaces usable at scale.
Executive brief
☝️The system must replace memory with visibility so users can act immediately.
Core questions → Recognition
🤔“Can users act by recognition rather than recall?”
“Does the system make the right information visible at the moment of choice?”
Focus areas
Recognition-first
“What is visible right away that would otherwise need to be remembered?”
“Where is recall being required when recognition would work?”
Action-ready
“Are options, state, and consequences clear at the moment of action?”
“Can new or infrequent users act correctly without prior knowledge?”
Context-aware
“Is recognition aligned with users’ current task and goals?”
“Does the system surface relevant cues when and where they are needed?”
AI-aware
“Does the system reveal what it knows instead of relying on user recall?”
“Is intelligence being used to expose state, not to demand recall?”
🧬 UX directives → Recognition
Directive13/01
Favor recognition over recall.
Design interfaces so users can act by seeing and choosing rather than by remembering and reconstructing.
Directive13/02
Substitute memory with perception wherever possible.
Present information whenever possible so users do not have to remember it.
Directive13/03
Make action-relevant state continuously visible.
Do not hide state that influences outcomes or availability.
Directive13/04
Expose choices at the point of decision.
Ensure users can see available options when they need to choose, not before or after.
Directive13/05
Maintain spatial stability to reinforce recognition.
Keep controls and feedback in consistent locations so recognition replaces recall over time.
Directive13/06
Make meaningful differences perceptible.
Do not require users to remember rules or exceptions to distinguish safe actions from risky ones.
Directive13/07
Support error recovery through recognition.
Provide visible history and undo so users can recover without relying on memory.
Directive13/08
Design for infrequent and returning use through recognition.
Ensure users can reorient and resume work without relying on memory or relearning prior knowledge.
Directive13/09
Do not sacrifice recognition for minimalism.
Visual restraint must not remove cues users rely on to recognize actions, state, or structure.
Directive13/10
Design recognition-based interfaces to scale.
Prefer recognition over training so usability does not degrade as systems grow in scope or complexity.
Executive summary
⚡- Recognition must replace recall as the primary interaction strategy.
- It allows users to act by seeing rather than remembering.
- Recognition is faster, safer, and more reliable than recall.
- The system must make key information visible at the moment of action.
- Immediate user action is the practical payoff of recognition.
- Recognition succeeds when users can orient, choose, and recover without relying on recall.
Success indicators
😎- Users can act by seeing options, not remembering them.
- Information needed for action is visible when decisions are made.
- System state and available actions are easy to recognize.
- Controls and feedback appear in stable and predictable locations.
- Users can recover and resume work without relying on memory.
One-line summary
☝️Before users can decide confidently, they must be able to recognize rather than remember.