Loading…
Loading…
Users prefer to just start using things rather than reading instructions.
stellae.design
Users prefer to jump straight into using a product rather than reading instructions or completing onboarding. They would rather learn by doing — even when that means making mistakes.
Users never read the manual. Given the choice between learning a system thoroughly before using it and diving in to start accomplishing tasks immediately, users will almost always choose to act. This bias toward action means tutorials, documentation, and onboarding flows are routinely skipped.
Contextual tooltips that appear when needed
Help appears inline, exactly when and where the user needs it
Mandatory tutorial before first use
Forced walkthrough that users skip or rush through without retaining
This paradox explains why elaborate onboarding tours fail and help documentation goes unread. Users are motivated by their immediate goal, not by learning the tool itself. Products that accommodate this bias — making features discoverable through use rather than instruction — see higher engagement and lower support costs.
Figma drops new users into a canvas with a minimal set of visible tools rather than forcing a tutorial. Users can immediately start drawing, and contextual hints appear as they encounter new features. This approach respects the user's desire to act while still providing guidance at the moment of need.
Gmail's 'Undo Send' feature gives users a brief window to retract a sent email. Rather than forcing users to triple-check before sending, it lets them act quickly and recover from mistakes. This design elegantly accommodates the active user's bias toward immediate action.
Many enterprise platforms require users to complete hours of video training before accessing the system. Employees often rush through without absorbing the content, then struggle with the actual interface. The mandatory training creates a false sense of preparedness while frustrating users who want to start working.
Nintendo games famously teach mechanics through gameplay itself — the first level of Super Mario teaches jumping, running, and power-ups through carefully designed encounters rather than instruction screens. Players learn by doing, and the lessons stick because they are tied to immediate goals and feedback.
• Some teams interpret this paradox as justification for providing zero guidance, resulting in interfaces that are needlessly opaque. Others build multi-step onboarding wizards 'because users need to learn' while ignoring the evidence that most users skip them. The paradox is about meeting users where they are, not about removing all instructional support.
| Check | Good Pattern | How to Test |
|---|---|---|
| Onboarding skip rate | The product is usable and core tasks are completable even when users skip 100% of onboarding content. | Have new users attempt key tasks with all onboarding disabled. Measure task completion rate and time-to-success compared to the onboarded group. |
| Reversibility of actions | All non-destructive actions are undoable, and destructive actions require explicit confirmation with clear consequences explained. | Map every user action and classify it as reversible or irreversible. Ensure undo is available for all reversible actions and that irreversible ones have confirmation dialogs. |
| Contextual guidance | Help and hints appear at the moment of need — at decision points and first encounters — rather than in a separate documentation section. | Track help-tooltip impression rates versus help-page visit rates. Contextual guidance should have significantly higher engagement than standalone documentation. |
When the consequences of uninformed action are severe or irreversible — for example, medical device interfaces, financial trading platforms, or infrastructure management tools. In high-stakes domains, gated onboarding that ensures competence before granting access is appropriate.
Was this article helpful?