![]() ![]() Plenty of voices weigh in - like sales and engineering teams, and company leaders. But you do not do this important work in isolation. Product managers decide what to build next. Why is it important to prioritize features? It is more important to choose a framework that your team will apply uniformly across the product. One approach is no better or worse than another. The framework product teams choose is usually informed by product type, customers served, organizational culture, and individual preferences. It is also easier to communicate priorities to stakeholders and leadership when you have an agreed-upon framework for making tradeoff decisions. Frameworks can support more strategic decisions, minimize biases, and avoid analysis paralysis. What is a prioritization framework?Ī prioritization framework contains consistent criteria for product teams to use when putting features in priority order or ranking according to business value. This is where prioritization frameworks come in. That requires a repeatable, objective way to estimate the value of features. You want the features you choose to prioritize to help you achieve your product vision. The more you hone your understanding of customers, the better you are able to anticipate what they want.īut what makes product managers particularly good at feature prioritization is the ability to connect strategy to implementation. The risks involved if the underlying assumptions are wrong.įeatures with higher risk and higher perceived value should receive the highest priority-because if the underlying hypotheses related to those features are wrong (or even partly wrong), it could have dire consequences for your project.Do skillful product managers have a sixth sense? It might seem that way, especially when it comes to evaluating which product features will deliver the most value.The value you believe the feature will generate and.So, to put the proposed features in some sort of priority order, the authors suggest using a Risk Prioritization Matrix to better assess: Not everything can be implemented all at once. This should leave you with a backlog of features to implement, all of which are aligned to key business outcomes. To do this effectively, you may need to reorganize the first three columns a bit in order to better connect the dots between the proposed features and the underlying goals and hypotheses you’re hoping to achieve. Once you’ve finished brainstorming, it’s time to align each feature to at least one-and sometimes several-user outcomes. At the very least, every member on the team should suggest one feature to add to the list. Now, the only thing that’s left to do is to have the development team brainstorm all of the features that may help users achieve their desired outcomes. You should be able to fill in the first three columns based on the work you’ve already completed in your Strategic Roadmap and Personas documents. How to run this exerciseīuild a four-column table (like the one below). It’s an effective way to get development teams and key stakeholders aligned on the same set of goals and hypotheses, ideally, to inform which features to implement and in what order.īefore tackling this exercise, however, be sure to document your desired business outcomes via a Strategic Roadmap and also identify the primary Personas that you would like to target. That’s precisely what makes this exercise so valuable. And when that happens, it should normally drive meaningful results for your business, too. Fortunately, the authors of Lean UX, Jeff Gothelf and Josh Seiden, have come up with a simple exercise that can help you define and prioritize product features according to desired business outcomes.Īs a rule of thumb, the product features you implement should always enable users to achieve specific outcomes. When you find yourself in charge of a product’s strategy-much less in an uncertain or ever-changing business environment-oftentimes, the biggest challenge is identifying the right or most valuable features to implement at any given time. ![]() How to define and prioritize the right features to implement ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |