Use BRICE, Not RICE Scoring for Product Prioritization.

One of a product managers main responsibilities is the prioritization of features/functionality to ensure successful product outcomes. There are several frameworks for doing this such as ICE and RICE, but in my opinion they all fall short because, perhaps intentionally, they don’t factor in the importance of a feature/function to the business/stakeholders, which is why I created BRICE Scoring.

Before I introduce the B in BRICE, I’ll first quickly explain the standard RICE framework just in case you’re not familiar with it.

RICE Scoring is a well known product management tool that can be used as a prioritization framework, which looks at four categories to help assess priority of feature/functions that will deliver the best outcome, as it relates to the end user: Reach, Impact, Confidence, and Effort. This can be an effective way to quantify what should be focused on.

I recommended that for each calculation, you document how and why you determined the (B)RICE Score. There is no perfect prioritization system and this scoring can be subjective, so it is important to document the assumptions made for others to see.

Reach

Reach helps us understand the size by thinking about how many people will be impacted by a feature/function. This is measured in two ways based on what makes the most sense for the business.

The first is between 1 and 100. Reflecting the % of users you think will be…