Ensure all necessary capabilities are visibly accessible.
Accelerate confident engagement and product adoption by helping users quickly understand what they can do without training.
Contents 2. Information Architecture & Wayfinding 2. Discoverability
What systems reveal they can do.
First, ask yourself
“Can users of your system discover core capabilities without instruction?”
Mission statement
Ensure users find available actions by exposing system capabilities clearly.
Key heuristics Discoverability
- All necessary capabilities must be visibly accessible.
- Actionable elements must carry the signifiers governed in 3.2 Affordances.
- Hidden or gesture-based interactions must be explicitly indicated.
- Relevant actions must appear within the user’s current context.
- Progressive disclosure must not obscure advanced capability.
- Critical functionality must be directly discoverable.
- Actionability must be reliably discoverable before it is optimized for speed.
- Discoverability must foster a sense of mastery and control.
Executive brief
The system must visibly reveal what it can do without requiring explanation.
Core questions Discoverability
“Can users see what they can do, right when they need to?”
“If they are new, is it obvious what actions are available?”
Focus areas
Perceptual-first
“What looks clickable or usable right now?”
“What clearly invites action? What does not?”
Anti-accidental discovery
“Are features intentionally revealed, or only found by accident?”
“Would a careful user still discover them?”
State-aware
“Do available actions change clearly with context?”
“Are options visible, or dependent on memory?”
AI-aware
“Does AI clearly surface useful options, or make users guess?”
“Are capabilities explicit, or only implied through behavior?”
UX directives Discoverability
Merged into 32/02—Provide clear signifiers for all actionable elements.
Merged into 32/03—Make interactive elements visually distinguishable.
Use hidden or gesture-based interactions only with explicit signaling.
Prevent discoverability issues for essential tasks by ensuring users know those actions exist.
Surface actions when they become relevant.
Ensure users can discover appropriate actions within context rather than through explanation.
Ensure progressive disclosure does not obscure access.
Advanced capability must remain clearly reachable as complexity unfolds.
Design for intentional discovery.
Make critical functionality directly discoverable, not dependent on chance exploration.
Prioritize discoverability before optimizing efficiency.
Ensure actionable elements are found reliably before improving speed.
Design discoverability to build user confidence.
Guide users so they feel a sense of mastery and control over product capabilities.
Executive summary
- Discoverability is visible capability, not accidental discovery.
- It ensures users can see what they can do without instruction or guesswork.
- The system must make all essential actions perceptible and clearly signified.
- Progressive disclosure must manage depth without obscuring access.
- Discoverability must precede efficiency.
- Speed is meaningless if actions cannot be found.
- Discoverability succeeds when users engage confidently, knowing what is possible and how to act.
Success indicators
- Available actions are visible and easy to notice.
- Users can tell what the system can do before they need it.
- Users can find important features without training or instructions.
- Relevant actions appear when they are needed.
- Users can discover new capabilities as they continue using the system.
One-line summary
Before users can act, they must perceive what is possible.