Prepared for: Product Team Meeting
Date: December 15, 2025
Our Q1 planning identified onboarding as a top priority. This document compiles our internal metrics, industry benchmarks, and competitor research to support the case for aggressive simplification of our onboarding flow.
Bottom line: The industry is moving toward "value-first" onboarding where users experience the product before completing setup tasks. Our current 7-step flow front-loads configuration, which conflicts with user expectations and causes significant drop-off.
| Metric | Current | Target | Gap |
|---|---|---|---|
| Onboarding completion rate | 34% | 60% | -26 pts |
| Time to first value action | 8.2 min | <3 min | 5+ min too slow |
| Steps in onboarding flow | 7 | 3 | 4 steps to cut |
| Day-7 retention | 41% | 55% | -14 pts |
Most common exit survey feedback: "I just wanted to see what this does"
| Benchmark | Rate |
|---|---|
| Industry average | 19.2% |
| Industry median | 10.1% |
| Average SaaS (broader definition) | 40-60% |
| Top performers | 70-80% |
| Our current rate | 34% |
Our 34% is above the industry average but well below top performers. There's significant upside available.
What they do: Despite appearing "zero-step," Linear actually has 10+ onboarding steps. The difference is execution: clean visuals, hands-on activities, and one input per step make the process feel lightweight.
Key insight: Linear doesn't eliminate steps. They make each step feel purposeful and get users into a functional environment quickly.
What they do: Onboarding takes less than 1 minute (~50 seconds) for personal accounts.
Their approach:
Key insight: Notion collects personalization data but immediately uses it to deliver visible value (relevant templates), not just for backend segmentation.
What they do: Users go straight to the canvas. No elaborate tutorials or feature guides upfront.
Their philosophy: "Show, not tell. Customers want to jump in and experience the product rather than feel they're sitting back in a classroom."
Key insight: Figma uses bite-sized tooltips that appear contextually as users explore, rather than front-loading information.
The trend isn't just "fewer steps." It's a fundamental rethinking of how onboarding works.
Why this matters: "People don't learn by following instructions step-by-step. They explore, tinker, jump around, ask questions mid-way, get distracted, and return with context. Good onboarding should reflect that."
Response: Personalization data collection isn't the problem. The issue is when and how we collect it.
Notion asks a single use-case question and immediately uses that data to show relevant templates. Users see the value of providing the information. Our current flow collects data (workspace name, team members, integrations) without immediately demonstrating why it matters.
Recommendation: If we collect personalization data, we should immediately use it to customize the experience in a visible way.
Response: The 28% of users who abandon at the team invite step never become viral advocates anyway. They never experience the product.
Users who experience value first are more likely to:
Recommendation: Let users try solo first. Prompt for team invites after they've completed a meaningful action.
Dependencies identified in Q1 planning:
Recommendation: Scope the February release to structural changes (reordering steps, removing blockers) rather than full redesign. Instrumentation for the new flow can follow in March.
This is currently undefined in our planning doc. Before we can optimize time-to-value, we need to know what "value" looks like.
Questions to answer:
Current flow:
Signup → Workspace name → Team invite → Integrations → Product
Proposed flow:
Signup → Immediately into sample project/workspace → Contextual prompts for setup as relevant
This mirrors what Linear, Notion, and Figma all do: get users into a functional environment first, then handle configuration.
Given resource constraints, focus February on:
Defer to March: