onboarding

---
name: onboarding
description: >
license: MIT
---

# Onboarding

## Mandatory Content Standards

Every output from this skill follows these standards without exception.

- Match the output length to the task. For full audits, strategies, plans, or multi-part deliverables, write 1,500 to 10,000 words. For quick tasks, single assets, snippets, or narrow revisions, keep the output concise and provide only the useful variations, rationale, and next steps.
- Write in a way that sounds like a knowledgeable human wrote it. No robotic or templated phrasing.
- Use short sentences. One idea per sentence. One focus per paragraph.
- Use active voice. Never passive constructions.
- Address the reader directly using "you" and "your."
- Use bullet points only when they genuinely improve readability.
- Replace all em dashes with commas, parentheses, semicolons, or a new sentence. No hidden Unicode characters.
- End every sentence with a period.
- No hashtags, emojis, or asterisks.
- No introductory or closing filler phrases such as "in conclusion," "in summary," or "in a world where."
- No warnings, notes, or disclaimers. Stick to requested output.
- No AI cliches: no "game-changer," "unlock," "leverage," "dive into," "delve," "cutting-edge," "transformative," "revolutionize."
- No excessive adjectives or adverbs. Let specifics do the work.
- No AI cliches: no "game-changer," "unlock," "leverage," "dive into," "delve," "cutting-edge," "transformative," "revolutionize."
- No excessive adjectives or adverbs. Let specifics do the work.
- No broad generalizations. Every claim tied to specific context.
- Use specific examples, data, and scenarios.
- Pose at least one thought-provoking question per skill.
- Mobile-friendly: short paragraphs, clear headers, scannable.
- Practical and actionable. Every section connects to a next step.

---

## What This Skill Does

This skill helps you design, diagnose, and improve the post-signup onboarding experience. That includes everything from the first screen a new user sees through the moment they get enough value from your product to stick around.

Onboarding is not a welcome email sequence. It is not a product tour. It is the entire system that takes a new user from "I signed up" to "this product works for me." Most companies treat it as a single feature. The ones with the highest activation rates treat it as a continuous system.

The question worth sitting with before you start: what does a user need to experience to decide your product is worth continuing to use?

---

## How to Use This Skill

When you bring an onboarding problem, provide this context:

- What does your product do? One to two sentences, in customer language.
- What is your current activation rate, and how do you define activation?
- Where in the onboarding flow are users dropping off? (If you know.)
- What is the user's job to be done immediately after signup?
- What data, integrations, or setup does your product require before it is useful?
- Do you have onboarding emails currently? What is the open and click rate?

If you do not have clear answers to these questions, this skill will help you figure out what to measure first.

---

## Defining Activation

Activation rate is the percentage of new signups who reach a predefined milestone that correlates with long-term retention.

Most teams get activation wrong by defining it too broadly ("the user logged in twice") or too narrowly ("the user completed all 14 onboarding steps"). The right activation milestone is the action that most strongly predicts whether a user will still be using the product 30 days from now.

To find your activation milestone, you need retention data. Look at users who retained versus users who churned. What did the retained group do in their first session, or first week, that the churned group did not? That action (or set of actions) is your activation milestone.

Common activation milestones by product type:

- A project management tool might define activation as "created a project and invited at least one teammate."
- A reporting tool might define it as "ran a report on your own data."
- A CRM might define it as "imported contacts and logged one activity."
- An email tool might define it as "sent your first campaign to a list you own."

Notice that each of these milestones requires the user to use real data and achieve a real outcome. "Completed the tour" is not an activation milestone. Watching a tour does not predict retention. Doing a meaningful thing with the product does.

Once you define activation, you can measure your activation rate and start improving it systematically.

---

## The First-Run Experience

The first-run experience is the sequence of screens, prompts, and interactions a user encounters between signup and their first meaningful action in the product.

Most first-run experiences fail for one of three reasons:

They ask the user for information the product does not immediately use. A form asking for company size, industry, and role before the user has seen anything valuable feels like an interrogation.

They show a feature tour before the user has context for why the features matter. Showing someone a list of features they have not used yet is like showing someone a map of a city they have never been to.

They leave the user in a blank, empty interface with no clear next step.

A well-designed first-run experience does the opposite. It starts with the user's job to be done. It moves them toward value as quickly as possible. It defers setup questions until they are actually needed.

The test for your first-run experience: can a new user, with no help from your team, go from signup to completing their first meaningful action in under 10 minutes? If not, your first-run experience needs work.

The design sequence that works for most products:

1. One or two targeted questions that help the product personalize the experience. Not demographic information for your CRM. Questions that change what the user sees next.
2. A short, purposeful setup step that directly enables their first use. Import a file, connect an integration, create their first item.
3. An immediate payoff. Show them something useful based on what they just did.
4. A clear next step that builds on the first payoff.

---

## Empty State Strategy

An empty state is any screen in your product that shows no content yet because the user has not created or imported any. Empty states are one of the highest-leverage design opportunities in onboarding.

Most empty states fail because they show a blank screen with a vague CTA like "Get started" or "Create your first [thing]." This puts the entire burden of understanding what to do on the user.

Effective empty states do three things:

They tell the user what they will see here when they take action. "This is where you'll see all your campaigns once you send your first one" sets a clear expectation.

They show example content that demonstrates the value. A reporting tool might show a sample report with real-looking data. A CRM might show an example contact record. This gives the user a concrete picture of what they are building toward.

They provide a single clear action to fill the empty state. Not three options. One.

Empty states are also prime real estate for social proof at the moment of highest anxiety. A new user staring at a blank product interface is wondering whether they made the right decision. An empty state that shows "Here's how a team like yours started" with a brief testimonial directly addresses that doubt.

---

## Onboarding Checklists

An onboarding checklist is a persistent UI element that shows new users a prioritized list of setup tasks, with completion tracked as they finish each one.

Checklists work because of two psychological effects. First, progress momentum: completing an item on a list creates a positive feeling that motivates completing the next item. Second, completion anxiety: an incomplete list creates mild discomfort that motivates finishing.

Checklists do not work when they are too long, when the tasks are not clearly prioritized, or when completing the checklist does not clearly connect to the user getting value.

How to design an effective checklist:

Keep it short. Five to seven items maximum. A 12-item checklist is a to-do list for a full-time employee, not an onboarding guide.

Order items by dependency and value. The first item should be the one that makes the most other items possible. The last item should be the one that completes the user's first meaningful use of the product.

Write checklist items as action phrases, not feature names. "Connect your data source" is better than "Data source integration." "Invite your first teammate" is better than "Team management."

Show progress explicitly. A progress bar or "3 of 5 complete" counter increases completion rates. People respond to seeing how close they are to finishing.

When a user completes the checklist, celebrate it and immediately show them their next milestone. The checklist is not the end of onboarding. It is the beginning.

---

## Identifying the Aha Moment

The aha moment is the specific instant when a new user first understands, experientially, why your product is worth using. It is not a feature. It is an experience.

Slack's aha moment is sending and receiving a message in a real team conversation. Not reading about how Slack works. Not watching a demo. Actually feeling the speed of team communication in a live channel.

Dropbox's aha moment is seeing a file you saved on one device appear on another device without doing anything. The magic is in the experience, not the explanation.

Your aha moment might be obvious to you. But it is worth verifying with data. Interview users who converted from free to paid. Ask them: "Was there a specific moment when you knew this product was worth paying for? What were you doing?" The answers will cluster around a small number of specific in-product actions.

Once you know the aha moment, your entire onboarding system should be designed to get users there as fast as possible. Remove anything in the first-run experience that delays it. Add anything that accelerates it.

How many steps does it currently take for a new user to reach your aha moment? If the answer is more than five, you have an onboarding opportunity.

---

## Activation Milestone Definition

Your activation milestone is the measurable proxy for the aha moment. It is what you track as your activation metric.

The aha moment is experiential and hard to measure directly. The activation milestone is the observable action that corresponds to it. If your aha moment is "seeing automated reporting save you from manual work," your activation milestone might be "created a scheduled report."

Activation milestones should be:

Specific: not "engaged with the product" but "created a project with at least three tasks."

Time-bound: not just "ever did X" but "did X within 7 days of signup." Time-bounding forces you to focus on speed, not just eventual completion.

Correlated with retention: verify that users who hit the milestone retain at a meaningfully higher rate than users who do not.

Actionable: you should be able to design specific interventions (emails, in-app prompts, onboarding steps) to drive users toward the milestone.

Once you define your activation milestone, track it weekly. Build a dashboard that shows your activation rate for each cohort of new signups. When you make onboarding changes, look at whether the next cohort's activation rate improves.

---

## Onboarding Email Sequences

Onboarding emails are the communication layer that supports users through the first days and weeks of using your product. They do not replace in-app guidance. They support it.

The most effective onboarding email sequences have three phases:

Phase 1: Immediate value (Days 0-2). These emails help the user take their first meaningful action. They are triggered by signup and should arrive within minutes. Their job is to get the user back into the product if they signed up and did not complete setup.

The Day 0 email should be the confirmation email rewritten as a "here's what to do right now" email. Instead of "Thanks for signing up," it should say "Here's your first step" and give one specific action.

Phase 2: Activation (Days 3-7). These emails are triggered by what the user has and has not done. If the user already hit your activation milestone, these emails should push toward a second value moment. If the user has not activated, these emails should address the specific barrier.

Do not send the same email to everyone. A user who connected their data source but has not run a report needs a different email than a user who has not even finished setup.

Phase 3: Engagement and retention (Days 8-30). These emails shift from "help you set up" to "help you get more value." They highlight features the user has not discovered, share use cases relevant to their profile, and build toward the habit loop that drives retention.

Email metrics to watch:

- Open rate by email in the sequence. A drop-off at a specific email reveals where users are losing interest.
- Click-to-open rate. This shows whether the email content, not just the subject line, is relevant.
- In-app action rate after click. If users click but do not complete the intended action in the product, the problem is in the product, not the email.

---

## In-App Tooltip Strategy

Tooltips are small contextual messages that appear within the product interface to guide users toward specific actions or explain specific elements.

Most teams overuse tooltips. A product covered in tooltips trains users to ignore them. A product with one well-timed tooltip at the right moment creates a meaningful assist.

The principle: show a tooltip when a user encounters a new or unfamiliar element at the moment they are most likely to need it. Not on first login to every surface. At the moment the user first interacts with or navigates near a specific feature.

Types of tooltips and when to use each:

Announcement tooltips introduce a new feature to existing users. Show them once, triggered by the user's first visit to the area after the feature launches.

Guidance tooltips help users complete a specific action. These appear inline, adjacent to the element the user needs to interact with. Keep them one sentence. One action.

Dismissal is required. Every tooltip needs a clear way to dismiss it. If users cannot easily dismiss a tooltip, they will avoid the area of the product where it appears.

Tooltips should not explain. They should direct. "Click here to add your first data source" is a tooltip. "The data source connection module allows you to synchronize external data into the platform" is documentation that belongs in help center, not a tooltip.

---

## Diagnosing Low Activation Rates

If your activation rate is low, the problem is somewhere in the sequence from signup to first value. Finding it requires narrowing down where users are stopping.

Step 1: Map the activation path. Draw out every step between signup and your activation milestone. Include every screen, every prompt, every required action.

Step 2: Add analytics to every step. You need to know what percentage of users complete each step. Funnel analytics tools (Mixpanel, Amplitude, Heap) can show you the drop-off at each stage.

Step 3: Find the biggest drop-off. Where do you lose the most users? That is your highest-priority fix.

Step 4: Diagnose why. The drop-off data tells you where the problem is, not what the problem is. To understand why, you need to:

- Watch session recordings (Hotjar, FullStory) of users who drop off at that step. What are they doing before they leave?
- Survey users who did not activate. A simple email asking "You signed up last week but haven't [reached the milestone] yet. What got in the way?" produces more actionable data than most analytics.
- Talk to 5-10 users who did activate. What made it easy for them that was hard for others?

Common causes of low activation, and their fixes:

Setup is too complex: the product requires too much work before delivering value. Fix: reduce required setup to the minimum needed for a first payoff, and defer everything else.

The first payoff is not visible: the user completes setup but does not see anything that demonstrates value. Fix: design the first-payoff screen to be explicit about what just happened and why it matters.

The product requires data the user does not have ready: if your product requires a CSV import and the user does not have their data ready, they will leave and not come back. Fix: provide sample data or a demo mode so users can experience the product while they prepare their own data.

Users do not understand what to do next: after completing one step, they face an empty interface with no clear next action. Fix: explicit "your next step is X" prompts after every completed action.

---

## Measuring Activation Rate Improvements

Activation rate is a lagging metric. When you make an onboarding change today, you will not see the full impact until you observe what percentage of users who signed up this week hit the activation milestone within your time window (typically 7 or 14 days).

This means onboarding improvements take time to validate. Do not make five changes at once and try to attribute the result.

The measurement framework:

Define your activation rate clearly: "percentage of new signups who [activation milestone] within [X days]." Track this by weekly cohort.

Set a baseline: run at least four weeks of data before making changes. Understand natural variation in your activation rate.

Make one change at a time: isolate variables. If you rewrite your Day 1 email and simplify your setup flow in the same week, you cannot tell which change drove the improvement.

Wait for the full window: if your activation window is 14 days, wait 14 days after the last user in a cohort signed up before recording that cohort's rate.

Look for statistically significant changes: a two-percentage-point improvement might be real or might be noise. Track direction across three to four consecutive cohorts before concluding a change worked.

Leading indicators to watch while waiting for lagging activation data:

- Setup completion rate (what percentage of users complete initial setup).
- Time to first key action.
- In-app email click rates.
- Day 1, Day 3, and Day 7 return rates (what percentage of users come back).

---

## Onboarding for Different User Types

Not all users need the same onboarding. A well-designed system adapts based on user profile and behavior.

Segmentation that typically matters:

Role: a team admin who is evaluating the product for their team needs different onboarding than an individual contributor who was invited to join. The admin needs to see team management and configuration. The contributor needs to see their personal use case.

Technical sophistication: a user who immediately navigates to API settings needs different guidance than a user who has never used this category of product before.

Use case: if your product serves multiple use cases, users who identify their use case at signup should see an onboarding flow relevant to that use case, not a generic flow.

Behavior: a user who signs up and immediately starts exploring the product is different from a user who signs up, spends two minutes on the empty dashboard, and then goes idle. The idle user needs a re-engagement prompt. The active user needs to be channeled toward the activation milestone.

Most products start with a single onboarding flow and add personalization over time as they learn where the biggest experience gaps are. That is the right approach. Do not build a complex segmented system before you understand the basics.

---

## Common Onboarding Mistakes

Making the welcome email about your company, not the user's next step. No user cares about your company's story in the first email. They care about what to do right now.

Requiring account setup before showing value. If the user has to enter billing information, configure settings, and invite their team before seeing anything useful, they will leave.

Running a linear checklist for a non-linear product. If users can do things in any order, a checklist that assumes a specific sequence will frustrate users who have already done step 3 but not step 1.

Sending the same email to every user regardless of behavior. Behavior-triggered emails convert 3-5x better than time-based emails in most tests. Set up branching based on whether users have hit your activation milestone.

Measuring completion of the onboarding tour instead of actual activation. The tour is a means to an end. If users complete the tour but do not activate, the tour is not working.

Treating onboarding as a one-time project. Onboarding degrades over time as your product changes. The setup flow that worked when you had five features does not work when you have fifty. Revisit onboarding quarterly.