A lot of the work of a product manager is communication—communication with operations, design, development, bosses, etc. So in the time-consuming communication, can the product manager find some ways to sum up experience bulk sms service and learn product knowledge, so as to avoid repeated communication but not learn anything. In this article, the author introduces the relevant methods, I hope to help you. 01 Who am I I am Zhong Qing, a product person who has been in the business for two years. I have been making B-end products and will continue to develop in the direction of B-end in the future. 02 Questions After two years of working as a B-end product, from an intern to a junior product manager, I found that bulk sms service many needs were obtained through feedback from operators, and communication work would take up a lot of time, and the rest of the work time was also used by some review meetings and third parties.
Matchmaking Divide. After a long time, I feel that I am just repeating my work, and my product skills have not improved; moreover, there will be a lot of mistakes, the requirements are not sorted out in place, and the requirements will be bulk sms service missed during the review; the relevant operations are not notified when they go online. People, resulting in insufficient service by operation personnel; then the next wave of demand comes again, and there is absolutely no space to think deeply about the product. So in order to change this working state, I reflected on the entire work process myself, and found that most of our time is spent on communication needs, and needs are the link between users and bulk sms service products, so I can continue to practice through daily needs communication Product-related skills, so how to do it? 03 How to do it 1.
Analyze requirements and think about products What needs to be done before communication, screen requirements, eliminate pseudo-requirements and bug-type requirements, and screen out valuable requirements ; then we analyze these bulk sms service requirements through our understanding of the product, and list possible implementation plans and requirements scenarios. Check existing products. 1) Why do we do this? For the product itself: screening out the valuable demand for the product can be closer to the user and increase the user's stickiness to the product. For individuals: deepen our understanding of existing products and know bulk sms service what kind of scenarios this function is ultimately designed to meet and what kind of problems users solve. 2) How to practice it? I divide requirements into four categories: bug-type requirements,