User journey: Difference between revisions
m replaced: short-hand → shorthand; delink using AWB (8853) |
m →References: Tagging using AWB (10458) |
||
| Line 6: | Line 6: | ||
== References == |
== References == |
||
{{ |
{{Refimprove|date=September 2014}} |
||
<references> |
<references> |
||
</references> |
</references> |
||
Revision as of 13:44, 15 September 2014
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 shorthand 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.
User Journeys are focused on the User and what they see and what they click on,[1] in comparison to the related term click path which is just a plain list of the text URLs that are hit when a user follows a particular Journey.
References
 | This article needs additional citations for verification. (September 2014) |
- ^ "What is a User Journey". SciVisum Ltd. Retrieved 4 July 2012.
 | This computing article is a stub. You can help Wikipedia by expanding it. |
 | This technology-related article is a stub. You can help Wikipedia by expanding it. |