User journey: Difference between revisions
Appearance
Content deleted Content added
Corrected stub categorization. |
No edit summary |
||
Line 1: | Line 1: | ||
A '''user journey''' is, [[colloquialism|colloquially]] in the UK and parts of the US, the experiences a person has when utilizing/interacting with something (typically software). This idea is generally found in user experience circles around [[web design]] and how users interact with [[software]] experiences. It is often used as a [[shorthand|short-hand]] for the overall [[user experience]] and set of actions that one can take in a software/[[virtual reality|virtual]] experience. |
A '''user journey''' is, [[colloquialism|colloquially]] in the UK and parts of the US, the experiences a person has when utilizing/interacting with something (typically software). This idea is generally found in user experience circles around [[web design]] and how users interact with [[software]] experiences. It is often used as a [[shorthand|short-hand]] for the overall [[user experience]] and set of actions that one can take in a software/[[virtual reality|virtual]] experience. |
||
User Journeys describe at a high level of detail exactly what steps different users take to complete a specific task within a system, application or website. This technique shows the current (as-is) user workflow, and reveals areas of improvement for the to-be workflow. |
|||
== References == |
== References == |
||
{{Unreferenced|date=February 2010}} |
{{Unreferenced|date=February 2010}} |
Revision as of 13:59, 22 May 2012
A user journey is, colloquially in the UK and parts of the US, the experiences a person has when utilizing/interacting with something (typically software). This idea is generally found in user experience circles around web design and how users interact with software experiences. It is often used as a short-hand for the overall user experience and set of actions that one can take in a software/virtual experience.
User Journeys describe at a high level of detail exactly what steps different users take to complete a specific task within a system, application or website. This technique shows the current (as-is) user workflow, and reveals areas of improvement for the to-be workflow.