Back to Details

onboarding-wizard-design

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Onboarding Wizard Design

产品引导向导设计

A senior product marketing director's playbook for designing first-run product onboarding wizards that get users to the ah-ha moment without overwhelming them. Step architecture, progressive disclosure, escape hatches, completion incentives, drop-off measurement. The discipline of building an onboarding sequence the user actually completes.
Most product onboarding wizards fail in one of two ways. They cram every feature into a 12-step intro the user has not earned the patience for. Or they offer a "skip onboarding" button so prominent that users skip into an empty product with no context, and then churn the next day because they never found the value. The activation rate is the metric that matters, and most wizards are optimizing for the wrong thing.
The wizards that work do something different. Each step earns the user one step closer to value. The wizard surfaces the right thing at the right moment, not everything upfront. Skip exists but is balanced against staying engaged. The user reaches the ah-ha moment with a sense that the product respected their time.
The voice is the senior product marketing director who has watched activation rates double when wizards were redesigned and watched them collapse when "more onboarding" was added without discipline. Practical, opinionated about the design choices that distinguish completed wizards from skipped ones, willing to call out when no wizard at all is the right answer.
When to use this skill: scoping a first-run onboarding wizard for the first time, auditing a wizard with poor completion or activation, deciding which features warrant inclusion in onboarding vs deferred to in-product help, or designing the ah-ha moment the wizard is engineering toward.
这是一份资深产品营销总监的实操手册，指导如何设计首次产品引导向导，让用户在不感到负担的情况下抵达Ah-ha moment。涵盖步骤架构、渐进式信息披露、退出机制、完成激励、流失率衡量。核心是打造用户真正会完成的引导流程。
大多数产品引导向导的失败分为两种情况：要么在12步介绍中塞满所有功能，超出用户的耐心承受范围；要么设置过于显眼的“跳过引导”按钮，导致用户直接进入无上下文的空产品，次日就因未发现产品价值而流失。激活率才是关键指标，但大多数向导都在错误的方向上优化。
有效的向导做法截然不同：每一步都让用户更接近价值，在正确的时机呈现正确内容，而非一次性展示所有信息。跳过选项存在，但会与保持用户参与度的设计相平衡。用户在抵达Ah-ha moment时，会感受到产品尊重他们的时间。
本文作者是资深产品营销总监，亲眼见证过向导重新设计后激活率翻倍，也见过无节制添加“更多引导”后激活率暴跌。内容务实，对区分完成率高与被跳过的向导设计选择有明确观点，也会指出完全不需要向导的场景。
何时使用此方法：首次规划首次使用引导向导、审核完成率或激活率低下的向导、决定哪些功能需纳入引导而非延后至产品内帮助、设计向导要达成的Ah-ha moment。

What this skill covers

此方法涵盖的内容

This skill spans first-run product onboarding wizards. The growth-tooling distinctions:
  • multi-step-form-design
    is pre-signup data capture (forms before the user has access). This skill is post-signup product onboarding. Different phase, different audience state.
  • interactive-product-tour
    is contextual help WITHIN the product, surfacing across the lifecycle. This skill is the sequential first-run experience.
  • chatbot-flow-design
    is conversational help. This skill is non-conversational sequential setup.
  • onboarding-wizard-design
    (this skill)     is the post-signup wizard's structure, ah-ha moment design, progressive disclosure, skip mechanics, drop-off measurement.
  • pm-spec-writing
    is the spec for engineers building the wizard. This skill is about WHAT to build; pm-spec-writing is about communicating it.
The audience: product marketers, growth marketers, in-house product teams designing activation flows, agencies running activation work for SaaS clients.
Out of scope: pre-signup forms (covered by 
multi-step-form-design
); in-product contextual tours (covered by 
interactive-product-tour
); the engineering implementation; specific Userpilot/Userflow/Pendo/Appcues platform configurations (those stay implementation-side).
本方法聚焦首次产品引导向导，与其他增长工具的区别：
  • multi-step-form-design
    是注册前的数据收集（用户获得权限前的表单），本方法针对注册后的产品引导，属于不同阶段、用户状态不同。
  • interactive-product-tour
    是产品内的上下文帮助，贯穿整个生命周期，本方法是顺序式的首次使用体验。
  • chatbot-flow-design
    是对话式帮助，本方法是非对话式的顺序设置流程。
  • onboarding-wizard-design
    （本方法）     是注册后向导的结构、Ah-ha moment设计、渐进式信息披露、跳过机制、流失率衡量。
  • pm-spec-writing
    是给工程师的向导开发规格，本方法关注要做什么，而pm-spec-writing关注如何传达需求。
受众：产品营销人员、增长营销人员、设计激活流程的内部产品团队、为SaaS客户提供激活服务的代理机构。
不涵盖范围：注册前表单（由
multi-step-form-design
覆盖）、产品内上下文引导（由
interactive-product-tour
覆盖）、工程实现细节、Userpilot/Userflow/Pendo/Appcues等平台的具体配置（这些属于实现层面内容）。

The wizard decision: when wizards earn vs when contextual help suffices

向导决策：何时值得投入向导，何时上下文帮助足够

Before designing the wizard, decide whether a wizard is the right tool.
Wizards earn investment when:
  • The product has a meaningful setup step before value emerges. Connect a data source, invite a teammate, configure a workspace. Without setup, the product is empty; the wizard makes setup tractable.
  • The ah-ha moment requires multiple actions in sequence. Single-action ah-ha moments (paste a URL, see a result) often work better with contextual prompts than with wizards.
  • The audience expects guided onboarding. B2B SaaS with technical setup, enterprise software, configurable products. Some audiences (consumer, frictionless tools) reject wizard friction.
  • The team can maintain the wizard. Wizards decay as the product evolves; without maintenance commitment, the wizard becomes a liability.
Wizards do NOT earn investment when:
  • The product reaches value immediately. Single-input tools, simple consumer products. A wizard adds friction without lift.
  • Contextual help would suffice. Tooltips, in-feature hints, and progressive in-product education sometimes serve better than upfront wizards.
  • The audience expects no friction. Some audiences abandon at any wizard; meet them where they are.
  • The team cannot maintain the wizard alongside product changes. Stale wizards point to deprecated features; users hit broken steps.
The decision is not "should we have an onboarding wizard"; it is "is the wizard the right tool for this specific product and audience."
Detail in 
references/wizard-decision-criteria.md
.
设计向导前，先判断向导是否是合适的工具。
值得投入向导的场景：
  • 产品在产生价值前需要有意义的设置步骤，比如连接数据源、邀请团队成员、配置工作区。没有这些设置，产品就是空的，向导能让设置过程更易完成。
  • Ah-ha moment需要多个连续操作。单操作即可达成的Ah-ha moment（如粘贴URL查看结果）通常用上下文提示比向导效果更好。
  • 受众期望引导式体验，如需要技术设置的B2B SaaS、企业软件、可配置产品。部分受众（消费者、低摩擦工具）会排斥向导带来的摩擦。
  • 团队能够维护向导。随着产品演进，向导会逐渐过时；若没有维护承诺，向导会成为负担。
不值得投入向导的场景：
  • 产品能立即产生价值，如单输入工具、简单消费产品。向导只会增加摩擦，无法提升效果。
  • 上下文帮助足够，如工具提示、功能内提示、渐进式产品内教育有时比前置向导效果更好。
  • 受众期望零摩擦，部分受众会因任何向导而放弃，需贴合他们的需求。
  • 团队无法随产品变更维护向导。过时的向导会指向已弃用的功能，用户会遇到步骤失效的问题。
决策不是“我们是否应该有引导向导”，而是“向导是否是针对这款产品和受众的合适工具”。
详情见 
references/wizard-decision-criteria.md
。

Tutorial-overload vs skip-friendly-empty vs earned-progressive-disclosure

教程过载 vs 易跳过空状态 vs 渐进式价值披露

The keystone framing.
Tutorial-overload. Every feature explained in a 12-step intro before the user has touched the product. Cognitive overload. Users skip if they can; abandon if they cannot. Cost: the wizard's design effort produces a sequence almost nobody completes; activation rate suffers because the user did not reach the value-giving moment.
Skip-friendly-empty. "Skip onboarding" button at every step, so prominent that users always take it. Users skip; arrive at an empty product with no context; churn within hours. Cost: activation rate falls off a cliff because users never set up the basics that make the product functional.
Earned-progressive-disclosure. Each step earns the user one step closer to value. The wizard surfaces the right thing at the right moment, not everything upfront. Skip exists but is friction-balanced against staying engaged (e.g., skip places the user in a partially-set-up state with clear callouts to complete setup later). Cost: design effort is significant; activation rate often climbs significantly as a result.
The litmus test. Watch a new user complete (or skip) the wizard. Did they reach a moment where the product visibly demonstrated value within their first session? If yes, the wizard is earned-progressive-disclosure. If they completed every step but never reached value, tutorial-overload. If they skipped and never returned, skip-friendly-empty.
核心框架。
教程过载：在用户接触产品前，用12步介绍讲解所有功能，导致认知过载。用户能跳过就跳过，不能跳过就直接放弃。代价：向导的设计投入产出了几乎没人完成的流程，激活率因用户未抵达价值时刻而受损。
易跳过空状态：每一步都设置“跳过引导”按钮，且过于显眼，用户总会选择跳过。用户跳过后来到空产品，无上下文，数小时内就流失。代价：激活率骤降，因为用户从未完成让产品可用的基础设置。
渐进式价值披露：每一步都让用户更接近价值，在正确的时机呈现正确内容，而非一次性展示所有信息。跳过选项存在，但会通过设计平衡摩擦与用户参与度（如跳过会让用户进入部分设置完成状态，并明确提示后续可完成设置）。代价：设计投入较大，但激活率通常会显著提升。
检验标准：观察新用户完成（或跳过）向导的过程。他们是否在首次使用会话内就看到产品明确展现价值？若是，说明向导属于渐进式价值披露；若完成所有步骤却未抵达价值，属于教程过载；若跳过就不再返回，属于易跳过空状态。

Step architecture: what belongs in each step, sequence logic

步骤架构：每步内容与顺序逻辑

The structure that makes wizards actually work.
The principle. Each step should move the user one step closer to value. Steps that do not should be cut.
Common step patterns.
  • Welcome and orientation. Quick context-setting, often skippable. Sets expectations for what the wizard will do.
  • Identity and account context. Who are you, what's your role, what brought you here. Often used to personalize subsequent steps.
  • Critical setup step. The one thing the product cannot work without (connect data source, invite teammates, set primary use case). This is often where wizards justify their existence.
  • First-action step. Get the user to take a meaningful action that produces visible result. The ah-ha moment lives here or right after.
  • Configuration deferral. Surface the things that can be set up later but are commonly needed; let the user defer with a clear path back.
  • Confirmation and next steps. Recap what was set up; surface what to do next; route to in-product home.
Step coherence test. Each step should answer: did this step move the user closer to value? Steps that exist for completeness or feature-pride should be cut.
Detail in 
references/step-architecture-patterns.md
.
让向导真正有效的结构。
原则：每一步都应让用户更接近价值，无此作用的步骤应删除。
常见步骤模式：
  • 欢迎与定位：快速设定上下文，通常可跳过。明确向导的作用。
  • 身份与账户上下文：了解用户是谁、角色是什么、使用产品的原因。通常用于个性化后续步骤。
  • 关键设置步骤：产品运行必需的操作（如连接数据源、邀请团队成员、设置主要用例），这通常是向导存在的意义。
  • 首次操作步骤：让用户执行有意义的操作并看到可见结果，Ah-ha moment通常在此或之后出现。
  • 配置延后：展示常用但可后续设置的内容，让用户可延后设置并明确返回路径。
  • 确认与下一步：回顾已完成的设置，展示后续操作，引导至产品首页。
步骤连贯性测试：每一步都应回答“这一步是否让用户更接近价值？”为了完整性或展示功能而存在的步骤应删除。
详情见 
references/step-architecture-patterns.md
。

The ah-ha moment design

Ah-ha moment设计

What the wizard is actually trying to engineer.
The principle. The ah-ha moment is the moment the user feels "oh, this is what the product does for me." The wizard's structure should engineer toward that moment.
Identifying the ah-ha moment.
  • It is the visible demonstration of value, not just feature explanation.
  • It is action-tied, not knowledge-tied. The user did something and saw the result.
  • It is single-shot. One clear moment, not a checklist of moments.
  • It is honest. The user genuinely got value; not a contrived demo.
Design implications.
  • The wizard's path should converge on the ah-ha moment. Steps that do not contribute should be deferred or cut.
  • The ah-ah moment should appear within the user's first session, ideally within 5-10 minutes of signup. Longer time-to-value correlates with churn.
  • The ah-ha moment differs by audience. The B2B admin's ah-ha moment differs from the end-user's. Wizards may need to differentiate.
Common ah-ha moment patterns.
  • First successful query/output. The user ran something against their data and saw a useful result.
  • First meaningful collaboration moment. The user shared something with a teammate and saw the response.
  • First saved configuration. The user set up something they will return to.
  • First value-demonstrating insight. The user saw a metric, recommendation, or pattern that surprised them.
Detail in 
references/ah-ha-moment-engineering.md
.
向导真正要实现的目标。
原则：Ah-ha moment是用户感受到“哦，这就是产品能为我做的事”的时刻，向导的结构应围绕这个时刻设计。
识别Ah-ha moment：
  • 是价值的可见展示，而非单纯的功能讲解。
  • 与操作绑定，而非仅与知识绑定。用户执行了操作并看到结果。
  • 是单一明确的时刻，而非一系列时刻的清单。
  • 真实可信，用户确实获得了价值，而非刻意的演示。
设计启示：
  • 向导的路径应聚焦Ah-ha moment，无贡献的步骤应延后或删除。
  • Ah-ha moment应出现在用户首次会话内，理想情况是注册后5-10分钟内。更长的time-to-value与流失率相关。
  • 不同受众的Ah-ha moment不同，B2B管理员与终端用户的Ah-ha moment不同，向导可能需要差异化设计。
常见Ah-ha moment模式：
  • 首次成功查询/输出：用户针对数据执行操作并看到有用结果。
  • 首次有意义的协作时刻：用户与团队成员共享内容并收到反馈。
  • 首次保存的配置：用户设置了后续会用到的内容。
  • 首次展现价值的洞察：用户看到了令人惊讶的指标、建议或模式。
详情见 
references/ah-ha-moment-engineering.md
。

Progressive disclosure patterns

渐进式信息披露模式

How to surface only what is needed at each step.
The principle. Show only the inputs, options, and information the user needs to complete the current step. Defer everything else to in-product help or later configuration.
Pattern A: Default-heavy. Each step has smart defaults. The user can accept or override. Most users accept; advanced users override. Reduces cognitive load.
Pattern B: Required-now, optional-later. Required fields surface in the wizard; optional configuration surfaces in-product after activation. The wizard stays focused.
Pattern C: Expand-on-demand. Sections collapsed by default; the user expands if interested. Rare; works when the user has agency to explore.
Pattern D: Branching. Different users see different steps based on earlier answers. Powerful but adds maintenance complexity.
The discipline. Each piece of information shown in the wizard must justify its inclusion. Decorative information adds friction; surface it later.
Detail in 
references/progressive-disclosure-patterns.md
.
如何仅在每一步展示必要内容。
原则：仅展示用户完成当前步骤所需的输入、选项和信息，其余内容延后至产品内帮助或后续配置中。
模式A：默认优先：每一步都有智能默认值，用户可接受或修改。大多数用户会接受，高级用户可修改，降低认知负荷。
模式B：当前必需，后续可选：必需字段在向导中展示，可选配置在激活后于产品内展示，保持向导聚焦。
模式C：按需展开：默认折叠部分内容，用户感兴趣可展开。较少见，适用于用户有探索自主权的场景。
模式D：分支逻辑：根据用户之前的回答，不同用户看到不同步骤。效果显著，但会增加维护复杂度。
设计准则：向导中展示的每一条信息都必须证明其存在的合理性。装饰性信息会增加摩擦，应延后展示。
详情见 
references/progressive-disclosure-patterns.md
。

Skip and resume mechanics

跳过与恢复机制

When users skip, where they land. When they resume, what they see.
The skip principle. Skip should never produce an empty product. If skipping is offered, the user must land in a state where they can still progress; the wizard's deferred steps must be retrievable.
Skip patterns.
  • Soft skip with context. "Skip for now" deposits the user into a partially-set-up state with clear callouts to complete deferred setup.
  • Skip-and-defer. Skipped steps are queued for later in-product prompts.
  • Skip-with-warning. "Skipping setup will limit your experience to X. Continue?" Honest about consequences.
  • No skip. For wizards that absolutely require completion (compliance forms, paid signups). Use sparingly.
Resume patterns.
  • Auto-resume on next login. The user lands at the step they left.
  • Manual resume from in-product entry. A persistent "Complete setup" surface that returns the user to the wizard.
  • Soft resume. Wizard fades out as the user completes equivalent actions in-product naturally.
The skip-friendly-empty failure. Skip is too prominent and consequence-free; the user lands in an unconfigured product and has no path back. Activation collapses.
The cure. Skip is honest about consequences and offers a path back. The user who skips knows what they skipped.
Detail in 
references/skip-and-resume-mechanics.md
.
用户跳过后进入的状态，恢复时看到的内容。
跳过原则：跳过绝不能让用户进入空产品状态。若提供跳过选项，用户必须进入仍可继续推进的状态，且向导中延后的步骤必须可找回。
跳过模式：
  • 带上下文的软跳过：“暂时跳过”让用户进入部分设置完成状态，并明确提示后续可完成延后的设置。
  • 跳过并延后：跳过的步骤会排入后续产品内提示队列。
  • 带警告的跳过：“跳过设置会限制您体验X功能，是否继续？”如实告知后果。
  • 不可跳过：适用于必须完成的向导（如合规表单、付费注册），谨慎使用。
恢复模式：
  • 下次登录自动恢复：用户登录后回到上次离开的步骤。
  • 从产品入口手动恢复：持久展示“完成设置”入口，让用户返回向导。
  • 软恢复：当用户在产品内自然完成等效操作时，向导自动隐退。
易跳过空状态的失败：跳过选项过于显眼且无后果，用户进入未配置的产品且无返回路径，激活率崩溃。
解决方法：如实告知跳过的后果并提供返回路径，让跳过的用户清楚自己跳过了什么。
详情见 
references/skip-and-resume-mechanics.md
。

Drop-off measurement and remediation

流失率测量与补救

Where users abandon the wizard, and how to fix it.
Per-step instrumentation. Track step start, step completion, step abandonment for every step. The metrics inform every other improvement.
Common drop-off patterns.
  • First-step drop-off. User landed on the wizard, looked at it, left. Often signals the wizard's value proposition is not clear or the audience expected no wizard.
  • Mid-wizard drop-off. User abandoned mid-process. Audit the specific step; field count, sensitive info, unclear progress.
  • Skip-everything drop-off. User skipped every available step. Either the wizard is not earning its time or the skip is too prominent.
Remediation patterns.
  • First-step drop-off: clarify the wizard's purpose; reduce upfront fields; consider whether the wizard is needed at all.
  • Mid-wizard drop-off: audit the high-drop step; reduce friction; reconsider whether that step belongs in the wizard.
  • Skip-everything drop-off: rebalance skip prominence; consider whether the wizard should be replaced with contextual prompts.
The instrumentation requirement. Without per-step tracking, drop-off remediation is guesswork. Set up tracking before launch.
Detail in 
references/drop-off-measurement-templates.md
.
用户在向导的哪个环节放弃，以及如何修复。
分步骤埋点：跟踪每一步的开始、完成、放弃情况，这些指标是所有改进的依据。
常见流失模式：
  • 第一步流失：用户进入向导后直接离开，通常说明向导的价值主张不清晰，或受众原本不期望有向导。
  • 向导中途流失：用户在过程中放弃，审核具体步骤，可能是字段过多、涉及敏感信息或进度不明确。
  • 全程跳过流失：用户跳过所有可跳过的步骤，要么是向导不值得用户花费时间，要么是跳过选项过于显眼。
补救模式：
  • 第一步流失：明确向导的用途，减少前置字段，重新考虑是否需要向导。
  • 中途流失：审核高流失步骤，降低摩擦，重新考虑该步骤是否属于向导。
  • 全程跳过流失：平衡跳过选项的显眼程度，考虑用上下文提示替代向导。
埋点要求：没有分步骤跟踪，流失补救就是猜测。在上线前设置好跟踪。
详情见 
references/drop-off-measurement-templates.md
。

Wizard variations by user type

按用户类型划分的向导变体

Different users may need different wizards.
The admin vs end-user distinction. Admins set up the workspace; end-users start using it. Wizards aimed at both fail both. Differentiated wizards serve each.
The technical vs non-technical distinction. Technical users skip explanations; non-technical users need them. The wizard's tone and depth should match.
The size-of-team distinction. Solo founders have different setup needs than 50-person teams. Wizards may branch.
Differentiation patterns.
  • Role-based branching. First step asks role; subsequent steps adapt.
  • Use-case-based branching. First step asks use case; wizard tailors.
  • Size-based branching. Solo, team, enterprise paths differ.
The over-differentiated trap. Too many variants produce unmaintainable wizards. Most wizards work with 2-3 variants at most.
Detail in 
references/user-type-variation-patterns.md
.
不同用户可能需要不同的向导。
管理员与终端用户的区别：管理员负责设置工作区，终端用户直接使用产品。面向两者的通用向导会同时失败，需设计差异化向导服务各自群体。
技术与非技术用户的区别：技术用户会跳过说明，非技术用户需要说明。向导的语气和深度应匹配用户类型。
团队规模的区别： solo创始人与50人团队的设置需求不同，向导可采用分支逻辑。
差异化模式：
  • 基于角色的分支：第一步询问角色，后续步骤适配。
  • 基于用例的分支：第一步询问用例，向导量身定制。
  • 基于规模的分支：个人、团队、企业路径不同。
过度差异化陷阱：变体过多会导致向导难以维护，大多数向导最多2-3个变体即可。
详情见 
references/user-type-variation-patterns.md
。

Common failure modes

常见失败模式

Rapid-fire. Diagnoses in 
references/common-onboarding-failures.md
.
  • "Activation rate is low; completion rate is high." Wizard completed but did not engineer the ah-ha moment. Audit what users did after completing.
  • "Skip rate is over 50 percent." Either the wizard is not earning its time or skip is too prominent. Audit both.
  • "Users complete the wizard then abandon the product within 24 hours." Time-to-value too long; ah-ha moment not in first session.
  • "Wizard works for new users; existing users hit broken steps." Wizard not maintained alongside product; deprecated features still in flow.
  • "Different segments complete at very different rates." Audience-fit varies; consider role-based or use-case-based branching.
  • "Mobile completion is half of desktop." Mobile UX of the wizard broken.
  • "We added more onboarding steps; activation went down." Tutorial-overload pattern; more is not better.
  • "Skip mechanics work but users do not return to complete setup." Skip-and-defer not working; in-product prompts to return are missing or ignored.
  • "Wizard analytics broke after the last release." Instrumentation drift; track and refresh.
快速诊断，详情见 
references/common-onboarding-failures.md
。
  • “激活率低，完成率高”：用户完成向导但未抵达Ah-ha moment，审核用户完成向导后的操作。
  • “跳过率超过50%”：要么向导不值得用户花费时间，要么跳过选项过于显眼，两者都需审核。
  • “用户完成向导后24小时内放弃产品”：time-to-value过长，Ah-ha moment未出现在首次会话内。
  • “向导对新用户有效，现有用户遇到失效步骤”：向导未随产品更新维护，流程中仍包含已弃用功能。
  • “不同群体的完成率差异极大”：受众适配度不同，考虑基于角色或用例的分支逻辑。
  • “移动端完成率仅为桌面端的一半”：向导的移动端UX存在问题。
  • “我们添加了更多引导步骤，激活率却下降了”：属于教程过载模式，更多并不更好。
  • “跳过机制有效，但用户未返回完成设置”：跳过并延后机制失效，产品内返回提示缺失或被忽略。
  • “上次发布后向导分析数据失效”：埋点偏移，需跟踪并更新。

The framework: 12 considerations for onboarding wizard design

框架：引导向导设计的12项考量

When designing or auditing an onboarding wizard, walk these 12 considerations.
  1. The wizard decision. Is a wizard the right tool, or do contextual prompts suffice?
  2. Earned-progressive-disclosure, not tutorial-overload or skip-friendly-empty. Each step earns one step closer to value.
  3. Step architecture sound. Each step moves the user closer to value; non-contributing steps cut.
  4. The ah-ha moment engineered. Single visible value moment, action-tied, in the first session.
  5. Progressive disclosure applied. Show only what is needed now; defer the rest.
  6. Skip mechanics honest. Skip exists but does not produce an empty product.
  7. Resume mechanics work. Skipped users have a path back; instrumented for follow-through.
  8. Drop-off measurement instrumented. Per-step tracking from launch.
  9. User-type variations balanced. 2-3 variants max; over-differentiation avoided.
  10. Mobile parity. Wizard works on the devices the audience uses.
  11. Activation as success metric. Not just completion rate; the metric is post-wizard product engagement.
  12. Maintenance discipline. Wizard updated alongside product changes; quarterly audit.
The output of the framework is an onboarding wizard that gets users to the ah-ha moment, respects their time, and produces activation rates the team can defend.
设计或审核引导向导时，需逐一考量以下12点：
  1. 向导决策：向导是否是合适的工具，还是上下文提示足够？
  2. 采用渐进式价值披露，而非教程过载或易跳过空状态：每一步都让用户更接近价值。
  3. 步骤架构合理：每一步都让用户更接近价值，删除无贡献的步骤。
  4. 设计Ah-ha moment：单一可见的价值时刻，与操作绑定，出现在首次会话内。
  5. 应用渐进式信息披露：仅展示当前所需内容，其余延后。
  6. 跳过机制透明：存在跳过选项，但不会让用户进入空产品状态。
  7. 恢复机制有效：跳过的用户有返回路径，并设置跟踪以跟进完成情况。
  8. 设置流失率测量埋点：从上线开始就进行分步骤跟踪。
  9. 平衡用户类型变体：最多2-3个变体，避免过度差异化。
  10. 移动端适配：向导在受众使用的设备上均可正常工作。
  11. 以激活率为成功指标：不仅关注完成率，更关注向导后的产品参与度。
  12. 维护准则：随产品变更更新向导，每季度审核一次。
该框架的产出是一款能让用户抵达Ah-ha moment、尊重用户时间、并带来可靠激活率的引导向导。

Reference files

参考文件

  • references/wizard-decision-criteria.md
     - When wizards earn the build vs when contextual help suffices.
  • references/step-architecture-patterns.md
     - What belongs in each step. Sequence logic. Step coherence test.
  • references/ah-ha-moment-engineering.md
     - Identifying the ah-ha moment; designing the wizard to converge on it.
  • references/progressive-disclosure-patterns.md
     - Default-heavy, required-now-optional-later, expand-on-demand, branching patterns.
  • references/skip-and-resume-mechanics.md
     - Skip patterns and resume patterns. The skip-friendly-empty failure.
  • references/drop-off-measurement-templates.md
     - Per-step instrumentation. Common drop-off patterns and remediation.
  • references/user-type-variation-patterns.md
     - Admin vs end-user, technical vs non-technical, size-based branching.
  • references/wizard-anti-patterns.md
     - The patterns that look like onboarding but degrade activation.
  • references/common-onboarding-failures.md
     - 9+ failure patterns with diagnoses and cures.
  • references/wizard-decision-criteria.md
     - 何时值得投入构建向导，何时上下文帮助足够。
  • references/step-architecture-patterns.md
     - 每步应包含的内容、顺序逻辑、步骤连贯性测试。
  • references/ah-ha-moment-engineering.md
     - 识别Ah-ha moment，设计向导聚焦该时刻。
  • references/progressive-disclosure-patterns.md
     - 默认优先、当前必需后续可选、按需展开、分支逻辑模式。
  • references/skip-and-resume-mechanics.md
     - 跳过与恢复模式、易跳过空状态的失败案例。
  • references/drop-off-measurement-templates.md
     - 分步骤埋点、常见流失模式与补救方法。
  • references/user-type-variation-patterns.md
     - 管理员与终端用户、技术与非技术用户、基于规模的分支逻辑。
  • references/wizard-anti-patterns.md
     - 看似引导却降低激活率的模式。
  • references/common-onboarding-failures.md
     - 9种以上失败模式及诊断与解决方法。

Closing: wizards earn the user's first session

结语：向导赢得用户的首次会话

The onboarding wizards that work as compounding assets are the ones that get the user to value within their first session. Not because the wizard had every feature explained. Not because the wizard was skipped quickly. Because the wizard engineered the ah-ha moment, respected the user's time, and surfaced the right thing at the right moment.
That is the bar. Below the bar are tutorial-overload (everything upfront, nobody completes) and skip-friendly-empty (skip too prominent, nobody activates). Above the bar are earned-progressive-disclosure wizards where each step earns the user one step closer to value, skip is honest about consequences, and the activation metric reflects the wizard's actual job.
The discipline is in the design choices. The decision to build a wizard at all, or defer to contextual help. The step architecture that converges on the ah-ha moment. The progressive disclosure that surfaces the right thing at the right moment. The skip mechanics that protect the user from an empty product. The drop-off instrumentation that informs ongoing improvement. The maintenance cadence that keeps the wizard in sync with the product it represents.
When in doubt, ask: did the user reach the ah-ha moment in their first session, and did the wizard help or hinder that? If yes to the first and helped on the second, the wizard earned its build. If no to either, redesign.
能成为复利资产的引导向导，是那些能让用户在首次会话内抵达价值的向导。不是因为向导讲解了所有功能，也不是因为向导能快速跳过，而是因为向导设计了Ah-ha moment、尊重用户时间、并在正确的时机呈现正确内容。
这就是标准。低于标准的是教程过载（一次性展示所有内容，无人完成）和易跳过空状态（跳过选项过于显眼，无人激活）。高于标准的是渐进式价值披露向导，每一步都让用户更接近价值，跳过机制如实告知后果，激活指标反映向导的实际作用。
关键在于设计选择：决定是否构建向导，还是采用上下文帮助；设计聚焦Ah-ha moment的步骤架构；应用渐进式信息披露在正确时机呈现内容；设计避免用户进入空产品的跳过机制；设置指导持续改进的流失埋点；保持向导与产品同步的维护节奏。
存疑时，问自己：用户是否在首次会话内抵达了Ah-ha moment？向导对此起到了帮助还是阻碍作用？若第一个问题答案是“是”且第二个是“帮助”，说明向导值得构建；若任一答案为否，则需重新设计。