Back to Details

user-story-mapping-workshop

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Purpose

目的

Guide product managers through creating a user story map by asking adaptive questions about the system, users, workflow, and priorities—then generating a two-dimensional map with backbone (activities), user tasks, and release slices. Use this to move from flat backlogs to visual story maps that communicate the big picture, identify missing functionality, and enable meaningful release planning—avoiding "context-free mulch" where stories lose connection to the overall system narrative.
This is not a backlog generator—it's a visual communication framework that organizes work by user workflow (horizontal) and priority (vertical).
通过询问关于系统、用户、工作流和优先级的适应性问题，引导产品经理创建User Story Map，随后生成包含Backbone（活动）、User Tasks和发布切片的二维地图。使用此工具可从扁平化待办事项转变为可视化故事地图，从而传达全局视角、识别缺失功能，并支持有意义的发布规划——避免出现“无上下文的杂乱内容”，即故事与整体系统叙事失去关联。
这不是待办事项生成器——而是一个可视化沟通框架，按用户工作流（横向）和优先级（纵向）组织工作内容。

Key Concepts

核心概念

What is a User Story Map?

什么是User Story Map？

A story map (Jeff Patton) organizes user stories in two dimensions:
Horizontal axis (left to right): Activities arranged in narrative/workflow order—the sequence you'd use explaining the system to someone
Vertical axis (top to bottom): Priority within each activity, with the most essential tasks at the top
Structure:
Backbone (Activities across top)
↓
User Tasks (descending vertically by priority)
↓
Details/Acceptance Criteria (at the bottom)
Story Map（由Jeff Patton提出）从两个维度组织用户故事：
横轴（从左到右）： 按叙事/工作流顺序排列的活动——即向他人解释系统时会采用的顺序
纵轴（从上到下）： 每个活动内的优先级，最核心的任务位于顶部
结构：
Backbone (Activities across top)
↓
User Tasks (descending vertically by priority)
↓
Details/Acceptance Criteria (at the bottom)

Key Principles

核心原则

The Backbone: Essential activities form the system's structural core—these aren't prioritized against each other; they're the narrative flow.
Walking Skeleton: The highest-priority tasks across all activities form the minimal viable product—the smallest end-to-end functionality.
Ribs: Supporting tasks descend vertically under each activity, indicating priority through placement.
Left-to-Right, Top-to-Bottom Build Strategy: Build incrementally across all major features rather than completing one feature fully before starting another.
Backbone： 核心活动构成系统的结构核心——它们之间不进行优先级排序，而是代表叙事流程。
Walking Skeleton： 所有活动中优先级最高的任务构成最小可行产品（MVP）——即最小的端到端功能集合。
Ribs： 支撑任务在每个活动下方垂直排列，通过位置体现优先级。
Left-to-Right, Top-to-Bottom Build Strategy： 跨所有主要功能逐步构建，而非在开始另一个功能前完全完成当前功能。

Why This Works

为何此方法有效

  • Visual communication: Story maps remain displayed as information radiators, maintaining focus on the big picture
  • Narrative structure: Organizes by user workflow, not technical architecture
  • Release planning: Horizontal slices reveal MVPs and incremental releases
  • Gap identification: Reveals missing functionality that flat backlogs obscure
  • 可视化沟通： 故事地图可作为信息辐射源持续展示，保持对全局视角的聚焦
  • 叙事结构： 按用户工作流而非技术架构组织内容
  • 发布规划： 横向切片可清晰呈现MVP和增量发布内容
  • 缺口识别： 揭示扁平化待办事项中被隐藏的缺失功能

Anti-Patterns (What This Is NOT)

反模式（此方法不适用的场景）

  • Not a Gantt chart: Story maps show priority, not time estimates
  • Not technical architecture: Maps follow user workflow, not system layers (UI → API → DB)
  • Not a project plan: It's a discovery and communication tool, not a schedule
  • 不是甘特图： 故事地图展示优先级，而非时间估算
  • 不是技术架构图： 地图遵循用户工作流，而非系统层级（UI → API → DB）
  • 不是项目计划： 它是一个探索和沟通工具，而非进度计划表

When to Use This

适用场景

  • Starting a new product or major feature
  • Reframing an existing backlog (moving from flat list to visual map)
  • Aligning stakeholders on scope and priorities
  • Planning MVP or incremental releases
  • 启动新产品或重大功能
  • 重构现有待办事项（从扁平化列表转变为可视化地图）
  • 对齐利益相关者的范围和优先级认知
  • 规划MVP或增量发布

When NOT to Use This

不适用场景

  • Single-feature projects (story map overkill)
  • When backlog is already well-understood and prioritized
  • For technical refactoring work (no user workflow to map)
  • 单一功能项目（使用故事地图属于过度设计）
  • 待办事项已被充分理解并完成优先级排序时
  • 技术重构工作（无用户工作流可映射）

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
作为此技能的默认交互协议。
它定义了：
  • 会话提醒 + 进入模式（引导式、上下文转储、最佳猜测）
  • 采用通俗易懂提示的单轮提问模式
  • 进度标签（例如，Context Qx/8 和 Scoring Qx/5）
  • 中断处理和暂停/恢复行为
  • 决策点处的编号建议
  • 常规问题的快速选择编号响应选项（必要时包含
    Other (specify)
    ）
此文件定义了特定领域的评估内容。若存在冲突，以本文件的领域逻辑为准。

Application

应用

This interactive skill asks up to 5 adaptive questions, offering 3-4 enumerated options at each step.
Use 
template.md
for the facilitation agenda and outputs checklist.
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个枚举选项。
使用
template.md
作为工作坊议程和输出检查清单。
交互模式：当你需要分步流程、决策点处的编号建议以及常规问题的快速选择选项时，与
skills/workshop-facilitation/SKILL.md
配合使用。若用户要求单次输出，则跳过多轮引导流程。

Step 0: Gather Context (Before Questions)

步骤0：收集上下文（提问前）

Agent suggests:
Before we create your story map, let's gather context:
Product/Feature Context:
  • What system or feature are you mapping?
  • Product concept, PRD draft, or existing backlog
  • Website copy, positioning materials, or user flows
  • Existing user stories (if transitioning from flat backlog)
User Context:
  • Target personas or user segments
  • User research, interviews, or journey maps
  • Jobs-to-be-done or problem statements
You can paste this content directly, or describe the system briefly.
Agent建议：
在创建你的故事地图之前，我们先收集上下文信息：
产品/功能上下文：
  • 你要映射的是哪个系统或功能？
  • 产品概念、PRD草稿或现有待办事项
  • 网站文案、定位材料或用户流
  • 现有用户故事（若从扁平化待办事项转型）
用户上下文：
  • 目标用户角色或用户细分
  • 用户研究、访谈或用户旅程图
  • 待完成工作（Jobs-to-be-done）或问题陈述
你可以直接粘贴这些内容，或简要描述系统。

Question 1: Define Scope

问题1：定义范围

Agent asks: "What are you mapping? (What's the scope?)"
Offer 4 enumerated options:
  1. Entire product — "Full end-to-end system from discovery to completion" (Common for new products or full rewrites)
  2. Major feature area — "Specific workflow within a larger product (e.g., 'onboarding,' 'checkout,' 'reporting')" (Common for feature launches)
  3. User journey — "Specific user goal or job-to-be-done (e.g., 'hire a contractor,' 'file taxes')" (Common for JTBD-driven mapping)
  4. Redesign/refactor — "Existing product/feature being rebuilt or simplified" (Common for legacy system modernization)
Or describe your specific scope.
User response: [Selection or custom]
Agent提问： "你要映射的内容是什么？（范围是什么？）"
提供4个枚举选项：
  1. 整个产品 — "从发现到完成的完整端到端系统"（适用于新产品或全面重写）
  2. 主要功能领域 — "大型产品中的特定工作流（例如：'注册流程'、'结账流程'、'报表功能'）"（适用于功能上线）
  3. 用户旅程 — "特定用户目标或待完成工作（例如：'雇佣承包商'、'报税'）"（适用于基于JTBD的映射）
  4. 重新设计/重构 — "正在重建或简化的现有产品/功能"（适用于遗留系统现代化）
或描述你的特定范围。
用户回复： [选择或自定义内容]

Question 2: Identify Users/Personas

问题2：识别用户/角色

Agent asks: "Who are the primary users for this map? (List personas or user segments.)"
Offer 4 enumerated options:
  1. Single persona — "One primary user type (e.g., 'small business owner')" (Simplifies mapping, good for MVP)
  2. Multiple personas, shared workflow — "Different user types, same core activities (e.g., 'buyer' and 'seller' both browse listings)" (Common for marketplaces)
  3. Multiple personas, different workflows — "Different user types with distinct workflows (e.g., 'admin' vs. 'end user')" (Requires separate maps or swim lanes)
  4. Roles within organization — "Different job functions (e.g., 'PM,' 'designer,' 'engineer')" (Common for internal tools)
Or describe your users.
Adaptation: Use personas from context provided in Step 0 (proto-personas, JTBD, etc.)
User response: [Selection or custom]
Agent提问： "此地图的主要用户是谁？（列出用户角色或用户细分。）"
提供4个枚举选项：
  1. 单一角色 — "一种主要用户类型（例如：'小企业主'）"（简化映射，适合MVP）
  2. 多角色，共享工作流 — "不同用户类型，拥有相同核心活动（例如：'买家'和'卖家'均可浏览商品列表）"（适用于平台类产品）
  3. 多角色，不同工作流 — "不同用户类型拥有不同工作流（例如：'管理员' vs '终端用户'）"（需要单独地图或泳道）
  4. 组织内角色 — "不同职能岗位（例如：'PM'、'设计师'、'工程师'）"（适用于内部工具）
或描述你的用户。
适配： 使用步骤0中提供的上下文里的用户角色（原型角色、JTBD等）
用户回复： [选择或自定义内容]

Question 3: Generate Backbone (Activities)

问题3：生成Backbone（活动）

Agent says: "Let's build the backbone—the narrative flow of activities users perform to accomplish their goal."
Agent generates 5-8 activities based on scope (Q1) and users (Q2), arranged left-to-right in workflow order.
Example (if Scope = "E-commerce checkout"):
Backbone Activities (left to right):

1. Browse Products
2. Add to Cart
3. Review Cart
4. Enter Shipping Info
5. Enter Payment Info
6. Confirm Order
7. Receive Confirmation
Agent asks: "Does this backbone capture the full workflow? Should we add, remove, or reorder activities?"
User response: [Approve, modify, or add custom activities]
Agent说明： "让我们构建Backbone——即用户为实现目标而执行的活动叙事流程。"
Agent基于范围（问题1）和用户（问题2）生成5-8个活动，按工作流顺序从左到右排列。
示例（若范围 = "电商结账流程"）：
Backbone Activities (left to right):

1. Browse Products
2. Add to Cart
3. Review Cart
4. Enter Shipping Info
5. Enter Payment Info
6. Confirm Order
7. Receive Confirmation
Agent提问： "此Backbone是否覆盖了完整工作流？我们是否需要添加、删除或重新排序活动？"
用户回复： [批准、修改或添加自定义活动]

Question 4: Generate User Tasks (Under Each Activity)

问题4：生成User Tasks（每个活动下）

Agent says: "Now let's add user tasks under each activity, organized by priority (top = must-have, bottom = nice-to-have)."
Agent generates 3-5 user tasks per activity, arranged vertically by priority.
Example (for Activity 2: "Add to Cart"):
Add to Cart (Activity)
├─ Add single item to cart (must-have, walking skeleton)
├─ Adjust quantity (must-have)
├─ Add multiple items at once (should-have)
├─ Save item for later (nice-to-have)
└─ Add gift wrapping (nice-to-have)
Agent repeats for all backbone activities, showing the full map.
Agent asks: "Does this capture the key tasks? Are priorities correct (top = MVP, bottom = later releases)?"
User response: [Approve, modify, or add custom tasks]
Agent说明： "现在我们在每个活动下添加User Tasks，按优先级排列（顶部 = 必备项，底部 = 锦上添花项）。"
Agent为每个活动生成3-5个User Tasks，按优先级垂直排列。
示例（针对活动2："Add to Cart"）：
Add to Cart (Activity)
├─ Add single item to cart (must-have, walking skeleton)
├─ Adjust quantity (must-have)
├─ Add multiple items at once (should-have)
├─ Save item for later (nice-to-have)
└─ Add gift wrapping (nice-to-have)
Agent为所有Backbone活动重复此操作，展示完整地图。
Agent提问： "此内容是否覆盖了关键任务？优先级是否正确（顶部 = MVP，底部 = 后续发布）？"
用户回复： [批准、修改或添加自定义任务]

Question 5: Identify Release Slices (Walking Skeleton + Increments)

问题5：识别发布切片（Walking Skeleton + 增量内容）

Agent says: "Let's define release slices by drawing horizontal lines across the map."
Agent generates 3 release slices:
Release 1 (Walking Skeleton): Top-priority tasks across all activities—minimal end-to-end functionality
Release 2 (Next Increment): Second-priority tasks that enhance the core workflow
Release 3 (Polish/Expansion): Third-priority tasks (nice-to-haves, edge cases, optimizations)
Example:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Release 1 (Walking Skeleton):
- Browse products (basic list view)
- Add single item to cart
- Review cart (line items + total)
- Enter shipping info (name, address)
- Enter payment info (credit card only)
- Confirm order (basic confirmation)
- Receive email confirmation
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Release 2 (Enhanced):
- Product filtering/search
- Adjust quantity in cart
- Save for later
- Multiple shipping options
- Multiple payment methods
- Order tracking link
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Release 3 (Polish):
- Product recommendations
- Guest checkout
- Gift wrapping
- Promo codes
- Advanced payment options
- Post-purchase surveys
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Agent asks: "Do these release slices make sense? Should we adjust scope or priorities?"
User response: [Approve or modify]
Agent说明： "让我们通过在地图上绘制水平线来定义发布切片。"
Agent生成3个发布切片：
Release 1 (Walking Skeleton)： 所有活动中优先级最高的任务——最小的端到端功能
Release 2 (Next Increment)： 可增强核心工作流的次优先级任务
Release 3 (Polish/Expansion)： 第三优先级任务（锦上添花项、边缘案例、优化项）
示例：
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Release 1 (Walking Skeleton):
- Browse products (basic list view)
- Add single item to cart
- Review cart (line items + total)
- Enter shipping info (name, address)
- Enter payment info (credit card only)
- Confirm order (basic confirmation)
- Receive email confirmation
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Release 2 (Enhanced):
- Product filtering/search
- Adjust quantity in cart
- Save for later
- Multiple shipping options
- Multiple payment methods
- Order tracking link
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Release 3 (Polish):
- Product recommendations
- Guest checkout
- Gift wrapping
- Promo codes
- Advanced payment options
- Post-purchase surveys
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Agent提问： "这些发布切片是否合理？我们是否需要调整范围或优先级？"
用户回复： [批准或修改]

Output: User Story Map

输出：User Story Map

After completing the flow, the agent outputs:
markdown
undefined
完成流程后，Agent输出：
markdown
undefined

User Story Map: [Scope from Q1]

User Story Map: [Scope from Q1]

Users: [From Q2] Date: [Today's date]
Users: [From Q2] Date: [Today's date]

Backbone (Activities)

Backbone (Activities)

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

Full Story Map

Full Story Map

[Activity 1: Name]

[Activity 1: Name]

  • [Task 1.1] — Must-have (Release 1)
  • [Task 1.2] — Should-have (Release 2)
  • [Task 1.3] — Nice-to-have (Release 3)
  • [Task 1.1] — Must-have (Release 1)
  • [Task 1.2] — Should-have (Release 2)
  • [Task 1.3] — Nice-to-have (Release 3)

[Activity 2: Name]

[Activity 2: Name]

  • [Task 2.1] — Must-have (Release 1)
  • [Task 2.2] — Should-have (Release 2)
  • [Task 2.3] — Nice-to-have (Release 3)
[...repeat for all activities...]
  • [Task 2.1] — Must-have (Release 1)
  • [Task 2.2] — Should-have (Release 2)
  • [Task 2.3] — Nice-to-have (Release 3)
[...repeat for all activities...]

Release Slices

Release Slices

Release 1: Walking Skeleton (MVP)

Release 1: Walking Skeleton (MVP)

Goal: Minimal end-to-end functionality
Stories:
  • [Task 1.1] — [Activity 1]
  • [Task 2.1] — [Activity 2]
  • [Task 3.1] — [Activity 3]
  • [Task 4.1] — [Activity 4]
  • [Task 5.1] — [Activity 5]
  • [Task 6.1] — [Activity 6]
Why this is the walking skeleton: Delivers complete workflow with simplest version of each activity.
Goal: Minimal end-to-end functionality
Stories:
  • [Task 1.1] — [Activity 1]
  • [Task 2.1] — [Activity 2]
  • [Task 3.1] — [Activity 3]
  • [Task 4.1] — [Activity 4]
  • [Task 5.1] — [Activity 5]
  • [Task 6.1] — [Activity 6]
Why this is the walking skeleton: Delivers complete workflow with simplest version of each activity.

Release 2: Enhanced Functionality

Release 2: Enhanced Functionality

Goal: Improve core workflow with priority enhancements
Stories:
  • [Task 1.2] — [Activity 1]
  • [Task 2.2] — [Activity 2]
  • [Task 3.2] — [Activity 3] [...]
Goal: Improve core workflow with priority enhancements
Stories:
  • [Task 1.2] — [Activity 1]
  • [Task 2.2] — [Activity 2]
  • [Task 3.2] — [Activity 3] [...]

Release 3: Polish & Expansion

Release 3: Polish & Expansion

Goal: Nice-to-haves, edge cases, optimizations
Stories:
  • [Task 1.3] — [Activity 1]
  • [Task 2.3] — [Activity 2] [...]
Goal: Nice-to-haves, edge cases, optimizations
Stories:
  • [Task 1.3] — [Activity 1]
  • [Task 2.3] — [Activity 2] [...]

Next Steps

Next Steps

  1. Refine stories: Use 
    skills/user-story/SKILL.md
    to write detailed stories with acceptance criteria
  2. Estimate effort: Score stories (story points, t-shirt sizes)
  3. Validate with stakeholders: Walk through map left-to-right, confirm priorities
  4. Display map: Print/post as information radiator for ongoing reference
Ready to write user stories? Let me know if you'd like to refine the map or break down specific stories.

---
  1. Refine stories: Use 
    skills/user-story/SKILL.md
    to write detailed stories with acceptance criteria
  2. Estimate effort: Score stories (story points, t-shirt sizes)
  3. Validate with stakeholders: Walk through map left-to-right, confirm priorities
  4. Display map: Print/post as information radiator for ongoing reference
Ready to write user stories? Let me know if you'd like to refine the map or break down specific stories.

---

Examples

示例

Example 1: Good Story Map (E-commerce Checkout)

示例1：优质故事地图（电商结账流程）

Q1 Response: "Major feature area — E-commerce checkout workflow"
Q2 Response: "Single persona — Online shopper"
Q3 - Backbone Generated:
Browse → Add to Cart → Review Cart → Enter Shipping → Enter Payment → Confirm → Receive Confirmation
Q4 - User Tasks Generated:
Browse Products
├─ View product list (R1)
├─ Search/filter (R2)
└─ Product recommendations (R3)

Add to Cart
├─ Add single item (R1)
├─ Adjust quantity (R2)
└─ Save for later (R3)

Review Cart
├─ View line items + total (R1)
├─ Apply promo code (R2)
└─ Estimate shipping cost (R3)

[...etc...]
Q5 - Release Slices:
  • Release 1: Walking skeleton—basic flow with no extras
  • Release 2: Search, quantity adjustment, promo codes
  • Release 3: Recommendations, guest checkout, gift options
Why this works:
  • Backbone follows user narrative (not technical layers)
  • Walking skeleton delivers end-to-end value
  • Incremental releases add sophistication without breaking core flow
问题1回复： "Major feature area — E-commerce checkout workflow"
问题2回复： "Single persona — Online shopper"
问题3 - 生成的Backbone：
Browse → Add to Cart → Review Cart → Enter Shipping → Enter Payment → Confirm → Receive Confirmation
问题4 - 生成的User Tasks：
Browse Products
├─ View product list (R1)
├─ Search/filter (R2)
└─ Product recommendations (R3)

Add to Cart
├─ Add single item (R1)
├─ Adjust quantity (R2)
└─ Save for later (R3)

Review Cart
├─ View line items + total (R1)
├─ Apply promo code (R2)
└─ Estimate shipping cost (R3)

[...etc...]
问题5 - 发布切片：
  • Release 1： Walking Skeleton——无额外功能的基础流程
  • Release 2： 搜索、数量调整、优惠码
  • Release 3： 推荐功能、访客结账、礼品选项
为何此地图有效：
  • Backbone遵循用户叙事（而非技术层级）
  • Walking Skeleton可交付端到端价值
  • 增量发布可在不破坏核心流程的前提下增加功能复杂度

Example 2: Bad Story Map (Technical Layers)

示例2：劣质故事地图（技术层级）

Backbone (WRONG):
UI Layer → API Layer → Database Layer → Deployment
Why this fails:
  • Not user-centric (users don't care about technical architecture)
  • Can't deliver end-to-end value incrementally
  • Waterfall thinking disguised as story mapping
Fix:
  • Map by user workflow: "Sign Up → Configure Settings → Invite Team → Start Project"
  • Each release delivers full workflow, not a single layer
Backbone（错误示例）：
UI Layer → API Layer → Database Layer → Deployment
为何失败：
  • 非用户中心（用户不关心技术架构）
  • 无法逐步交付端到端价值
  • 是伪装成故事地图的瀑布式思维
修复方案：
  • 按用户工作流映射："Sign Up → Configure Settings → Invite Team → Start Project"
  • 每个发布交付完整工作流，而非单一层级

Common Pitfalls

常见陷阱

Pitfall 1: Flat Backlog in Disguise

陷阱1：伪装的扁平化待办事项

Symptom: Story map is just a vertical list, no horizontal narrative
Consequence: Loses communication benefit; still "context-free mulch"
Fix: Force horizontal structure—activities across top, tasks descending vertically
症状： 故事地图只是一个垂直列表，无横向叙事结构
后果： 失去沟通价值；仍属于“无上下文的杂乱内容”
修复方案： 强制采用横向结构——顶部为活动，任务垂直排列

Pitfall 2: Technical Architecture as Backbone

陷阱2：以技术架构为Backbone

Symptom: Backbone = "Frontend → Backend → Database"
Consequence: Not user-centric, can't deliver value incrementally
Fix: Backbone should follow user workflow, not system layers
症状： Backbone = "Frontend → Backend → Database"
后果： 非用户中心，无法逐步交付价值
修复方案： Backbone应遵循用户工作流，而非系统层级

Pitfall 3: Feature-Complete Waterfall

陷阱3：功能完整的瀑布式开发

Symptom: Release 1 = "Build Activity 1 fully," Release 2 = "Build Activity 2 fully"
Consequence: No end-to-end value until all activities complete
Fix: Walking skeleton = thin slice across ALL activities, incrementally enhanced
症状： Release 1 = "完整构建活动1"，Release 2 = "完整构建活动2"
后果： 所有活动完成前无法交付端到端价值
修复方案： Walking Skeleton = 跨所有活动的精简切片，逐步增强

Pitfall 4: Too Much Detail Too Soon

陷阱4：过早添加过多细节

Symptom: Trying to map every edge case and acceptance criterion upfront
Consequence: Analysis paralysis, lost big picture
Fix: Start with backbone + high-level tasks, refine later
症状： 试图提前映射所有边缘案例和验收标准
后果： 分析瘫痪，失去全局视角
修复方案： 从Backbone + 高层级任务开始，后续再细化

Pitfall 5: Map Hidden in a Tool

陷阱5：地图隐藏在工具中

Symptom: Story map lives in Jira/Miro, never displayed
Consequence: Loses value as information radiator
Fix: Print/post map physically; make it visible to team daily
症状： 故事地图存储在Jira/Miro中，从未展示出来
后果： 失去作为信息辐射源的价值
修复方案： 打印/张贴地图，让团队日常可见

References

参考资料

Related Skills

相关技能

  • skills/user-story-mapping/SKILL.md
    — Component skill with story mapping template
  • skills/user-story/SKILL.md
    — Converts map tasks into detailed user stories
  • skills/proto-persona/SKILL.md
    — Defines users for mapping
  • skills/jobs-to-be-done/SKILL.md
    — Informs backbone activities
  • skills/user-story-mapping/SKILL.md
    — 包含故事地图模板的组件技能
  • skills/user-story/SKILL.md
    — 将地图任务转换为详细用户故事的技能
  • skills/proto-persona/SKILL.md
    — 为映射定义用户的技能
  • skills/jobs-to-be-done/SKILL.md
    — 为Backbone活动提供依据的技能

External Frameworks

外部框架

  • Jeff Patton, User Story Mapping (2014) — Origin of story mapping framework
  • Jeff Patton, "The New User Story Backlog is a Map" (blog) — Explains backbone concept
  • Jeff Patton, User Story Mapping (2014) — 故事地图框架的起源
  • Jeff Patton, "The New User Story Backlog is a Map" (博客) — 解释Backbone概念

Dean's Work

Dean的工作

  • [If Dean has story mapping resources, link here]
  • [若Dean有故事地图相关资源，请在此处链接]
Skill type: Interactive Suggested filename: 
user-story-mapping-workshop.md
Suggested placement: 
/skills/interactive/
Dependencies: Uses 
skills/user-story-mapping/SKILL.md
, 
skills/user-story/SKILL.md
, 
skills/proto-persona/SKILL.md

Provenance

—
  • Derived from 
    skills/user-story/SKILL.md
    , 
    skills/user-story-splitting/SKILL.md
    , and 
    skills/user-story-mapping/SKILL.md
    .
Skill type: Interactive Suggested filename: 
user-story-mapping-workshop.md
Suggested placement: 
/skills/interactive/
Dependencies: Uses 
skills/user-story-mapping/SKILL.md
, 
skills/user-story/SKILL.md
, 
skills/proto-persona/SKILL.md
—