What is BRICE Scoring?

BRICE Scoring is a quantitative framework designed to help teams determine which tasks or features to focus on. Originally tailored for product management, its applicability extends across various business domains. The scoring methodology assesses five key criteria, enabling you to evaluate potential features or tasks against each aspect. Ultimately, this process yields a score that can be compared with other initiatives, where items with higher scores typically receive priority.

• Business Importance | Score 1–3: How closely does this work align with the company's strategic goals?
• Reach | Score 1–100% or actual #: What is the estimated number of end-users affected by this work?
• Impact | Score 0.25–3: How significant will the solution be for users after its release?
• Confidence | Score 1–100%: Based on both quantitative and qualitative insights, how confident are you that this feature will deliver the anticipated results?
• Effort | Score 1–4: How much work will be required to implement this feature, akin to T-shirt sizing?

To calculate your BRICE Score, simply use the formula: (B x R x I x C) / E. After applying this to all considered items, you will end up with a table that looks like this:

When to Apply BRICE Scoring

In my observations, many people tend to initiate the prioritization process with BRICE Scoring. However, this approach can often lead to suboptimal outcomes. BRICE Scoring should ideally be employed once you have a clear understanding of the problem you aim to address and have conducted some preliminary validation. This ensures that your evaluation is relevant and that the tasks you're considering are comparable in scope and effort.

For instance, if you're weighing the options between merely updating text on a screen or completely rebuilding an application, BRICE may not yield significant insights.

Understanding What to Build

Before implementing BRICE, you must first grasp the problem at hand. I prefer to use mind maps to identify key drivers and opportunities. For example, if you're developing an app that allows users to create custom-flavored coffee beans, and your primary goal is to boost sales, you might construct a mind map like this:

Recognizing these drivers helps you pinpoint areas of focus. When strategizing, it’s beneficial to analyze your drivers in this manner, as it clarifies the levers available for adjustment. In the previous example, if increasing purchases proves challenging, you might need to shift your attention to enhancing basket size, which could involve introducing different items, raising prices, or reducing discounts.

Mind Map Opportunity Analysis Example

You can further dissect each stage of your process to identify drop-off points, thereby revealing opportunities for improvement. Once you understand these areas, you’ll be poised to utilize BRICE Scoring effectively.

Generating and Validating Potential Solutions

Following this structured approach, you should now have clarity on the specific area to concentrate on. It’s time to brainstorm solutions with your team and validate them. Avoid the temptation to assume that your preferred solution will yield the best results. While you may have an excellent idea, it might not be the one that provides the most value, and thus shouldn’t be prioritized.

Continuing with the earlier example, if you decide to address the drop-off that occurs during the “bean flavor selection” phase, your team should investigate the underlying causes (through quantitative data, qualitative feedback, and technical error logs, for example), compile a list of potential solutions, validate them, and then apply BRICE Scoring. Only after narrowing down your list should you utilize BRICE to evaluate these ideas, which will keep the focus relevant and enhance clarity regarding the effectiveness of the options being considered.

Once you have a curated list of items, it’s time to choose a solution and either validate it further or initiate its implementation.

BRICE Scoring Template

If you're interested in experimenting with BRICE Scoring, feel free to access the template I’ve created. You can find it here.

Additional Prioritization Methodologies

I also advocate for conducting a Product Profit Impact Analysis. Learn more by reading: “Transforming Your Product Decisions: The Power of Profit Impact Analysis.”

About the Author

Kasey Kaplan is a product and strategy executive, as well as a three-time founder. At the time of this writing, he serves as the Chief Product Officer at Beforepay. He has held prominent global product leadership positions and is the co-founder of Urban FT, in addition to founding KWK Studio.