Professional Documents
Culture Documents
Story Mapping PDF
Story Mapping PDF
r
itles e
Wr
y
• Exceptions
Use ite short
Use release slices to identify small experiments, minimal viable
product releases, or a “walking skeleton” version of your product. stor
them verb
later phra t • Details
Identify the target outcomes of your slice in a sticky note or card to the left
y
nice templa as you ses on
ly rig t r c
ht a e to writ story tit ards or
! Down in the details of the map, it’s OK to
include details about what UI might look like or
of the slice.
fter e de les. stick
“I s If ie what the system might do in the background.
righ want to cription you us s.
t aft
er “s ,” the ac s, the ta e the
o th t iv s k
at… ity fits fits
”
nice
ly
1! Frame
Before mapping, create a short product or
feature brief to frame and constrain what you
map. Think of this as the big story.
What names the product, feature to add to a Why describes the benefit your organization gets
product, or problem you’d like to solve.
by building the product or feature. Say what
users do and how their use leads to increased
Who names the different types of users who will revenue or reduced costs.
use the product, and the “chooser” or customers
who will buy it. For each user and chooser state
the benefit they get from using the product.
3! Explore
Fill the body of your story map by breaking • Play “wouldn’t it be cool if...” to help think of Involve others. Tell your product’s story to others
down larger user tasks into smaller subtasks and great product ideas.
that understand users and use. They’ll find holes
user interface details. During this phase you’ll add • Look for variations: What else might users of in your story and help build it up. Tell your
cards, split one card into two, rewrite cards, and the system have done?
product’s story to software developers. They’ll
reorganize them.
• Look for exceptions: What could go wrong, point out risky or expensive areas, and add in
and what would the user have to do to recover?
great technology solutions.
Use this phase to think “blue sky” about all the • Consider other users: What might other types
great possibilities. Use this time to think of of users do to reach their goals?
everything that could go wrong. Don’t worry if • Add in other product details like: Description
your ideas are “in or out of scope.” You’ll of proposed UI; Business rules; Data elements
deliberately move things out of scope later.