Foreword: As a business support product manager, the product that has been made hard, has experienced the embarrassing situation of "the product is successfully launched, and there are few users". If there is a cause, there must be an effect. Whatsapp Database Now I will share with you the "cause" and "effect" I have summarized. 1. Product managers fail to truly understand the needs of the business Requirements comprehension is the ability of product Whatsapp Database managers to understand requirements. Different comprehension ability and understanding degree will result in different products.
If the user's needs cannot be understood, the product functions made will be "inappropriate". The user wants A function, and the product understands the B function and finally realizes it. The product that does not meet the requirements is Whatsapp Database delivered to the other party. won't buy it. If we communicate and redesign the research and development again, it will not only delay the construction period, but also cause a series Whatsapp Database of impacts such as cost consumption again. So, why does the product not really understand the needs of the business? 1. The product does not understand the "user usage scenario" The product manager needs to know what the other party wants to do in the part of the demand according to the description of the other party.
This is the so-called understanding of "user usage scenarios". In daily work, product managers need to observe and understand Whatsapp Database more "objective scenarios". When users put forward demands, they can "put themselves in their shoes" to know what they want, and design products that meet the needs of users. Take the product people of the Whatsapp Database marketing business as an example, they need to understand the entire work process of the sales staff, such as introducing to users which products of ours, when to communicate with users the best, and so on. For example: Generally, when contacting new users for the first time, the sales staff will send corresponding product introductions.