RICE Prioritization Template
Evaluate and prioritize project and product ideas based on reach, impact, confidence, and effort.
About the RICE template
The RICE template helps you evaluate and prioritize new ideas. Product teams often use it to gain perspective before starting their product roadmap.
Your typical product roadmap contains a ton of moving parts — lots of exciting ideas that your team might be eager to implement ASAP. Using the RICE template, you make sure that you stay on track throughout the entire process. You’ll be able to prioritize the most important tasks and focus on creating a product roadmap that’ll bring you the most success.
What is a RICE framework?
When you think about your ultimate goal, delighting your customers, it’s hard not to get overwhelmed with all these new ideas. Teams might be tempted to dive right into the cleverest ones first without considering the potential lift. When there’s so much to consider, how do you determine priorities?
This is where the RICE prioritization framework can help.
The RICE acronym stands for reach, impact, confidence, and effort — four factors to help you evaluate and prioritize ideas. It’s a prioritization process that allows your team to consider each project and assess its feasibility. When used correctly, it can have a massive impact on the direction and growth of your business.
When to use RICE
RICE is an adaptable scoring model. It forces you to think through how and why a project idea will or will not have an impact. It removes some of the emotion from the decision-making process, making it easier for teams to come to a consensus.
Here are some common scenarios where using the RICE framework template can be helpful for teams:
You’re struggling to narrow down your ideas. Working in a team is great, but it often means that you have various ideas and suggestions to contend with. To help you impartially decide between several compelling ideas, use the RICE method.
You need to assign priorities in a product roadmap. A product roadmap outlines the direction and vision for your project line over time. Chances are, your product roadmap will feature a variety of ideas and suggestions. To narrow down your ideas and help your business grow as quickly as possible, use the RICE framework. Putting your ideas in the framework will show you what to prioritize.
Your team doesn’t agree. When your team is struggling to align or agree on new ideas, the RICE method is a simple way to get everyone together for a productive discussion.
You’re about to start a new project or launch a new product. Many teams find it useful to employ RICE at the beginning of each major project or when planning a new product launch. It helps them narrow down their ideas and focus on the most important aspects of the new project or product launch.
How do you use the RICE template?
With Miro, making a RICE framework is easy. Our whiteboard tool is the perfect canvas to create and share your RICE model with the rest of your team and any key stakeholders that might want to take a look.
Get started by selecting this RICE template, then take the following steps:
1. Evaluate the reach of a project. How many people will the project affect? Will your customer see a direct impact? Typically, teams measure reach as the number of people impacted or the number of events occurring in a given period of time.
For some teams, this means customers per quarter. For others, page views per month. It’s important to quantify this value with real data, such as product metrics. Remember, the outcome of this exercise is a numerical value that will help you prioritize tasks.
2. Think about the impact of the project. If reach is how many people will be affected by this project, impact measures the effect itself. Let’s say you’re launching a new paid feature in your app. reach is the number of people affected by this launch, while impact is how likely the launch is to convert them to paying customers.
Unlike reach, impact can be difficult to quantify. Many teams evaluate impact scores using a scale from 1 to 3. 1 is low impact, 2 is medium, and 3 is high.
3. Define your confidence score. How confident are you that this project will have the desired impact? It might be the greatest idea you’ve ever had, but if you don’t have the data to corroborate its success, it might not make sense to work on it right now.
Your confidence score is evaluated as a percentage. 100% is total confidence, 80% signifies optimism but not total certainty, and 50% is low confidence. Anything under 50% is very low.
4. Think about effort. What’s the total time it will take to complete this project? To evaluate effort, don’t just think about the project itself, but also think about the teams who will contribute. It might take four days to complete the project as a whole, which breaks down into ten hours for engineering, 12 hours for marketing, and so on.
Your effort score is measured in person-months or the work that one team member can execute in a month.
5. Calculate your score. To get a RICE score for a particular task, perform the following simple calculation:
Reach x Impact x Confidence / Effort
A higher score indicates that you’ll get more value for your time. In other words, you’ll spend less time working on it but yield the best results.
Although a lower score suggests less value, it doesn’t mean it’s not important. Park it for now and return to it when the time is right. For now, you need to focus on your top priorities, which will be the tasks with the higher scores.
6. Repeat the process for each task. Compile a list of tasks and scores to assess your priorities. By the end of this process, you’ll have a clear idea of what to do going forward.
Who invented RICE prioritization?
The RICE model was invented by Intercom. Or, more specifically, Sean McBride co-developed the framework as a product manager at Intercom. Since its inception, it’s been widely used by businesses from a variety of industries.
How is the RICE score calculated?
Your score is calculated using the following RICE formula: Reach x Impact x Confidence / Effort. With this formula, businesses can figure out whether their ideas and initiatives are worth including in their roadmaps.
What is the RICE method for prioritization?
The RICE method for prioritization determines which of your ideas, concepts, or products to focus on. It’s split into four categories: reach, impact, confidence, and effort. You then use these categories to calculate the RICE score. Using this method, you effectively prioritize which ideas are right for your business. It helps you focus your efforts on initiatives that are more likely to help your business succeed.
Is a higher or lower RICE score better?
With the RICE scoring model, bigger is better. Why? Because the bigger the score, the more value you’ll get. Having a high RICE score indicates that you have a successful idea on your hands. It’ll likely require less effort and time than some of your other ideas, giving you some quick wins. A low RICE score implies the opposite. Your idea might not be as successful, and it might require more time and effort to bring it to life.
How do you prioritize a roadmap?
There are lots of ways to prioritize product roadmaps. When using RICE, you’ll use the existing framework as guidance. This means you’ll use the RICE scoring method to identify which ideas and concepts to prioritize in your roadmap.
Product/Market Fit Canvas Template
Works best for:
Market Research, Strategic Planning, Product Management
The product/market fit canvas template is used to help product teams meet customer and market needs with their product design. This template looks at a product in two dimensions: first, how the product fits user needs, and second, how the fully designed product fits within the market landscape. This combined metric understands a product holistically from the way customers use and desire a product, to the market demand. By comparing customer and product qualities side by side, users should better understand their product space and key metrics.
HEART Framework Template
Works best for:
Desk Research, Project Management, User Experience
Happiness, Engagement, Adoption, Retention, and Task Success. Those are the pillars of user experience — which is why they serve as the key metrics in the HEART framework. Developed by the research team at Google, this framework gives larger companies an accurate way to measure user experience at scale, which you can then reference throughout the product development lifecycle. While the HEART framework uses five metrics, you might not need all five for every project — choose the ones that will be most useful for your company and project.
Project Proposal Template
Works best for:
Project Management, Documentation, Project Planning
For any type of project, the Project Proposal template can be a crucial step toward clarifying the context, goals, and scope of a project to get stakeholder buy-in. A project proposal outlines what you want to accomplish, your goals, and how you plan to achieve them. Generally, a project proposal gives the reader some context on the project, explains why it is important, and lists the actions that you will take to complete it. Project proposals have myriad uses. Often, businesses use project proposals to get external buy-in from a donor or outside stakeholder. But many companies draw up project proposals for internal buy-in too.
Product Roadmap Template
Works best for:
Product Management, Roadmaps
Product roadmaps help communicate the vision and progress of what’s coming next for your product. It’s an important asset for aligning teams and valuable stakeholders – including executives, engineering, marketing, customer success, and sales – around your strategy and priorities. Product roadmapping can inform future project management, describe new features and product goals, and spell out the lifecycle of a new product. While product roadmaps are customizable, most contain information about the products you’re building, when you’re building them, and the people involved at each stage.
User Story Map Template
Works best for:
Marketing, Desk Research, Mapping
Popularized by Jeff Patton in 2005, the user story mapping technique is an agile way to manage product backlogs. Whether you’re working alone or with a product team, you can leverage user story mapping to plan product releases. User story maps help teams stay focused on the business value and release features that customers care about. The framework helps to get a shared understanding for the cross-functional team of what needs to be done to satisfy customers' needs.
Research Topic Brainstorm Template
Works best for:
Desk Research, Brainstorming, Ideation
Coming up with a topic for a research project can be a daunting task. Use the Research Topic Brainstorm template to take a general idea and transform it into something concrete. With the Research Topic Brainstorm template, you can compile a list of general ideas that interest you and then break them into component parts. You can then turn those parts into questions that might be the focus for a research project.