![]() ![]() ![]() While it is important to listen to the sales team as they are closest to interacting with customers, features shouldn’t be prioritized in a very reactionary manner without considering the long-term value it will add to the customer. Sales and Support Requests: They are often the loudest people at the table and can be difficult to ignore. All too often product managers fall prey to HiPPO ( Highest Paid Person’s Opinion) and prioritize features that have no lasting value in the development of products. In large organizations, with multiple stakeholders with different levels of investment and control, people in higher positions can insert their choices or opinions without the necessary data or understanding and consequences. Every single feature idea represents someone’s hard work and opinion. Personal Biases: The decision to build a particular feature is oftentimes not just a product decision, but a personal one. This is largely due to the haphazard nature in which feature requests come in and not having standardized ways to measure the impact of working on a particular feature. ![]() In a study conducted by Mind the Product Survey, 49% of product managers said that their biggest challenge was not being able to conduct proper market research to validate whether the market truly needs what they are building. In this article, we will look at some of the best ways to prioritize features and the visual tools you can use to align teams and make collective decisions on how to manage your product backlog. Prioritizing potential features from a long list means deciding on what’s important, realistic, and urgent. A list of good feature ideas may be endless but time, resources, money, and energy are not. Product management has many moving parts, but any product manager will tell you that the hardest part of the job is deciding what to build when. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |