User-story mapping
User-story mapping, formalised by Jeff Patton in his 2014 book of the same name, is a workshop technique for organising product backlogs around the user's journey rather than as a flat list. The map has activities across the top (the user's high-level steps in chronological order), and stories underneath each activity stacked by priority — making the shape of the product visible and slicing for releases tractable.
The technique solves a problem most product backlogs share: a flat list of stories with no visible relationship to the user's experience. With a story map, the team can see: which user activities are covered, which are missing, and where the gaps in the experience are. Release slicing happens horizontally — a 'walking skeleton' release picks one story under each activity (a minimum viable journey); subsequent releases deepen the coverage where it matters most. Story maps pair well with JTBD (the activities are the user's job steps) and with vertical slicing (each release is a vertical slice across the entire journey).
Related terms
- Jobs-to-be-done
Jobs-to-be-done (JTBD) is a product-discovery framework, popularised by Clayton Christensen, that frames features in terms of the 'job' a customer is hiring the product to do — the underlying outcome they want — rather than demographic personas or feature lists.
- Story splitting
Story splitting is the practice of breaking a large user story into smaller stories that each independently deliver value.