In the Usage of User Story Map, the usage method of user story map was described, that is, the product requirements were iteratively divided into three stages: 1, 1.51.5, 11 and +∞.

user journey map, user story map, user story map, user experience map, storyboard ... a bunch of common terms are confusing, not to mention how to use them. This paper mainly introduces the user journey map and user story map. Use the user journey map to restore the scene and find the user's pain points; Then sort out the product requirements according to the pain points, and plan iterations in different versions to get the user story map; Finally, communicate and confirm the requirements with user stories.

Based on the achievement of user goals, go back to the requirements of scene mining

1. Why do you need a user journey map?

what people need is not a product or function, but a problem, and a product is just a tool to solve the problem. The user's needs occur in specific scenarios, and the needs in different scenarios are different. Focusing on the problem itself helps to gain insight into opportunities for optimization and innovation.

2. What is the user journey map

The user journey map is a visual tool for summarizing user scenarios. Describe the user's process of using the product by telling stories, find out the pain points and satisfaction points of the user in the whole use process, and finally extract the product optimization ideas and opportunities

3. Classification of user journey map

1) As is user journey before going online: pay attention to interactive behavior and contacts, and evaluate the feasibility. Make an implementation plan

2) After going online, To be user journey: pay attention to pain points and opportunities, Looking for optimization and innovation

4. The value of user journey map

5. How to write down the user's goals and stages using the user journey map

Step.1

Step.2 Write down the user's behavior

Step.3 List the people and things that the user contacts

Step.4 Draw the user's mood curve using the scene

Step.5 List the pain points and gains

Step.6 Insight into possible optimization and innovation opportunities

Give it to the user Si Manan. It is often used when a business design scheme has been formed and it is necessary to identify what requirements should be made on the product.

1. What problems can the user story map solve?

1) Effectively avoid duplication or omission of product requirements

2) Be able to see the whole picture of requirements. Avoid scattered requirements with unclear logical relationship

3) Plan version iteration

2. How to build a user story map

Step.1) Select user activities and user tasks from the user journey (we got the user journey map in the first part)

Step.2) Identify functional requirements that support user tasks (blue cards)

Step.3) Identify supporting requirements. Firstly, from the core scenario, identify the functional requirements of each user task; Then, from other secondary scenarios, the functional requirements supporting each user's tasks are identified.

2) Supportive requirements: the system capabilities needed to meet the business, such as security, reliability, interoperability, maintainability, portability, etc.

3. How to use the user story map to divide the version

Step.1 to find out the running skeleton (MVP)

Step.2 Divide the subsequent versions according to the business objectives

User stories are brief intentional descriptions. Emphasize dialogue, not documents. Do a good job in clarifying, splitting, transferring and verifying requirements.

The purpose of using user stories is to stimulate discussion, promote the team to fully understand the requirements, reach a * * * understanding, and * * * take responsibility for the requirements.

User story card

Elements on a user card: What do you want and why?