Paradox of the Active User
Users start acting immediately rather than reading, even when reading would be faster, so design has to teach through doing.
Definition
Carroll and Rosson (1987) observed that users do not take time to learn a system before using it, because they are motivated by immediate productivity. The paradox is that this costs them more time overall, and they do it anyway.
Established research. Originates in published research and has been replicated. The effect is real. Its size in your product still needs measuring.
Design implications
Documentation-first onboarding fails, not because the documentation is bad but because it will not be read. The same applies to tours, which users click through to reach the interface.
The response is to make the interface teachable through use: safe defaults, forgiving actions, visible affordances, and help delivered at the exact moment of need rather than in advance.
Teaching through doing
- Start with a working state rather than an empty one, such as sample data that can be edited or removed.
- Put help where the question arises, not in a separate help section.
- Make the first action succeed, then reveal the next capability.
- Make exploration safe with undo, so trial and error is a viable strategy.
- Prefer inline hints to modal tours, since tours are dismissed.
In practice
Sample content on first run
Creation toolsOpening with an editable example teaches the model by letting the user manipulate something real. An empty canvas teaches nothing and creates a decision the user is not ready for.
Contextual hints over tours
SaaS onboardingA hint attached to a control the first time it becomes relevant reaches users that a five-step tour never does.
Sources
Where a source establishes something narrower than the popular reading of it, the note says so.
Paradox of the active user
J. M. Carroll and M. B. Rosson, in Interfacing Thought: Cognitive Aspects of Human-Computer Interaction, 1987
Continue from here
Each link says what the connection is, so you can tell a principle from an alternative from a thing people mix this up with.
Applies when you are designing
Explains
The mechanism underneath these entries.
- Help and DocumentationHeuristic
- DiscoverabilityPrinciple
- ForgivenessPrinciple
Applied through
Where this shows up as a concrete interface decision.
- Empty StatesPattern
- OnboardingPattern
- Empty State CopyUX writing
- Onboarding CopyUX writing
Related concept
Connected closely enough to change how you apply this.
- Curse of KnowledgeCognitive bias
- Spacing EffectPsychology