RICE Prioritization Template
Evaluate and prioritize project and product ideas based on reach, impact, confidence, and effort.
About the RICE Template
The RICE framework (Reach, Impact, Confidence, and Effort) helps product teams evaluate and prioritize new ideas before building a product roadmap. This RICE template makes it easy to gain perspective and prioritize effectively.
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 can 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.
How do you use the RICE template?
Miro makes following the RICE framework easy with this handy template. Get started by opening the RICE template on a board, 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.
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.
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.
Get started with this template right now.
The 4-Step Retrospective
Works best for:
Retrospectives, Agile Methodology, Meetings
The 4-Step Retrospective template offers a simple yet effective framework for conducting retrospectives. It provides steps for reflecting on what went well, what didn't go well, what could be improved, and action planning. This template enables teams to systematically review past iterations, identify areas for growth, and implement actionable improvements. By promoting a structured approach to reflection and improvement, the 4-Step Retrospective empowers teams to drive continuous learning and enhancement effectively.
Product Management Onboarding Map
Works best for:
Product Management, Planning
Product Management Onboarding Map template facilitates the onboarding of new product management team members. By outlining key responsibilities, processes, and stakeholder interactions, this template helps new hires quickly acclimate to their roles. With sections for setting learning objectives and resources, it supports structured onboarding experiences, ensuring that new team members are equipped with the knowledge and tools needed to contribute effectively to product initiatives.
Customer Touchpoint Map Template
Works best for:
Desk Research, Product Management, Mapping
To attract and keep loyal customers, you have to truly start to understand them—their pain point, wants, and needs. A customer touchpoint map helps you gain that understanding by visualizing the path your customers follow, from signing up for a service, to using your site, to buying your product. And because no two customers are exactly alike, a CJM lets you plot out multiple pathways through your product. Soon you’ll be able to anticipate those pathways and satisfy your customers at every step.
Product Roadmap by Petra Ivanigova
Works best for:
Product Management, Roadmap
Plan your product journey with the Product Roadmap by Petra Ivanigova. This template helps you outline key milestones, set priorities, and visualize your development path. Use it to align your team, ensure everyone is focused on the same goals, and keep stakeholders informed. Ideal for product managers and teams looking to streamline their planning process and achieve strategic objectives efficiently.
Technology Roadmap Template
Works best for:
Agile Methodology, Roadmaps, Agile Workflows
A technology roadmap helps teams document the rationale of when, why, how, and what tech-related solutions can help the company move forward. Also known as IT roadmaps, technology roadmaps show teams what technology is available to them, focusing on to-be-scheduled improvements. They allow you to identify gaps or overlap between phased-out tech tools, as well as software or programs soon to be installed. From a practical point of view, the roadmap should also outline what kinds of tools are best to spend money on, and the most effective way to introduce new systems and processes.
Work Plan Template
Works best for:
Mapping, Project Planning
A work plan is essentially a roadmap for a project. It articulates the steps you must take to achieve the desired goal, sets demonstrable objectives, and establishes measurable deliverables. An effective work plan guides you throughout the project lifecycle, allowing you to realize an outcome by collaborating with your team. Although work plans vary, they generally contain four core components: goals, strategy, tactics, and deliverables.