Onboarding
Getting someone to their first real outcome, which is a very different goal from explaining the interface.
Definition
Onboarding is the path from first arrival to first genuine value. The measure of success is whether the user achieved something meaningful, not whether they completed a tour.
Craft convention. True because the industry converged on it. Breaking it costs familiarity, not correctness.
On this plate
Reach for this when
- Activation or early retention is weak.
- Launching a new product.
- Introducing a significant new capability.
Common mistakes
- Tours instead of interface fixes.
- Front-loading every explanation.
- Asking for commitment before delivering value.
- Measuring tour completion instead of activation.
- Treating a tour as onboarding, when a tour is usually evidence that the interface cannot explain itself.
Designing it around a single outcome
- 1
Name the activation moment
The specific thing a user does that predicts retention. Find it in data by comparing retained and churned cohorts.
- 2
Remove everything between arrival and that moment
Every field, permission request and explanation before it is a leak. Defer what can be deferred.
- 3
Deliver value before asking for commitment
Let the user see the product work before demanding an account, payment details or a team invitation, where the product allows it.
- 4
Teach at the point of need
Introduce each capability when it first becomes relevant, not in a front-loaded sequence.
- 5
Make the first result real
Something the user made, that persists, and that they would miss.
Onboarding by what the reader needs
| Reader | Needs | Wrong answer |
|---|---|---|
| Has not decided yet | To see value before committing anything | A signup wall |
| Just signed up | One successful action | A tour of twelve features |
| Set up, not yet habitual | A reason to return, and a next step | Silence |
| Returning after a gap | Reorientation, not reintroduction | The same first-run tour again |
| Migrating from a competitor | Import, and their existing vocabulary | Being taught from scratch |
Signals that onboarding is failing
Onboarding is measured by what people do afterwards, not by completion of the onboarding itself.
- A completion rate far higher than the activation rate, which means people finish the flow and still do not reach the point of value.
- Tours dismissed within a few seconds, followed by support questions about the things the tour explained.
- Setup steps abandoned at a permission or payment request placed before any value was delivered.
- Week-one support tickets clustering on one screen, which names the design problem precisely.
- Returning users seeing the first-run experience again, which reads as the product having forgotten them.
- High signup with low second-session return, the clearest sign that nothing worth coming back for was created.
The first session
Do
- Get the reader to one real result, with their own content, before anything else.
- Defer every field that is not needed to produce that result.
- Offer import, and accept the vocabulary of whatever they are moving from.
- Let people skip, and make skipping recoverable later rather than permanent.
Do not
- Ask for permissions before the reader has seen why they would grant them.
- Front-load a tour of features nobody has needed yet.
- Gate the product behind a team invitation, which makes one person's evaluation depend on someone else's calendar.
- Count completing the onboarding as success. The measure is what happens in the second session.
In practice
- i.
Value before signup
Tools and utilitiesProducts that let people use the core function before creating an account convert better, because the account request arrives after the value has been demonstrated rather than before.
- ii.
One outcome, not twelve features
What first run is forOnboarding designed around getting one real thing done outperforms a feature tour on every measure that matters, because the reader leaves having experienced the product rather than having been told about it.
Local chart
PAT·014 · Region III · Grid F2
This entry and the entries it is stated to connect with. Each line is labelled with what the connection means.
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
Principles behind this
The reasoning this solution is an application of.
- Endowment EffectBIAS·007 · Cognitive bias
- Loss AversionBIAS·002 · Cognitive bias
- Help and DocumentationHEUR·010 · Heuristic
- Goal-Gradient EffectLAW·014 · Law
- Zeigarnik EffectLAW·010 · Law
An unfinished checklist is why setup progress pulls people back.
- DiscoverabilityPRIN·005 · Principle
- Paradox of the Active UserPSY·007 · Psychology
- Spacing EffectPSY·008 · Psychology
Often used with
These usually appear in the same screen or the same decision.
- Empty StatesPAT·010 · Pattern
The first screen after signup is usually an empty state, and it is the strongest teaching moment you get.
Practical example
A worked decision where this was the deciding factor.
- Building Trust on a Payment ScreenCASE·002 · Case study
- Whether to Require an Account at CheckoutCASE·001 · Case study
Check your work
Review passes that test whether this was done properly.
- Onboarding ChecklistCHK·005 · Checklist
- SaaS Product ChecklistCHK·007 · Checklist
Short definition
The one-paragraph version, for when that is all you need.
- ActivationTERM·103 · Term
- Empty StateTERM·050 · Term
Related concept
Connected closely enough to change how you apply this.
- Diary StudiesRES·013 · Research method
- Funnel AnalysisRES·011 · Research method
- Empty State CopyWRT·010 · UX writing
- Onboarding CopyWRT·016 · UX writing
- Permission RequestsWRT·014 · UX writing