S
Site Building SOPKnowledge Base
Search
← All topics

onboarding-cro

Optimize post-signup onboarding, user activation, and first-run experience to maximize time-to-value and reach the aha moment. For signup flows see signup-flow-cro.

site-buildingcroonboardingconversion
Agent trigger phrases: onboarding-cro · onboarding flow · activation rate · user activation · first-run experience · empty states · onboarding checklist · aha moment · new user experience

Trigger: Use when "onboarding flow", "activation rate", "user activation", "aha moment", "new user experience". For signup see signup-flow-cro. For email sequences post-activation see email-sequence.

Core Principles

  1. Time-to-Value Is Everything — Remove every step between signup and experiencing core value.
  2. One Goal Per Session — Focus the first session on one successful outcome. Save advanced features for later.
  3. Do, Don't Show — Interactive beats tutorial. Doing the thing beats learning about the thing.
  4. Progress Creates Motivation — Show advancement. Celebrate completions. Make the path visible.

Define Activation First

Before optimizing, define what "activated" means:

  • What action proves a user "gets it"?
  • What metric correlates with 30-day retention?
  • What is the minimum viable first success?

Example activations: "created their first project", "imported their first contact", "sent their first message", "saw their first dashboard with real data".

Onboarding Patterns

Checklist pattern: Show 3-5 setup tasks with checkmarks. Users complete on their timeline. Progress bar drives completion instinct.

Wizard pattern: Guided step-by-step. User can't skip. Best when the setup IS the value.

Empty state pattern: Design empty states to guide first action. "You have no projects yet. Create your first project →"

Product tour pattern: Tooltip-based walkthrough. Use sparingly — only for non-obvious features. Maximum 5 steps.

Audit Framework

| Dimension | Question | |---|---| | Time-to-value | How many minutes from signup to first success? | | Step count | How many screens before the user does something valuable? | | Empty states | Do empty states guide action or just show nothing? | | Progress visibility | Can users see how far they are? | | Celebration | Is there a moment of delight at first success? | | Exit points | Where do users abandon without activating? |

Empty State Design Rules

  1. Never show a blank screen — always suggest the first action
  2. Illustration + headline + single CTA works best
  3. Copy pattern: "You haven't [done X] yet. [Do X] →"
  4. Pre-populate with sample data if possible (user sees value immediately)

Onboarding Emails (Days 1-7)

| Day | Email Purpose | |---|---| | Day 0 (immediate) | Welcome + one-click path to first action | | Day 1 | "Here's what you can do next" — feature discovery | | Day 3 | Success story / social proof from a similar user | | Day 7 | Check-in — "Did you accomplish X?" with support offer |