Linking UX Ideas for an Aha Moment from Non-Empathizers

I will describe a specific set of tools I've been using in a particular order that really helps all the members of a project (makers, monetizers and managers) understand user needs and build for those needs. None of the methods I use are new, but by focusing on the idea of empathizers and systemizers I ensure that there is sufficient continuity between the activities we perform that non-empathizers can still understand that they are not the user, and agree on a sensible user-centric way forward. This stops arguments and focuses everyone on the team towards customer based solutions.

There is always a paper trail back to observed user data. There is always enough information pinned to the wall that people can point and say "see, this is why we're doing what we are doing". There is always enough verification built in to the process that we know whether we're on track before we invest in code. I'll describe the concept of systemizers and empathizers, share the set of tools I use and show the flow of information between each tool.

18.
User
Ac?vity
User
Ac?vity
User
Ac?vity
Epic
Epic
Epic
Epic
Story
Story
Story
Story
Story
Story
Story
Story
Story
Story
Story
Story
Concept
What
do
users
need?
Process
How
do
we
enable
it?
User
Ac?vity
Epic
User
Ac?vity
Epic
Story
User
Ac?vity
Epic
Epic
Story
Story
Story
Story
Story
Story
lem
Prob
ome
Outc ric)
(met
Story
Execu?on
What
capabili(es
must
we
build?
Story
Hat-­‐?p
to
Jeﬀ
Paeon
(www.agileproductdesign.com),
an
avid
promoter
of
user
story
maps.
Story
Story
lem
Prob
ome
Outc ric)
(met
Story
lem
Prob
me
utco c)
O
ri
(met

19.
User
Ac?vity
User
Ac?vity
Epic
Epic
Story
User
Ac?vity
Epic
Epic
Story
Story
Story
Story
User
Ac?vity
User
Ac?vity
Story
Epic
Story
Story
Story
Epic
User
Ac?vity
Epic
Epic
Story
Story
Story
Story
Story
Story
Story
Story
Story
Hat-­‐?p
to
Carissa
Demetris
(ProQuest
LLC)
for
the
cupcake
analogy.
.
Story
Story
Story