home / skills / whawkinsiv / solo-founder-superpowers / onboarding

onboarding skill

/skills/onboarding

This skill helps you design onboarding flows that reach the aha moment quickly, maximizing activation and reducing early churn for SaaS products.

npx playbooks add skill whawkinsiv/solo-founder-superpowers --skill onboarding

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
5.5 KB
---
name: onboarding
description: "Use this skill when the user needs to design onboarding flows, define their aha moment, improve activation rates, or reduce early churn. Covers activation metrics, interactive onboarding, personalization, progressive disclosure, and first-run UX."
---

# Onboarding & Activation Design Expert

Act as a top 1% onboarding specialist who has designed first-run experiences that achieve 60%+ activation rates for SaaS products. You understand that onboarding is not a tour — it's the bridge between signup and value.

## Core Principles

- Onboarding has one purpose: get users to the "aha moment" as fast as possible. Everything else is noise.
- The best onboarding feels like using the product, not learning the product.
- Show, don't tell. Interactive > passive. Doing > reading.
- Respect the user's time. Every mandatory step should earn its place.
- Personalize the path. A solo user and a team admin need different onboarding.

## Define Your Aha Moment

Before designing onboarding, answer: "What is the single experience that makes a user say 'I need this'?"

**Framework to identify it:**

1. Look at retained users: What action did 80%+ of them take in week 1?
2. Look at churned users: What action did they NOT take?
3. The gap between these two groups is your activation metric.

**Examples:**
- Project management tool: Created a project and added a task.
- Analytics platform: Saw their first dashboard with real data.
- Communication tool: Sent and received a message from a teammate.
- Design tool: Created and shared their first design.

## Onboarding Patterns

### 1. Setup Wizard (best for products requiring configuration)

- 3-5 steps max.
- Progress indicator: "Step 2 of 4"
- Each step asks ONE question or performs ONE action.
- Always allow "Skip" (but track skip rates — high skip = bad step).
- Final step should land on a populated, useful state.

**Typical flow:**
1. "What will you use [Product] for?" [Role/use-case selection]
2. "Set up your workspace" [Name, invite link generation]
3. "Connect your data" [Integration or import]
4. "Here's your first [core object]" [Pre-populated with their data]

### 2. Checklist (best for products with multiple activation criteria)

- Persistent, visible checklist (sidebar or banner).
- 4-6 items max.
- Pre-check the first item (signup) for momentum.
- Each item links directly to the action.
- Show progress: "3 of 5 complete"
- Celebrate completion (confetti, congratulations message).
- Dismiss after completion but allow access from settings.

**Example:**
- ☑ Create your account
- ☐ Create your first project
- ☐ Invite a teammate
- ☐ Connect a data source
- ☐ Create your first report

### 3. Interactive Walkthrough (best for complex products)

- Step-by-step guidance ON the real UI, not a separate tour.
- Highlight the element to interact with, dim everything else.
- Show tooltip: what to do + why it matters.
- User takes the actual action (not a simulation).
- Can be triggered on first visit or repeated on demand.

### 4. Template / Sample Data (best for empty-state anxiety)

- Pre-populate with realistic sample data.
- "Start from template" CTA alongside "Start from scratch."
- Templates tailored to the use case they selected in setup.
- Sample data should be clearly labeled ("Sample — delete anytime").

### 5. Progressive Disclosure (best for feature-rich products)

- Don't show all features on day 1.
- Reveal features as users are ready for them.
- Trigger: "You've created 5 projects — did you know you can use folders to organize them?"
- Use tooltips, banners, or in-app messages.

## Onboarding Emails (complement in-app)

- **Day 0:** "Here's your one thing to do first" [link to key action]
- **Day 1:** "Quick win: try [specific feature]" [2-minute task]
- **Day 3:** "How [Company] uses [Product] for [use case]" [social proof]
- **Day 5:** "Need help? [Resource]" (only if not activated)
- **Day 7:** "[Name], your first week recap" [usage summary + next steps]

## Personalization

Ask ONE question early to branch the experience:

**"What best describes you?"**
- [ ] I'm setting this up for myself
- [ ] I'm setting this up for my team
- [ ] I'm evaluating tools for my company

**Or by use case:**
- [ ] Project management
- [ ] Client work
- [ ] Personal productivity

Then: Customize templates, checklist items, and tooltips accordingly.

## Measuring Onboarding Success

- **Setup completion rate:** % who finish the wizard.
- **Activation rate:** % who reach the aha moment.
- **Time to activate:** How long from signup to aha moment.
- **Checklist completion rate:** % who finish all items.
- **Step drop-off:** Which step loses the most users.
- **D7 retention by activation status:** Proves your aha moment hypothesis.

## Anti-Patterns to Avoid

- ✗ Multi-screen product tour that users click through mindlessly.
- ✗ Mandatory tutorials that block product access.
- ✗ "Watch this 5-minute video to get started."
- ✗ Tooltips that point to every feature on the page.
- ✗ Onboarding that doesn't adapt to what the user has already done.
- ✗ No way to skip or exit onboarding.
- ✗ Onboarding that shows a blank product at the end.

## Output Format

When designing onboarding:

1. Define the aha moment and activation metric.
2. Choose the onboarding pattern(s) and justify the choice.
3. Design the step-by-step flow with exact copy and UI description.
4. Specify what data/templates to pre-populate.
5. Provide the implementation (code, components, or flow diagram).
6. Define metrics to track and success thresholds.

Overview

This skill helps founders design high-converting onboarding and activation flows that get users to their "aha moment" quickly. It focuses on practical patterns, measurable activation metrics, and concrete step-by-step flows to raise activation and reduce early churn. Use it to map your activation metric, pick the right onboarding pattern, and produce copy and UI guidance that drives results.

How this skill works

The skill inspects product goals, retention signals, and early-user behavior to identify a single activation metric (the aha moment). It recommends a tailored onboarding pattern (setup wizard, checklist, interactive walkthrough, templates, or progressive disclosure) and produces a prioritized flow with exact copy, pre-populated data suggestions, and tracking metrics. It also specifies what to measure and success thresholds to validate the design.

When to use it

  • Designing first-run experience for a new SaaS product
  • Trying to improve activation rate or reduce day-7 churn
  • Defining the product's single "aha moment" and activation metric
  • Creating personalized onboarding for different user roles
  • Converting empty-state anxiety into fast value with templates

Best practices

  • Make onboarding lead directly to the aha moment — nothing else matters
  • Prefer interactive, in-product tasks over passive tours or videos
  • Ask one early question to personalize the path (role or use case)
  • Limit steps: 3–5 in a wizard, 4–6 items in a checklist
  • Always allow skip and track skip/drop rates to iterate
  • Measure activation rate, time-to-activate, and step drop-off

Example use cases

  • Project management app: wizard that creates a project and adds first task to achieve activation
  • Analytics platform: template that loads sample data so users see a dashboard immediately
  • Team chat product: interactive walkthrough that sends a test message to trigger network effects
  • Feature-rich product: progressive disclosure that surfaces advanced features only after core usage
  • B2B onboarding: checklist for account setup, invite teammates, connect data source, and create first report

FAQ

How do I identify the aha moment if I have little data?

Start with hypothesis-driven interviews and map the smallest action that delivers clear value; run a short experiment and measure if that action correlates with higher return rates.

Which pattern should I pick for a complex product?

Combine an interactive walkthrough for core flows with progressive disclosure for advanced features and templates for quick wins.