Feature prioritization templates
Customizable prioritization templates are available in Aha! Roadmaps as part of your 30-day free trial.
You cannot build everything — even if you wanted to. That is why the best product plans are cohesive. You want to help the team focus on the features that will bring the highest value to customers and the company. But product plans are also dynamic. As plans shift, most product managers and engineers will have strong opinions about what to build next.
Common sources of conflict? Opinion and preference. In the absence of strategic goals and prioritization, people argue their own viewpoints and make decisions based on who has the most influence in the room.
Product teams deserve clarity and stability. Prioritization frameworks provide a more objective, repeatable way to score features in the backlog based on strategic value. The free templates included in this guide can help you be more intentional about prioritization so you can deliver new customer experiences with confidence.
These templates are a good starting point to establish a prioritization process and score features based on metrics that make sense for your business. Download and customize the templates to suit your unique needs. When you find a framework that serves the team well, consider bringing it into a roadmapping tool like Aha! Roadmaps — where you can integrate strategic planning, idea management, and feature prioritization all in one system.
What are some common prioritization criteria?
There is no one-size-fits-all prioritization framework. You will need to thoughtfully consider criteria that maps to business value — such as new conversions, customer adoption, and sales revenue. It may take some trial and error to find the right mix of factors. It is well worth the effort when you identify a prioritization framework that supports your product goals and provides transparency to the rest of the organization on how work will be prioritized.
"If you understand your goals, the customer’s challenges, and the high-level initiatives that will help you succeed, it is relatively easy to prioritize what capabilities to work on." — Lovability by Brian de Haaff
Some common criteria for prioritization include:
Will the feature help to gain new customers?
How many customers will the feature impact?
How does the feature help to increase revenue?
How does the feature help to retain customers?
How does the feature create more awareness in the market?
Let's look at an example prioritization framework. The Aha! scorecard is one of the most comprehensive available. Product managers can assign unique metrics and define an equation to score each initiative, idea, or feature. In this particular example, the equation adds sales, customer retention, and marketing opportunity while subtracting development effort.
By using a consistent scorecard that is built into your roadmapping tool, you can make quick decisions about the overall importance and relative effort for each feature.
6 versatile prioritization templates
If you are just getting started with prioritization, experiment with the six templates below. These are based on the most common product prioritization frameworks — some are fairly simple and others are more complex. Remember that greater complexity does not mean the framework is any better or more advanced. What is more important is choosing a framework that your team values and will use consistently.
The Kano model weighs customer satisfaction with feature sophistication to determine what to build now and what to deprioritize. It is especially useful for teams that are bringing a new product to market and need to understand where to focus time and energy.
The MoSCoW framework focuses on reaching consensus by sorting features into Must haves, Should haves, Could haves, and Won't haves. The goal is to deliver incremental value across each of the categories. Use either of the two templates below that visualize the MoSCoW method.
The RICE framework scores features based on Reach, Impact, Confidence, and Effort. It is another simple way to balance value against effort and minimize feature creep.
User story map
User story maps visualize the interactions a customer has with the product at every touchpoint. This comprehensive view can be used to understand which steps are in the most need of improvement in order to deliver a better customer experience.
Value vs. effort
The value vs. effort framework classifies work into four quadrants — do first, do later, delegate, and will not do. This simple method, favored by lean teams, places features in these quadrants based on the organizational effort and customer value.
Aha! is a trademark of Aha! Labs Inc. All other company and product names may be trademarks of the respective companies with which they are associated.
- What is the role of a product manager?
- What makes up the product team?
- Which tools do product managers use?
- What skills are required to be a product manager
- How do product managers work with other teams?
- How do product managers work with engineers?
- What are some product management job titles?
- What does a product manager do each day?