Skip to content

SCOPE SLICER · FREE SOLO TOOL

A smaller slice. A clear outcome.

Map one person’s journey. Choose what belongs in the next slice, keep what comes later visible, and make your assumptions easier to discuss.

Manual choices.
Useful questions.

Your story map

One person. One useful result. Small slices you choose.

Start in three steps

  1. Describe the result. Choose one person and what they should be able to do.
  2. Map the journey. Name the main steps. Use Add story in a step, then choose each story’s delivery slice.
  3. Review a small slice. Choose a slice below. Describe its result and how you will check it, then review missing details and needs.

Try Load example map to see how the parts work together.

Start with one user outcome. Name the journey’s activities, then add and place stories manually.

User outcome

One person or user role. Keep the journey from their point of view.

Sequencing assumptions
New
0
Earlier
0
Deferred
0

Earlier stories are included as an assumption. This does not mean they are finished.

THE USER JOURNEY

Activities, in the order you choose.

New in this sliceEarlier scopeDeferredEarlier scope is a comparison assumption, not a shipped status.
STEP 01

    No stories here yet. Add a story to this step.

    Unmapped0

    These stories have no journey step yet. They stay in the map, and can still belong to a delivery slice.

      No unmapped stories.

      DELIVERY SLICES · 1 / 5

      Keep each slice useful.

      You choose the order. A review includes this slice’s stories and stories from earlier slices. Later stories and stories without a slice stay Deferred.

      STORIES · 0 / 40

      Write the pieces. Choose their place.

      Add a story in the map to choose its activity first, or add it here with no activity. Choose a delivery slice when you are ready.

      Start with the smallest useful journey.

      Add a few stories, or load the clearly labelled example map.

      Keep the scope and the reasoning.

      Exports keep the full map, selected slice context, deferred work, notes and declared dependencies together.

      Local saving starts after your first edit.
      Terms explained
      User or actor
      The person this journey is for. Choose one person or role, such as a first-time customer. Keep the map from their point of view.
      User outcome
      The result this person should get. Describe what they can do, not the tasks your team must finish.
      Journey activity
      A main step in the person’s journey, such as “Choose a product”. Put smaller stories under it.
      Story
      One thing the person can do within a step, such as “See the price”. It can belong to one activity and one slice.
      Delivery slice
      A small set of stories you plan to deliver together. Choose enough to give the person a useful result.
      Slice to review
      The slice you are checking now. The review includes its stories and stories from earlier slices. Changing this choice does not move stories.
      Completion conditions
      What you will see or test to know this slice works. For example, “The user gets a confirmation after sending the form”.
      Sequencing assumptions
      Things you expect to be true, but still need to check. Include what must be available and what can be done by hand at first.
      New in this slice
      Stories assigned to the slice you are reviewing. These are the new pieces you plan to add in this slice.
      Earlier scope
      Stories from slices before the selected slice. The review assumes they are available; it does not confirm they are finished.
      Deferred
      Stories left out of this review. They belong to a later slice or have no slice yet. They stay in your map.
      Unmapped
      Stories with no journey activity yet. They can still belong to a slice. Choosing an activity does not change their slice.
      Declared needs
      Other stories this story depends on. Choose only needs you know about. This does not move or order stories.
      Dependency cycle
      A group of stories that depend on one another. Review how they can work together or change the needs.
      Review checks
      Checks look for missing details, missing activities and declared needs outside the review or in a cycle. Passing them does not prove that the slice is useful or ready to deliver.

      A USEFUL RESULT, EACH TIME

      Review the journey,
      not just the pieces.

      Activities are the main steps in a person’s journey. Stories describe what they can do at each step. Choose a small slice that gives them a useful result across the journey.

      • Choose one person and the result they need. Put activities and slices in the order you choose. The tool does not decide the order or dates for you.
      • For each slice, describe what the person can do and how you will check it works. Check the story names, their journey steps, your assumptions and what you leave for later.
      • The review includes stories in your selected slice and in earlier slices. Later stories and stories without a slice stay Deferred. Unmapped means no journey activity; it is a separate choice.
      • Checks use only the needs you add. They show when a story needs work outside the review, or when stories depend on one another in a cycle.
      • Checks complete does not prove usefulness or show that work is finished. You still need to check that the slice works. Discuss whether it is small enough and gives a useful result before agreeing to deliver it.

      Your map stays with you.

      No account, uploads or workspace connection. The map is stored only in this browser after an edit. You choose when to copy or download it. This tool does not create issues, publish a plan or commit scope.