Back to Details

onboarding-cro

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Onboarding CRO

Onboarding CRO

Design and optimize user onboarding flows that drive activation and long-term retention.
设计并优化用户Onboarding流程，驱动用户激活与长期留存。

1. Onboarding Frameworks

1. Onboarding 框架

Jobs-To-Be-Done (JTBD) Onboarding

Jobs-To-Be-Done (JTBD) Onboarding

The best onboarding flows are organized around the user's job, not the product's features.
Process:
  1. Identify the user's primary job-to-be-done
  2. Map the minimum steps to complete that job in your product
  3. Guide the user through those steps, removing all distractions
  4. Celebrate completion (aha moment)
Example (Notion):
  • Job: "I need to organize my team's projects"
  • Steps: Create workspace > Invite team > Create first page > Use a template
  • The onboarding flow guides exactly this path, nothing more
Anti-pattern: Feature tours that show every feature. Users do not care about features during onboarding; they care about solving their problem.
优秀的Onboarding流程围绕用户的核心需求（Job）构建，而非产品功能。
流程：
  1. 明确用户的核心需求
  2. 梳理产品中完成该需求的最少步骤
  3. 引导用户完成这些步骤，移除所有干扰项
  4. 为用户的完成动作庆祝（即Aha Moment）
示例（Notion）：
  • 用户需求：“我需要整理团队的项目”
  • 步骤：创建工作区 > 邀请团队成员 > 创建首个页面 > 使用模板
  • Onboarding流程仅引导用户完成这条路径，无多余内容
**反模式：**展示所有功能的产品导览。用户在Onboarding阶段并不关心功能，他们只关注如何解决自己的问题。

Progressive Disclosure

渐进式披露（Progressive Disclosure）

Reveal functionality gradually as users demonstrate readiness.
Levels:
  1. First session: Only show core functionality needed for primary job
  2. After first success: Introduce secondary features that enhance the core workflow
  3. After repeated use: Surface power features, integrations, customization
  4. After mastery: Invite to advanced features, API, automation
Implementation:
  • Use feature flags or user state to control what's visible
  • Track user actions to determine when to advance disclosure level
  • Never show everything at once
随着用户展现出使用意愿，逐步开放功能。
层级：
  1. **首次会话：**仅展示完成核心需求所需的基础功能
  2. **首次成功后：**介绍可增强核心工作流的次要功能
  3. **重复使用后：**呈现高级功能、集成工具与自定义选项
  4. **熟练使用后：**邀请用户体验进阶功能、API与自动化工具
实施方式：
  • 使用功能开关或用户状态控制可见内容
  • 追踪用户行为，判断何时升级披露层级
  • 切勿一次性展示所有功能

Activation Metrics

激活指标（Activation Metrics）

Define your activation metric before designing onboarding. The activation metric is the action most correlated with long-term retention.
Examples:
ProductActivation MetricTimeframe
SlackSend 2,000 messages (team)First 30 days
DropboxUpload 1 file from 2 devicesFirst 7 days
FacebookAdd 7 friendsFirst 10 days
ZoomHost first meetingFirst 7 days
NotionCreate 3 pagesFirst 7 days
FigmaCreate first designFirst 3 days
HubSpotImport contacts + send first emailFirst 14 days
How to find your activation metric:
  1. Cohort analysis: Compare retained vs churned users
  2. Identify actions that retained users took that churned users did not
  3. Find the action with strongest correlation to 30-day retention
  4. Validate by testing whether guiding users to that action improves retention
在设计Onboarding流程前，先定义你的激活指标。激活指标是与长期留存相关性最高的用户行为。
示例：
产品激活指标时间范围
Slack团队发送2000条消息前30天
Dropbox从2台设备上传1个文件前7天
Facebook添加7位好友前10天
Zoom主持首次会议前7天
Notion创建3个页面前7天
Figma创建首个设计文件前3天
HubSpot导入联系人并发送首封邮件前14天
如何找到你的激活指标：
  1. 群组分析：对比留存用户与流失用户
  2. 找出留存用户完成、但流失用户未完成的行为
  3. 找到与30天留存相关性最强的行为
  4. 通过测试验证：引导用户完成该行为是否能提升留存率

Aha Moment Identification

Aha Moment 识别

The aha moment is when a user first experiences the core value of your product.
Framework for identifying it:
  1. What do users say when they recommend your product? ("It's amazing because...")
  2. When during their journey do users typically say "wow" or "this is cool"?
  3. What single action separates users who stay from those who leave?
The aha moment is NOT:
  • Signing up
  • Completing onboarding
  • Seeing a feature demo
The aha moment IS:
  • Getting their first result
  • Experiencing time saved
  • Seeing their data visualized for the first time
  • Completing their first task successfully
Aha Moment是用户首次体验到产品核心价值的时刻。
识别框架：
  1. 用户推荐产品时会怎么说？（“它很棒，因为……”）
  2. 用户在旅程中的哪个阶段通常会说“哇”或“这太酷了”？
  3. 哪个单一行为能区分留存用户与流失用户？
Aha Moment 不是：
  • 注册账号
  • 完成Onboarding流程
  • 观看功能演示
Aha Moment 是：
  • 获得首个成果
  • 感受到时间节省
  • 首次看到自己的数据可视化效果
  • 成功完成首个任务

2. Onboarding Components

2. Onboarding 组件

Welcome Screens

欢迎界面（Welcome Screens）

The first screen after signup. Serves two purposes: make the user feel welcomed and collect information for personalization.
Best Practices:
  • Use the user's name ("Welcome, Sarah!")
  • Keep it to 1-3 questions maximum
  • Use visual selectors (cards with icons) instead of dropdowns
  • Every question should directly affect their experience
  • Always allow skipping
Template:
Welcome to [Product], [Name]!

Let's personalize your experience.

What's your primary goal?
[ ] [Goal 1 -- with icon]
[ ] [Goal 2 -- with icon]
[ ] [Goal 3 -- with icon]
[ ] Something else

[Continue]  [Skip for now]
Example (Notion):
What will you use Notion for?
[Personal] [Team] [School]

How big is your team?
[Just me] [2-10] [11-50] [50+]
用户注册后的首个界面，有两个作用：让用户感受到被欢迎，以及收集信息用于个性化服务。
最佳实践：
  • 使用用户姓名（“欢迎，Sarah！”）
  • 最多设置1-3个问题
  • 使用带图标的卡片选择器而非下拉菜单
  • 每个问题都应直接影响用户体验
  • 始终提供跳过选项
模板：
欢迎来到[产品], [姓名]!

让我们为你定制专属体验。

你的核心目标是什么？
[ ] [目标1 -- 带图标]
[ ] [目标2 -- 带图标]
[ ] [目标3 -- 带图标]
[ ] 其他需求

[继续]  [稍后跳过]
示例（Notion）：
你将用Notion做什么？
[个人使用] [团队协作] [校园学习]

你的团队规模是？
[仅我自己] [2-10人] [11-50人] [50人以上]

Setup Wizards

设置向导（Setup Wizards）

Guided multi-step flows that set up the product for use.
When to use: When the product requires configuration before it can deliver value (CRM, analytics, marketing automation).
Best Practices:
  • Maximum 3-5 steps
  • Show progress indicator
  • Pre-fill defaults where possible
  • Allow skipping non-essential steps
  • Provide "try it with sample data" option
  • End with a clear next action, not a blank screen
Template:
Step 1: Connect your [data source]
  [Connect Google] [Connect manually] [Use sample data]

Step 2: Configure your [workspace/project]
  [Pre-filled sensible defaults with edit option]

Step 3: Invite your team (optional)
  [Email input] [Copy invite link] [Skip]

You're all set!
  [Go to your dashboard]
引导式多步骤流程，帮助用户完成产品配置。
**适用场景：**产品需要先完成配置才能交付价值时（如CRM、分析工具、营销自动化平台）。
最佳实践：
  • 最多3-5个步骤
  • 显示进度指示器
  • 尽可能预填默认值
  • 允许跳过非必要步骤
  • 提供“使用示例数据体验”选项
  • 流程结束时给出明确的下一步动作，而非空白界面
模板：
步骤1：连接你的[数据源]
  [连接谷歌] [手动连接] [使用示例数据]

步骤2：配置你的[工作区/项目]
  [预填合理默认值，支持编辑]

步骤3：邀请你的团队（可选）
  [邮箱输入框] [复制邀请链接] [跳过]

设置完成！
  [前往你的仪表盘]

Product Tours

产品导览（Product Tours）

Interactive walkthroughs of the product interface.
Types:
  1. Tooltip tour: Highlights UI elements with explanatory tooltips (Intercom, Appcues)
  2. Video walkthrough: Short video showing key workflows
  3. Interactive tutorial: User performs real actions with guidance
  4. Sandbox mode: Pre-populated environment for safe exploration
Best Practices:
  • Keep tours under 5 steps (3 is ideal)
  • Focus on ONE workflow per tour
  • Let users exit at any point
  • Make the user DO something, not just read
  • Trigger contextually (first time visiting a feature), not globally
  • Never replay completed tours unless user requests it
Anti-patterns:
  • 15-step tours that show every button
  • Forced tours that cannot be dismissed
  • Tours that explain obvious UI elements
  • Tours that trigger repeatedly
Template (per step):
Step [X] of [Y]:

[Pointer to UI element]

"[Action verb] here to [achieve result]."

[Try it now] / [Next] / [Skip tour]
交互式的产品界面 walkthrough。
类型：
  1. **提示框导览：**用提示框突出UI元素并解释（如Intercom、Appcues）
  2. **视频导览：**展示关键工作流的短视频
  3. **交互式教程：**引导用户完成真实操作
  4. **沙盒模式：**预填充环境供用户安全探索
最佳实践：
  • 导览步骤控制在5步以内（3步最佳）
  • 每次导览聚焦一个工作流
  • 允许用户随时退出
  • 让用户实际操作，而非仅阅读
  • 上下文触发（首次访问某功能时触发），而非全局触发
  • 除非用户主动请求，否则不要重复播放已完成的导览
反模式：
  • 15步的全功能导览
  • 无法关闭的强制导览
  • 解释明显UI元素的导览
  • 重复触发的导览
单步骤模板：
第[X]步/共[Y]步：

[指向UI元素的指示器]

“点击此处以[达成某结果]。”

[立即尝试] / [下一步] / [跳过导览]

Onboarding Checklists

引导任务清单（Onboarding Checklists）

Persistent task lists that guide users through activation.
Why they work:
  • Zeigarnik effect: People feel compelled to complete unfinished tasks
  • Clear progress visualization
  • Users self-pace through the list
  • Can be dismissed and revisited
Template:
Get started with [Product]  [3/5 complete]

[x] Create your account
[x] Set up your profile
[x] [First key action]
[ ] [Second key action] <-- "Do this next"
[ ] [Third key action]

[Dismiss checklist]
Best Practices:
  • 4-6 items maximum
  • Pre-check easy items (account creation) for momentum
  • Order by dependency and importance
  • Highlight the next recommended step
  • Celebrate completion (confetti, badge, reward)
  • Include at least one "aha moment" action
  • Show percentage complete or progress bar
Example (Slack):
Getting started  [2/4]
[x] Set your profile photo
[x] Join a channel
[ ] Send your first message
[ ] Invite a teammate
Example (Figma):
Welcome to Figma  [1/5]
[x] Create your account
[ ] Create a design file
[ ] Add a frame
[ ] Use a component
[ ] Share with your team
持续显示的任务清单，引导用户完成激活。
为何有效：
  • 蔡格尼克效应：人们会被未完成的任务驱动
  • 清晰的进度可视化
  • 用户可自主控制节奏
  • 可关闭并重新访问
模板：
开始使用[产品]  [3/5已完成]

[x] 创建账号
[x] 设置个人资料
[x] [首个关键动作]
[ ] [第二个关键动作] <-- “下一步请完成此项”
[ ] [第三个关键动作]

[关闭任务清单]
最佳实践：
  • 最多4-6个任务项
  • 预先勾选简单任务（如账号创建）以建立动力
  • 按依赖关系与重要性排序
  • 高亮推荐的下一步动作
  • 庆祝完成（如撒花动画、徽章、奖励）
  • 至少包含一个“Aha Moment”动作
  • 显示完成百分比或进度条
示例（Slack）：
开始使用  [2/4已完成]
[x] 设置个人头像
[x] 加入一个频道
[ ] 发送首条消息
[ ] 邀请一位同事
示例（Figma）：
欢迎使用Figma  [1/5已完成]
[x] 创建账号
[ ] 创建设计文件
[ ] 添加框架
[ ] 使用组件
[ ] 分享给团队

Email Onboarding Sequences

邮件引导序列（Email Onboarding Sequences）

Drip emails that complement the in-app experience.
Sequence structure:
DayEmailPurpose
0Welcome + quick startImmediate value, link to first action
1Tip: [Core feature]Teach one key feature
3Social proofShow what others achieve with the product
5"Need help?"Address common obstacles, offer support
7Feature highlightIntroduce a secondary feature
10Activation reminderIf not activated, nudge toward key action
14Upgrade promptIf activated, pitch premium features
Day 0 Welcome Email Template:
Subject: Welcome to [Product] -- here's your quick start

Hi [Name],

You're in! Here's how to get the most out of [Product] in the next 5 minutes:

1. [First action] -- [link directly to it]
2. [Second action] -- [link]
3. [Third action] -- [link]

[Primary CTA: "Go to your dashboard"]

Need help? Reply to this email or check our [getting started guide].

[Signature]
Day 3 Social Proof Email Template:
Subject: How [Customer] uses [Product] to [Result]

Hi [Name],

Did you know that [Customer/Company] uses [Product] to [specific result with metric]?

Here's what they did:
1. [Step they took]
2. [Step they took]
3. [Result they achieved]

You can do the same:
[CTA: "Try it now"]
与应用内体验互补的 drip 邮件序列。
序列结构：
天数邮件内容目的
0欢迎邮件+快速上手指南即时传递价值，链接至首个动作
1技巧：[核心功能]教授一个关键功能
3社交证明展示其他用户通过产品获得的成果
5“需要帮助吗？”解决常见障碍，提供支持
7功能亮点介绍次要功能
10激活提醒若用户未激活，引导其完成关键动作
14升级提示若用户已激活，推广付费功能
第0天欢迎邮件模板：
主题：欢迎使用[产品] -- 快速上手指南

嗨[姓名]，

你已成功加入！以下是5分钟内玩转[产品]的方法：

1. [首个动作] -- [直接链接]
2. [第二个动作] -- [链接]
3. [第三个动作] -- [链接]

[主要CTA：“前往你的仪表盘”]

需要帮助？回复此邮件或查看我们的[快速上手指南]。

[签名]
第3天社交证明邮件模板：
主题：[客户]如何用[产品]实现[成果]

嗨[姓名]，

你知道吗？[客户/公司]使用[产品]实现了[带数据的具体成果]。

他们的做法是：
1. [步骤1]
2. [步骤2]
3. [达成的成果]

你也可以做到：
[CTA：“立即尝试”]

3. Onboarding Examples from Top Products

3. 顶级产品的Onboarding示例

Notion

Notion

What they do well:
  • Welcome screen asks role + use case (2 questions)
  • Offers templates based on selection
  • Pre-populates workspace with starter content
  • Progressive disclosure: basic blocks first, databases later
  • Checklist in sidebar tracks setup progress
  • Empty states have clear CTAs
Activation metric: Create 3+ pages in first 7 days
亮点：
  • 欢迎界面询问角色与使用场景（2个问题）
  • 根据选择提供对应模板
  • 预填充工作区的初始内容
  • 渐进式披露：先展示基础块，再开放数据库
  • 侧边栏的任务清单追踪设置进度
  • 空状态界面有明确的CTA
**激活指标：**前7天创建3个以上页面

Slack

Slack

What they do well:
  • Workspace setup wizard is 3 steps (name, invite, channel)
  • Slackbot guides first interactions conversationally
  • Pre-created #general and #random channels with welcome messages
  • Teaches features by having users use them (send a message, react with emoji)
  • Onboarding checklist in sidebar
Activation metric: Team sends 2,000 messages in first 30 days
亮点：
  • 工作区设置向导仅3步（命名、邀请成员、创建频道）
  • Slackbot以对话形式引导首次交互
  • 预创建#general与#random频道并附带欢迎消息
  • 通过让用户实际操作来教授功能（发送消息、用表情反应）
  • 侧边栏的引导任务清单
**激活指标：**团队在前30天发送2000条消息

Figma

Figma

What they do well:
  • Minimal signup (Google OAuth one-click)
  • Immediately drops user into a canvas with interactive tutorial
  • Tutorial teaches by doing (create shape, move it, style it)
  • Sample files available to explore
  • Team collaboration demonstrated early (cursor presence)
Activation metric: Create first design file in first 3 days
亮点：
  • 极简注册（谷歌OAuth一键登录）
  • 直接将用户带入带有交互式教程的画布
  • 教程通过实操教学（创建形状、移动、样式设置）
  • 提供示例文件供探索
  • 早期展示团队协作（光标实时显示）
**激活指标：**前3天创建首个设计文件

Canva

Canva

What they do well:
  • Asks "What will you design today?" with visual categories
  • Immediately shows templates relevant to selection
  • First design experience uses pre-made template (user edits, not creates from scratch)
  • Celebrates first download with sharing prompt
亮点：
  • 询问“你今天要设计什么？”并提供可视化分类
  • 立即展示与选择相关的模板
  • 首次设计体验使用预制模板（用户只需编辑，无需从零创建）
  • 庆祝首次下载并提示分享

Linear

Linear

What they do well:
  • Import from existing tools (Jira, Asana) as first step
  • Pre-configured with sensible defaults (workflow states, labels)
  • Keyboard shortcuts taught in context
  • Empty states show exactly what to do next
亮点：
  • 将从现有工具（Jira、Asana）导入数据作为第一步
  • 预配置合理默认值（工作流状态、标签）
  • 上下文教学键盘快捷键
  • 空状态界面明确告知下一步动作

4. Measuring Onboarding Success

4. 衡量Onboarding成功

Key Metrics

核心指标

MetricFormulaTarget
Onboarding completion rateUsers who complete onboarding / signups60-80%
Time to first key actionTime from signup to first meaningful actionUnder 5 min
Activation rateUsers hitting activation metric / signups20-40%
Day 1 retentionUsers returning day after signup / signups40-60%
Day 7 retentionUsers returning 7 days after signup / signups20-35%
Day 30 retentionUsers active 30 days after signup / signups10-25%
Onboarding step drop-offUsers completing step N / users starting step NTrack per step
Time to value (TTV)Median time from signup to aha momentAs low as possible
指标计算公式目标值
Onboarding完成率完成Onboarding的用户数 / 注册用户数60-80%
首次关键动作耗时从注册到完成首个有意义动作的时间5分钟以内
激活率完成激活指标的用户数 / 注册用户数20-40%
次日留存率注册次日返回的用户数 / 注册用户数40-60%
7日留存率注册7日后返回的用户数 / 注册用户数20-35%
30日留存率注册30日后活跃的用户数 / 注册用户数10-25%
Onboarding步骤流失率完成第N步的用户数 / 进入第N步的用户数按步骤追踪
价值实现时间（TTV）从注册到Aha Moment的中位时间越短越好

Funnel Analysis

漏斗分析

Build an onboarding funnel in your analytics tool:
Signup completed
  -> Welcome screen completed
    -> First key action
      -> Second key action (aha moment)
        -> Activation metric reached
          -> Day 7 return
Track conversion rate between each step. The biggest drop-off is your biggest opportunity.
在分析工具中构建Onboarding漏斗：
完成注册
  -> 完成欢迎界面
    -> 完成首个关键动作
      -> 完成第二个关键动作（Aha Moment）
        -> 达成激活指标
          -> 7日返回
追踪每个步骤间的转化率。流失率最高的步骤就是最大的优化机会。

5. A/B Test Ideas for Onboarding

5. Onboarding的A/B测试思路

Welcome Screen

欢迎界面

  1. 1 question vs 3 questions on welcome screen
  2. Visual card selection vs dropdown
  3. Personalized template suggestions vs generic
  1. 1个问题 vs 3个问题的欢迎界面
  2. 可视化卡片选择 vs 下拉菜单
  3. 个性化模板推荐 vs 通用模板

Setup Flow

设置流程

  1. Guided setup vs "explore on your own"
  2. Pre-populated sample data vs empty state
  3. Setup wizard vs onboarding checklist
  1. 引导式设置 vs “自主探索”
  2. 预填充示例数据 vs 空状态
  3. 设置向导 vs 引导任务清单

Product Tour

产品导览

  1. Tooltip tour vs video walkthrough
  2. 3-step tour vs 5-step tour
  3. Auto-triggered tour vs user-initiated
  1. 提示框导览 vs 视频导览
  2. 3步导览 vs 5步导览
  3. 自动触发导览 vs 用户主动触发

Activation

激活环节

  1. Email nudge on day 1 vs day 3 for inactive users
  2. In-app prompt for next action vs no prompt
  3. Celebrating milestones (confetti, badge) vs no celebration
  4. Showing progress ("You're 60% set up") vs not showing
  1. 对未活跃用户在第1天 vs 第3天发送邮件提醒
  2. 应用内下一步动作提示 vs 无提示
  3. 庆祝里程碑（撒花、徽章） vs 无庆祝
  4. 显示进度（“你已完成60%的设置”） vs 不显示进度

Engagement

参与度

  1. Daily tip emails vs weekly digest
  2. Push notifications for incomplete onboarding vs email only
  3. Peer comparison ("Teams like yours usually...") vs no comparison
  1. 每日技巧邮件 vs 每周摘要
  2. 推送通知提醒未完成Onboarding vs 仅邮件提醒
  3. 同行对比（“与你类似的团队通常会……”） vs 无对比

6. Onboarding Audit Template

6. Onboarding审计模板

When auditing an existing onboarding flow:
undefined
审计现有Onboarding流程时使用：
undefined

Onboarding Audit: [Product Name]

Onboarding审计：[产品名称]

Date: [Date]

日期：[日期]

Current Flow Map

当前流程地图

[Step-by-step flow with screenshots]
[带截图的分步流程]

Time to Complete

完成时间

  • Minimum path: [X] minutes
  • Average path: [X] minutes
  • 最短路径：[X]分钟
  • 平均路径：[X]分钟

Drop-off Analysis

流失分析

StepUsers EnteringCompletion RateDrop-off
Signup100%X%X%
Welcome screenX%X%X%
Setup step 1X%X%X%
Setup step 2X%X%X%
First key actionX%X%X%
ActivationX%----
步骤进入用户占比完成率流失率
注册100%X%X%
欢迎界面X%X%X%
设置步骤1X%X%X%
设置步骤2X%X%X%
首个关键动作X%X%X%
激活X%----

Scores (1-10)

评分（1-10分）

DimensionScoreNotes
Time to valueX
Clarity of next stepX
Progressive disclosureX
Error recoveryX
Mobile experienceX
PersonalizationX
OverallX
维度分数备注
价值实现时间X
下一步动作清晰度X
渐进式披露X
错误恢复X
移动端体验X
个性化程度X
整体评分X

Issues Found

发现的问题

  1. [Critical] [Issue] -- Impact: [X]% activation loss
  2. [High] [Issue]
  3. [Medium] [Issue]
  1. [严重] [问题描述] -- 影响：[X]%的激活率损失
  2. [高优先级] [问题描述]
  3. [中优先级] [问题描述]

Recommendations (Priority Order)

建议（按优先级排序）

  1. [Recommendation] -- Expected lift: X% on [metric]
  2. [Recommendation] -- Expected lift: X%
  3. [Recommendation] -- Expected lift: X%
  1. [建议内容] -- 预期提升：[X]%的[指标]
  2. [建议内容] -- 预期提升：X%
  3. [建议内容] -- 预期提升：X%

Quick Wins

快速优化项

  • [Immediate fix]
  • [Immediate fix]
  • [立即修复内容]
  • [立即修复内容]

Long-term Improvements

长期改进项

  • [Bigger initiative]
  • [Bigger initiative]

---
  • [大型改进计划]
  • [大型改进计划]

---

7. Common Onboarding Mistakes

7. 常见的Onboarding错误

  1. Showing everything at once -- Overwhelms users. Use progressive disclosure.
  2. Explaining features, not outcomes -- "This is our dashboard" vs "See your results here."
  3. Forcing completion before value -- Let users explore, then guide.
  4. No empty state strategy -- Blank screens kill activation. Use templates, samples, or guided prompts.
  5. One-size-fits-all flow -- Different user types need different onboarding paths.
  6. Ignoring mobile -- Mobile onboarding needs its own design (not a shrunk desktop flow).
  7. No re-engagement for drop-offs -- Users who abandon onboarding need targeted email nudges.
  8. Celebrating signup, not activation -- "Welcome!" is not the goal. The first success moment is.
  9. Too many tooltips -- If you need 10 tooltips, your UI is too complex.
  10. No measurement -- If you are not tracking step-by-step drop-offs, you are guessing.
  1. 一次性展示所有功能 -- 让用户不知所措。使用渐进式披露。
  2. 解释功能而非价值 -- “这是我们的仪表盘” vs “在这里查看你的成果”。
  3. 强制完成后才提供价值 -- 让用户先探索，再进行引导。
  4. 无空状态策略 -- 空白界面会扼杀激活率。使用模板、示例或引导式提示。
  5. 一刀切的流程 -- 不同类型的用户需要不同的Onboarding路径。
  6. 忽视移动端 -- 移动端Onboarding需要独立设计（而非桌面端的缩小版）。
  7. 不对流失用户进行再触达 -- 放弃Onboarding的用户需要针对性的邮件提醒。
  8. 庆祝注册而非激活 -- “欢迎！”不是目标，首次成功时刻才是。
  9. 过多提示框 -- 如果你需要10个提示框，说明你的UI过于复杂。
  10. 无数据度量 -- 如果你不追踪每一步的流失率，那就是在凭猜测优化。