onboarding-flow

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Onboarding Flow

用户引导流程（Onboarding Flow）

When to Use

适用场景

Activate when a founder or product lead needs to design onboarding for new users, improve activation rates, reduce time-to-value, fix drop-off after signup, redesign a guided setup experience, or re-engage users who stalled during onboarding. This includes prompts like "design our onboarding flow," "users are dropping off after signup," "build an activation checklist," "our time-to-value is too long," "how do we get users to their aha moment faster," or "first sessions are not sticking."

Do NOT use for employee onboarding, service process design, or when the product lacks a stable value proposition. This skill is for in-product user activation only.

当创始人或产品负责人需要为新用户设计引导流程、提升激活率、缩短价值获取时间、解决注册后用户流失问题、重新设计引导式设置体验，或重新激活在引导流程中停滞的用户时，可启用此技能。常见触发需求包括“设计我们的用户引导流程”、“用户注册后大量流失”、“创建激活 checklist”、“我们的价值获取时间太长”、“如何让用户更快抵达Aha Moment”或“首次用户会话留存率低”。

请勿用于员工入职、服务流程设计，或产品缺乏稳定价值主张的场景。此技能仅适用于产品内的用户激活场景。

Context Required

所需上下文

From startup-context: product type (B2B/B2C/PLG), target user persona, current activation rate, defined "aha moment," product complexity level, existing onboarding steps, and current tools (email platform, analytics, in-app messaging).
From the user: where users currently drop off, the key action that correlates with retention (the activation event), number of steps currently required to reach value, any qualitative feedback from churned users about the setup experience, and what "healthy" first-session behavior looks like.

来自初创企业上下文： 产品类型（B2B/B2C/PLG）、目标用户画像、当前激活率、已定义的“Aha Moment”、产品复杂度、现有引导步骤及当前使用工具（邮件平台、分析工具、应用内消息工具）。
来自用户： 当前用户流失节点、与留存高度相关的关键动作（激活事件）、当前抵达价值所需的步骤数、流失用户对设置体验的定性反馈，以及“健康”的首次会话行为表现。

Workflow

工作流程

Intake and goal-framing — Read startup-context if available. Establish the activation goal, current baseline metrics, and what success looks like. If the user does not know their activation event, help them hypothesize based on product type (see benchmarks below).
Map the current journey — Document every step from signup to activation event, including screens, emails, wait states, and decision points. Identify friction points, unnecessary steps, and moments of confusion.
Identify friction and drop-off — Pinpoint where users abandon the flow. Categorize blockers: too many steps, unclear value, technical obstacles, cognitive overload, or missing guidance.
Define behavioral activation moments — Identify the specific user actions that predict long-term retention. These become the milestones the onboarding flow drives toward.
Design the first experience — Apply the progressive onboarding framework to restructure the journey. Focus on the "first 30 seconds" experience and minimize steps before first value. Defer non-essential setup.
Build the milestone-based onboarding plan — Create a "first mile" plan with clear milestones from signup through habit formation, with coordinated in-app and email touchpoints.
Establish measurement and experiments — Set up tracking for each step in the funnel. Build an experiment backlog prioritized by impact, confidence, and effort. Design A/B tests for the highest-leverage changes.

需求收集与目标设定 — 若有初创企业上下文则先阅读。明确激活目标、当前基准指标及成功标准。若用户不清楚其激活事件，可根据产品类型协助其假设（参考下方基准数据）。
绘制当前用户旅程 — 记录从注册到激活事件的每一个步骤，包括页面、邮件、等待状态及决策点。识别摩擦点、冗余步骤及易混淆环节。
定位摩擦与流失原因 — 找出用户放弃流程的节点。将阻碍因素分类：步骤过多、价值不明确、技术障碍、认知过载或缺乏引导。
定义行为激活节点 — 识别能预测长期留存的特定用户行为。这些行为将成为引导流程需推动用户达成的里程碑。
设计首次体验 — 应用渐进式引导框架重构用户旅程。聚焦“前30秒”体验，最小化首次价值获取前的步骤，延迟非必要设置。
构建基于里程碑的引导计划 — 创建“第一阶段”计划，包含从注册到习惯养成的清晰里程碑，并协调应用内与邮件触点。
建立测量与实验机制 — 为漏斗中的每个步骤设置追踪。构建按影响力、可信度与实施成本优先级排序的实验待办清单。针对高杠杆变化设计A/B测试。

Output Format

输出格式

A comprehensive Onboarding & Activation Pack including:

Activation spec — Defined activation event with behavioral criteria and baseline metrics
First 30 seconds design — The immediate post-signup experience optimized for first value
First mile milestone plan — Stage-by-stage plan from signup through habit formation
Funnel map — Every step with expected conversion rates
In-app UX specifications — Checklists, tooltips, empty states, progress indicators
Email sequence copy — Welcome through re-engagement with timing and triggers
Experiment backlog — Prioritized list of onboarding experiments (impact/confidence/effort)
Measurement framework — Leading indicators, tracking plan, and success criteria
Risk documentation — Open questions, assumptions, and next-step recommendations

一份完整的《用户引导与激活方案包》，包含：

激活规范 — 明确激活事件的行为标准及基准指标
前30秒体验设计 — 优化后的注册后即时体验，聚焦首次价值获取
第一阶段里程碑计划 — 从注册到习惯养成的分阶段计划
漏斗图 — 包含预期转化率的每一步流程
应用内UX规范 — 清单、提示框、空状态、进度指示器
邮件序列文案 — 从欢迎到重新激活的邮件内容，含发送时机与触发条件
实验待办清单 — 按优先级排序的引导实验列表（影响力/可信度/实施成本）
测量框架 — 领先指标、追踪计划及成功标准
风险文档 — 待验证假设、未解决问题及下一步建议

Onboarding Funnel Template

用户引导漏斗模板

Stage 1: Signup -> Profile Setup            (Target: 90%+)
Stage 2: Profile Setup -> First Key Action  (Target: 60-70%)
Stage 3: First Key Action -> Aha Moment     (Target: 50-60%)
Stage 4: Aha Moment -> Habit Formation      (Target: 30-40%)

Stage 1: Signup -> Profile Setup            (Target: 90%+)
Stage 2: Profile Setup -> First Key Action  (Target: 60-70%)
Stage 3: First Key Action -> Aha Moment     (Target: 50-60%)
Stage 4: Aha Moment -> Habit Formation      (Target: 30-40%)

Frameworks & Best Practices

框架与最佳实践

The Progressive Onboarding Framework

渐进式用户引导框架

Structure onboarding in three layers that unlock sequentially:

Layer 1: Immediate Value (Minutes 0-5)
- Get the user to one small win before asking for anything.
- Pre-fill data where possible (import, templates, sample data).
- Use empty states as onboarding — every blank screen should guide the next action.
- Ask only for information required to deliver that first win. Defer everything else.
Layer 2: Core Setup (Day 1-3)
- Introduce a checklist with 3-5 items (never more than 7). Show progress visually.
- Each checklist item should unlock a visible capability ("Complete this to enable X").
- Use contextual tooltips triggered by user behavior, not a grand tour on first login.
- Send a Day 1 email reinforcing the first win and previewing the next step.
Layer 3: Expansion (Week 1-2)
- Prompt team invites after the individual user has experienced value (not before).
- Introduce advanced features through progressive disclosure, not feature dumps.
- Trigger expansion prompts based on usage patterns, not arbitrary timelines.

将引导流程分为三层，依次解锁：

第一层：即时价值（0-5分钟）
- 在向用户索取任何信息前，先让用户获得一个小成功。
- 尽可能预填充数据（导入、模板、示例数据）。
- 将空状态用作引导环节 — 每个空白页面都应指引下一步动作。
- 仅索取提供首次价值所需的信息，其余信息延迟收集。
第二层：核心设置（第1-3天）
- 引入包含3-5项内容的checklist（最多不超过7项）。可视化展示进度。
- 每个checklist项应解锁一项可见功能（“完成此项即可启用X功能”）。
- 根据用户行为触发上下文提示框，而非首次登录时的全景式导览。
- 发送第1天邮件，强化首次成功体验并预告下一步。
第三层：功能拓展（第1-2周）
- 待用户体验到产品价值后，再提示邀请团队成员（而非之前）。
- 通过渐进式披露引入高级功能，而非一次性展示所有功能。
- 根据使用模式触发拓展提示，而非基于任意时间线。

Activation Event Benchmarks by Product Type

按产品类型划分的激活事件基准

Product Type	Common Activation Event	Target Time-to-Value
B2B SaaS (simple)	Complete first core workflow	< 10 minutes
B2B SaaS (complex)	Import data + run first report	< 24 hours
PLG / Self-serve	Invite first team member + collaborate	< 48 hours
Developer tool	First successful API call or deploy	< 30 minutes
B2C app	Complete first session/transaction	< 3 minutes

产品类型	常见激活事件	目标价值获取时间
简单B2B SaaS	完成首个核心工作流	< 10分钟
复杂B2B SaaS	导入数据 + 生成首份报告	< 24小时
PLG / 自助服务	邀请首位团队成员 + 协作	< 48小时
开发者工具	首次成功API调用或部署	< 30分钟
B2C应用	完成首次会话/交易	< 3分钟

Inside-the-Product Onboarding

产品内用户引导

Prioritize onboarding that happens within the product experience itself, not detached from it. Product tours that overlay the UI without context are less effective than:

Empty states that teach — Every blank screen guides the next action
Inline prompts — Contextual guidance that appears when the user reaches a decision point
Progressive disclosure — Reveal complexity as the user demonstrates readiness
Sample data — Let users experience the product's value before investing their own data

优先选择在产品体验内完成的引导，而非脱离产品的引导。相比无上下文的UI覆盖式产品导览，以下方式更有效：

具备教学功能的空状态 — 每个空白页面都指引下一步动作
内嵌提示 — 在用户到达决策点时展示上下文引导
渐进式披露 — 当用户表现出准备度时，再揭示复杂功能
示例数据 — 让用户在投入自有数据前先体验产品价值

Multi-Channel Coordination Rules

多渠道协同规则

In-app: Real-time guidance for active users. Checklists, tooltips, progress bars, empty state CTAs.
Email: Async nudges for users who leave. Day 0 welcome, Day 1 reinforcement, Day 3 re-engagement, Day 7 value recap.
Push/SMS: Reserve for high-intent signals only ("Your report is ready," "Your teammate just joined"). Never use for generic reminders.
Suppression rule: If the user completed the action in-app, suppress the corresponding email. Nothing kills trust faster than "Complete your setup!" emails sent after setup is done.

应用内： 为活跃用户提供实时引导。包括清单、提示框、进度条、空状态CTA。
邮件： 为离开产品的用户提供异步提醒。包括注册当日欢迎邮件、第1天强化邮件、第3天重新激活邮件、第7天价值回顾邮件。
推送/SMS： 仅用于高意向信号（如“您的报告已准备好”、“您的队友已加入”）。绝不用于通用提醒。
抑制规则： 若用户已在应用内完成动作，则取消发送对应邮件。用户完成设置后仍收到“完成您的设置！”邮件，是最破坏信任的行为。

Checklist Design Principles

Checklist设计原则

3-5 items maximum. Completion rates drop sharply above 5.
First item should be pre-completed. Starting with visible progress significantly increases completion rates (endowed progress effect).
Each item takes under 2 minutes. If longer, break it into sub-steps.
Show the reward. "Connect Slack -> Get instant notifications" not just "Connect Slack."
Allow skipping with consequences. Let users skip but show what they lose.

最多3-5项内容。超过5项后完成率会大幅下降。
第一项自动标记为已完成。起始阶段展示可见进度会显著提升完成率（禀赋效应）。
每项耗时不超过2分钟。若耗时更长，则拆分为子步骤。
展示奖励。应写“连接Slack -> 获取即时通知”而非仅“连接Slack”。
允许跳过并告知后果。让用户可跳过，但需展示其将失去的权益。

Re-Engagement for Stalled Users

停滞用户的重新激活

Diagnose before prescribing. Different stall points indicate different problems:

Stall Point	Likely Cause	Intervention
Signed up, never returned	Unclear value prop or bad timing	Email with specific use case matching signup context
Started setup, abandoned	Too many steps or hit a blocker	Email linking directly to where they stopped
Completed setup, never used	No compelling reason to return	Trigger-based email when something relevant happens
Used once, never returned	First experience was not valuable	Ask what they were trying to accomplish; offer guided call

先诊断再制定方案。不同停滞点对应不同问题：

停滞节点	可能原因	干预措施
注册后从未返回	价值主张不清晰或时机不当	发送与注册上下文匹配的特定使用场景邮件
开始设置后放弃	步骤过多或遇到障碍	发送直接链接至停滞节点的邮件
完成设置后从未使用	缺乏返回动力	当相关事件发生时触发邮件
使用一次后从未返回	首次体验无价值	询问用户目标，提供引导式通话

Quality Guardrails

质量保障准则

All onboarding designs should include:

Risk documentation identifying assumptions that could be wrong
Open questions that need user research to answer
Explicit next steps with owners and timelines
Leading indicators to measure before waiting for retention data

所有引导设计应包含：

风险文档，列出可能错误的假设
需要用户研究才能解答的未解决问题
明确的下一步动作，含负责人与时间线
在等待留存数据前可测量的领先指标

Related Skills

Examples

示例

Example 1: Designing a new onboarding flow

示例1：设计全新用户引导流程

User: "We're a B2B project management tool. Users sign up but only 20% create their first project. Help us fix onboarding."

Good output excerpt:

Activation Event: Create first project + add at least one task (correlates with 60-day retention).

First 30 Seconds Design: After signup, land on a pre-built sample project (not an empty dashboard). The user sees what the product looks like when populated. A single guided prompt says "Create your first real project" with 3 templates to choose from. After project creation, inline prompt to add a first task with an example. Celebration state: "Your project is live! Invite your team to collaborate."

Expected impact: Reducing pre-value steps from 4 to 2 should increase project creation from 20% to 45-55%.

用户：“我们是一款B2B项目管理工具。用户注册后仅20%会创建首个项目。帮我们优化引导流程。”

优质输出节选：

激活事件： 创建首个项目 + 添加至少一个任务（与60天留存高度相关）。

前30秒体验设计： 注册后，直接进入预构建的示例项目（而非空仪表盘）。用户可看到产品填充数据后的样子。仅展示一个引导提示：“创建您的首个真实项目”，提供3个模板可选。创建项目后，内嵌提示引导用户添加首个任务并提供示例。完成后显示庆祝状态：“您的项目已上线！邀请团队成员协作吧。”

预期影响： 将价值获取前的步骤从4步减少至2步，预计可将项目创建率从20%提升至45-55%。

Example 2: Activation is lagging

示例2：激活率低迷

User: "We have 3,000 signups from last month and 60% never completed setup. How do we bring them back?"

Good output approach: Segment the 60% by where they stalled. Design different re-engagement emails for each stall point. Include subject lines, body copy, and CTAs linking directly to the abandoned step. Recommend a sunset policy (stop emailing after 30 days to protect deliverability). Build an experiment backlog testing different interventions at each stall point, prioritized by volume of stalled users and estimated recovery rate.

用户：“上月我们有3000个注册用户，其中60%未完成设置。如何召回这些用户？”

优质输出方案： 按停滞节点对60%的用户进行细分。为每个停滞节点设计不同的重新激活邮件，包含主题、正文及直接链接至停滞步骤的CTA。建议设置日落政策（30天后停止发送邮件以保护送达率）。构建实验待办清单，测试每个停滞节点的不同干预措施，按停滞用户数量及预估恢复率排序。