“Users don't skip the manual because they're impatient. They skip it because reading isn't the task — and every second spent reading feels like a second not spent doing the thing they actually came to do.”
Why the onboarding tour gets clicked past
Carroll and Rosson called this the production paradox: people are consistently more motivated to produce something — to act, to make progress — than to spend time up front learning how to act more efficiently, even when that up-front learning would save them time overall.
This is why an onboarding tour so often gets dismissed after the second slide. It's not that the content is wrong. It's that reading it doesn't feel like progress, and getting to the point where something is clickable does.
What people learn from instead
If people won't read before acting, they'll learn by acting and recovering — clicking the thing that looks most promising, noticing when it goes wrong, and adjusting. That's a real learning strategy, just an expensive one when the product doesn't support it.
It only works well when mistakes are cheap: when there's an obvious undo, when errors explain what happened instead of just failing silently, when nothing important gets deleted by accident. Trial and error is a fine way to learn a product that's built to tolerate it, and a frustrating way to learn one that isn't.
Designing for the behavior you'll actually get
The practical response isn't to give up on helping people — it's to move the help to the moment it's needed instead of the moment before they need it. A hint that appears the first time someone hesitates over a specific control teaches more than a tour that explained the same control three screens earlier and was already forgotten by the time it mattered.
Assume the tutorial will be skipped, because it will be. Design so that skipping it is survivable.
Assume your onboarding tour will be skipped, because it will be — the product needs to make sense without it.
Put explanations at the moment of the action, not several screens before it.
Make mistakes cheap and reversible — that's what actually replaces reading the instructions.
The paradox isn't that users are lazy. It's that doing feels like progress and reading doesn't — and no amount of well-written onboarding copy changes that math.
