Skip to content
Nerdy beta

User Journeys

Add to Space
 Product UX Discovery

A story map tells you everything the user might do. A user journey tells you what to build first and why.

Overview

User journeys are paths traced through a story map that represent end-to-end slices of user value. Where a story map lays out the full landscape of user activities and tasks, journeys select specific routes through that landscape and sequence them for delivery. Each journey represents a coherent experience a persona would recognize as useful.

The technique works by taking 3-4 routes through the story map and naming them. Color-code each journey and label it descriptively. Then prioritize: which journey delivers the most learning? Which one is ready for engineering? Which needs more discovery or design work first? This creates a natural backlog that stays connected to user needs rather than decomposing into disconnected technical tasks.

Journeys provide optionality and easy prioritization. A high-priority journey goes straight to engineering for delivery. A mid-priority journey might need UX design work first. A journey full of unknowns needs more discovery before anyone builds anything. This is where multi-track becomes concrete: the team can see which journeys are in discovery, which are in design, and which are in delivery, all at once.

The classic work breakdown structure (Project > Feature > Story/Task) tends to lose sight of user needs as you decompose. Journeys preserve the user’s perspective all the way down to implementable stories while keeping product and technical concerns visible in the same map.

Resources