Onboarding Flow Template for Product Growth

Run a retention correlation analysis. Compare users who retained at 90 days vs those who churned. Look at every action taken in the first 7 days and find the action (or combination) with the highest correlation to retention. The [Product Analytics Handbook](/analytics-guide) walks through this analysis step by step. Common activation events include: creating core content, inviting a teammate, completing a workflow, or connecting an integration.

Always skippable. Forced onboarding flows that block product access frustrate experienced users and increase bounce rates. Show the checklist prominently, send nudge emails, and highlight the value of each step. But never lock the product behind completion. The exception is essential setup like connecting a data source that the product literally cannot function without.

Target 3-5 steps for the primary onboarding flow. More than 5 steps creates fatigue and drop-off between each step compounds. If your activation event requires more than 5 actions, look for ways to combine steps, pre-fill data, or break onboarding into "essential" (3 steps to first value) and "advanced" (shown after activation).

Redesign when activation rates drop below your target for two consecutive months, when you launch a major new feature that changes the core workflow, or when qualitative feedback (support tickets, session recordings) shows persistent confusion. Minor iterations (copy changes, tooltip adjustments) should happen monthly. Full redesigns should happen no more than once per quarter.

Use a segmentation question early in the flow (first modal after signup). Ask about role, use case, or team size. Then branch the onboarding: show different templates, different empty states, and different email sequences based on the answer. Most products can handle 2-3 persona paths without building anything complex. The [PLG Handbook](/plg-guide) covers persona-based onboarding in depth. ---