My Role in this workshop:
I investigate, prepared the materials and carried on this 30 minutes workshop about “User Journeys”.
What is this workshop about:
The target of this workshop is to understand what a User Journey is and how we can use it in our design process.
The activity helps teams the different context where people (our users) live and work while they are performing our expected tasks.
Motivation to create this workshop:
Some organizations or even design teams are not familiar with these type of techniques we use in the Design Thinking approach.
User Journeys could be used in many situations from gathering data in user research to create the dream scenario for the new experience we are planning to deliver.
Intro to the workshop
Seven people were invited to participate to this workshop and this was an individual activity.
It was given an small intro about what User Journeys are how we use it to describe (graphically) a particular task.
Participants received an A3 sheet of paper with a 1 line representing a timeline.
The corner of the paper had a drawing with their own person, just to add some fun in the activity.
The paper was divided in 3 sectors: the first one belongs to feelings, the seond one to actions and the third and last one belongs to 'things I like'. The Task
Participants were asked to add all the actions from the moment they wake up until they arrive to work in the 'actions sector'. Then they had to add to those actions the correspondant feeling associated to it using emojis.
In this type of activities in order to avoid wasting time I always explain things with examples, so people can feel comfortable with the task. This is my own example of the user journey I asked participants to create.
Outcomes from the workshop
Participants could identify what a user journey is and the different ways to use them in the design process.
When the activity was over they were discussing several options to introduce them in the stories they were working at this moment and how beneficial could be introducing them into the backlog stories as a way to proof their design concepts to the developement team.