Skip to content
Cardboardit Docs

Story mapping

Story mapping is the practice CardBoard was built for. This guide is how to run one well.

What story mapping is

Section titled “What story mapping is”

Story mapping organizes work from the user’s point of view. Cards across the top are user activities — the backbone — read left to right in roughly the order a user does them. Cards down each column are the stories that make up each activity. Horizontal dividers slice the map into releases. (Jeff Patton’s User Story Mapping is the canonical reference.)

When to run a session

Section titled “When to run a session”

Early product discovery, pre-MVP scoping, post-research synthesis, or planning a major feature. Not for daily standup, and not for sprint planning — that’s the tracker.

Running a session

Section titled “Running a session”
  1. Define the user. (Use a separate persona map if it helps.)
  2. Lay the backbone — user activities, left to right, in the order the user does them.
  3. Break each activity into stories — vertical columns under each backbone card.
  4. Slice into releases — horizontal dividers; the top slice is the MVP, lower slices are later.
  5. Name each slice. The slice name becomes the outcome name.
  6. Prioritize within each release.

Common patterns

Section titled “Common patterns”

Use parent/child for sub-stories; use color for status or theme; link to ADO or Jira once stories are agreed.

Common pitfalls

Section titled “Common pitfalls”
  • Packing too much into the MVP.
  • Treating the backbone as a fixed chronological order — it’s user-centric, not a timeline.
  • Confusing story mapping with backlog grooming. Story mapping is upstream of the backlog.

After the session

Section titled “After the session”

Export to CSV, link to your tracker, and share with stakeholders.