. "Eternal Question" What do you do? There is always one in the endless questions in the product world: What do you do?
Whenever your relatives and friends ask about it during the holidays, you may be shocked.
For people in the non-Internet industry, we often cannot grasp the degree of this answer. If you talk too much technology, you are afraid that people will not understand it. If you say too little, you are afraid that people will think they are administrative. If you don’t speak well, you will be considered the product manager at the bank counter. So I feel extremely tired.
For this purpose, the author summarized the complete workflow of the product manager and sorted out at least 25 things, which are the unique workflow of the product manager.
I hope the following content can give you inspiration. Let’s first go to the brain map:
2. "25 things" complete workflow
The author sorted out the complete process of the product from 0 to 1, ruled out the scope of post-optimization and product operation, and obtained three major stages: product sorting, product design, and product implementation
, at least 25 things we have to do are what the product manager must do, otherwise it will have a great impact on our product effect. Let’s take a look at the details below.
1. Ideas
Product managers need to find out the ideas, no matter where the source is. To do a good job of ideas, we need to master the brain map skills and storm skills, produce flexible and changeable ideas and record them.
2.Requirements
In terms of demand, we need to borrow knowledge from psychology and other aspects to summarize the ideas into clear requirements and put them into the demand pool for analysis.
3. Solution
Solution For this, we need to plan the requirements in the demand pool into a prototype to see if it is suitable for doing it under the existing resource environment, and give a rough plan and workload schedule.
4. Target
We need to give the goals and effects that the product wants to achieve. We cannot do it just because this function is cool, but we need to see where it is cool.
5. Strategy
After having a goal, we also need to look at the strategy, whether it is restrained or extensive, whether it is cautious or open. We all need to think about it.
6.Definition
After clearing the goals and strategies, we should give the product definition. Product definition is the core essence of our later evaluation needs. All requirements and priorities cannot violate the product definition, which is also our original intention.
7. Insufficient
After these things are completed, we will definitely leave some problems that are difficult to solve in the short term, or require trial and error. Therefore, we need to record the shortcomings and focus on the later product iteration process.
8. Scene
gives the target user and scenario, propose solutions one by one, and deduce them.
9. Business Process
After the scene is available, we will sort out a user's business process and then take a look at the situation of each link as a whole.
10. Functional structure diagram
After the scene and process are clarified, please make a functional structure diagram. A storm meeting is also needed here, and the focus this time is on the plan.
11. Page relationship diagram
After the overall function site map, we need to add the jump relationship between pages and the design and planning of the specific content of each page.
12.UE interactive map
After finalizing the general content and relationship of the page, we need to refine the content. At this time, we may need to connect with the demand party and users, and investigate the real data of each page to facilitate the designer to give interactive scripts.
13.UI renderings
Interactive manuscripts are given, and after that, you need to find the renderings and cuts for the designer, and prepare to enter the development.
14. Project launch meeting
After obtaining the requirements, solutions and requirements documents, as well as the renderings required by the front-end, please call all personnel to conduct a project launch meeting to mark whether the requirements are communicated and the progress is known, which is crucial to avoid development loss and other situations.
15. User verification
in the early stage of development, especially startups, please do user verification. This is the easiest way for us to conduct trial and error and avoid direction deviations, so as not to cause greater sunk costs when we go astray.
16. After the resource is confirmed, the resource investment has finally been finalized. Please be sure to confirm with the senior management to avoid unclear positioning and difficulty in reaching the order of magnitude. 17. calendar
After everything is confirmed, please give the calendar. This is more important for project progress tracking and is also a reassurance for leaders and users. It will also be of great benefit when reviewing later.
18. Report
Report runs through the above, but a report is especially needed at this stage. Reporting at this stage marks the surface of demand and is a point that senior management values more. We must report fully to solicit the Sword of Shangfang to facilitate subsequent actions.
19. Project Management
After entering the development stage, we must track the project progress and arrange the workload. This is to gain time for our later acceptance and optimization.
20. Check Acceptance
Please arrange the test engineer to prepare for checking the environment and give designers time to optimize. After checking, send a summary email for the problem waiting for the front-end to modify. After the investigation, you must confirm the problems with the front-end in person to ensure that he is clear and knows how to modify them. After the modification, accept them as soon as possible and conduct multiple rounds of investigations.
21. Update information
Please update the requirements changes and requirements documents in a timely manner, and prepare the operation manual and FAQ for promotion personnel to use.
22. Test
In addition to the front-end inspection and acceptance, we must also conduct tests on the overall environment, data logic and other conditions, as well as DEBUG, and promptly discover and solve them.
23. User verification
24.UAT
This is our most important link, ensuring that a small range of UAT and play can be performed after each overall function is completed, otherwise it will be shelved until it is launched. If you do not do a good job in UAT and have serious interaction loopholes, you can only wait for the next version to be modified. This has a great impact on the reputation of the product.
25. When publishing
, please think of the time and strategy, from cold start solutions to prompts, you must consider everything in detail. Otherwise, it is easy to crash and package errors. You must test thoroughly during the release stage.
3. "Summary" What have you done
After sorting out these 25 things, we gave each thing a brief noun and explanation.
. I think we can already answer the above question:
As the product manager, we are the person in charge of the entire process of demand analysis to implementation and launch. The work content includes more than 20 items, such as...
For interview scenarios, we can also give corresponding answers:
In the previous company, I mainly did 2 projects. In addition to maintaining the global demand documents, I am also responsible for user verification and storm meeting promotion in the project launch stage... Does
look much more professional?
Many times, you don’t know what you have done, and you don’t have concrete sorting and expression. A lot of communication and display is hidden in the process of being confused. Therefore, the product manager should not only do well, but also speak well and summarize and report well. Only by can you share the brilliant starry sky in your heart with everyone.
#Columnist#
Mr. Peanut Butter, everyone is a product manager columnist, WeChat official account: Product Art. Senior product manager in the financial industry, has rich experience in career planning and personal development, has a wide range of products, and has many ERP and financial fields.
This article was originally published by Everyone is a product manager. Reproduction is prohibited without permission.
question picture is from Pixabay, based on CC0 protocol
