What it is
A two-dimensional arrangement of user stories: the horizontal backbone is the sequence of user activities; vertical columns hold the detailed stories under each, sliced into release increments.
When to use it
During Synthesize and Ideate, when planning scope and releases around the user’s whole journey.
Why (value)
Prevents flat, disconnected backlogs, keeps the end-to-end experience visible, and helps carve minimal but coherent releases.
How to run it
- Map the backbone: the sequence of user activities.
- Break each activity into tasks and stories.
- Arrange stories vertically by priority under each activity.
- Draw slices for releases that each deliver a coherent experience.
- Refine with the team.
Inputs and outputs
- Inputs: User activities, stories, priorities.
- Outputs: A story map with prioritized release slices.
Time and effort
Medium. A workshop session or two.
Evidence and limitations
A planning and framing artifact, not user evidence. Prioritization should reference evidence where available. See Evidence and limitations.
Tips and pitfalls
- Keep the backbone at the activity level, not the feature level.
- Slice releases so each is usable end to end.
- Do not let it collapse into a flat backlog.
Variations
Release-slice mapping, journey-aligned story maps.
Related methods
Need help choosing and applying a method?
Gumshoe helps teams connect research, collaborative workshops and service design to the decisions they need to make.
Sources and further reading
- UX Tigers, “100 UX methods.”
Explore related methods
- User stories — Capture a need from the user's perspective in a small, buildable increment.
- Journey mapping — Visualize a person's end-to-end experience across steps, emotions, and touchpoints to find pain and opportunity.
- Impact-effort prioritization — Plot options by impact and effort to spot the quick wins and avoid the money pits.
