user journey design studio senior thesis

1. USER JOURNEY
1

2. Turning first-time users into long-term customers
2

3. A user journey is a series of
steps (typically 4-12) which
represent a scenario in which a
user might interact with the
thing you are designing.
3

4. Demonstrating the way users currently interact with the service / website / product
4

5. Demonstrating the way users could interact with the service / website / product
5

6. Demonstrating the vision for the project
6

7. They help us understand user behavior
7

8. They help identify possible functionality at a high level
8

9. They help you define your taxonomy and interface
9

10. User journeys typically come
towards the beginning of a project
10

11. normally after personas
11

12. • Your user’s goals
• Their motivations
• Their current pain points
• Their overall character
• The main tasks they want to achieve
12
THINGS TO
CONSIDER

13. User journeys tie back to
personas and real people. You
will want to create at least one
journey for each of your primary
personas at a bare minimum.
13

14. 14

15. What should a user journey contain?
15

16. Where is the user? What is around
them? Are there any external
factors which may be distracting
them?
16
Context

17. How does each step enable them to get to
the next?
17
Progression

18. what device are they using? Are they a novice
or expert? What features does the device
have?
18
Devices

19. What type of functionality are they expecting?
Is it achievable?
19
Functionality

20. What is their emotional state in each step?
Are they engaged, bored, annoyed?
20
Emotion

21. 21
What should a user journey look like?

22. There is no set template, and a
lot can depend on who the
audience for the user journey is.
22

23. 23

24. • A picture of the persona the journey relates to
• A title summarizing the journey e.g “Faster
uploading with new CMS”
• A series of steps in short, concise text
• An illustration of what’s happening in the step
(if deemed necessary)
24
THEY MUST
INCLUDE

25. 25

26. 26

27. • The device used
• Changes to the current journey (if future state)
• Benefits to the user and/or business
• Any functionality being demonstrated
27
PER STEP

28. 28

29. User journeys feed into a number activities including
information architecture and sitemaps, wireframing
and functional specifications.
29
What’s next?

30. 30

31. 31