At different stages of the workplace, the focus is different. As a junior product manager, you need to clarify your own positioning and goals, practice basic skills, and don't be too ambitious.
1. Clear self-positioning
A junior product manager is generally in charge email list of a functional module or a system. First of all, he needs to be fully familiar with the module he is responsible for, and then he knows it well, so that everyone who needs to connect with this function knows that if there is a problem, just ask you to solve it. This is also The process of building influence gradually;
Secondly, after getting familiar with the module, think deeply about how different competing products of this module are doing, which grade your product is in, how far away from the best product is, and how to improve the competitiveness of this module based on the company's business;
Finally, after you have mastered the content of your own responsibility, you can continue to improve and deepen your understanding of the company's products and business with point-to-point lead, in order to gain more opportunities to undertake more important projects.
The above three processes are a progressive relationship, and it is also the different positioning of the junior product manager at different stages of work.
2. Clear work goals
For the first two years of work, in terms of personal ability improvement goals, we should focus on the three major areas of execution, communication and project management. Execution includes demand analysis, product design, and promotion of the project from the start to the launch process. In all aspects , these three pieces of content are the most basic basic skills as a product manager.
2. Requirements gathering and filtering
1. Demand pool management
The product manager's management of demand is like the chef's management of ingredients. The chef selects a reasonable combination of many ingredients and processes it into delicious food. The product manager designs the combination according to the needs put forward by many business parties and processes it into product functions.
A good demand pool management is not only to filter requirements, but also to record and summarize the work content in detail, which is conducive to orderly project management and later review. I will summarize the management content of the demand pool into three parts:
Judge and record the authenticity, importance, urgency, realization difficulty, business value and related parties of requirements
Record the current project implementation status of each requirement
Track user and data feedback after requirements are realized
As for the form template of the demand pool, I think that everyone's actual needs and habits are different, and there is no need to copy others, as long as the above three parts are covered, it can play the role of demand pool management.