One of the challenges we face in product management world is how to say NO to the stakeholder. As a product manager, I get lot of requirements but prioritizing and selecting the right requirement is most important.
So how to say NO to the requirement which is not a value addition to the product at that point of time?
1. Understand the requirement very well.
2. Think about the customer journey
3. Analyze how the requirement is going to make an impact and which stage of the customer journey it is going to make an impact
4. There is multiple way to prioritize a requirement. It is not mandatory to select only one method to prioritize your requirement. You can use multiple filter criteria - Time to market, business value, cost cutting, technical feasibility, resource availability etc.
5. It is very important that you say to the stakeholder the analogy to say NO or YES of the requirement. Why YES or Why NO, explain that very simple way to the stakeholder. The stakeholder needs to understand and agree after your explanation.
Once I explained the reason to not select one requirement to a stakeholder, and he decided himself that the requirement is not proper for that product at that particular time. I did not make the decision; the stakeholder only made the decision based on my analysis.
No comments:
Post a Comment