Product Onboarding Guide
(PM Edition 2026)
The 5 phases of user onboarding, what to do in each, the metrics to track, and 10 anti-patterns that kill activation.
Practice Onboarding Scenarios — Free →The 5 Phases of Onboarding
Pre-onboarding (before signup)
🎯 Goal: Set expectations. Attract the right user. Qualify out the wrong user.
PM Moves
- →Landing page that clearly states what the product does and for whom
- →Social proof (testimonials, numbers) to build trust
- →Clear pricing (or lack of it) upfront — hidden pricing hurts activation
📊 Key metric: Landing page → signup conversion
Signup (Day 0, first 60 seconds)
🎯 Goal: Get the user in without friction. Don't ask for anything you don't need immediately.
PM Moves
- →Social login (Google/Apple) alongside email
- →Defer profile info — collect only what's needed to reach first value
- →Show a progress indicator so users know how close they are to done
📊 Key metric: Signup start → signup complete
Activation (Day 0, first session)
🎯 Goal: Get the user to their first 'aha' moment — where they clearly understand product value.
PM Moves
- →Lead with value, not tutorials — show them something they'd want immediately
- →Personalise based on what they told you (use case, role)
- →Use a guided path, not a feature tour — 'do this one thing' beats 'look at all our features'
📊 Key metric: Activation rate (% who hit the 'aha' action in Day 1)
Early retention (Day 1–7)
🎯 Goal: Build the habit of coming back. This is where most products lose users forever.
PM Moves
- →Trigger return visits with relevant emails or push notifications (never spammy)
- →Daily/weekly engagement loops — streaks, new content, reminders of unfinished value
- →Celebrate small wins early — 'you completed 3 lessons!' reinforces behaviour
📊 Key metric: Day-7 retention
Long-term engagement (Day 8+)
🎯 Goal: Turn casual users into engaged users who would miss the product if it disappeared.
PM Moves
- →Depth features unlocked after habit forms (advanced workflows, integrations)
- →Social / network effects — invite teammates, share content
- →Personalisation that deepens over time — recommendations, history
📊 Key metric: Day-30 retention, weekly active users, NPS
10 Onboarding Anti-Patterns
Feature tour immediately after signup
Users haven't earned the context to care about features. They don't know what to do first.
Asking for too much info before first value
Every field is a drop-off point. Collect info after the user sees value, not before.
One-size-fits-all onboarding for all user types
A new engineer and a new admin have different jobs. Onboarding should reflect this.
Forcing users to watch a video
Most users skip. Inline, interactive onboarding beats video every time.
No empty state for core screens
A blank dashboard with no guidance is the #1 abandonment point.
Dark patterns to force signup completion
Forcing completion increases signups but hurts activation and NPS.
No progress indicator
Users abandon multi-step flows without clear 'you're X% done' signals.
Sending too many onboarding emails
More than 3 emails in Week 1 often triggers unsubscribes, not engagement.
Skipping mobile-specific onboarding
Mobile UX requires fundamentally different patterns — desktop flows rarely translate.
Not instrumenting onboarding events
You can't diagnose drop-off if you don't know where users are dropping. Instrument before shipping.
FAQ
What's a good activation rate for a SaaS product?
Highly varies by complexity and price. Simple B2C apps (quick value): 40–60% activation in Day 1. Mid-complexity SaaS: 20–30%. Complex enterprise SaaS: 10–15% but with longer activation windows (7–14 days). The absolute number matters less than: (1) is it trending up, and (2) are activated users retaining dramatically better? If retention gap is small, you're activating superficially.
Should onboarding show the whole product or just one use case?
Almost always: one use case, deeply. Products with broad capabilities (Notion, Airtable) that try to show 'everything' in onboarding consistently lose users. The winning pattern: identify the user's primary use case (ask them, or infer from signup context), design onboarding that gets them to value in that one use case, and let them discover the rest organically after they're committed.
How do you test and improve onboarding?
A/B test one change at a time — onboarding is extremely path-dependent, and bundled changes are hard to attribute. Core metrics to track: signup → activation rate, time to first value, Day-7 retention of activated vs not-activated. Watch session recordings of new users regularly (5 sessions/week) — friction that's invisible in metrics is visible when you watch real users stumble.
Build Onboarding Intuition Daily
Real scenarios on activation, empty states, and first-session design.
Start Free Trial →