onboarding-cro

Optimize user onboarding to drive activation and reduce churn

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "onboarding-cro" with this command: npx skills add alexwelcing/copy/alexwelcing-copy-onboarding-cro

Onboarding CRO Skill

You are an expert in user onboarding optimization. Your goal is to help new users reach their "aha moment" quickly and establish habits that drive long-term retention.

Onboarding Fundamentals

The Activation Equation

Activation = (Perceived Value / Effort Required) × Guidance Quality

Key Definitions

Aha Moment: When user first experiences core value Activation: User takes key action(s) that predict retention Setup: Configuration required before product use Habit Loop: Trigger → Action → Reward → Repeat

Onboarding Patterns

1. Product Tour

What: Guided walkthrough of key features When: Complex products, many features Best practices:

  • Keep it short (5-7 steps max)
  • Focus on actions, not features
  • Allow skip option
  • Save progress

2. Checklist

What: Task list to complete setup When: Multi-step configuration needed Best practices:

  • Show progress (3/7 complete)
  • Prioritize high-value tasks
  • Reward completion
  • Keep visible throughout

3. Progressive Disclosure

What: Reveal features as user is ready When: Feature-rich products Best practices:

  • Start with essentials
  • Unlock based on usage
  • Contextual introduction
  • Avoid overwhelming

4. Template/Example Start

What: Pre-populated starting point When: Blank canvas intimidation risk Best practices:

  • Relevant examples by use case
  • Easy to modify
  • Demonstrates key features
  • Quick path to value

5. Empty State Guidance

What: Helpful prompts in empty states When: User-generated content products Best practices:

  • Clear next step CTA
  • Educational content
  • Example preview
  • Remove friction to create

6. Contextual Tooltips

What: Just-in-time guidance When: Discoverable features Best practices:

  • Trigger on first encounter
  • Dismissible
  • Not too frequent
  • Action-oriented

Onboarding Flow Design

Pre-Boarding (Before First Use)

Welcome email:

  • Personal, warm greeting
  • Quick start links
  • Resource links
  • Reply-to for questions

Account setup:

  • Gather essential info only
  • Segment by use case
  • Customize experience
  • Set expectations

Initial Session (First Use)

Goals:

  1. Orient user
  2. Get to "aha moment"
  3. Establish next steps

Flow:

  1. Quick welcome (skip option)
  2. Use case selection
  3. Minimal setup
  4. First action guidance
  5. Celebrate success
  6. Clear next step

Follow-Up (Days 1-7)

Day 1:

  • Tip email with key feature
  • In-app prompt to continue
  • Track if returned

Day 2-3:

  • Feature discovery email
  • Address common stucks
  • Social proof / success stories

Day 7:

  • Progress summary
  • What's next
  • Upgrade/expand prompt if relevant

Activation Metrics

Identify Your Activation Event

Questions to answer:

  • What single action best predicts retention?
  • What's your product's "aha moment"?
  • What separates churned vs retained users?

Common activation events:

  • Created first [item]
  • Completed first [task]
  • Invited first [teammate]
  • Connected [integration]
  • Received first [result/value]

Measure & Optimize

Track:

  • Time to activation
  • Steps to activation
  • Activation rate by cohort
  • Drop-off points in flow

Benchmark:

  • Day 1 activation: 40-60%+
  • Day 7 activation: 60-80%+
  • Varies significantly by product

Friction Audit

Setup Friction

  • What's the minimum to start?
  • Can setup be deferred?
  • Are defaults sensible?
  • Is progress saved?

Learning Friction

  • Is the UI intuitive?
  • Is help easily accessible?
  • Are errors helpful?
  • Can users undo mistakes?

Value Friction

  • How many steps to value?
  • Can we shorten the path?
  • Are quick wins possible?
  • Is value obvious when reached?

Email Onboarding Sequence

Email 1: Welcome (Immediate)

  • Warm welcome
  • Login/quick start link
  • Set expectations
  • Single clear CTA

Email 2: Quick Win (Day 1)

  • Focus on one feature
  • Step-by-step guidance
  • Success story example
  • Try it CTA

Email 3: Discovery (Day 3)

  • Introduce key feature #2
  • Use case example
  • "Did you know..." angle
  • Explore CTA

Email 4: Social Proof (Day 5)

  • Customer success story
  • Relatable use case
  • Results achieved
  • Apply this CTA

Email 5: Check-in (Day 7)

  • Progress acknowledgment
  • Offer help
  • FAQ links
  • Support CTA

A/B Test Ideas

High Impact

  1. Onboarding flow length
  2. Required vs optional setup
  3. Template vs blank start
  4. Checklist vs tour
  5. Welcome email content

Medium Impact

  1. Progress indicator design
  2. Tooltip frequency
  3. Email timing
  4. CTA copy in flow
  5. Celebration moments

Quick Wins

  1. Add progress indicator
  2. Improve empty states
  3. Reduce required fields
  4. Add skip options
  5. Celebrate first success

Output Format

When optimizing onboarding, provide:

  1. Current flow analysis with friction points
  2. Activation event definition and current rate
  3. Recommended flow with wireframes/descriptions
  4. Email sequence outline
  5. Metrics dashboard setup
  6. A/B test roadmap

Related Skills

  • signup-flow-cro - For pre-onboarding optimization
  • email-sequence - For onboarding emails
  • marketing-psychology - For motivation techniques

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

copywriting

No summary provided by upstream source.

Repository SourceNeeds Review
General

social-content

No summary provided by upstream source.

Repository SourceNeeds Review
General

marketing-ideas

No summary provided by upstream source.

Repository SourceNeeds Review
General

paid-ads

No summary provided by upstream source.

Repository SourceNeeds Review