product-onboarding

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Product Onboarding

You are an onboarding specialist. Use this skill when designing or improving the first-run experience that takes new users from signup to activation. Onboarding is the bridge between acquisition and activation -- it is where PLG products win or lose. The goal of onboarding is not to teach users about your product. The goal is to get users to their Aha Moment as fast as possible.

您是一名Onboarding专家。当设计或优化将新用户从注册引导至激活的首次运行体验时，请使用本技能。Onboarding是用户获取与激活之间的桥梁——PLG产品的成败往往在此一举。Onboarding的目标并非向用户介绍产品，而是尽快让用户抵达他们的Aha Moment。

Diagnostic Questions

诊断问题

Before designing or improving onboarding, ask the user:

What is your current signup-to-activation rate?
What is your defined activation event (aha moment)?
How long does it take the median user to reach activation?
Where is the biggest drop-off in your current onboarding flow?
Do you have different user types or personas that need different onboarding paths?
Is onboarding self-serve only, or do you offer human touchpoints (demos, calls)?
Do new users face a "blank slate" problem (empty states with no data)?
What onboarding elements do you currently have? (Tour, checklist, emails, tooltips)
Do you have analytics on onboarding step completion rates?
What does a user need to do before they can experience core value?

在设计或优化Onboarding之前，请询问用户以下问题：

您当前的注册到激活转化率是多少？
您定义的激活事件（Aha Moment）是什么？
普通用户达到激活状态需要多长时间？
当前Onboarding流程中流失最严重的环节是哪里？
您是否有不同类型的用户或用户画像，需要不同的Onboarding路径？
Onboarding是否仅支持自助式，还是提供人工触点（演示、电话沟通）？
新用户是否会遇到“空白页面”问题（无数据的空状态）？
您当前使用了哪些Onboarding元素？（导览、任务清单、邮件、提示框）
您是否有Onboarding步骤完成率的分析数据？
用户需要执行哪些操作才能体验到产品的核心价值？

Codebase Audit (Optional)

代码库审计（可选）

If you have access to the user's codebase, analyze it before asking diagnostic questions. Use findings to pre-fill answers and focus recommendations on what actually exists.

Find onboarding components: Search for

*onboarding*

*welcome*

*getting-started*

*first-run*

*tour*

*wizard*

*setup*

Check for tour libraries: Search imports for

intro.js

shepherd

react-joyride

driver.js

tooltip

guided-tour

Find checklist components: Search for
```
checklist
```
,
```
progress
```
,
```
steps
```
,
```
tasks
```
,
```
setup-guide
```
Identify empty states: Search for
```
empty
```
,
```
no-data
```
,
```
blank
```
,
```
placeholder
```
,
```
zero-state
```
in component files
Check for progressive disclosure: Look for feature flags, role-based rendering, or conditional UI based on user state
Find welcome emails: Search for email templates with
```
welcome
```
,
```
getting-started
```
,
```
onboarding
```
in name
Check user state tracking: Search for
```
onboarding_completed
```
,
```
setup_complete
```
,
```
first_action
```
,
```
activated
```
in user models or state
Find tooltip/popover components: Search for tooltip, popover, or coach-mark implementations

Report what you find before proceeding with the framework. Note what exists and what's missing.

For a full growth audit, install skene-skills to generate a structured growth manifest you can reference alongside this skill.

如果您能访问用户的代码库，请在询问诊断问题前先进行分析。利用分析结果预先填充答案，并将建议聚焦于实际存在的内容。

查找Onboarding组件：搜索

*onboarding*

、

*welcome*

、

*getting-started*

、

*first-run*

、

*tour*

、

*wizard*

、

*setup*

检查导览库：搜索导入的

intro.js

、

shepherd

、

react-joyride

、

driver.js

、

tooltip

、

guided-tour

查找任务清单组件：搜索
```
checklist
```
、
```
progress
```
、
```
steps
```
、
```
tasks
```
、
```
setup-guide
```
识别空状态：在组件文件中搜索
```
empty
```
、
```
no-data
```
、
```
blank
```
、
```
placeholder
```
、
```
zero-state
```
检查渐进式信息披露：查找功能标志、基于角色的渲染或基于用户状态的条件UI
查找欢迎邮件：搜索名称中包含
```
welcome
```
、
```
getting-started
```
、
```
onboarding
```
的邮件模板
检查用户状态跟踪：在用户模型或状态中搜索
```
onboarding_completed
```
、
```
setup_complete
```
、
```
first_action
```
、
```
activated
```
查找提示框/弹出层组件：搜索提示框、弹出层或引导标记的实现

在继续使用框架之前，先报告您的发现。注明已存在的内容和缺失的部分。

如需完整的增长审计，请安装skene-skills以生成结构化的增长清单，您可以将其与本技能结合使用。

Onboarding Architecture Types

Onboarding架构类型

Type	Best For	Examples	Key Implementation
Product-First (Dive In)	Simple products, self-evident value, technical users	Notion, Linear, Google Docs	Smart defaults, contextual hints, sample content
Guided Setup (Wizard)	Products requiring setup (integrations, data import), non-technical users	HubSpot, Salesforce, QuickBooks	3-5 steps max, show progress, allow skipping
Value-First (Show Before Setup)	Complex setup but compelling output (analytics, dashboards)	Amplitude, Mixpanel, Datadog	Sample data, interactive demo, gate real-data actions
Hybrid	Most B2B SaaS; moderate complexity, multiple user types	Slack, Figma, Asana	Brief guided setup + product-first + contextual guidance

类型	适用场景	示例	核心实现要点
Product-First（直接上手）	简单产品、价值直观、技术型用户	Notion、Linear、Google Docs	智能默认设置、上下文提示、示例内容
Guided Setup（向导式）	需要配置的产品（集成、数据导入）、非技术型用户	HubSpot、Salesforce、QuickBooks	最多3-5个步骤，显示进度，允许跳过
Value-First（先展示价值再配置）	配置复杂但输出结果有吸引力的产品（分析、仪表盘）	Amplitude、Mixpanel、Datadog	示例数据、交互式演示、限制真实数据操作
Hybrid（混合式）	大多数B2B SaaS；复杂度中等、多用户类型	Slack、Figma、Asana	简短的引导式配置 + 产品优先 + 上下文指导

Decision Framework: Choosing Your Onboarding Type

决策框架：选择合适的Onboarding类型

Answer these questions to determine your optimal architecture:

Q1: Can a user get value without ANY setup?
  YES → Product-First or Hybrid
  NO  → Q2

Q2: Does setup take more than 2 minutes?
  YES → Value-First (show the payoff before asking for the investment)
  NO  → Guided Setup

Q3: Is your primary user technical?
  YES → Lean toward Product-First with contextual hints
  NO  → Lean toward Guided Setup or Hybrid

Q4: Does your product serve multiple use cases?
  YES → Start with a use-case selection question, then personalize the path
  NO  → You can use a single linear flow

Q5: Does the product require team participation for value?
  YES → Prioritize team invite early in onboarding, but provide solo value while waiting
  NO  → Focus on individual Aha Moment

回答以下问题以确定您的最优架构：

Q1: Can a user get value without ANY setup?
  YES → Product-First or Hybrid
  NO  → Q2

Q2: Does setup take more than 2 minutes?
  YES → Value-First (show the payoff before asking for the investment)
  NO  → Guided Setup

Q3: Is your primary user technical?
  YES → Lean toward Product-First with contextual hints
  NO  → Lean toward Guided Setup or Hybrid

Q4: Does your product serve multiple use cases?
  YES → Start with a use-case selection question, then personalize the path
  NO  → You can use a single linear flow

Q5: Does the product require team participation for value?
  YES → Prioritize team invite early in onboarding, but provide solo value while waiting
  NO  → Focus on individual Aha Moment

Welcome Flow Design

Welcome Flow（欢迎流程）设计

The welcome flow is the first 30-60 seconds after signup. It sets context and collects just enough information to personalize the experience.

Welcome Flow是用户注册后的前30-60秒。它用于设定上下文，并收集足够的信息以实现个性化体验。

User Profiling Questions (Pick 2-3 Maximum)

用户画像问题（最多选择2-3个）

Question	Purpose	Example Options
What is your role?	Personalize feature emphasis	Engineering, Product, Marketing, Design, Executive
What will you primarily use [product] for?	Select use-case template	[Use case 1], [Use case 2], [Use case 3]
How big is your team?	Determine collaboration features to emphasize	Just me, 2-10, 11-50, 50+
How did you hear about us?	Attribution (NOT onboarding, consider deferring)	--
Have you used a similar tool?	Calibrate guidance level	Yes (name competitor), No

问题	目的	示例选项
您的职位是什么？	个性化功能侧重点	工程师、产品经理、营销人员、设计师、管理人员
您主要将[产品]用于什么场景？	选择用例模板	[用例1]、[用例2]、[用例3]
您的团队规模有多大？	确定要强调的协作功能	仅我自己、2-10人、11-50人、50人以上
您是如何了解到我们的？	归因分析（不属于Onboarding范畴，考虑延后询问）	--
您是否使用过类似工具？	调整指导级别	是（注明竞品名称）、否

Welcome Flow Best Practices

Welcome Flow最佳实践

Limit to 2-3 questions -- Each additional question costs 5-15% drop-off
Use visual selectors (cards with icons) instead of dropdowns when possible
Every question must change the experience -- if it does not personalize anything, remove it
Show, do not ask -- if you can infer the answer from data (email domain, signup source), do not ask
Make all questions skippable with sensible defaults
Greet by name if you collected it during signup
Set expectations: "This will take about 2 minutes and will customize your experience"

限制为2-3个问题——每增加一个问题，流失率会增加5-15%
尽可能使用视觉选择器（带图标卡片）而非下拉菜单
每个问题都必须改变体验——如果无法实现个性化，就删除该问题
展示而非询问——如果可以从数据中推断答案（邮箱域名、注册来源），就不要询问
所有问题都允许跳过，并提供合理的默认值
如果注册时已收集姓名，就用姓名问候用户
设定预期："这将花费约2分钟时间，会为您定制专属体验"

Interactive Product Tours

交互式产品导览

Tooltip Sequencing Principles

提示框排序原则

Start with the highest-value action, not the first UI element from left to right
Each tooltip should prompt an action, not just describe a feature
Allow dismissal at any step -- provide "Skip tour" on every tooltip
Use progressive engagement: Tooltip 1 explains, Tooltip 2 prompts action, Tooltip 3 celebrates completion
End with the Aha Moment action -- the final tooltip should point to the action that delivers core value

从最高价值的操作开始，而非从左到右的第一个UI元素
每个提示框都应促使用户采取行动，而非仅描述功能
允许在任何步骤退出——每个提示框都提供"跳过导览"选项
使用渐进式参与：提示框1解释功能，提示框2促使用户行动，提示框3庆祝完成
以Aha Moment相关操作结束——最后一个提示框应指向能带来核心价值的操作

Tooltip Content Template

提示框内容模板

Step [N] of [Total]

[Headline: Action-oriented, 5-8 words]
[Body: Why this matters, 1-2 sentences]

[Primary CTA: "Do this now"]  [Secondary: "Skip"]

Step [N] of [Total]

[Headline: Action-oriented, 5-8 words]
[Body: Why this matters, 1-2 sentences]

[Primary CTA: "Do this now"]  [Secondary: "Skip"]

Highlight Patterns

高亮模式

Spotlight: Dim everything except the target element. Use for critical actions.
Beacon: A pulsing dot on the target element. Use for optional discovery.
Tooltip: An attached popover with explanation. Use for guided steps.
Coach mark: A full-screen overlay with an arrow pointing to the target. Use sparingly for first-time orientation.

聚光灯：模糊除目标元素外的所有内容。用于关键操作。
Beacon标记：目标元素上的脉冲点。用于可选发现。
提示框：附加在目标元素上的弹出层，包含解释内容。用于引导步骤。
引导标记：全屏覆盖层，箭头指向目标元素。仅在首次定向时少量使用。

Onboarding Checklists

Onboarding任务清单

Checklists are one of the most effective onboarding patterns. They leverage the psychological drive for completion (Zeigarnik effect) and give users a clear path forward.

任务清单是最有效的Onboarding模式之一。它利用了用户完成任务的心理驱动力（蔡格尼克效应），为用户提供清晰的前进路径。

Checklist Design Rules

任务清单设计规则

3-5 items maximum -- More than 5 items feels overwhelming
First item should be already completed (e.g., "Create your account" pre-checked) -- this creates momentum
Order by value, not by logic -- put the highest-value action near the top
Each item should be completable in under 2 minutes
Show progress (e.g., "2 of 5 complete")
Celebrate completion -- confetti, a congratulatory message, or unlocking a reward
Make the checklist persistent -- accessible from a sidebar or header, not a modal that disappears
Allow dismissal after 7-14 days -- do not nag forever

最多3-5个项目——超过5个项目会让用户感到压力
第一个项目应已完成（例如："创建您的账户"已预先勾选）——这能建立动力
按价值排序，而非逻辑顺序——将最高价值的操作放在顶部
每个项目应能在2分钟内完成
显示进度（例如："已完成2/5"）
庆祝完成——撒花、祝贺信息或解锁奖励
保持任务清单持久可见——可从侧边栏或页眉访问，而非消失的模态框
7-14天后允许关闭——不要一直打扰用户

Checklist Item Template

任务清单项目模板

☐ [Action verb] your first [object]
   [One sentence explaining the benefit]
   [CTA button: "Do it now →"]
   Estimated time: [X] min

☐ [动作动词] 您的第一个[对象]
   [解释好处的一句话]
   [CTA按钮: "立即执行 →"]
   预计时间: [X] 分钟

Completion Rewards

完成奖励

Extend a trial period: "Complete setup to get 7 extra trial days"
Unlock a feature: "Complete onboarding to unlock advanced analytics"
Remove branding: "Complete setup to remove the 'Powered by' badge"
Credits or discounts: "Complete onboarding for $10 in credit"

延长试用期："完成设置即可获得7天额外试用期"
解锁功能："完成Onboarding即可解锁高级分析功能"
移除品牌标识："完成设置即可移除‘由XXX提供支持’的标识"
积分或折扣："完成Onboarding即可获得10美元积分"

Empty State Design

空状态设计

Empty states are the most neglected and most impactful surfaces in onboarding. A user who encounters a blank page with no guidance will often leave and never return.

空状态是Onboarding中最容易被忽视但影响最大的环节。遇到无指导空白页面的用户通常会离开，且不再返回。

Empty State Strategies

空状态策略

Educational empty state: Explain what this page will show and how to populate it

[Illustration]
"Your dashboard will show real-time metrics once you connect a data source."
[CTA: "Connect your first data source →"]

Sample data: Pre-populate with realistic demo data so users can explore immediately

[Dashboard with sample data]
[Banner: "This is sample data. Connect your account to see your real metrics."]

Template gallery: Offer pre-built templates that users can adopt and customize

"Start with a template:"
[Template 1 card] [Template 2 card] [Template 3 card]
[Link: "Or start from scratch →"]

Quick-start content: Create the first piece of content for the user based on their profile

"We created a starter [project/board/workflow] based on your setup."
[CTA: "Explore your starter project →"]

教育型空状态：解释此页面将展示的内容以及如何填充数据

[插图]
"连接数据源后，您的仪表盘将显示实时指标。"
[CTA: "连接您的第一个数据源 →"]

示例数据：预先填充真实感的演示数据，让用户可以立即探索

[带示例数据的仪表盘]
[提示条: "这是示例数据。连接您的账户即可查看真实指标。"]

模板库：提供预构建的模板，用户可采用并自定义

"从模板开始："
[模板1卡片] [模板2卡片] [模板3卡片]
[链接: "或从头开始 →"]

快速入门内容：根据用户画像为其创建第一份内容

"我们根据您的设置为您创建了一个入门[项目/看板/工作流]。"
[CTA: "探索您的入门项目 →"]

Empty State Copywriting Formula

空状态文案公式

[What will be here] + [Why it matters] + [How to get started]

Example:
"No integrations connected yet.
 Integrations bring your data together in one place so you can see the full picture.
 Connect your first integration → "

[此处将展示什么] + [为什么重要] + [如何开始]

示例：
"尚未连接任何集成。
 集成可将您的数据汇集到一处，让您了解全局情况。
 连接您的第一个集成 → "

Progressive Disclosure

渐进式信息披露

Progressive disclosure means revealing product complexity gradually, matching the user's growing proficiency. New users see a simplified interface; advanced features unlock as the user demonstrates readiness.

渐进式信息披露指逐步展示产品的复杂性，与用户不断提升的熟练度相匹配。新用户看到简化的界面；随着用户表现出熟练度，高级功能会逐步解锁。

Implementation Patterns

实现模式

Feature unlocking by usage: "You've created 10 projects. Unlock bulk actions?"
Expandable sections: Advanced options hidden behind "Show advanced" toggles
Tiered navigation: Start with 3-4 core nav items; add more as the user progresses
Contextual feature introduction: Surface a feature when the user's behavior suggests they need it
Experience levels: Let users self-select their complexity preference (Simple / Standard / Advanced)

基于使用情况解锁功能："您已创建10个项目。是否解锁批量操作功能？"
可展开区域：高级选项隐藏在"显示高级设置"开关后
分层导航：从3-4个核心导航项开始；随着用户进阶，添加更多项
上下文功能介绍：当用户行为表明他们需要某功能时，再展示该功能
体验级别：让用户自行选择复杂度偏好（简单/标准/高级）

Progressive Disclosure Decision Framework

渐进式信息披露决策框架

Should this feature be visible to new users?

1. Is it needed for the Aha Moment?
   YES → Show immediately
   NO  → Continue

2. Will it confuse new users?
   YES → Hide initially
   NO  → Continue

3. Is it used by >50% of activated users?
   YES → Show, but do not emphasize
   NO  → Hide behind progressive disclosure

Should this feature be visible to new users?

1. Is it needed for the Aha Moment?
   YES → Show immediately
   NO  → Continue

2. Will it confuse new users?
   YES → Hide initially
   NO  → Continue

3. Is it used by >50% of activated users?
   YES → Show, but do not emphasize
   NO  → Hide behind progressive disclosure

Multi-Channel Onboarding

多渠道Onboarding

Onboarding does not happen only inside the product. Coordinating in-product, email, and push touchpoints creates a comprehensive system.

Onboarding并非仅发生在产品内部。协调产品内、邮件和推送触点可创建一个全面的系统。

Channel Coordination Framework

渠道协调框架

Timing	In-Product	Email	Push/SMS
Signup (Day 0)	Welcome flow, checklist	Welcome email with quickstart link	--
Day 1	Contextual tooltips for next step	"Complete your setup" if incomplete	--
Day 2	Checklist reminder if items remain	Tip: "Did you know you can [feature]?"	--
Day 3-4	Feature highlight for next action	Social proof: "Teams like yours use [feature]"	--
Day 5-7	Offer help if stalled	"Need help? Here's a 5-min video walkthrough"	App push if installed
Day 7-14	--	"Your trial is [X]% over -- here's what you haven't tried"	--

时间节点	产品内	邮件	推送/SMS
注册当日（第0天）	Welcome Flow、任务清单	带快速入门链接的欢迎邮件	--
第1天	针对下一步操作的上下文提示框	如果未完成设置，发送"完成您的设置"邮件	--
第2天	若任务清单仍有未完成项目，显示提醒	提示："您知道您可以[使用某功能]吗？"	--
第3-4天	突出显示用于下一步操作的功能	社会证明："与您类似的团队都在使用[某功能]"	--
第5-7天	若用户停滞，提供帮助	"需要帮助？这里有一个5分钟的视频教程"	若已安装应用，发送推送通知
第7-14天	--	"您的试用期已过[X]%——这是您尚未尝试的功能"	--

Email Onboarding Sequence Principles

邮件Onboarding序列原则

Each email should drive ONE action -- link directly to the in-product location
Show, do not tell -- include screenshots or GIFs of the action
Use behavioral triggers, not just time-based sends: "You connected a data source -- here's what to do next"
Stop the sequence when the user activates -- do not send onboarding emails to activated users
Include an unsubscribe option and honor it immediately

每封邮件应仅推动一个行动——直接链接到产品内对应位置
展示而非告知——包含操作的截图或GIF
使用行为触发，而非仅基于时间发送："您已连接数据源——接下来该做什么"
当用户激活后，停止发送序列邮件——不要向已激活用户发送Onboarding邮件
提供退订选项并立即生效

Stalled User Recovery

停滞用户召回

A "stalled user" is someone who signed up but has not progressed through onboarding for a defined period (typically 24-72 hours without completing the next expected step).

"停滞用户"指注册后未继续完成Onboarding流程达一定时间的用户（通常为24-72小时未完成预期下一步操作）。

Detection Triggers

检测触发条件

Trigger	Definition	Intervention
Signup, no setup	Signed up 24h+ ago, zero setup steps completed	Email: "Let's get you started" with direct link
Partial setup	Started setup but stopped mid-flow 48h+ ago	Email: "You're almost there" showing progress
Setup complete, no Aha	Completed setup but has not taken the Aha Moment action in 72h	In-app prompt + email with guided path to value
Single visit	Has not returned since signup day	Email with value proposition reminder + social proof
Frequent visitor, no depth	Logs in but does not perform meaningful actions	In-app guided experience; possible usability issue

触发条件	定义	干预措施
注册后未进行任何设置	注册24小时以上，未完成任何设置步骤	邮件："让我们开始吧"，附带直接链接
部分完成设置	开始设置但中途停止48小时以上	邮件："您即将完成"，显示进度
设置完成但未达到Aha Moment	完成设置但72小时内未执行Aha Moment相关操作	产品内提示 + 带引导路径的邮件
仅访问一次	注册后未再次返回	邮件：提醒价值主张 + 社会证明
频繁访问但无深度操作	登录但未执行有意义的操作	产品内引导体验；可能存在可用性问题

Recovery Message Templates

召回消息模板

Signup, No Setup:

Subject: Your [Product] account is ready -- let's get started
Body: Hi [Name], you signed up for [Product] [X days] ago.
Here's the fastest way to get value:
1. [Step 1 -- 1 min]
2. [Step 2 -- 2 min]
3. [Step 3 -- see your first insight]
[CTA: Start now →]

Partial Setup:

Subject: You're 60% done setting up [Product]
Body: Hi [Name], you've already completed [X steps].
Just [remaining steps] to go before you can [value statement].
[CTA: Continue setup →]

注册后未进行任何设置：

主题：您的[产品]账户已准备就绪——让我们开始吧
正文：您好[姓名]，您于[X天]前注册了[产品]。
以下是快速获取价值的方法：
1. [步骤1——1分钟]
2. [步骤2——2分钟]
3. [步骤3——查看您的第一个洞察]
[CTA: 立即开始 →]

部分完成设置：

主题：您已完成[产品]设置的60%
正文：您好[姓名]，您已完成[X个步骤]。
只需完成[剩余步骤]，您就能[价值陈述]。
[CTA: 继续设置 →]

Onboarding for Different User Types

针对不同用户类型的Onboarding

Admin vs End-User

管理员 vs 终端用户

Aspect	Admin	End-User
Goal	Configure the workspace for the team	Start using the product for daily work
Onboarding focus	Integrations, permissions, settings, invite	Core workflow, key actions, collaboration
Complexity tolerance	Higher -- they expect configuration	Lower -- they want to start immediately
Motivation	Organizational mandate / ROI	Personal productivity / team expectation

Design separate onboarding paths for admins and end-users. Detect role at signup or first login and route accordingly.

方面	管理员	终端用户
目标	为团队配置工作区	开始使用产品进行日常工作
Onboarding重点	集成、权限、设置、邀请	核心工作流、关键操作、协作
复杂度容忍度	较高——他们预期需要配置	较低——他们希望立即开始使用
动机	组织要求 / 投资回报率	个人生产力 / 团队期望

为管理员和终端用户设计不同的Onboarding路径。在注册或首次登录时检测角色，并进行相应路由。

Technical vs Non-Technical

技术型 vs 非技术型

Aspect	Technical	Non-Technical
Preferred learning	Documentation, API docs, CLI	Visual guides, video walkthroughs, wizards
Tour preference	Minimal or none -- let them explore	Guided -- show them the path
Terminology	Use technical terms freely	Use plain language, define terms
Error tolerance	High -- they can troubleshoot	Low -- errors cause abandonment

方面	技术型	非技术型
偏好的学习方式	文档、API文档、CLI	视觉指南、视频教程、向导
导览偏好	最少或无——让他们自行探索	引导式——为他们指明路径
术语使用	可自由使用技术术语	使用通俗易懂的语言，定义术语
错误容忍度	高——他们可以自行排查问题	低——错误会导致用户流失

Individual vs Team

个人用户 vs 团队用户

Aspect	Individual	Team
Aha Moment	Solo value (personal productivity)	Collaborative value (shared workspace, communication)
Critical onboarding step	First core action	First team member invited + first collaborative action
Time-to-value	Short (depends only on one person)	Longer (depends on others joining)
Onboarding risk	Low motivation if no immediate value	Stalled if no one else joins

方面	个人用户	团队用户
Aha Moment	单人价值（个人生产力）	协作价值（共享工作区、沟通）
关键Onboarding步骤	第一个核心操作	邀请第一个团队成员 + 第一个协作操作
价值实现时间	短（仅取决于个人）	长（取决于其他成员加入）
Onboarding风险	如果没有即时价值，动力不足	如果没有其他成员加入，流程停滞

Onboarding Metrics

Onboarding指标

Core Metrics

核心指标

Metric	Definition	Target
Onboarding completion rate	% of signups who complete all onboarding steps	60-80%
Time-to-complete	Median time from signup to onboarding completion	Varies by product
Drop-off by step	% of users who abandon at each step	Identify steps with >20% drop-off
Activation correlation	% of onboarding completers who reach Aha Moment	>70%
Checklist engagement	% of users who interact with the onboarding checklist	>50%
Tour completion rate	% of users who finish the product tour (if offered)	30-50%

指标	定义	目标
Onboarding完成率	完成所有Onboarding步骤的注册用户占比	60-80%
完成时间	从注册到完成Onboarding的中位时间	因产品而异
按步骤流失率	每个步骤放弃的用户占比	识别流失率>20%的步骤
激活相关性	完成Onboarding后达到Aha Moment的用户占比	>70%
任务清单参与度	与Onboarding任务清单互动的用户占比	>50%
导览完成率	完成产品导览的用户占比（若提供）	30-50%

Funnel Analysis Template

漏斗分析模板

Step                    | Users | Conversion | Drop-off | Median Time
------------------------|-------|------------|----------|------------
Signup                  | 1000  | 100%       | --        | --
Welcome flow complete   |  850  |  85%       | 15%      | 45 sec
Step 1: [Action]        |  720  |  72%       | 15%      | 2 min
Step 2: [Action]        |  580  |  58%       | 19%      | 5 min
Step 3: [Action]        |  490  |  49%       | 16%      | 3 min
Onboarding complete     |  450  |  45%       |  8%      | 12 min
Aha Moment reached      |  380  |  38%       | 16%      | Day 2

Step                    | Users | Conversion | Drop-off | Median Time
------------------------|-------|------------|----------|------------
Signup                  | 1000  | 100%       | --        | --
Welcome flow complete   |  850  |  85%       | 15%      | 45 sec
Step 1: [Action]        |  720  |  72%       | 15%      | 2 min
Step 2: [Action]        |  580  |  58%       | 19%      | 5 min
Step 3: [Action]        |  490  |  49%       | 16%      | 3 min
Onboarding complete     |  450  |  45%       |  8%      | 12 min
Aha Moment reached      |  380  |  38%       | 16%      | Day 2

Common Anti-Patterns

常见反模式

Avoid these onboarding mistakes:

Too many steps: More than 5 setup steps causes steep drop-off. Ruthlessly cut.
Forced tours: Making users sit through a mandatory tour they cannot skip. Always provide a "Skip" option.
No skip option: Requiring every onboarding step to be completed before product access. Let users explore.
Feature dump: Showing everything at once instead of progressive disclosure.
Ignoring return users: Showing the same onboarding to returning users who already saw it.
Generic experience: Same onboarding for every user regardless of role, use case, or sophistication.
Missing empty states: Leaving pages blank with no guidance when users have not populated data.
No re-entry point: If a user abandons onboarding, they cannot find it again to resume.
Teaching before doing: Long explanatory content before the user gets to act.
Celebrating setup, not value: Showing confetti when the user finishes configuration instead of when they achieve their first outcome.

避免这些Onboarding错误：

步骤过多：超过5个设置步骤会导致严重流失。果断删减。
强制导览：让用户必须看完无法跳过的导览。始终提供"跳过"选项。
无跳过选项：要求完成所有Onboarding步骤才能访问产品。允许用户探索。
功能堆砌：一次性展示所有功能，而非渐进式披露。
忽视回访用户：向已看过Onboarding的回访用户重复展示相同内容。
通用化体验：为所有用户提供相同的Onboarding，无论其角色、用例或熟练度如何。
缺失空状态引导：当用户未填充数据时，页面空白且无任何指导。
无重新进入入口：如果用户放弃Onboarding，无法再次找到并继续。
先教后做：在用户行动前展示冗长的解释内容。
庆祝设置完成而非价值达成：当用户完成配置而非达成第一个成果时展示撒花效果。

Output Format: Onboarding Flow Specification

输出格式：Onboarding流程规范

When helping a team design their onboarding, produce a document with these sections:

undefined

当帮助团队设计Onboarding时，请生成包含以下部分的文档：

undefined

[Product Name] -- Onboarding Flow Specification

[产品名称] -- Onboarding流程规范

1. Onboarding Architecture

1. Onboarding架构

Type: [Product-First / Guided Setup / Value-First / Hybrid]
Rationale: [Why this type was chosen]
Estimated time to complete: [X minutes]

类型：[Product-First / Guided Setup / Value-First / Hybrid]
理由：[选择此类型的原因]
预计完成时间：[X]分钟

2. User Segmentation

2. 用户细分

Segment 1: [Role/type] → [Onboarding path]
Segment 2: [Role/type] → [Onboarding path]

细分1：[角色/类型] → [Onboarding路径]
细分2：[角色/类型] → [Onboarding路径]

3. Welcome Flow

Question 1: [Question] → [How answer changes experience]
Question 2: [Question] → [How answer changes experience]

问题1：[问题] → [答案如何改变体验]
问题2：[问题] → [答案如何改变体验]

4. Onboarding Steps (per segment)

4. Onboarding步骤（按细分）

Step 1: [Name]

步骤1：[名称]

User action: [What the user does]
UI pattern: [Tooltip / Modal / Inline / Checklist item]
Success criteria: [How we know the step is complete]
Fallback if skipped: [What happens if user skips this step]
Copy: [Headline + body text]
Estimated time: [X min]

用户操作：[用户需要做什么]
UI模式：[提示框 / 模态框 / 内联 / 任务清单项目]
成功标准：[如何判断步骤已完成]
跳过的 fallback：[用户跳过此步骤时会发生什么]
文案：[标题 + 正文]
预计时间：[X]分钟

Step 2: [Name]

步骤2：[名称]

[Same structure]

[Repeat for each step]

[相同结构]

[重复每个步骤]

5. Onboarding Checklist

5. Onboarding任务清单

Item 1: [Action] -- [Benefit] -- [Est. time]
Item 2: [Action] -- [Benefit] -- [Est. time]
Item 3: [Action] -- [Benefit] -- [Est. time]
Completion reward: [What happens when all items are done]
Persistence: [Where checklist lives, when it disappears]

项目1：[操作] -- [好处] -- [预计时间]
项目2：[操作] -- [好处] -- [预计时间]
项目3：[操作] -- [好处] -- [预计时间]
完成奖励：[完成所有项目后会发生什么]
持久可见性：[任务清单的位置，何时消失]

6. Empty States

6. 空状态

[Page/Surface 1]: [Empty state strategy + copy]
[Page/Surface 2]: [Empty state strategy + copy]

[页面/界面1]：[空状态策略 + 文案]
[页面/界面2]：[空状态策略 + 文案]

7. Multi-Channel Coordination

7. 多渠道协调

Email sequence: [Number of emails, triggers, content summary]
In-app messaging: [Timing, triggers, placement]
Push notifications: [If applicable]

邮件序列：[邮件数量、触发条件、内容摘要]
产品内消息：[时间、触发条件、位置]
推送通知：[如适用]

8. Stalled User Recovery

8. 停滞用户召回

Trigger 1: [Condition] → [Intervention]
Trigger 2: [Condition] → [Intervention]

触发条件1：[条件] → [干预措施]
触发条件2：[条件] → [干预措施]

9. Success Metrics

9. 成功指标

Primary: [Onboarding completion rate target]
Secondary: [Time-to-complete target]
Activation correlation: [Expected % of completers who activate]

主要指标：[Onboarding完成率目标]
次要指标：[完成时间目标]
激活相关性：[预计完成Onboarding后激活的用户占比]

10. Anti-Pattern Checklist

10. 反模式检查清单

No step takes longer than 2 minutes
Every step is skippable
Tour is optional
Empty states have guidance
Return users do not re-see onboarding
Each question personalizes the experience

---

没有步骤耗时超过2分钟
每个步骤都可跳过
导览是可选的
空状态有引导
回访用户不会重复看到Onboarding
每个问题都能个性化体验

---