Paradox of the Active User
People often start doing the task before they invest time in learning the system.
Most people want progress now, not a lesson they might need later.
A new user skips the product tour and opens a blank project. That is not impatience to design around later. It is the starting condition. The first useful action should teach the product while moving real work forward.
Origin
Carroll and Rosson described the active-user paradox in 1987. People focused on immediate tasks often avoid systematic learning, even when learning first could improve their longer-term performance.
Make the first useful action easy to discover. Learning should begin with progress on the person's goal, not a tour of the product's feature set.
Put help beside the moment of uncertainty. A short example or hint is more useful when the person has a real question to answer.
Make exploration safe. Undo, previews, sensible defaults, and clear consequences let people learn without risking important work.
Keep reference material for depth, but do not make routine success depend on reading it before the task begins.
Digital systems
An editable starter project
The product opens with a small real example that can be changed, undone, and saved. Each action teaches a working pattern while producing something useful.
Physical signals
A self-service ticket machine
The screen begins with the trip people came to buy. Help appears beside fare or route choices instead of requiring everyone to read a separate instruction panel first.
The product expects people to complete a tour, read a guide, or understand its structure before they can make meaningful progress.
Make the first actions discoverable and reversible, then provide concise help at the exact point where the person needs a deeper explanation.