The review after completing a project is extremely important for product managers. It can help you find the key problems of failure and make constructive bulk sms service suggestions. A product manager who doesn't know how to review, either relies on talent to really do a good job, or is a blind cat and kills a mouse, or only can do functions. The value of job resumption 1. As a reporting tool Report to your boss regularly in a “review” way, telling your boss how the output of the project he allows you to put in resources is. [Good job] The boss's trust in you is intensified. He sees your abilities, and he will be more assured to give you more projects and more responsibilities in the bulk sms service future. [Do not do well] Don't be afraid that your boss will think that you "can't do it". If you have done a good review, you can find the key problems of failure, and you can put forward constructive suggestions.
He will think that you "know what you are wrong." , great potential. 2. Produce as your own regular results During the interview, the interviewer always grabs a key project and asks you the result of the project with "STAR". If it is a project you are responsible for bulk sms service alone, it can explain your business ability; if it is a project you cooperate with, then further ask you if you know why the project can achieve the goal, how to achieve the goal, and see if you have the vision and experience of the relevant experience. experience. Therefore, a review allows you to regularly summarize your work results and give you a sufficient basis for demonstrating your abilities both internally and bulk sms service externally. 3. As a ladder for your own growth In product work, our products are always making choices to ensure that they are making "the most correct/appropriate decision under a certain period, certain situation, and certain resources".
So what is "correct?" This is the hardest to explain. Some of the correctness is based on the product manager's understanding of people and economic bulk sms service models, and some of the correctness is proved by experience and experience. The review of requirements is precisely to use data to summarize whether the previous choices are correct. We also use the results of the review to determine whether this function and thinking can be extended to other similar scenarios, requirements, and product designs. I very much agree with this. Just imagine, if a product manager has an bulk sms service inner awareness of a choice that has no risk and probability of success at all, how to make an appropriate choice? Where does this awareness of risk and probability of success come from? If it is a function,