Member-only story
How to Choose a Product Prioritization Framework
Or combine many frameworks into one meta-framework
A lot of product management articles talk about all the choices you have when deciding how you want to prioritize the projects or features on your roadmap. However, those articles typically don’t focus on why or when you should be using one prioritization framework over another.
Product management is all about asking why (over and over again). Why does a user say they need a certain feature? Why are users unable to easily complete a given workflow? Why are users scared of clicking the “launch” button?
You can’t do every little thing users ask for. You need to understand the underlying needs.
The same is true for prioritization. You can’t just pick a prioritization method without first understanding why certain methods are better for certain situations. All those articles that detail all the options for prioritizing — they typically leave it up to you to figure out which one to actually use. Not so helpful, huh?
Let’s flip the conversation around. Ask yourself the below questions to figure out which prioritization framework might be best for you and your product. Then we can dig into how each of the methods work.
