Here are Jeff's Six Simple Steps to Story Mapping Book:
Frame the problem
Map the big picture
Explore
Slice out a release strategy
Slice out a learning strategy
Slice out a development strategy
Frame the problem
Too many initiatives start with the solution, but you have to understand your target users/customers their problem space and why it's important to even solve that problem.
Map the big picture
Go wide but shallow - you want to call out broadly what a solution should do, but not go too much into how it might do it (that comes later). Start with a goal and map out the steps a user would go through to achieve that goal. This is your backbone.
Explore
Dive into the steps! Call out specific user actions, call out risks and assumptions underpinning them, the importance of particular actions, and any alternative solutions. Your goal is to deeply understand all the different things that could help users succeed.
Release strategy
Slice out releases - work out what's the minimum solution you can build to understand if you should build more. Focus on what your users truly need to achieve their goals, and how these can support your business.
Learning strategy
Work out what you need to know to proceed with confidence. Ideas aren't worth anything until you've tested that they hit the spot. Design small experiments around the map to make sure you really know what's working and what's not.
Development strategy
If you've worked out what you need to deliver, work out how to deliver it. Break stuff down into small parts that can be built and inspected quickly, so you can evaluate (and adapt) the plan as well as surface risks, dependencies and blockers.
Here are Jeff's Six Simple Steps to Story Mapping Book:
Frame the problem
Map the big picture
Explore
Slice out a release strategy
Slice out a learning strategy
Slice out a development strategy
Frame the problem Too many initiatives start with the solution, but you have to understand your target users/customers their problem space and why it's important to even solve that problem.
Map the big picture Go wide but shallow - you want to call out broadly what a solution should do, but not go too much into how it might do it (that comes later). Start with a goal and map out the steps a user would go through to achieve that goal. This is your backbone.
Explore Dive into the steps! Call out specific user actions, call out risks and assumptions underpinning them, the importance of particular actions, and any alternative solutions. Your goal is to deeply understand all the different things that could help users succeed.
Release strategy Slice out releases - work out what's the minimum solution you can build to understand if you should build more. Focus on what your users truly need to achieve their goals, and how these can support your business.
Learning strategy Work out what you need to know to proceed with confidence. Ideas aren't worth anything until you've tested that they hit the spot. Design small experiments around the map to make sure you really know what's working and what's not.
Development strategy If you've worked out what you need to deliver, work out how to deliver it. Break stuff down into small parts that can be built and inspected quickly, so you can evaluate (and adapt) the plan as well as surface risks, dependencies and blockers.