Onboarding copy sells the value, not the steps
Aliases: first-value onboarding · onboarding value contract · consequence and choice
What it is
Verifiable value-first onboarding first states which task a capability enables, the consequences of adopting it, required investment, and available choices, then places procedural steps where the user performs them. Value is not a slogan such as “smarter” or “more efficient”; it is an outcome supported by current capability, role, plan, and data conditions. Onboarding also makes clear what can be started, deferred, skipped, or refused.
Why it happens
At first contact, users may be deciding whether to invest or may already have an urgent task. Front-loading click sequences consumes attention, decays when the interface changes, and requires instructions to be remembered before their controls appear. Pure vision copy hides costs and permission. Value, consequence, and choice provide a basis for proceeding; just-in-time steps reduce memory load when action and control are co-present. These layers work better than placing the whole tutorial at the entrance.
Studying it
Recruit first-time, returning, migrating, and delegated users with real goals. Compare value-first, steps-first, and on-demand guidance. Test whether they can state the outcome, prerequisites, cost, permissions, and alternative choices; measure first core-task completion, performance after skipping, help seeking, abandonment, and later adoption. Choose the observation window from the product's value cycle rather than a fixed number of days, and hold capability and flow constant across copy variants.
Where it stops holding
Hidden gestures, invisible prerequisites, and high-risk choices need explanation before commitment; procedural detail is not always deferred. A setup wizard is itself a task flow and can explain the current step, while still stating why it is required and what refusal changes. A first-use empty state focuses on what appears after adding data, including samples, cost, and permission. This leaf governs value, consequence, and choice across the first-use journey rather than repeating empty-surface design.
Applying it
- Record target task, verifiable outcome, prerequisites, time/data/permission cost, known limits, role or plan availability, and reversible choices for each introduced capability.
- Keep entry copy to value and consequences needed for the decision. Put control steps at the action and keep help reopenable rather than depending on one-time memory.
- Offer clear skip, later, back, and refuse paths. Send practiced users with completed setup or existing data directly to the task while preserving on-demand guidance.
- Regress promises against actual capability, permission refusal, network failure, assistive technology, and localization. Remove or revise guidance when the outcome is no longer available.