Skip to content
UX Atlas
Plate PSY·007 · PsychologyGrid B1 · Rev. 2026-08-14

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.

PsychologyEstablished researchIntermediate

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.

On this plate
  1. 1Definition
  2. 2Design implications
  3. 3Teaching through doing
  4. 4Teaching people who will not read
  5. 5In practice
  6. 6Local chart
  7. 7Sources
  8. 8Continue from here

Reach for this when

  • Designing onboarding and first-run experience.
  • Deciding between documentation and interface change.
  • Reviewing feature adoption after launch.
  • Designing first-run experience, or explaining why a well-written tour is not being used.

Common mistakes

  • Relying on tours or documentation for essential knowledge.
  • Empty first-run states with no starting point.
  • Assuming users will read anything before acting.

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.

Teaching people who will not read

Do

  • Put the instruction inside the task, at the moment it is needed.
  • Make the first action possible without any reading at all.
  • Use sample content, so the product is explorable before it is understood.
  • Make errors cheap, because exploration is how people are going to learn this.

Do not

  • Open with a tour of features nobody has a use for yet.
  • Gate the first action behind a setup wizard.
  • Assume documentation will be read because it is good.
  • Interpret skipped onboarding as a lack of interest.

In practice

  1. i.

    Sample content on first run

    Creation tools

    Opening 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.

  2. ii.

    Contextual hints over tours

    SaaS onboarding

    A hint attached to a control the first time it becomes relevant reaches users that a five-step tour never does.

  3. iii.

    Skipped, and then stuck

    The paradox in numbers

    Most people skipped the tour and a sizeable minority then failed the first task. Both facts are the paradox: the reading would have helped, and no amount of writing it better makes it get read.

Local chart

PSY·007 · Region I · Grid B1

This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.

Help and DocumentationHEUR·010 · EXPLAINSDiscoverabilityPRIN·005 · EXPLAINSForgivenessPRIN·006 · EXPLAINSEmpty StatesPAT·010 · APPLIED THROUGHOnboardingPAT·014 · APPLIED THROUGHEmpty State CopyWRT·010 · APPLIED THROUGHOnboarding CopyWRT·016 · APPLIED THROUGHOnboarding ChecklistCHK·005 · CHECK YOUR WORKCurse of KnowledgeBIAS·008 · RELATED CONCEPTSpacing EffectPSY·008 · RELATED CONCEPT

Sources

Where a source establishes something narrower than the popular reading of it, the note says so.

  1. [1]

    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

An Onboarding Flow

Explains

The mechanism underneath these entries.

Applied through

Where this shows up as a concrete interface decision.

Check your work

Review passes that test whether this was done properly.

Related concept

Connected closely enough to change how you apply this.