How to Pick the Right Feature Prioritization Framework

As product management professionals making informed decisions about what features to develop next is crucial. This is where feature prioritization frameworks come into play. They provide a structured approach to decision-making, helping teams focus on what matters most to the business and the users.

Here is a reference list of frameworks, many of which I've used throughout my career, and a few others that I've encountered and tweaked to make it effective for the size, stage, culture and goals of the organization. At the end of this article there is also links to some tools that can help with implementing your framework(s) of choice.

In the end it could be best to combine frameworks to arrive at the right blend for your needs. Note the list I have below is not exhaustive, please comment if you have suggestions to add or clarify frameworks or tools.

Expanded Details

Value vs. Effort (Complexity)

This is a simple to use framework and provides a good overview of the value and effort involved in each feature. The framework scores features based on their value and effort, and the scores can be easily plotted on a graph to see which features are the most important.

Go deeper at https://www.productplan.com/glossary/value-vs-complexity/

RICE Framework

The RICE framework is simple to use and provides a good balance of quantitative and qualitative factors. The framework scores features based on their Reach, Impact, Confidence, and Effort, and the scores can be easily calculated and compared.

Go deeper at https://roadmunk.com/guides/rice-score-prioritization-framework-product-management/

Weighted Scoring?

The Weighted Scoring framework is a more flexible framework that can be used to prioritize features based on a variety of factors. The framework allows product managers to assign weights to different factors, such as value, effort, and risk. This can help to ensure that the most important features are prioritized, even if they are not the easiest or cheapest to implement.

Go deeper at https://productfolio.com/weighted-impact-scoring/

ICE Scoring?

The ICE Scoring framework is similar to the RICE framework, but it uses Impact, Confidence, and Effort instead of Reach, Impact, Confidence, and Effort. The ICE framework is a bit simpler to use than the RICE framework, but it can be less accurate.

Go deeper at https://jexo.io/blog/backlog-prioritization-techniques-ice-method/

Opportunity Scoring?

The Opportunity Scoring framework is used to prioritize features based on the potential opportunity they represent. The framework scores features based on their potential impact, their likelihood of success, and their cost. This can help product managers to identify features that have the potential to generate the most value for the business.

Go deeper at https://storiesonboard.com/blog/best-prioritization-models#2-opportunity-scoring

Kano Model?

The Kano Model is a more complex framework that is used to understand customer needs and expectations. The framework divides features into five categories: Must-be, One-dimensional, Attractive, Indifferent, and Reverse. This can help product managers to identify features that will delight customers and features that are simply expected.

Go deeper at https://www.prodify.group/blog/a-product-managers-guide-to-the-kano-model

Story Mapping?

Story Mapping is a framework that is used to visualize the customer journey and identify the features that are needed to improve the customer experience. Story Mapping is a more qualitative framework, but it can be a valuable tool for understanding customer needs and prioritizing features.

Go deeper at https://www.aha.io/roadmapping/guide/release-management/what-is-user-story-mapping

MoSCoW?

The MoSCoW framework is often used for early-stage prioritization. The framework divides features into four categories: Must-have, Should-have, Could-have, and Won't-have. This makes it easy to quickly identify the most important features and focus on those first.

Go deeper at https://productschool.com/blog/product-fundamentals/complete-guide-feature-prioritization-fast-growing-startups

Priority Poker?

Priority Poker is a relatively new framework, but it is gaining popularity because it is a quick and easy way to get estimates from a team of developers. For each item you outline the idea/milestone/etc., and then everyone determines how important that particular idea is using one of their numbered cards. While a fun and collaborative way to get a party started. Finalizing priorities using this method would not be my choice.

Go deeper at https://airfocus.com/blog/priority-poker-guide/

HiPPO?

The HiPPO framework is used to prioritize features based on the opinion of the Highest Paid Person in the Organization. The HiPPO framework is a bit tongue in cheek, but it's seen in organizations where there is a lot of politics and control. This form of prioritization rarely ends well for all concerned.

Go deeper at https://www.productboard.com/blog/dangerous-animals-product-management-infographic/

??? Tools for Gathering Requirements and Prioritization

There are several tools available that can aid in the process of gathering requirements and prioritizing features. The list below is in alphabetical order. I've evaluated most of these so feel free to DM me if you want my opinion on any of them.

• Aha!
• airfocus
• ClickUp
• Craft.io
• Harvestr
• ProdPad
• Productboard
• ProductPlan