prd-v04-user-journey-mapping

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

User Journey Mapping

用户旅程映射

Position in workflow: v0.4 Persona Definition → v0.4 User Journey Mapping → v0.4 Screen Flow Definition

User journeys transform features into paths. A journey answers: "How does [persona] go from [trigger] to [value moment] using [features]?"

在工作流中的位置：v0.4 用户角色定义 → v0.4 用户旅程映射 → v0.4 界面流程定义

用户旅程将功能转化为路径。一个旅程需要回答：“[用户角色]如何通过[功能]从[触发点]到达[价值时刻]？”

Journey Types

旅程类型

Type	Purpose	Priority Signal	Example
Core	Primary value delivery	Must complete for activation	First report generated
Onboarding	First-time user setup	Blocks all other journeys	Account creation → first action
Recovery	Error handling, support	Retention protection	Password reset, billing issue
Power User	Advanced workflows	Expansion/upsell	Bulk operations, integrations

Rule: Define Onboarding first (it gates everything), then Core journeys (they deliver KPI-), then others.

类型	目的	优先级信号	示例
核心旅程	传递核心价值	激活必须完成	生成第一份报告
新用户引导	首次用户设置	阻碍所有其他旅程	创建账户 → 首次操作
恢复旅程	错误处理、支持	保障留存	重置密码、账单问题处理
资深用户旅程	高级工作流	拓展/增购	批量操作、集成功能

规则：首先定义新用户引导旅程（它是所有旅程的前提），然后定义核心旅程（它们关联KPI-），最后定义其他类型的旅程。

Journey Anatomy

旅程结构

Every journey has:

Trigger — What causes the user to start? (Event, not "opens app")
Steps — Actions linked to FEA- features
Pain Points — Where friction exists (design around these)
Moment of Value — When user achieves goal (this drives KPI-)

每个旅程包含：

触发点 —— 是什么促使用户开始旅程？（具体事件，而非“打开应用”）
步骤 —— 与FEA-功能关联的操作
痛点 —— 存在摩擦的环节（需要围绕这些进行设计优化）
价值时刻 —— 用户达成目标的时刻（这是KPI-的驱动因素）

Mapping Process

映射流程

Pull PER- (personas) from Persona Definition
- Each journey belongs to a specific persona
Pull FEA- (features) and KPI- (outcomes) from v0.3
- Features are the building blocks of journey steps
- KPIs tell you which journeys matter most
Define trigger events
- What causes the user to start this journey?
- Be specific: "Receives calendar invite" not "opens app"
Map step flow using features
- Each step = an action the user takes
- Link each step to the FEA- that enables it
Identify pain points
- Where might the user get confused, frustrated, or blocked?
- These inform UX design decisions
Mark "moments of value"
- When does the user get the payoff?
- This should tie to KPI- measurement
Create UJ- entries with full traceability

提取PER-（用户角色）：来自用户角色定义
- 每个旅程都属于特定的用户角色
提取FEA-（功能）和KPI-（成果）：来自v0.3版本
- 功能是旅程步骤的构建模块
- KPI告诉你哪些旅程最为重要
定义触发事件
- 是什么促使用户开始这个旅程？
- 要具体：比如“收到日历邀请”而非“打开应用”
使用功能映射步骤流程
- 每个步骤 = 用户执行的一个操作
- 将每个步骤与支持它的FEA-关联
识别痛点
- 用户可能在哪些环节感到困惑、沮丧或受阻？
- 这些信息为UX设计决策提供依据
标记“价值时刻”
- 用户何时获得回报？
- 这需要与KPI-的衡量指标关联
创建具备完整可追溯性的UJ-条目

UJ- Output Template

UJ-输出模板

UJ-XXX: [Journey Title]
Persona: [PER-XXX]
Type: [Core | Onboarding | Recovery | Power User]
Trigger: [Event that initiates journey]
Goal: [What user wants to accomplish]

Steps:
  1. [Action] → FEA-XXX
  2. [Action] → FEA-XXX
  3. [Action] → FEA-XXX
  ...

Pain Points:
  - [Step X]: [Potential friction — e.g., "requires context switch"]
  - [Step Y]: [Potential friction]

Moment of Value: [When user achieves goal — be specific]
KPI Link: [KPI-XXX this journey drives]
Success Metric: [How we measure journey completion]
Dependencies: [BR-XXX constraints, API-XXX if known]

Example UJ- entry:

UJ-001: First Report Generation
Persona: PER-001 (Overwhelmed Ops Manager)
Type: Core
Trigger: User completes onboarding and sees empty dashboard
Goal: Generate first automated report to see time-saving value

Steps:
  1. Click "Create Report" → FEA-003 (one-click reports)
  2. Select data source → FEA-001 (auto-sync)
  3. Choose report template → FEA-008 (templates)
  4. Preview report → FEA-003
  5. Export/share report → FEA-009 (export)

Pain Points:
  - Step 2: User may not have connected data source yet (dependency on UJ-002)
  - Step 3: Template overload if too many choices

Moment of Value: Seeing the completed report with their actual data
KPI Link: KPI-002 (activation rate)
Success Metric: Time from "Create Report" click to export ≤ 5 minutes
Dependencies: BR-015 (data format rules), UJ-002 (data source connection)

UJ-XXX: [旅程标题]
Persona: [PER-XXX]
Type: [Core | Onboarding | Recovery | Power User]
Trigger: [触发旅程的事件]
Goal: [用户想要达成的目标]

Steps:
  1. [操作] → FEA-XXX
  2. [操作] → FEA-XXX
  3. [操作] → FEA-XXX
  ...

Pain Points:
  - [步骤X]: [潜在摩擦 —— 例如：“需要切换上下文”]
  - [步骤Y]: [潜在摩擦]

Moment of Value: [用户达成目标的时刻 —— 需具体]
KPI Link: [该旅程关联的KPI-XXX]
Success Metric: [我们衡量旅程完成度的指标]
Dependencies: [已知的BR-XXX约束、API-XXX]

UJ-条目示例：

UJ-001: 生成第一份报告
Persona: PER-001 (不堪重负的运维经理)
Type: Core
Trigger: 用户完成新用户引导后看到空仪表盘
Goal: 生成第一份自动化报告，体验省时价值

Steps:
  1. 点击“创建报告” → FEA-003 (一键生成报告)
  2. 选择数据源 → FEA-001 (自动同步)
  3. 选择报告模板 → FEA-008 (模板库)
  4. 预览报告 → FEA-003
  5. 导出/分享报告 → FEA-009 (导出功能)

Pain Points:
  - Step 2: 用户可能尚未连接数据源（依赖UJ-002）
  - Step 3: 模板过多导致选择困难

Moment of Value: 看到包含自身实际数据的完整报告
KPI Link: KPI-002 (激活率)
Success Metric: 从点击“创建报告”到导出的时间 ≤ 5分钟
Dependencies: BR-015 (数据格式规则), UJ-002 (数据源连接)

Feature-to-Journey Validation

功能到旅程的验证

After mapping journeys, validate:

No orphaned features: Every FEA- appears in at least one UJ-
No journey gaps: Every step has a FEA- that enables it
KPI coverage: Core journeys tie to Tier 1/2 KPIs

If a FEA- isn't in any journey, either:

Add it to a journey (you missed a use case), or
Cut it from scope (it's not needed)

完成旅程映射后，需验证：

无孤立功能：每个FEA-至少出现在一个UJ-中
无旅程缺口：每个步骤都有对应的FEA-支持
KPI覆盖：核心旅程关联1/2级KPI

如果某个FEA-未出现在任何旅程中，要么：

将其添加到某个旅程中（你遗漏了一个使用场景），要么
将其从范围中移除（不需要该功能）

Journey Sequencing

旅程排序

Map dependencies between journeys:

UJ-000: Onboarding (gates all)
    ↓
UJ-001: First Report (Core) ← KPI-002 (activation)
    ↓
UJ-002: Data Source Connection (Core) ← KPI-003 (depth)
    ↓
UJ-003: Team Invite (Power User) ← KPI-004 (expansion)

映射旅程之间的依赖关系：

UJ-000: 新用户引导（所有旅程的前提）
    ↓
UJ-001: 第一份报告（核心） ← KPI-002 (激活率)
    ↓
UJ-002: 数据源连接（核心） ← KPI-003 (使用深度)
    ↓
UJ-003: 团队邀请（资深用户） ← KPI-004 (用户拓展)

Anti-Patterns to Avoid

需避免的反模式

Anti-Pattern	Signal	Fix
Feature-first journeys	Steps = feature list dumped in order	Start with user goal, then map features to it
No trigger	"User opens app"	Define specific event: "receives notification"
No value moment	Journey ends without payoff	Each journey needs clear outcome
Orphaned features	FEA- not in any journey	Add to journey or cut from scope
Generic personas	"User does X"	Specify PER-: "PER-001 does X"
Happy path only	No pain points identified	Anticipate where users struggle
Mega-journeys	15+ steps	Split into sub-journeys

反模式	信号	修复方案
功能优先的旅程	步骤 = 按顺序罗列的功能列表	从用户目标出发，再将功能映射到目标
无触发点	“用户打开应用”	定义具体事件：比如“收到通知”
无价值时刻	旅程结束时没有回报	每个旅程都需要明确的成果
孤立功能	FEA-未出现在任何旅程中	添加到旅程或从范围中移除
通用用户角色	“用户执行X操作”	明确PER-：比如“PER-001执行X操作”
仅考虑顺畅路径	未识别任何痛点	预判用户可能遇到的困难
超大型旅程	包含15个以上步骤	拆分为子旅程

Quality Gates

质量检查门

Downstream Connections

下游关联

UJ- entries feed into:

Consumer	What It Uses	Example
v0.4 Screen Flow Definition	Steps become screens	UJ-001 Step 3 → SCR-005
v0.6 Technical Specification	Journeys inform API sequences	UJ-001 → API-001, API-002 flow
v0.7 Test Planning	Journeys become E2E tests	TEST-020 validates UJ-001
v0.9 GTM	Journey-based onboarding messaging	"Complete [UJ-001] in 5 minutes"

UJ-条目为以下环节提供输入：

使用者	使用内容	示例
v0.4 界面流程定义	步骤转化为界面	UJ-001 步骤3 → SCR-005
v0.6 技术规格说明	旅程为API序列提供依据	UJ-001 → API-001、API-002流程
v0.7 测试规划	旅程转化为端到端测试	TEST-020 验证UJ-001
v0.9 上市准备（GTM）	基于旅程的新用户引导消息	“在5分钟内完成[UJ-001]”

Detailed References

详细参考

Journey mapping examples: See
```
references/examples.md
```
UJ- entry template: See
```
assets/uj.md
```
Journey sequencing guide: See
```
references/sequencing.md
```

旅程映射示例：查看
```
references/examples.md
```
UJ-条目模板：查看
```
assets/uj.md
```
旅程排序指南：查看
```
references/sequencing.md
```