Users start using software immediately. They do not read documentation, watch tutorial videos, or work through onboarding guides before they begin. This is the Paradox of the Active User, documented by John Carroll and Mary Beth Rosson in 1987 through observations of users learning word processing software. Despite clearly suboptimal outcomes from diving in without preparation, users consistently chose immediate action over learning the system first. The paradox is that this strategy is actually rational: learning by doing produces value immediately, while reading documentation delays value and requires retaining abstract information with no concrete referent.
The Psychology
Carroll and Rosson identified several manifestations of this pattern. Users resist reading manuals even when they acknowledge the manual would help. Users apply existing knowledge from similar systems as their primary strategy, which works when the new system matches prior experience and fails when it does not. Users interpret errors as evidence that they are close to the right approach and continue trying variations rather than stepping back and reading instructions. And users build satisficing strategies — approaches that work well enough for their immediate need — rather than learning the full capability of the system, which means they consistently underutilise available features.
In Product Design
The design implications are clear: the interface must work for users who will not read instructions, because most users will not read them. This drives several concrete design patterns. Empty states should not be blank screens — they should be examples of the finished state or first-action prompts that initiate the productive loop immediately. Inline hints and contextual tooltips that appear at the relevant moment are orders of magnitude more effective than documentation because they appear when the user is already attempting the action. Progressive disclosure allows users to start simple and encounter complexity only when they have already established the basic workflow. Onboarding flows should deliver value in the first session, not require setup before value is possible.
How to Apply It
The practical test is to observe a new user's first session without providing any guidance. Watch where they get stuck, what they try, what errors they encounter, and — critically — what they do when an error occurs. Do they stop and seek help, or do they keep trying variations? In most cases, they keep trying, which means every dead end they reach in exploration costs real engagement time. The design response to each observed sticking point is to either eliminate the friction or add contextual guidance at exactly that moment. Guidance embedded in the interface at the point of need is more effective than any documentation written outside it.
Why It Matters
Ignoring the Paradox of the Active User produces products that rely on documentation that users will not read to close the gap between what the interface communicates and what users need to know. The gap is real — users have genuine needs and the product has genuine capability — but the communication channel is broken. Products that close this gap by making the interface itself the teacher, rather than relying on external documentation, produce dramatically better first-session outcomes and stronger long-term retention.
