Have you committed the three toxic problems of newcomers to data products?

31962d290c938c988f96a4e4a6e7151f.png

Have you committed the three toxic problems of newcomers to data products?


Meimei is a newly hired product manager with a high degree of education and talent. I learned a lot from a certain class, a certain starting point, and a certain steamed bun course, but after being tempered by a large factory for a month, there are still many problems.


No way, people grow up slowly. But with these problems, Meimei, I hope you in front of the screen can learn something.



01Users   /boss/operators are all over the demand, how can I avoid becoming a drawing tool person?



Background restoration:

As a novice data product manager, Meimei will receive many temporary needs from users, bosses, and operations. These needs are scattered, and the front-end and back-end students who cooperate are also temporary. So here comes the problem. If every requirement is done, it is definitely not enough; if not, then users are unwilling to raise requirements. How should these needs be evaluated?

0be0727b95dcf7aafddf1854b318984d.png

Suggest:

There are a few points to note here:

1. Understand the needs. The first priority of the product manager is to understand this need and match the best solution.

2. In addition to requirements, can you master the background of the entire project? This includes internal and external information such as the user's background and real demands, how the boss thinks about the priority of the demand, whether the team and the demanding team have interacted with each other before.

3. Incorporate demand into the demand pool. Time, project classification and division of this demand. The time is recommended to be divided into the "emergency & important four quadrants", and the project is recommended to be marked in several dimensions such as experience optimization, functional modules, and technology upgrades.

4. Contact the front-end, back-end, and design leaders to evaluate and give manpower and time.

5. Regardless of whether it is successful or not, give feedback to the user/boss/operator.



02    Without sufficient in-depth study/research, the solution will not be implemented?


 

Background restoration:

Meimei received an innovative project, and there is no good product to learn from. Meimei can only learn from commercial products on the market to write the first version of the prd. However, the prd review, what ushered in her is a siege of front-end, back-end, and design.


Front end: If the user deletes and restores, what is our restoration logic? How to design aging? How to display the interface?

Backend: The permissions of this scheme are involved, which cannot be achieved in this prd. It is recommended to understand our product permission role, empowerment process, and permission settings for different types of personnel.

Design: This page jumps back and forth, and the user path is up to 7 steps. This solution still needs to consider the interface call.

Mimi: ……

1023594b78f428ee333cbe17322725a6.png

Suggest:

1. Peace of mind. Novice data product managers need to learn a lot of knowledge at the beginning. Knowledge includes professional knowledge, data knowledge, and more importantly, the information knowledge that supports the problem being solved every day. Among the above-mentioned problems, some problems are caused by inexperience, some problems are caused by not learning to ask questions, and some problems are caused by incomplete supplementation of information background, which leads to decision-making mistakes.

2. Complete information & continuous learning. There is no good way, just communicate with the front and back end and design.

3. In-depth research. Completing the above can only guarantee that our plan is technically and humanly correct, but it cannot be guaranteed that our plan is unreasonable. The rationality still comes from the user, and the product needs to be continuously digging and thinking.



03   Frequent accidents, tired of fighting fire every day?


Background restoration: The project team finally started, and Meimei set a time for everyone to go online on the 3.1st.


Front end: Does the copywriting link need to be changed? Is the final copywriting confirmed?

Back-end: St has been posted, what is the grayscale strategy? When?

Test: The previous schedule was 2.25-2.28. Now some data cannot be transmitted for the engine technology upgrade. I have tested the team that was ranked in March. What should I do?

Mimi:

Guess you like

Origin blog.51cto.com/13526224/2659389