~~NOTOC~~ ======== User Journey Map ======== ==== General Information ==== |Name|User Journey Map| |Abbreviation|UJM| |Learning Cost|120| |Playing Cost|200| |Suggested Phases|1| == Engineers == ^ Mechanical Engineer ^ Industrial Design ^ System Engineer ^ Electrical Engineer ^ Production Engineer ^ Software Engineer ^ |✗|✔|✗|✗|✗|✗| == Technique and Issue Views == ^ BusinessNeeds ^ Stakeholder ^ Stakeholder Needs ^ System Requirements ^ System Structure Architecture ^ |✗|✔|✔|✔|✗| ^System Functional Architecture ^Detail Hardware Design ^Detail Service Design ^Detail Software Design ^Manufacturing Operations ^ |✔|✗|✗|✗|✗| == Technique Traits == ^Identify Stakeholders ^Elicit Needs ^Remove Ambiguity ^Layman's Terms ^Technical Terms ^Teamworkings^ | 2 | 4 | 3 | 3 | 0 | 2 | ^Traceability ^Prioritizing ^Exploring Breadth ^Inside the Box ^Outside the box ^ V&V^ | 3 | 2 | 2 | 0 | 0 | 2 | == Verification and Validation == ^Analysis ^Calculus ^Inspection ^Demonstration ^Test ^ | ✔ | ✗ | ✗ | ✗ | ✗ | ==== Description ==== A user journey map is a visual or graphic interpretation of the overall story/ relationships with a service, product, or brand over time and across different channels. They come in all shapes and formats but are most often represented as a timeline of all points of interaction between the user and a product/service. Product designers use this technique to determine how people use the product and better understand the experience of a product or service from a user’s perspective. User/Customer Journey Maps are used to identify and understand the weaknesses of a product, understand the behavior of KPI’s, and to put the focus on the customer instead of the product. The technique can help create a competitive advantage and increase the overall user experience. [1][2] {{:fUser Journey Map.png|}}