Definition of Roadmap
Roadmaps are used to direct people to a certain location, or to show how to get from place A to place B. In a general sense, route maps are more often referred to as geographic pictures, such as treasure hunt maps, partial location maps, traffic diagrams, and so on.
In a broad sense, a Roadmap can also be a descriptive document that guides people to achieve any goal, even without any picture description can be referred to as a "Roadmap". Extending to product design, it is a quick way to express the success of the country email list product and the end result.
2. Features of Roadmap
1) There is a beginning and an end
Unlike traditional maps, Roadmaps have a starting point and an ending point. Usually the starting point is 1, but the end point may be 1 or more, because the path of product development may be derived from the first idea into 1 or more product solutions.
2) Have a clear path
This is very similar to the navigation of map software. The route from the starting point to the ending point must have a clear path. Based on the different demands of users, the route is different. For example, from point A to point B, the route recommended by the navigation software is different according to different demands such as subway priority, less walking, less transfer, and shorter time.
But no matter what kind of path, the user can get a clear path on the map, and guide himself from point A to point B step by step.
3) Simple to understand and easy to read
Roadmaps are generally easy to understand. According to the process of user experience scenarios, the graphics are expressed through concise and visual text descriptions. The steps are clear and carry relatively little information, making it easy to understand and read.
Second, why do Roadmap?
Roadmap allows the team to intuitively see the complete appearance of the product from the horizontal and vertical dimensions of the user experience scene.
Horizontal view: From the time the user starts to experience the product, to the completion of the experience and leaving the product, the scenes on the entire user experience path can be covered by the Roadmap;
Vertical view: In a certain user experience scenario, for example, from providing 10% of the scenario solution in the early stage to finally providing 100% of the scenario solution, it can be presented on the Roadmap.
2. The look of success
The value of the Roadmap is to give the team a clear idea of what the success of this product looks like? And what goals do you need to set to achieve what success looks like? What are these goals to achieve?
When do these standards need to provide what kind of solutions, so that in the initial product planning, product managers need to consider both user scenarios and existing capabilities of the enterprise, and finally draw a picture of "a successful product that can be implemented on the ground." blueprint".
3. Capacity Reserve
A roadmap that can be implemented and implemented allows the team to reserve the corresponding capabilities in advance, so as to perfectly realize the success of the Roadmap.
For example, it is necessary to reserve user in-depth research, demand mining, product design and other capabilities in advance to solve users' pain points in different scenarios; for example, it is necessary to reserve operational support capabilities in advance, product managers provide product solutions, and operations need to be matched with appropriate operation promotion solutions to better address user pain points.
For another example, to realize the corresponding product solutions and operation promotion plans, what technical capabilities do the technical team need to build? Do you want to build a middle station? And which middle stations to build?
3. What does the Roadmap look like?
Roadmap doesn't care what tool is used to describe it. It can use PPT, Xmind and other tools, but it cannot be separated from the following core elements. By combining these core elements according to a certain logic, the appearance of Roadmap is presented.