用户故事地图（User Story Mapping）完整指南：Jeff Patton框架、步骤与实战应用

user-story-mapping by deanpeters/product-manager-skills

563 周安装量

2,800 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/deanpeters/product-manager-skills --skill user-story-mapping

方法论用户体验产品管理

🇨🇳中文介绍

目的

通过创建层次化地图来可视化用户旅程，将高级活动分解为步骤和任务，并按照从左到右的叙事流进行组织。使用此方法来建立产品、设计和工程团队之间的共同理解，基于用户工作流确定功能优先级，并识别用户体验中的差距或机会。

这不是待办事项清单——它是一种战略产物，展示了用户_如何_实现其目标，从而指导_要构建什么_。

核心概念

Jeff Patton 故事地图框架

由 Jeff Patton 发明，故事地图将工作组织成二维结构：

水平轴（从左到右）： 随时间推移的用户旅程

主干： 用户执行的高级活动
步骤： 每个活动中的具体行动
任务： 完成每个步骤所需的详细工作

垂直轴（从上到下）： 优先级和发布

顶部行： 基本任务（MVP / 发布 1）
底部行： 锦上添花的任务（未来发布）

故事地图结构

Segment → Persona → Narrative (User's goal)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Activity 1] → [Activity 2] → [Activity 3] → [Activity 4] → [Activity 5]
     ↓              ↓              ↓              ↓              ↓
  [Step 1.1]     [Step 2.1]     [Step 3.1]     [Step 4.1]     [Step 5.1]
  [Step 1.2]     [Step 2.2]     [Step 3.2]     [Step 4.2]     [Step 5.2]
  [Step 1.3]     [Step 2.3]     [Step 3.3]     [Step 4.3]     [Step 5.3]
     ↓              ↓              ↓              ↓              ↓
  [Task 1.1.1]   [Task 2.1.1]   [Task 3.1.1]   [Task 4.1.1]   [Task 5.1.1]
  [Task 1.1.2]   [Task 2.1.2]   [Task 3.1.2]   [Task 4.1.2]   [Task 5.1.2]
  [Task 1.1.3]   [Task 2.1.3]   [Task 3.1.3]   [Task 4.1.3]   [Task 5.1.3]
  ...            ...            ...            ...            ...

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

反模式（这不是什么）

不是甘特图： 这不是项目管理——是用户旅程可视化
不是功能列表： 活动不是功能——它们是用户行为
不是静态的： 故事地图随着你对用户的了解而演变

启动新产品或主要功能时
协调利益相关者对用户工作流的理解时
基于用户需求确定待办事项优先级时
区分 MVP 与未来发布时
向新团队成员介绍产品愿景时

对于琐碎的功能（不要映射你已经理解的内容）
当用户工作流不断变化时（地图用于稳定工作流）
作为用户故事的替代品（地图为故事提供信息，而非取代它们）

步骤 1：定义上下文

使用 template.md 获取完整的填充结构。

### Segment:
- [指定目标细分市场，例如："使用 DIY 会计软件的小企业主"]

具体： 不是"用户"，而是"企业 IT 管理员"或"自由设计师"

提供此细分市场中用户画像的详细信息（参考 skills/proto-persona/SKILL.md）。

### Persona:
- [描述用户画像：人口统计、行为、痛点、目标]

"Sarah，35 岁的自由平面设计师，同时管理 5-10 个客户项目，在开具发票和付款跟踪方面遇到困难，希望减少花在行政事务上的时间，增加设计时间"

步骤 2：定义叙事

用户试图完成什么？将其框定为"待完成工作"陈述（参考 skills/jobs-to-be-done/SKILL.md）。

### Narrative:
- [用户画像目标的简明叙述，例如："完成一个客户项目，从启动到最终付款"]

关注结果： 不是"使用产品"，而是"按时交付客户项目并获得报酬"
一句话： 如果超过一句话，范围可能太广

步骤 3：识别活动（主干）

列出用户画像为实现叙事而参与的 3-5 个高级活动。这些构成了地图的主干。

### Activities:
1. [Activity 1, e.g., "Negotiate project scope and pricing"]
2. [Activity 2, e.g., "Execute design work"]
3. [Activity 3, e.g., "Deliver final assets to client"]
4. [Activity 4, e.g., "Send invoice and receive payment"]
5. [Activity 5, optional]

顺序性： 活动按顺序发生（从左到右）
用户行动： 描述用户_做什么_，而不是产品_提供什么_
3-5 个活动： 太少 = 过于简化，太多 = 令人不知所措

步骤 4：将活动分解为步骤

为每个活动列出 3-5 个详细说明活动如何执行的步骤。

### Steps:

**For Activity 1: [Activity Name]**
- Step 1: [Detail step 1, e.g., "Review client brief"]
- Step 2: [Detail step 2, e.g., "Draft project proposal"]
- Step 3: [Detail step 3, e.g., "Negotiate timeline and budget"]
- Step 4: [Optional step 4]
- Step 5: [Optional step 5]

**For Activity 2: [Activity Name]**
- Step 1: [Detail step 1]
- Step 2: [Detail step 2]
...

可操作： 每个步骤都是用户做的某件事
可观察： 你可以观察某人执行此步骤
逻辑顺序： 步骤遵循自然顺序

步骤 5：将步骤分解为任务

为每个步骤列出必须完成的 5-7 个任务。

### Tasks:

**For Activity 1, Step 1: [Step Name]**
- Task 1: [Detail task 1, e.g., "Read client brief document"]
- Task 2: [Detail task 2, e.g., "Identify key deliverables"]
- Task 3: [Detail task 3, e.g., "Note budget constraints"]
- Task 4: [Detail task 4, e.g., "Clarify timeline expectations"]
- Task 5: [Detail task 5, e.g., "List open questions for client"]
- Task 6: [Optional task 6]
- Task 7: [Optional task 7]

**For Activity 1, Step 2: [Step Name]**
- Task 1: [Detail task 1]
...

粒度细： 任务是具体的小行动
面向用户或幕后： 两者都包括（例如："发送邮件"和"接收确认"）
可确定优先级： 你将垂直确定任务优先级（顶部 = 基本，底部 = 锦上添花）

步骤 6：垂直确定优先级

按优先级从上到下排列任务：

顶部行： MVP / 发布 1（必须拥有）
中间行： 发布 2（重要但不关键）
底部行： 未来 / 锦上添花

绘制水平的"发布线"来划分范围。

步骤 7：识别差距和机会

审查地图并提出问题：

是否有缺失的步骤或任务？
是否有我们未解决的痛点？
是否有取悦用户的机会？
所有活动是否逻辑流畅？

查看 examples/sample.md 获取完整的故事地图示例。

陷阱 1：活动是功能，而非用户行为

症状： "活动 1：使用仪表板。活动 2：生成报告。"

后果： 你映射的是产品，而不是用户旅程。

解决方法： 重新定义为用户行动："活动 1：监控项目进度。活动 2：为利益相关者总结工作。"

陷阱 2：活动过多

症状： 主干上有 10 个以上的活动

后果： 地图变得令人不知所措且失去焦点。

解决方法： 合并。如果你有 10 个活动，你可能混淆了活动和步骤。目标是 3-5 个高级活动。

陷阱 3：任务过于模糊

症状： "任务 1：做这件事"

后果： 无法确定模糊任务的优先级或估算。

解决方法： 要具体："任务 1：在'账单接收人'字段中输入客户电子邮件地址。"

陷阱 4：忽略垂直优先级

症状： 所有任务处于同一级别——未定义 MVP 与未来发布

后果： 不清楚首先要构建什么。

解决方法： 明确确定优先级。绘制发布线。强制对 MVP 内容做出艰难选择。

陷阱 5：孤立地映射

症状： 产品经理独自创建地图，然后向团队展示

后果： 没有共同所有权或理解。

解决方法： 协作映射。与产品、设计和工程团队一起举办故事地图研讨会。

skills/proto-persona/SKILL.md — 定义故事地图的用户画像
skills/jobs-to-be-done/SKILL.md — 为叙事和活动提供信息
skills/user-story/SKILL.md — 地图中的任务变为用户故事
skills/problem-statement/SKILL.md — 问题陈述框定叙事

Jeff Patton, User Story Mapping (2014) — 故事地图技术的起源
Teresa Torres, Continuous Discovery Habits (2021) — 机会解决方案树（与故事地图互补）

User Story Mapping Prompt (adapted from Jeff Patton's methodology)

改编自 https://github.com/deanpeters/product-manager-prompts 仓库中的 prompts/user-story-mapping.md。

Skill type: Component Suggested filename: user-story-mapping.md Suggested placement: /skills/components/ Dependencies: References skills/proto-persona/SKILL.md, skills/jobs-to-be-done/SKILL.md, skills/user-story/SKILL.md, skills/problem-statement/SKILL.md

🇺🇸English

Purpose

Visualize the user journey by creating a hierarchical map that breaks down high-level activities into steps and tasks, organized left-to-right as a narrative flow. Use this to build shared understanding across product, design, and engineering, prioritize features based on user workflows, and identify gaps or opportunities in the user experience.

This is not a backlog—it's a strategic artifact that shows how users accomplish their goals, which then informs what to build.

Key Concepts

The Jeff Patton Story Mapping Framework

Invented by Jeff Patton, story mapping organizes work into a 2D structure:

Horizontal axis (left-to-right): User journey over time

Backbone: High-level activities the user performs
Steps: Specific actions within each activity
Tasks: Detailed work required to complete each step

Vertical axis (top-to-bottom): Priority and releases

Top rows: Essential tasks (MVP / Release 1)
Lower rows: Nice-to-have tasks (Future releases)

Story Map Structure

Segment → Persona → Narrative (User's goal)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[Activity 1] → [Activity 2] → [Activity 3] → [Activity 4] → [Activity 5]
     ↓              ↓              ↓              ↓              ↓
  [Step 1.1]     [Step 2.1]     [Step 3.1]     [Step 4.1]     [Step 5.1]
  [Step 1.2]     [Step 2.2]     [Step 3.2]     [Step 4.2]     [Step 5.2]
  [Step 1.3]     [Step 2.3]     [Step 3.3]     [Step 4.3]     [Step 5.3]
     ↓              ↓              ↓              ↓              ↓
  [Task 1.1.1]   [Task 2.1.1]   [Task 3.1.1]   [Task 4.1.1]   [Task 5.1.1]
  [Task 1.1.2]   [Task 2.1.2]   [Task 3.1.2]   [Task 4.1.2]   [Task 5.1.2]
  [Task 1.1.3]   [Task 2.1.3]   [Task 3.1.3]   [Task 4.1.3]   [Task 5.1.3]
  ...            ...            ...            ...            ...

Why This Works

User-centric: Organizes work around user goals, not engineering modules
Shared understanding: Product, design, engineering all see the same journey
Prioritization clarity: Top tasks = MVP, lower tasks = future iterations
Gap identification: Missing steps or tasks become obvious
Release planning: Draw horizontal "release lines" to define scope

Anti-Patterns (What This Is NOT)

Not a Gantt chart: This isn't project management—it's user journey visualization
Not a feature list: Activities aren't features—they're user behaviors
Not static: Story maps evolve as you learn more about users

When to Use This

Kicking off a new product or major feature
Aligning stakeholders on user workflow
Prioritizing backlog based on user needs
Identifying MVP vs. future releases
Onboarding new team members to the product vision

When NOT to Use This

For trivial features (don't map what you already understand)
When user workflows are constantly changing (map stabilizes workflows)
As a replacement for user stories (the map informs stories, doesn't replace them)

Application

Step 1: Define the Context

Use template.md for the full fill-in structure.

Segment

Who are you building for?

### Segment:
- [Specify the target segment, e.g., "Small business owners using DIY accounting software"]

Quality checks:

Specific: Not "users" but "enterprise IT admins" or "freelance designers"

Persona

Provide details about the persona within this segment (reference skills/proto-persona/SKILL.md).

### Persona:
- [Describe the persona: demographics, behaviors, pains, goals]

Example:

"Sarah, 35-year-old freelance graphic designer, manages 5-10 client projects at once, struggles with invoicing and payment tracking, wants to spend less time on admin and more time designing"

Step 2: Define the Narrative

What is the user trying to accomplish? Frame this as a Jobs-to-be-Done statement (reference skills/jobs-to-be-done/SKILL.md).

### Narrative:
- [Concise narrative of the persona's objective, e.g., "Complete a client project from kickoff to final payment"]

Quality checks:

Outcome-focused: Not "use the product" but "deliver a client project on time and get paid"
One sentence: If it takes more than one sentence, the scope may be too broad

Step 3: Identify Activities (Backbone)

List 3-5 high-level activities the persona engages in to fulfill the narrative. These form the backbone of your map.

### Activities:
1. [Activity 1, e.g., "Negotiate project scope and pricing"]
2. [Activity 2, e.g., "Execute design work"]
3. [Activity 3, e.g., "Deliver final assets to client"]
4. [Activity 4, e.g., "Send invoice and receive payment"]
5. [Activity 5, optional]

Quality checks:

Sequential: Activities happen in order (left-to-right)
User actions: Describe what the user does , not what the product provides
3-5 activities: Too few = oversimplified, too many = overwhelming

Step 4: Break Activities into Steps

For each activity, list 3-5 steps that detail how the activity is carried out.

### Steps:

**For Activity 1: [Activity Name]**
- Step 1: [Detail step 1, e.g., "Review client brief"]
- Step 2: [Detail step 2, e.g., "Draft project proposal"]
- Step 3: [Detail step 3, e.g., "Negotiate timeline and budget"]
- Step 4: [Optional step 4]
- Step 5: [Optional step 5]

**For Activity 2: [Activity Name]**
- Step 1: [Detail step 1]
- Step 2: [Detail step 2]
...

Quality checks:

Actionable: Each step is something the user does
Observable: You could watch someone perform this step
Logical sequence: Steps follow a natural order

Step 5: Break Steps into Tasks

For each step, list 5-7 tasks that must be completed.

### Tasks:

**For Activity 1, Step 1: [Step Name]**
- Task 1: [Detail task 1, e.g., "Read client brief document"]
- Task 2: [Detail task 2, e.g., "Identify key deliverables"]
- Task 3: [Detail task 3, e.g., "Note budget constraints"]
- Task 4: [Detail task 4, e.g., "Clarify timeline expectations"]
- Task 5: [Detail task 5, e.g., "List open questions for client"]
- Task 6: [Optional task 6]
- Task 7: [Optional task 7]

**For Activity 1, Step 2: [Step Name]**
- Task 1: [Detail task 1]
...

Quality checks:

Granular: Tasks are small, specific actions
User-facing or behind-the-scenes: Include both (e.g., "Send email" and "Receive confirmation")
Prioritizable: You'll prioritize tasks vertically (top = essential, bottom = nice-to-have)

Step 6: Prioritize Vertically

Arrange tasks top-to-bottom by priority:

Top rows: MVP / Release 1 (must-have)
Middle rows: Release 2 (important but not critical)
Bottom rows: Future / Nice-to-have

Draw horizontal "release lines" to demarcate scope.

Step 7: Identify Gaps and Opportunities

Review the map and ask:

Are there missing steps or tasks?
Are there pain points we're not addressing?
Are there opportunities to delight users?
Do all activities flow logically?

Examples

See examples/sample.md for a full story map example.

Common Pitfalls

Pitfall 1: Activities Are Features, Not User Behaviors

Symptom: "Activity 1: Use the dashboard. Activity 2: Generate reports."

Consequence: You've mapped the product, not the user journey.

Fix: Reframe as user actions: "Activity 1: Monitor project progress. Activity 2: Summarize work for stakeholders."

Pitfall 2: Too Many Activities

Symptom: 10+ activities across the backbone

Consequence: Map becomes overwhelming and loses focus.

Fix: Consolidate. If you have 10 activities, you're likely mixing activities with steps. Aim for 3-5 high-level activities.

Pitfall 3: Tasks Are Too Vague

Symptom: "Task 1: Do the thing"

Consequence: Can't prioritize or estimate vague tasks.

Fix: Be specific: "Task 1: Enter client email address in the 'Bill To' field."

Pitfall 4: Ignoring Vertical Prioritization

Symptom: All tasks at the same level—no MVP vs. future releases defined

Consequence: No clarity on what to build first.

Fix: Explicitly prioritize. Draw release lines. Force hard choices about what's MVP.

Pitfall 5: Mapping in Isolation

Symptom: PM creates the map alone, then presents it to the team

Consequence: No shared ownership or understanding.

Fix: Map collaboratively. Run a story mapping workshop with product, design, and engineering.

References

Related Skills

skills/proto-persona/SKILL.md — Defines the persona for the story map
skills/jobs-to-be-done/SKILL.md — Informs the narrative and activities
skills/user-story/SKILL.md — Tasks from the map become user stories
skills/problem-statement/SKILL.md — Problem statement frames the narrative

External Frameworks

Jeff Patton, User Story Mapping (2014) — Origin of the story mapping technique
Teresa Torres, Continuous Discovery Habits (2021) — Opportunity solution trees (complementary to story maps)

Dean's Work

User Story Mapping Prompt (adapted from Jeff Patton's methodology)

Provenance

Adapted from prompts/user-story-mapping.md in the https://github.com/deanpeters/product-manager-prompts repo.

Weekly Installs

255

Repository

deanpeters/prod…r-skills

GitHub Stars

1.5K

First Seen

Feb 12, 2026

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

codex226

opencode223

gemini-cli219

github-copilot218

cursor217

kimi-cli215

推荐与联盟计划设计优化指南：病毒式增长营销策略、客户推荐计划、联盟营销

26,100 周安装

用户故事地图（User Story Mapping）完整指南：Jeff Patton框架、步骤与实战应用

🇨🇳中文介绍

目的

核心概念

Jeff Patton 故事地图框架

故事地图结构

相关 Skills

为何有效

反模式（这不是什么）

何时使用

何时不使用

应用

步骤 1：定义上下文

细分市场

用户画像

步骤 2：定义叙事

步骤 3：识别活动（主干）

步骤 4：将活动分解为步骤

步骤 5：将步骤分解为任务

步骤 6：垂直确定优先级

步骤 7：识别差距和机会

示例

常见陷阱

陷阱 1：活动是功能，而非用户行为

陷阱 2：活动过多

陷阱 3：任务过于模糊

陷阱 4：忽略垂直优先级

陷阱 5：孤立地映射

参考资料

相关技能

外部框架

Dean's Work

来源

🇺🇸English

Purpose

Key Concepts

The Jeff Patton Story Mapping Framework

Story Map Structure

Why This Works

Anti-Patterns (What This Is NOT)

When to Use This

When NOT to Use This

Application

Step 1: Define the Context

Segment

Persona

Step 2: Define the Narrative

Step 3: Identify Activities (Backbone)

Step 4: Break Activities into Steps

Step 5: Break Steps into Tasks

Step 6: Prioritize Vertically

Step 7: Identify Gaps and Opportunities

Examples

Common Pitfalls

Pitfall 1: Activities Are Features, Not User Behaviors

Pitfall 2: Too Many Activities

Pitfall 3: Tasks Are Too Vague

Pitfall 4: Ignoring Vertical Prioritization

Pitfall 5: Mapping in Isolation

References

Related Skills

External Frameworks

Dean's Work

Provenance

最新 Skills