How users progress from novices to competent users.
First, ask yourself
“Can users of your system achieve competency quickly without long-term penalties?”
Mission statement
🫡Ensure users can reach competence quickly through progressive understanding.
Key heuristics → Learnability
🚀- Systems must enable rapid progression to user competence.
- Early success must not undermine long-term efficiency.
- Capability must be reinforced through use, not instruction alone.
- Early guidance must enable eventual user independence.
- Complexity must unfold without concealing capability.
- Behavioral patterns must generalize across contexts for knowledge transfer.
- Errors must be recoverable to encourage exploration.
- Core behaviors must align with established expectations where appropriate.
- Guidance must decrease as competence increases.
Executive brief
☝️The system must enable rapid learning without imposing long-term inefficiency.
Core questions → Learnability
🤔“Does the system help users get started quickly and keep improving over time?”
“Does it support learning now without slowing users down later?”
Focus areas
Lifecycle-focused
“How fast can beginners become productive? How far can they grow?”
“Does learning this system compound over time or level off?”
Design-responsibility
“What does the interface teach through use?”
“Where does it depend on extra explanations instead of clear design?”
Growth-aware
“Does the system encourage ongoing skill development?”
“Are learning opportunities aligned with users’ evolving goals?”
AI-aware
“Does AI help users learn faster, or make them reliant on it?”
“Is it teaching understanding, or just masking complexity?”
🧬 UX directives → Learnability
Directive16/01
Design for speed to user competence and ease of growth.
Measure learnability by how quickly and smoothly users become competent with the system.
Directive16/02
Optimize beyond first-use success.
Ensure early success does not compromise long-term efficiency or mastery.
Directive16/03
Enable learning through interaction.
Design workflows so capability is discovered and reinforced through use rather than dependent on instruction.
Directive16/04
Design constraints that enable transition to user autonomy.
Ensure early guidance supports later independence without structural reset.
Directive16/05
Reveal complexity progressively without concealing capability.
Advanced features must remain discoverable as user competence increases.
Directive16/06
Use consistency to facilitate learning transfer.
Ensure system behaviors and interaction patterns generalize across contexts.
Directive16/07
Make errors safe and recoverable.
Design error handling that encourages user experimentation and reduces hesitation.
Directive16/08
Leverage familiar conventions and prior knowledge.
Align core system behaviors with existing user expectations where appropriate.
Directive16/09
Adapt assistance to user competence growth.
Ensure guidance decreases as user expertise increases, avoiding permanent dependency.
Executive summary
⚡- Learnability is an accelerated path to competence, not superficial simplicity.
- It is a progression, not a moment, essential for rapid competence and ongoing growth.
- The system must enable learning through interaction without reliance on instruction.
- Safe exploration must be allowed, with any errors being understandable and recoverable.
- Consistency and familiar conventions support learning transfer and help reveal deeper complexity.
- Learnability succeeds when users transition from novice to expert without relearning the system.
Success indicators
😎- New users can complete basic tasks quickly.
- Users learn how the system works through normal use.
- Features and capabilities become discoverable as users gain experience.
- Errors are safe and easy to recover from.
- Users become faster and more confident with continued use.
One-line summary
☝️Before users can become proficient, they must be able to become competent quickly.