post

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Guest Post

How to build a companion product and win user trust

mission statement

Deep dive: Crafting your product vision and mission

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Join us at #mtpcon London in 2025 – mark your calendars

Connecting fans to creators at Spotify (Dariusz Dziuk, Product Lead, Spotify)

Why teams often struggle with OKRs: A conversation with Jeff Gothelf

5 ways to invent and simplify as an AI/ML product manager

<a href="http://jonathanwaddingham.com">Jonathan Waddingham</a> is an independent product consultant, who runs Products with Purpose. He helps tech for good startups and charities define, refine, and grow their digital products and services. Prior to consulting, he product-managed JustGiving Crowdfunding from an idea to raising over £100m in five years. You can say hi on <a href="https://twitter.com/jon_bedford">Twitter</a> or <a href="https://www.linkedin.com/in/jonathanwaddingham/">LinkedIn</a>.

Jonathan Waddingham

The great thing about technology is that anything is possible. But when anything is possible, how do you decide what to do? And, arguably more importantly, how do you decide what not to do? Every one of my clients struggles with this paradox of choice. Whether a small or large charity, Seed, Series A funded, or mature startup, deciding what to build is hard.
It’s hard because we’re human and we underestimate the time it takes to do things. We also place a higher value on our own ideas and don’t like making trade-offs (the list of <a href="https://en.wikipedia.org/wiki/List_of_cognitive_biases" target="_blank" rel="noopener noreferrer">cognitive biases</a> on Wikipedia is bewildering). But it’s not impossible. Here are some methods that help solve the prioritisation problem, depending on how product teams work and what they need.
<h2>Effort and Reward</h2>
I believe that the simplest solution is usually the best. And the simplest way to prioritise work is by giving each idea a score related to effort and reward and plotting them on a grid, grading each as high, medium or low.
<table>
<tbody>
<tr>
<td></td>
<td>Low Reward</td>
<td>Medium Reward</td>
<td>High Reward</td>
</tr>
<tr>
<td>Low Effort</td>
<td>Idea 3</td>
<td>Idea 1
Idea 5</td>
<td>Idea 7</td>
</tr>
<tr>
<td>Medium Effort</td>
<td>Idea 6</td>
<td>Idea 9</td>
<td>Idea 10
Idea 14</td>
</tr>
<tr>
<td>High Effort</td>
<td>Idea 11
Idea 13</td>
<td>Idea 4</td>
<td>Idea 2</td>
</tr>
</tbody>
</table>
&nbsp;
Once you’ve done this, it’s easy to see where you should prioritise your efforts. Anything in the top right, like ‘idea 7’, should go straight to the top of your roadmap. If the table is a tree, that’s where you’ll find the metaphorical low hanging fruit.
This is a good method for ballpark-sized estimation where there are a lot of unknowns. And not only does it help a product team to decide what to do, it’s an enormous help to demonstrate to your wider stakeholders why you’re not doing something.
<h2>The ICE method</h2>
Not all predictions of reward are equal, and when there’s a large degree of uncertainty about the chance of competing ideas having an impact, you might need more help to prioritise. This is where the ICE method helps.
ICE stands for Impact, Confidence, and Effort. With this method (made popular by <a href="https://www.slideshare.net/seanellis/building-a-companywide-growth-culture-saastr-annual-2016/17-Prioritize_by_ICE_Score_Focus" target="_blank" rel="noopener noreferrer">Sean Ellis</a>), you rate each idea on a numeric scale, usually 1-10, and then calculate a score for all ideas using the following equation:
ICE score = Impact x Effort x Confidence.
Here’s how that might look for your product:
<table>
<tbody>
<tr>
<td></td>
<td>Impact</td>
<td>Confidence</td>
<td>Effort</td>
<td>ICE rating</td>
</tr>
<tr>
<td>Idea 1</td>
<td>6</td>
<td>2</td>
<td>8</td>
<td>96</td>
</tr>
<tr>
<td>Idea 2</td>
<td>8</td>
<td>7</td>
<td>3</td>
<td>112</td>
</tr>
<tr>
<td>Idea 3</td>
<td>3</td>
<td>9</td>
<td>1</td>
<td>27</td>
</tr>
<tr>
<td>Idea 4</td>
<td>5</td>
<td>4</td>
<td>3</td>
<td>60</td>
</tr>
</tbody>
</table>
&nbsp;
Here we see that Idea 2 is the clear winner, and should be prioritised. Had we been only comparing ideas with Effort and Reward, we might have chosen Idea 1 as it would be classed as medium impact and low effort, whereas Idea 2 is high impact and low effort.
This is where adding confidence levels helps you get more granular with your decision making and potential. Depending on your preference, you could use a 1-5 scale, or divide your ICE rating by 3 to get a smaller average score that’s easier to compare.
While ICE is definitely a cool tool to use, you might find that you need a more substantial method to meet your hunger for prioritisation. This is where RICE can help.
<h2>The RICE Method</h2>
RICE is simply the same as ICE but with an added ‘R’ for Reach.  This method is helpful if it’s important to understand how many of your customers a given feature will benefit.
You can calculate a RICE rating by multiplying your ICE score by reach (<a href="https://www.intercom.com/blog/rice-simple-prioritization-for-product-managers/" target="_blank" rel="noopener noreferrer">Intercom recommends</a> another method) but it doesn’t really matter as long as you’re measuring each idea consistently.
So let’s add Reach to our previous example and see if the RICE is right.
<table>
<tbody>
<tr>
<td></td>
<td>Impact</td>
<td>Confidence</td>
<td>Effort</td>
<td>Reach</td>
<td>RICE rating</td>
</tr>
<tr>
<td>Idea 1</td>
<td>6</td>
<td>2</td>
<td>8</td>
<td>100</td>
<td>9600</td>
</tr>
<tr>
<td>Idea 2</td>
<td>8</td>
<td>7</td>
<td>3</td>
<td>50</td>
<td>5600</td>
</tr>
<tr>
<td>Idea 3</td>
<td>3</td>
<td>9</td>
<td>1</td>
<td>1000</td>
<td>27000</td>
</tr>
<tr>
<td>Idea 4</td>
<td>5</td>
<td>4</td>
<td>3</td>
<td>200</td>
<td>12000</td>
</tr>
</tbody>
</table>
&nbsp;
Suddenly ideas 3 and 4 are looking better after all. Scrap that roadmap, it’s time to pivot!
Well, in the oft-used words of any product professional, it depends. While these are made-up examples and numbers, it does demonstrate that these are just ways to help you prioritise based on broad measures, and what’s most important for any given product could be different – and can certainly change over time.
<h2>Prioritising Your own way</h2>
I recommend that product teams start by keeping prioritisation as simple as possible, and get more granular as the results aren’t different enough or if the business context changes. If, for example, your Q1 priority is to increase paid users, then you might add another column to ICE that relates to whether an idea affects paid customers. Or if your Q2 priority is increasing acquisition, you might add a filter that decreases a score if an idea doesn’t affect acquisition. Equally your definitions of Impact or Reward could be different depending on your product goals, so you can bake in your own priorities into those scores.
There is no way to remove risk from a prioritisation process and ensure 100% certainty in your outcomes, but the methods above can certainly help you reduce risk and make better informed decisions about what to prioritise. But as with any methodology, the one that works best is the one that works for you and your team.

core/freeform

Startup Roadmaps and Prioritisation, by Ahmed El-Sharkasy

Evidence-Based Product Backlogs, by John Pagonis

Roadmaps & Prioritisation – Lessons Learnt the Hard way, by Ren Yi Hooi

Embracing the Art of Prioritisation by Emily Tate

How to Start a Bank from Scratch by Megan Caywood

How to Start From Scratch and Prioritise by Marcel Britsch

Courtney Wylie – Building Your Business Model When Your Customer is not Your User

Three Simple Ways to Make Product Prioritisation Easier

Jonathan Waddingham

Read more

Comments