user-story-mapping

## 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)