This document provides an overview of using user story mapping to bridge design thinking and agile implementation. It begins with background on the presenter and defines key terms. The document then outlines challenges with handoffs between design and development. User story mapping is presented as a solution, with benefits like a visualized backlog and improved collaboration. The process of a user story mapping workshop is explained in three phases: pre-work, during the workshop, and post-work follow up. An example of a workshop with an IBM product team is described. Stakeholder feedback emphasizes benefits like iteration and alignment. The document concludes with dos/don'ts and fitting user story mapping into continuous delivery.

1. Linking user research to user
stories with user story mapping

2. I am John Murray
Design Lead, IBM Hybrid Cloud Developer Experience
Hello!

3. ● Design lead at IBM, 3 years
● Design leadership, 5 years
● Designer, 10 years
● IBM & AIGA design thinking
facilitator
About Me

4. The handoff
Design thinking to agile implementation should be
a smooth transition, but when it doesn’t go well it
can be problematic for everyone involved.

5. How design thinking should be

6. How it often turns out

7. The divide

8. I noticed that design thinking
workshops made product teams
think they were on the same page
until it was time to get granular.

9. The good vibes and sense of
alignment turned to uncertainty
about how to get to market.

10. “
Uncertainty turned to inactivity
We have mission statements for our release (hills) … now what?
We have hills … how do we act on them?
We have user research … how do we use it to impact the product?

11. “
Let’s not try to break this stuff down now.
We’ll figure it out as we go!
Inactivity turned into teams saying …

12. Product teams need a way to
bridge the divide.
User Story Mapping
YOU

13. User story mapping …
explained in actionvisualized

14. User story mapping explained
User story mapping takes a measured approach
to decomposing design thinking hills. At its core,
we break down hills by simply asking ourselves,
“what does the user need to do to get this
done?”

15. User story mapping visualized
◉ Represented as a tree
◉ Starts with an overarching vision
◉ Can be broken into corresponding agile
components

16. achieved by accomplishing goals.
broken down into agile stories.
completed by performing tasks.
reached by completing activities.
smallest increment of the
process.

17. Goal
Activity
Tasks Stories
Vision
Our online customers need an easier way to search through our inventory and find
the item they’re looking to buy.

18. User story mapping in action
We’ve been working with Hybrid Cloud product
teams to implement user story mapping.
The Continuous Release and Delivery Insights
teams were kind enough to work with us.
Examples today will come from our work with
them.

19. Delivery Insights As-Is
◉ Customers asking for features for different
use cases
◉ Lack of direction from previously written hills
◉ Design was building what dev said customers
needed

20. The benefits
User story mapping has a lot to offer product
teams that invest the time.

21. User story mapping benefits
◉ Visual presentation of your backlog
◉ High-level view of work being done in the
current release
◉ Improved collaboration between stakeholders

22. User story mapping benefits
◉ Prioritized work based on collaborative goals
◉ More accurate story sizing
◉ Simplification of product road map
◉ User stories become developer work items
◉ Iterative collaboration process

23. The process
Here’s how to run a user story mapping workshop
session with your team.

24. User story mapping phases
pre-work post-workduring

25. Pre-workshop homework
Know the stakeholders
Reach out to key stakeholders
before the session. Explain the
purpose of the exercise. This
generate advocates who come
in ready to participate.
Know your user
If you can get feedback
beforehand from users. Do it! If
you need to build a persona,
then come in with one that’s
been validated ahead of time.
Know the user’s experience
Map out the current user
experience. What’s the as-is?
You can’t make life better for
your user if you don’t know their
pain points .
Know what you want to do for them
You know the user. You know their
pain points. Now how are you going
to make things better for your user?
Create a draft of hills that
summarize the who, what, and wow
you plan to provide.

26. Know the stakeholders
◉ Researcher / design lead
◉ Product manager
◉ Development lead
Min. required stakeholders Meeting topics
◉ Introduce the topic and
explain the use and benefits
◉ Spend 15-20 minutes building
a user story map

28. Delivery Insights’ persona

29. Created by Delivery Insights after they
realized they weren’t focus on the right
user.
Delivery Insights’ As-Is

30. Delivery Insights’
draft hills

31. During the workshop
Revisit pre-workshop hills
Before you do anything align on
the hills you wrote beforehand
in case not everyone has seen
them.
First draft of to-be scenario
If the as-is tells us what the
user’s experience is like now,
the to-be tells us what it will be
like after we deliver on our hill
or mission statement.
Refine workshop hills
At this point we ask ourselves,
“knowing what we know about
the to-be we created, do we
need to revise the language of
the hills?”
Second pass at to-be scenario
If we’ve revised the language of
our hills, we need to reflect
those changes in the to-be
scenario.
Refine hills one last time
Now that we feel confident
about our to-be scenario, let’s
do our best to finalize our hills
before moving on.
Draft of Golden Thread
The purpose of the Golden
Thread is to prioritize what
development will deliver first,
with the specific intent that
research will validate it with the
user after the workshop.

32. Revisit
pre-workshop hills
Before After

33. First draft of
to-be scenario

34. Before After
Refine
workshop hills

35. Second pass at
to-be scenario

36. By the end, one hill became two separate hills.
Before After
Refine hills one
last time

37. Draft of
Golden Thread

38. Post-workshop follow up
Validate the
Golden Thread
Up until now your
scenario is a
hypothesis. Put it in
front of sponsor
users for validation.
Team finalizes hills,
epics, & user stories
Clean up the
language on any
unresolved hills,
epics or user stories.
Add finalized work to
product backlog
Start to create work
items in the backlog
that reflect the
Golden Thread.

39. Validate the
Golden Thread

40. Add finalized work
to product backlog

41. Stakeholder Feedback

42. “
“It was a breath of fresh air.”
Q: How was the user story mapping experience?

43. “
“We kept iterating on the same thing over and over
until we narrowed in on what was really good about
it. That refinement was really big for us.”
Q: What did you get most out of the process?

44. “
“I liked the idea of creating the Golden
Thread where—one, you pull out the
high priority items, and two, you tell
the story all the way through.

45. “
“We end up passing high level information from one
person to the next then back to customers … We
understand everything from high level value to what it
takes to implement, and everyone’s on the same page.”
Q: How have things changed since the workshop?

46. Dos & Donts
Learn from our mistakes by remembering these
key takeaways.

47. ◉ Don’t allow unvalidated personas from any stakeholder.
◉ Do your user research. Your success depends on it!
◉ Do get a facilitator. You need to focus on helping your
team.
◉ Don’t worry about perfection.

48. Fitting it together
Let’s take a step back and see how this fits into a
continuous delivery process.

50. If you have any questions …
@heyjohnmurray
On Medium, Twitter, and LinkedIn
Thanks!