Product managers often face demands from all directions, such as from company executives, business parties, user research feedback, and so on. How to judge which creative ideas are worth investing in development resources, usually PM will use MRD to complete this work, which is to evaluate product opportunities. In fact, it is very similar to the "demand source analysis" that I encountered in my work.
After evaluating and identifying product opportunities, it is also necessary to explore product solutions, including but not limited to product design focus, product process, interactive experience, etc., that is, "defining the product to be developed".
I will adopt agile development methods, that is, small steps and fast iterations, first looking for an MVP solution, that is, clarifying the core value of the product, and iterating the content of one core value with one version. This requires PM to understand what users want based on the company's business, and then to think about the essential requirements (purpose, value, action, verification).
For new product novice, one of the lessons I have concluded is: always keep thinking about requirements instead of project management. That is, don't spend too much time rushing around with development to solve problems, but spend more time thinking about the requirements themselves. The month I first became a product manager, I often thought of myself as a "project manager."
It is very typical that one's own needs are small, but he always pushes this and pushes that, and he does not think enough about needs.
Because people will always indulge in the "excitement of being able to solve problems", such as the feeling of finding the user's problem with the developer and solving the problem together with the developer, which is a very happy feeling. I remember that at that time, I was sorting out the introduction of the caliber, and spent the whole afternoon with the test to find the problem with the wrong caliber and solve it. At that time, I felt so happy that a country email list problem was solved.
But when my mentor asked me what I did all afternoon, and I answered this, she asked me "Did you feel happy and excited? But what did you learn?" It didn't seem to be.
Therefore, don't get immersed in this excitement. When you are a PM, you should think through each requirement step by step: think about the scenario, how the user's needs come, how to meet, which method is more suitable, and how to Qia...Although it is really difficult compared to "solving problems with development", but you have to step out of your comfort zone and gradually overcome it. After 3-5 months, you will find a different self!