| name | guided-onboarding-and-activation |
| description | Rebuild product onboarding flows using immersive "wizards" and high-correlation activation metrics. Use this when launching a self-serve product, optimizing low retention, or refining a complex PLG (Product-Led Growth) funnel. |
Onboarding is the highest-leverage growth lever for retention. By shifting from passive tooltips to immersive, guided experiences, you reduce cognitive load and lead users to "aha" moments faster.
The Guided Onboarding Pattern
Replace generic tooltips with a structured "wizard" that builds the user’s first workflow in real-time.
- Use an Immersive Wizard: Create a full-screen or focused interface that guides users through setting up their first project.
- Ask, Don't Tell: Use 2-3 simple questions to gather inputs (e.g., "What project are you tracking?", "What data points matter most?").
- Visualize Progress: Show a live preview of the product being built as the user selects options. This reduces the effort of building "scaffolding" from scratch.
- Prioritize Education over Features: Do not show every feature on day one. Focus on "beginner" steps first, moving "intermediate" and "advanced" education into the product (e.g., pop-ups that appear only when a user explores a specific area).
Personalization Strategy
Segment users by their learning and building style rather than just their job title.
- Learning Styles: Identify if a user is a "builder" (wants to start from scratch) or a "consumer" (wants a template/teammate view).
- The Teammate Experience: Recognize that someone invited to a project needs a completely different onboarding than the person who created it.
- Custom Routing: Based on initial questions, route users to different "paths"—some might need database basics, while others need visual layout tutorials.
Defining the Activation Metric
Pick a metric that is a high-bar indicator of long-term retention.
- Aim for the 5-15% Range: If your activation rate is 40-50%, your bar is likely too low. A lower percentage (5-15%) usually indicates a much higher correlation with users who will stay for 12+ months.
- The Multi-User Constraint: For B2B/Collaboration tools, include a multi-user component (e.g., "At least 2 people active in week 4").
- The "Portfolio" Metric Approach: Use three metrics together to evaluate onboarding success:
- Retention: Did they come back? (e.g., Week 2 or Week 4 retention).
- Sophistication (The "Build" Score): Did they use "intermediate" features (e.g., automations, integrations)?
- Team Use: Did they invite others and collaborate?
Examples
Example 1: Complex Project Management Tool
- Context: A new user signs up for a data-heavy project management app.
- Application: Instead of a blank table, the app launches a "Setup Wizard." It asks: "What are you tracking?" (Tasks). "What status columns do you need?" (To Do, Doing, Done).
- Output: As the user clicks "Done," the right side of the screen shows a populated board. The user enters the app with a functional workspace already built.
Example 2: Collaboration Tool for "Invited" Users
- Context: A marketing manager invites a freelance designer to a workspace.
- Application: The designer doesn't see the "Create a Workspace" wizard. Instead, they see a "Welcome to [Project Name]" screen with a 30-second video on how to comment and upload files—the only tasks relevant to them.
- Output: The designer is "activated" on their specific use case without being overwhelmed by admin settings.
Common Pitfalls
- Naming Features: Avoid tooltips that say "This is the Automations Tab." Instead, say "Click here to automatically notify your team when a task is finished."
- Mapping Onboarding to Pricing: Do not push premium features in onboarding just because they are expensive. Only push them if they are essential to the user’s initial success.
- Ignoring the "Teammate" Flow: Most growth teams optimize for the "Creator" (the person who signs up first) but ignore the "Invited User," who often makes up the bulk of the user base.
- Experimenting for Precision vs. Risk: Don't A/B test every small change. If qualitative research and logic show a change is better for the customer, ship it. Use experiments primarily for high-risk changes that might break the funnel.
