{"slug":"onboarding-cro","title":"onboarding-cro","tags":["site-building","cro","onboarding","conversion"],"agent_summary":"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.","trigger_phrases":["onboarding-cro","onboarding flow","activation rate","user activation","first-run experience","empty states","onboarding checklist","aha moment","new user experience"],"runnable":false,"markdown":"**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.\n\n### Core Principles\n\n1. **Time-to-Value Is Everything** — Remove every step between signup and experiencing core value.\n2. **One Goal Per Session** — Focus the first session on one successful outcome. Save advanced features for later.\n3. **Do, Don't Show** — Interactive beats tutorial. Doing the thing beats learning about the thing.\n4. **Progress Creates Motivation** — Show advancement. Celebrate completions. Make the path visible.\n\n### Define Activation First\n\nBefore optimizing, define what \"activated\" means:\n- What action proves a user \"gets it\"?\n- What metric correlates with 30-day retention?\n- What is the minimum viable first success?\n\nExample activations: \"created their first project\", \"imported their first contact\", \"sent their first message\", \"saw their first dashboard with real data\".\n\n### Onboarding Patterns\n\n**Checklist pattern:** Show 3-5 setup tasks with checkmarks. Users complete on their timeline. Progress bar drives completion instinct.\n\n**Wizard pattern:** Guided step-by-step. User can't skip. Best when the setup IS the value.\n\n**Empty state pattern:** Design empty states to guide first action. \"You have no projects yet. Create your first project →\"\n\n**Product tour pattern:** Tooltip-based walkthrough. Use sparingly — only for non-obvious features. Maximum 5 steps.\n\n### Audit Framework\n\n| Dimension | Question |\n|---|---|\n| Time-to-value | How many minutes from signup to first success? |\n| Step count | How many screens before the user does something valuable? |\n| Empty states | Do empty states guide action or just show nothing? |\n| Progress visibility | Can users see how far they are? |\n| Celebration | Is there a moment of delight at first success? |\n| Exit points | Where do users abandon without activating? |\n\n### Empty State Design Rules\n\n1. Never show a blank screen — always suggest the first action\n2. Illustration + headline + single CTA works best\n3. Copy pattern: \"You haven't [done X] yet. [Do X] →\"\n4. Pre-populate with sample data if possible (user sees value immediately)\n\n### Onboarding Emails (Days 1-7)\n\n| Day | Email Purpose |\n|---|---|\n| Day 0 (immediate) | Welcome + one-click path to first action |\n| Day 1 | \"Here's what you can do next\" — feature discovery |\n| Day 3 | Success story / social proof from a similar user |\n| Day 7 | Check-in — \"Did you accomplish X?\" with support offer |\n\n---\n","html":"

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.

\n

Core Principles

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

Define Activation First

\n

Before optimizing, define what \"activated\" means:

\n\n

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

\n

Onboarding Patterns

\n

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

\n

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

\n

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

\n

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

\n

Audit Framework

\n

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

\n

Empty State Design Rules

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

Onboarding Emails (Days 1-7)

\n

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

\n
\n"}