User Journey Mapping: Difference between revisions

From AgileMe
Jump to navigation Jump to search
(Created page with "Category:Agile:ArticlesCategory:Agile User journeys are a good way to visualise the user experience as they use your product or service and can be useful to gain deep...")
 
No edit summary
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
[[Category:Agile:Articles]][[Category:Agile]]
[[Category:Agile:Articles]][[Category:Agile]][[Category:Agile:Design Sprint]]


User journeys are a good way to visualise the user experience as they use your product or service and can be useful to gain deeper insights into the needs, pain points and the typical behaviour of users.
User journeys are a good way to visualise the user experience as they use your product or service and can be useful to gain deeper insights into the needs, pain points and the typical behaviour of users.
Line 12: Line 12:


==See Also==
==See Also==
* [[Customer Research]]
* [[Design Sprint]]
* [[How Might We... Note Taking]]
 
* [[Lightening Talks]]
==References==
* [[Personas]]
# [https://designsprintkit.withgoogle.com Design Sprint Kit], accessed December 2018
* [[Empathy Mapping]]
* [[User Interviews]]
* [[Empathy Exercises & Scenarios]]
* [[Success Metrics]]

Latest revision as of 05:45, 4 December 2018


User journeys are a good way to visualise the user experience as they use your product or service and can be useful to gain deeper insights into the needs, pain points and the typical behaviour of users.

User Experience Journeys

A user journey can represent a use case when using the product, or further upstream activities when they are researching and finding the product or service. User journeys can be specific for each persona or customer segment that has been identified.

Visually drawing the typical actions in the user journey can be a good way to provide some visual context to the journey and allow some empathy into the user actions along the way.

Start off by determining the user’s goal for the journey, and then drawing each step from use case entry point until the goal has been achieved, making notes along the way with descriptions and identified pain points to indicate possible areas for improvement.

See Also

References

  1. Design Sprint Kit, accessed December 2018