customer-journey-mapping-workshop

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Purpose

目的

Guide product managers through creating a customer journey map by asking adaptive questions about the actor (persona), scenario/goal, journey phases, actions/emotions, and opportunities for improvement. Use this to visualize the end-to-end customer experience, identify pain points, and create a shared mental model across teams—avoiding surface-level feature lists and ensuring discovery work focuses on real customer problems, not assumed solutions.

This is not a feature roadmap—it's a discovery and alignment tool that uncovers where the experience breaks down and where improvements will have the greatest impact.

通过提出关于参与者（Persona）、场景/目标、旅程阶段、行为/情绪以及改进机会的适应性问题，引导产品经理创建客户旅程地图。使用此工具可视化端到端的客户体验，识别痛点，并在团队间建立统一的认知模型——避免停留在表面功能列表，确保探索工作聚焦于真实的客户问题，而非假设的解决方案。

这不是功能路线图——它是一个探索与对齐工具，用于发现体验出现问题的环节，以及改进能产生最大影响的区域。

Key Concepts

核心概念

What is a Customer Journey Map?

什么是客户旅程地图？

A journey map (NNGroup) visualizes "the process that a person goes through in order to accomplish a goal." It compiles user actions into a timeline, enriched with thoughts and emotions to create a narrative, then condenses and polishes into a visual artifact.

旅程地图（NNGroup定义）可视化“一个人为达成目标所经历的过程”。它将用户行为整理成时间线，结合想法和情绪形成叙事，然后浓缩优化为可视化产物。

Five Key Components (NNGroup Framework)

五大核心组件（NNGroup框架）

Actor — A specific persona or user whose perspective anchors the map
Scenario + Expectations — The situational context and associated goals
Journey Phases — High-level stages organizing the experience (e.g., discover, try, buy, use, seek support)
Actions, Mindsets, and Emotions — User behaviors, thoughts, and emotional responses throughout phases
Opportunities — Insights identifying where experience can improve

参与者 — 锚定地图视角的特定Persona或用户
场景 + 期望 — 情境背景及相关目标
旅程阶段 — 组织体验的高级阶段（例如：发现、试用、购买、使用、寻求支持）
行为、思维与情绪 — 用户在各阶段的行为、想法和情绪反应
改进机会 — 识别体验可优化方向的洞察

Journey Map Structure

旅程地图结构

Actor: [Persona Name]
Scenario: [Goal/Context]

Phase 1: Discover → Phase 2: Try → Phase 3: Buy → Phase 4: Use → Phase 5: Support
   ↓                  ↓                ↓               ↓               ↓
Actions:           Actions:         Actions:        Actions:        Actions:
Thoughts:          Thoughts:        Thoughts:       Thoughts:       Thoughts:
Emotions: 😊😐😞    Emotions:        Emotions:       Emotions:       Emotions:
   ↓                  ↓                ↓               ↓               ↓
Opportunities:     Opportunities:   Opportunities:  Opportunities:  Opportunities:

Actor: [Persona Name]
Scenario: [Goal/Context]

Phase 1: Discover → Phase 2: Try → Phase 3: Buy → Phase 4: Use → Phase 5: Support
   ↓                  ↓                ↓               ↓               ↓
Actions:           Actions:         Actions:        Actions:        Actions:
Thoughts:          Thoughts:        Thoughts:       Thoughts:       Thoughts:
Emotions: 😊😐😞    Emotions:        Emotions:       Emotions:       Emotions:
   ↓                  ↓                ↓               ↓               ↓
Opportunities:     Opportunities:   Opportunities:  Opportunities:  Opportunities:

Why This Works

为何有效

Forces conversation: Teams align on shared understanding of customer experience
Reveals pain points: Emotions + actions highlight where experience breaks down
Prioritizes improvements: Opportunities ranked by impact guide roadmap decisions
Human-centered: Focuses on customer perspective, not internal processes

推动对话： 团队对齐对客户体验的共同理解
揭示痛点： 情绪+行为凸显体验失效的环节
优化优先级： 按影响排序的机会指导路线图决策
以人为本： 聚焦客户视角，而非内部流程

Anti-Patterns (What This Is NOT)

反模式（此工具不是什么）

Not a service blueprint: Journey maps focus on customer perspective; service blueprints map internal operations
Not a user story map: Journey maps support discovery; user story maps facilitate implementation planning
Not an experience map: Journey maps target specific users and products; experience maps explore broader human behaviors

不是服务蓝图： 旅程地图聚焦客户视角；服务蓝图映射内部运营
不是用户故事地图： 旅程地图支持探索；用户故事地图促进实施规划
不是体验地图： 旅程地图针对特定用户和产品；体验地图探索更广泛的人类行为

When to Use This

适用场景

Starting customer discovery (understanding current experience)
Identifying pain points for retention/engagement initiatives
Aligning cross-functional teams on customer perspective
Prioritizing which problems to solve first

启动客户探索（了解当前体验）
识别留存/参与计划的痛点
跨职能团队对齐客户视角
优先确定要解决的问题

When NOT to Use This

不适用场景

When you already understand the customer journey deeply
For technical refactoring (no customer-facing journey)
As a substitute for user research (maps require research input)

已深度理解客户旅程时
技术重构（无客户接触旅程）
替代用户研究（地图需要研究输入）

Facilitation Source of Truth

引导工作坊的权威依据

Use

workshop-facilitation

as the default interaction protocol for this skill.

It defines:

session heads-up + entry mode (Guided, Context dump, Best guess)
one-question turns with plain-language prompts
progress labels (for example, Context Qx/8 and Scoring Qx/5)
interruption handling and pause/resume behavior
numbered recommendations at decision points
quick-select numbered response options for regular questions (include
```
Other (specify)
```
when useful)

This file defines the domain-specific assessment content. If there is a conflict, follow this file's domain logic.

使用

workshop-facilitation

作为此技能的默认交互协议。

它定义了：

会话提醒 + 进入模式（引导式、情境输入、最佳猜测）
单轮提问，使用通俗易懂的提示
进度标签（例如：情境问题 Qx/8、评分问题 Qx/5）
中断处理与暂停/恢复行为
决策点的编号建议
常规问题的快速选择编号响应选项（必要时包含“其他（请说明）”）

本文件定义了特定领域的评估内容。若存在冲突，遵循本文件的领域逻辑。

Application

应用

This interactive skill asks up to 5 adaptive questions, offering 3-4 enumerated options at each step.

Interaction pattern: Pair with

skills/workshop-facilitation/SKILL.md

when you want a one-step-at-a-time flow with numbered recommendations at decision points and quick-select options for regular questions. If the user asks for a single-shot output, skip the multi-turn facilitation.

此交互式技能会提出最多5个适应性问题，每个步骤提供3-4个枚举选项。

交互模式：若希望采用分步流程，在决策点提供编号建议，常规问题提供快速选择选项，请搭配

skills/workshop-facilitation/SKILL.md

使用。若用户要求一次性输出，跳过多轮引导。

Step 0: Gather Context (Before Questions)

步骤0：收集背景信息（提问前）

Agent suggests:

Before we create your journey map, let's gather context:

Customer Research:

User interviews, discovery notes, support tickets
Churn reasons, exit surveys, NPS feedback
Analytics data (drop-off points, feature usage)
Personas or proto-personas

Product Context:

Website copy, product descriptions, positioning
Competitor journey maps or reviews (G2, Capterra)
Existing journey documentation (if any)

You can paste this content directly, or describe the customer experience briefly.

Agent建议：

在创建旅程地图前，我们先收集背景信息：

客户研究：

用户访谈、探索笔记、支持工单
流失原因、退出调查、NPS反馈
分析数据（流失点、功能使用情况）
Persona 或原型Persona

产品背景：

网站文案、产品描述、定位
竞品旅程地图或评测（G2、Capterra）
现有旅程文档（如有）

您可以直接粘贴内容，或简要描述客户体验。

Question 1: Identify Actor (Persona)

问题1：确定参与者（Persona）

Agent asks: "Who is the actor for this journey map? (Which persona or user segment?)"

Offer 4 enumerated options:

Primary persona — "Your main target customer (e.g., 'small business owner')" (Most common starting point)
Secondary persona — "A secondary user segment with different needs (e.g., 'enterprise admin' vs. 'end user')" (Use if primary persona already mapped)
High-churn persona — "User segment with highest churn rate (e.g., 'trial users who don't convert')" (Good for retention initiatives)
Newly discovered persona — "Emerging user segment from recent research (e.g., 'remote teams' post-COVID)" (Good for market expansion)

Or describe your specific persona.

Adaptation: Use personas from context (proto-personas, JTBD research, etc.)

User response: [Selection or custom]

Agent提问： “此旅程地图的参与者是谁？（对应哪个Persona或用户细分群体？）”

提供4个枚举选项：

核心Persona — “您的主要目标客户（例如：‘小企业主’）”（最常见的起点）
次要Persona — “具有不同需求的次级用户群体（例如：‘企业管理员’ vs ‘终端用户’）”（若核心Persona已完成映射时使用）
高流失Persona — “流失率最高的用户群体（例如：‘未转化的试用用户’）”（适合留存计划）
新发现Persona — 近期研究中出现的用户群体（例如：‘疫情后的远程团队’）”（适合市场拓展）

或描述您的特定Persona。

适配： 使用背景信息中的Persona（原型Persona、JTBD研究等）

用户回复： [选择或自定义]

Question 2: Define Scenario + Goal

问题2：定义场景 + 目标

Agent asks: "What's the scenario and goal for this journey? (What is the actor trying to accomplish?)"

Offer 4 enumerated options:

First-time use — "New user onboarding, from discovery to activation" (Common for SaaS, apps)
Core workflow — "Recurring task the user does regularly (e.g., 'create invoice,' 'run report')" (Common for established products)
Problem resolution — "User encounters issue and seeks help (e.g., 'forgot password,' 'billing question')" (Good for support/retention)
Upgrade/expansion — "Free user considering paid plan, or existing customer expanding usage" (Good for growth initiatives)

Or describe your specific scenario.

User response: [Selection or custom]

Agent extracts:

Actor: [Persona from Q1]
Scenario: [Context from Q2]
Goal: [What actor is trying to accomplish]

Agent提问： “此旅程的场景和目标是什么？（参与者试图完成什么？）”

提供4个枚举选项：

首次使用 — “新用户入职，从发现到激活”（SaaS、应用程序常见场景）
核心工作流 — “用户定期执行的重复性任务（例如：‘创建发票’、‘生成报表’）”（成熟产品常见场景）
问题解决 — “用户遇到问题并寻求帮助（例如：‘忘记密码’、‘账单疑问’）”（适合支持/留存计划）
升级/拓展 — “免费用户考虑付费方案，或现有客户扩大使用范围”（适合增长计划）

或描述您的特定场景。

用户回复： [选择或自定义]

Agent提取：

参与者： [问题1中的Persona]
场景： [问题2中的背景]
目标： [参与者试图完成的事]

Question 3: Identify Journey Phases

问题3：确定旅程阶段

Agent says: "Let's break the journey into high-level phases (typically 4-6 phases from start to end)."

Agent generates 4-6 journey phases based on scenario (Q2).

Example (if Scenario = "First-time use"):

Journey Phases (left to right):

1. Discover — User learns about product
2. Evaluate — User researches, compares alternatives
3. Try — User signs up, starts onboarding
4. Activate — User reaches "aha moment," experiences value
5. Use — User integrates product into workflow
6. Expand — User considers upgrading or inviting team

Agent asks: "Do these phases capture the full journey? Should we add, remove, or rename phases?"

User response: [Approve or modify]

Agent说明： “我们将旅程分解为高级阶段（通常从开始到结束为4-6个阶段）。”

Agent根据场景（问题2）生成4-6个旅程阶段。

示例（若场景=“首次使用”）：

Journey Phases (left to right):

1. Discover — User learns about product
2. Evaluate — User researches, compares alternatives
3. Try — User signs up, starts onboarding
4. Activate — User reaches "aha moment," experiences value
5. Use — User integrates product into workflow
6. Expand — User considers upgrading or inviting team

Agent提问： “这些阶段是否涵盖了完整旅程？我们需要添加、删除或重命名阶段吗？”

用户回复： [确认或修改]

Question 4: Map Actions, Thoughts, Emotions per Phase

问题4：按阶段映射行为、思维与情绪

Agent says: "Now let's map what the actor does, thinks, and feels in each phase."

Agent generates 3-5 actions, thoughts, and emotions per phase based on context (Step 0) and scenario (Q2).

Example (for Phase 3: "Try — User signs up, starts onboarding"):

Phase 3: Try (Onboarding)

Actions:
- Signs up with email
- Receives welcome email
- Logs in for the first time
- Sees empty dashboard
- Searches for "getting started" guide

Thoughts:
- "This looks promising, but I'm not sure where to start"
- "Do I need to watch a tutorial video?"
- "What's the first step?"

Emotions:
- Curious but uncertain 🤔
- Slightly frustrated (no clear next step) 😕
- Hopeful it will get easier 🙂

Pain Points:
- No onboarding checklist or guided tour
- Empty state doesn't suggest next action
- Too many options in navigation (overwhelming)

Agent repeats for all journey phases, showing full map.

Agent asks: "Does this capture the customer experience accurately? Should we adjust actions, thoughts, or emotions?"

User response: [Approve or modify]

Agent说明： “现在我们来映射参与者在每个阶段的行为、想法和感受。”

Agent根据背景信息（步骤0）和场景（问题2），为每个阶段生成3-5个行为、想法和情绪。

示例（针对阶段3：“Try — User signs up, starts onboarding”）：

Phase 3: Try (Onboarding)

Actions:
- Signs up with email
- Receives welcome email
- Logs in for the first time
- Sees empty dashboard
- Searches for "getting started" guide

Thoughts:
- "This looks promising, but I'm not sure where to start"
- "Do I need to watch a tutorial video?"
- "What's the first step?"

Emotions:
- Curious but uncertain 🤔
- Slightly frustrated (no clear next step) 😕
- Hopeful it will get easier 🙂

Pain Points:
- No onboarding checklist or guided tour
- Empty state doesn't suggest next action
- Too many options in navigation (overwhelming)

Agent为所有旅程阶段重复此操作，展示完整地图。

Agent提问： “这是否准确捕捉了客户体验？我们需要调整行为、想法或情绪吗？”

用户回复： [确认或修改]

Question 5: Identify Opportunities (Pain Points to Address)

问题5：识别改进机会（需解决的痛点）

Agent says: "Based on the journey map, let's identify opportunities for improvement—ranked by impact."

Agent generates 5-7 opportunities (pain points with highest emotional intensity or drop-off rates).

Example:

undefined

Agent说明： “基于旅程地图，我们来识别改进机会——按影响排序。”

Agent生成5-7个机会（情绪强度最高或流失率最高的痛点）。

示例：

undefined

Opportunities (Ranked by Impact)

1. Onboarding lacks guided first steps (Phase 3: Try)

Pain Point: Users see empty dashboard, don't know what to do first Evidence: 60% of signups don't complete first action within 24 hours Opportunity: Add interactive onboarding checklist ("Create your first project," "Invite a teammate") Impact: HIGH — Directly affects activation rate

2. Pricing page is confusing (Phase 2: Evaluate)

Pain Point: Users don't understand which plan fits their needs Evidence: High bounce rate on pricing page (70% leave without signing up) Opportunity: Add plan comparison tool or "Which plan is right for me?" quiz Impact: HIGH — Directly affects trial conversion

3. Support is hard to find (Phase 5: Use)

Pain Point: Users encounter issues, struggle to find help Evidence: Support tickets often say "I couldn't find an answer in docs" Opportunity: Add in-app help widget, contextual tooltips Impact: MEDIUM — Affects retention, but fewer users hit this phase

4. Email confirmations lack context (Phase 1: Discover)

Pain Point: Marketing emails don't explain value clearly Evidence: Low click-through rate on email campaigns (5% vs. industry avg 15%) Opportunity: Rewrite emails with customer language, clear CTAs Impact: MEDIUM — Affects top-of-funnel awareness

5. Upgrade prompts feel pushy (Phase 6: Expand)

Pain Point: Users perceive upgrade prompts as sales-y, not helpful Evidence: Negative sentiment in NPS comments ("too many upgrade popups") Opportunity: Show upgrade value contextually (when user hits free plan limit) Impact: LOW — Affects smaller user subset


**Agent asks:**
"Do these opportunities align with your priorities? Which should we focus on first?"

**User response:** [Selection or custom]

---


**Agent提问：**
“这些机会是否符合您的优先级？我们应首先聚焦哪些？”

**用户回复：** [选择或自定义]

---

Output: Customer Journey Map + Opportunity List

输出：客户旅程地图 + 机会列表

After completing the flow, the agent outputs:

markdown

undefined

完成流程后，Agent输出：

markdown

undefined

Customer Journey Map: [Scenario from Q2]

Actor: [Persona from Q1] Scenario: [Context from Q2] Goal: [What actor is trying to accomplish] Date: [Today's date]

Journey Phases

[Phase 1] → [Phase 2] → [Phase 3] → [Phase 4] → [Phase 5] → [Phase 6]

Full Journey Map

Phase 1: [Name]

Actions:

[Action 1]
[Action 2]
[Action 3]

Thoughts:

"[Quote 1]"
"[Quote 2]"

Emotions:

[Emotion 1] 😊
[Emotion 2] 😐

Pain Points:

[Pain point 1]
[Pain point 2]

Actions:

[Action 1]
[Action 2]
[Action 3]

Thoughts:

"[Quote 1]"
"[Quote 2]"

Emotions:

[Emotion 1] 😊
[Emotion 2] 😐

Pain Points:

[Pain point 1]
[Pain point 2]

Phase 2: [Name]

[...repeat structure for all phases...]

Opportunities (Prioritized)

Opportunity 1: [Name] (HIGH IMPACT)

Phase: [Journey phase] Pain Point: [Description] Evidence: [Data/research] Proposed Solution: [How to address] Impact: HIGH — [Rationale]

Opportunity 2: [Name] (HIGH IMPACT)

Phase: [Journey phase] Pain Point: [Description] Evidence: [Data/research] Proposed Solution: [How to address] Impact: HIGH — [Rationale]

[...continue for all opportunities...]

Phase: [Journey phase] Pain Point: [Description] Evidence: [Data/research] Proposed Solution: [How to address] Impact: HIGH — [Rationale]

[...continue for all opportunities...]

Next Steps

Validate opportunities: Use
```
discovery-interview-prep.md
```
to test hypotheses with customers
Prioritize fixes: Use
```
prioritization-advisor.md
```
to choose which opportunities to tackle first
Create problem statements: Use
```
problem-statement.md
```
to frame top opportunities
Build experiments: Use
```
opportunity-solution-tree.md
```
to design solutions and POCs

Ready to start addressing opportunities? Let me know if you'd like to refine the map or dive into a specific pain point.

---

Validate opportunities: Use
```
discovery-interview-prep.md
```
to test hypotheses with customers
Prioritize fixes: Use
```
prioritization-advisor.md
```
to choose which opportunities to tackle first
Create problem statements: Use
```
problem-statement.md
```
to frame top opportunities
Build experiments: Use
```
opportunity-solution-tree.md
```
to design solutions and POCs

Ready to start addressing opportunities? Let me know if you'd like to refine the map or dive into a specific pain point.

---

Examples

示例

Example 1: Good Journey Map (SaaS Onboarding)

示例1：优质旅程地图（SaaS入职）

Q1 Response: "Primary persona — Small business owner"

Q2 Response: "First-time use — New user onboarding, from discovery to activation"

Q3 - Phases Generated:

Discover → Evaluate → Try → Activate → Use → Expand

Q4 - Phase 3 (Try) Mapped:

Actions:
- Signs up via Google SSO
- Receives welcome email
- Logs in, sees empty dashboard
- Clicks "Help" button, watches 5-min tutorial
- Attempts to create first project, gets stuck on form

Thoughts:
- "This looks easy enough"
- "Wait, what's a 'workspace' vs. 'project'?"
- "Do I need to fill out all these fields?"

Emotions:
- Excited initially 😊
- Confused by terminology 😕
- Frustrated by unclear form 😞

Pain Points:
- No guided onboarding checklist
- Terminology not explained (workspace vs. project)
- Form has too many required fields upfront

Q5 - Opportunities Identified:

Add onboarding checklist (HIGH — affects activation)
Simplify terminology (MEDIUM — affects understanding)
Reduce required form fields (MEDIUM — affects completion rate)

Why this works:

Emotions + actions reveal pain points clearly
Opportunities tied to specific phases
Evidence from research (drop-off data, support tickets)

问题1回复： “核心Persona — 小企业主”

问题2回复： “首次使用 — 新用户入职，从发现到激活”

问题3 - 生成的阶段：

Discover → Evaluate → Try → Activate → Use → Expand

问题4 - 阶段3（Try）映射：

Actions:
- Signs up via Google SSO
- Receives welcome email
- Logs in, sees empty dashboard
- Clicks "Help" button, watches 5-min tutorial
- Attempts to create first project, gets stuck on form

Thoughts:
- "This looks easy enough"
- "Wait, what's a 'workspace' vs. 'project'?"
- "Do I need to fill out all these fields?"

Emotions:
- Excited initially 😊
- Confused by terminology 😕
- Frustrated by unclear form 😞

Pain Points:
- No guided onboarding checklist
- Terminology not explained (workspace vs. project)
- Form has too many required fields upfront

问题5 - 识别的机会：

添加入职清单（高影响 — 影响激活率）
简化术语（中影响 — 影响理解）
减少表单必填字段（中影响 — 影响完成率）

为何有效：

情绪+行为清晰揭示痛点
机会与特定阶段绑定
有研究证据支持（流失数据、支持工单）

Example 2: Bad Journey Map (Too Generic)

示例2：劣质旅程地图（过于笼统）

Phase: "Use Product"

Actions:

Uses product
Does tasks

Thoughts:

"This is good"

Emotions:

Happy 😊

Why this fails:

No specificity (what tasks? which features?)
No pain points identified (everything is "good")
Can't extract actionable opportunities

Fix:

Get specific: "User creates invoice → sends to client → tracks payment status"
Include real customer quotes: "I wish I could bulk-send invoices"
Show emotional highs AND lows (not just happy)

阶段：“使用产品”

行为：

使用产品
完成任务

想法：

“这很不错”

情绪：

开心 😊

为何失效：

缺乏具体性（什么任务？哪些功能？）
未识别痛点（一切都“很好”）
无法提取可落地的机会

修复方案：

具体化：“用户创建发票 → 发送给客户 → 跟踪付款状态”
加入真实客户语录：“我希望能批量发送发票”
展示情绪的高峰和低谷（不只是开心）

Common Pitfalls

常见陷阱

Pitfall 1: Mapping Internal Process, Not Customer Experience

陷阱1：映射内部流程，而非客户体验

Symptom: Journey phases = "Lead generated → Qualified → Demo scheduled → Deal closed"

Consequence: Focuses on sales process, not customer perspective

Fix: Map from customer POV: "Discovers problem → Researches solutions → Tries product → Adopts"

症状： 旅程阶段 = “线索生成 → 合格 → 演示预约 → 交易完成”

后果： 聚焦销售流程，而非客户视角

修复： 从客户视角映射：“发现问题 → 研究解决方案 → 试用产品 → 采用”

Pitfall 2: No Emotions or Pain Points

陷阱2：无情绪或痛点

Symptom: Journey map lists actions only, no thoughts/emotions

Consequence: Misses the point—can't identify where experience breaks down

Fix: Add customer quotes, emotional states (frustrated, delighted, confused)

症状： 旅程地图仅列出行为，无想法/情绪

后果： 偏离核心目的——无法识别体验失效的环节

修复： 添加客户语录、情绪状态（沮丧、愉悦、困惑）

Pitfall 3: Too Many Personas in One Map

陷阱3：单张地图包含过多Persona

Symptom: Trying to map "all users" in a single journey

Consequence: Loses focus, becomes generic

Fix: One map per persona. If multiple personas, create separate maps.

症状： 试图在一张地图中映射“所有用户”

后果： 失去焦点，变得笼统

修复： 一个Persona对应一张地图。若有多个Persona，创建单独的地图。

Pitfall 4: Opportunities Aren't Prioritized

陷阱4：机会未排序

Symptom: List 20 opportunities with no ranking

Consequence: Team paralyzed, doesn't know where to start

Fix: Rank by impact (HIGH/MEDIUM/LOW) based on evidence and emotional intensity

症状： 列出20个机会但未排名

后果： 团队陷入瘫痪，不知从何处着手

修复： 根据证据和情绪强度按影响排序（高/中/低）

Pitfall 5: Map Created in Isolation

陷阱5：孤立创建地图

Symptom: PM creates journey map alone, doesn't involve team

Consequence: No shared mental model, map doesn't drive decisions

Fix: Facilitate workshop with cross-functional team (PM, design, engineering, support)

症状： 产品经理独自创建旅程地图，未让团队参与

后果： 无统一认知模型，地图无法驱动决策

修复： 组织跨职能团队工作坊（产品经理、设计师、工程师、支持人员）

References

参考资料

Related Skills

External Frameworks

外部框架

Nielsen Norman Group, "Journey Mapping 101" (2016) — Definitive guide to journey mapping
Adaptive Path, "Guide to Experience Mapping" (2013) — Experience vs. journey maps

Nielsen Norman Group, "Journey Mapping 101" (2016) — 旅程映射的权威指南
Adaptive Path, "Guide to Experience Mapping" (2013) — 体验地图 vs 旅程地图

Dean's Work

Dean的工作

[If Dean has journey mapping resources, link here]

Skill type: Interactive Suggested filename:

customer-journey-mapping-workshop.md

Suggested placement:

/skills/interactive/

Dependencies: Uses

customer-journey-map.md

proto-persona.md

problem-statement.md

jobs-to-be-done.md

[若Dean有旅程映射资源，在此处链接]

Skill type: Interactive Suggested filename:

customer-journey-mapping-workshop.md

Suggested placement:

/skills/interactive/

Dependencies: Uses

customer-journey-map.md

proto-persona.md

problem-statement.md

jobs-to-be-done.md