methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session4-6 h for first map, then 1 h maintenance per releaseWorkshopStory Map

Session: User Story Mapping

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 4-10. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Story Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Build backbone

    45-60 min

    Collect user activities chronologically (yellow), at rough granularity: what does the user do from start to goal. Then order and condense to 8-15 backbone steps. Hint: If backbone has more than 20 steps, level is too fine. Activities are not clicks, but tasks ("place order", not "press button").

    FacilitatorStory Map
  2. 2

    Phase 2: Tasks and stories

    60-90 min

    For each activity, place required tasks (blue) and concrete stories (green) below it. Stories as small outcome steps, several possible per task. Hint: Do not formulate stories as implementation-heavy. If a story is technology-specific ("implement with React"), it belongs in tasks, not in the map.

    FacilitatorRelease Slices
  3. 3

    Phase 3: Mark risks

    20-30 min

    Place pink stickers on stories with high uncertainty or dependency. Briefly note what endangers the slice (technical, regulatory, user-side). Hint: If all stories are pink, the map is too early. Run discovery methods first, then map. Mark only truly critical risks.

    FacilitatorBacklog Candidates
  4. 4

    Phase 4: Cut slices

    45-60 min

    Draw horizontal lines across the map: first line for MVP (narrowest flow that delivers real value), second for Release 2 etc. Stories above the line are in, below are out. Hint: MVP slice must pass through every backbone activity, otherwise it is not end-to-end. Prefer less depth per step over omitting whole steps.

    FacilitatorStory Map
  5. 5

    Phase 5: Validate and hand over

    30-45 min

    Check MVP slice against user persona and vision. Can the persona do their job? Move slice stories into backlog with estimate size and owner. Hint: If the persona cannot do their job with the MVP slice, it is not an MVP but a fragment. Recut slice before filling backlog.

    OwnerRelease Slices
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerStory Map
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: User Story Mapping

Goal

Artifact: Story Map

Working Question

Which narrowest end-to-end flow delivers the first real value to the user, and what is the next meaningful slice after that?

Context

User persona; outcome hypothesis of product or release; known constraints (compliance, platform, dates); existing backlog as input, not as directive.

Setup

  • Format: Method session
  • Duration: 4-6 h for first map, then 1 h maintenance per release
  • Mode: Workshop
  • Participants: One facilitator with mapping experience; Product Owner; two to four engineers; UX lead; optional stakeholder from sales or support. Maximum eight people, otherwise flow breaks down.
  • Owner: One facilitator with mapping experience
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Story Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Long wall or Miro board with horizontal lanes; four sticky colors (yellow activities, blue tasks, green stories, pink risks); wide tables for sorting; timer; link to existing backlog if available.

Preparation

Prepare wall: persona top left, then timeline for user activities from left to right (backbone). Lane below for tasks, below that lane for stories. Right wall for later parking lot.

Agenda

  1. Phase 1: Build backbone (45-60 min) Owner: Facilitator Action: Collect user activities chronologically (yellow), at rough granularity: what does the user do from start to goal. Then order and condense to 8-15 backbone steps. Hint: If backbone has more than 20 steps, level is too fine. Activities are not clicks, but tasks ("place order", not "press button"). Output: Story Map

  2. Phase 2: Tasks and stories (60-90 min) Owner: Facilitator Action: For each activity, place required tasks (blue) and concrete stories (green) below it. Stories as small outcome steps, several possible per task. Hint: Do not formulate stories as implementation-heavy. If a story is technology-specific ("implement with React"), it belongs in tasks, not in the map. Output: Release Slices

  3. Phase 3: Mark risks (20-30 min) Owner: Facilitator Action: Place pink stickers on stories with high uncertainty or dependency. Briefly note what endangers the slice (technical, regulatory, user-side). Hint: If all stories are pink, the map is too early. Run discovery methods first, then map. Mark only truly critical risks. Output: Backlog Candidates

  4. Phase 4: Cut slices (45-60 min) Owner: Facilitator Action: Draw horizontal lines across the map: first line for MVP (narrowest flow that delivers real value), second for Release 2 etc. Stories above the line are in, below are out. Hint: MVP slice must pass through every backbone activity, otherwise it is not end-to-end. Prefer less depth per step over omitting whole steps. Output: Story Map

  5. Phase 5: Validate and hand over (30-45 min) Owner: Owner Action: Check MVP slice against user persona and vision. Can the persona do their job? Move slice stories into backlog with estimate size and owner. Hint: If the persona cannot do their job with the MVP slice, it is not an MVP but a fragment. Recut slice before filling backlog. Output: Release Slices

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Story Map

Closeout

  • Update result artifact: Story Map
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Story Map: User Story Mapping

Working Question

Which narrowest end-to-end flow delivers the first real value to the user, and what is the next meaningful slice after that?

Context

User persona; outcome hypothesis of product or release; known constraints (compliance, platform, dates); existing backlog as input, not as directive.

Participants

  • Owner: One facilitator with mapping experience
  • Participants: One facilitator with mapping experience; Product Owner; two to four engineers; UX lead; optional stakeholder from sales or support. Maximum eight people, otherwise flow breaks down.

Input

Long wall or Miro board with horizontal lanes; four sticky colors (yellow activities, blue tasks, green stories, pink risks); wide tables for sorting; timer; link to existing backlog if available.

Template

User Story Mapping Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Story map:
  • Release slices:
  • Backlog candidates:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Story Map is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

User Story Mapping Working Template

View templateCompact working template for User Story Mapping with context, input, output artifacts, and next step.
canvas

user-story-mapping-working-template.md

Compact working template for User Story Mapping with context, input, output artifacts, and next step.

User Story Mapping Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Story map:
  • Release slices:
  • Backlog candidates:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Story Map.
  • Store map per release as own snapshot. Link backlog stories with map ID. Change backbone only through mapping session, not silently in ticket system.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.
ProfileRunsheet