Paradox of the Active User
Users start using software immediately instead of reading instructions, even when learning first would save them time later.
Key takeaways
- Assume nobody reads the tutorial; teach inside the real task.
- Use contextual tips, empty states and progressive disclosure.
- Make the first steps forgiving so exploration doesn't punish users.
Origin
Coined by John M. Carroll and Mary Beth Rosson of IBM in 1987, after observing that people learning new software skipped manuals and jumped straight into tasks.
How to apply it
- Design for learning by doing: let users start their task immediately.
- Use contextual hints, tooltips and empty states instead of upfront tutorials.
- Make features discoverable within the flow where they are useful.
- Provide undo and safe exploration so mistakes are cheap.
- Keep any onboarding short and skippable, focused on the first valuable action.
How Science of Apps uses this law
7 checks in every investigation rely on Paradox of the Active User, for example: “Can users skip, go back and change answers without losing progress?”
Get your product investigated