Opportunity scoring measures the gap between how important a need is to customers and how satisfied they are with current solutions. Features with high importance but low satisfaction represent your biggest opportunities.
How Opportunity Scoring Works
The formula is straightforward: Opportunity = Importance + (Importance - Satisfaction). You survey customers on two questions per feature or job-to-be-done: "How important is this to you?" and "How satisfied are you with the current solution?" Both use a 1-10 scale.
Features that score high importance and low satisfaction land in the upper-left quadrant of your opportunity chart. These are underserved needs. Features with high importance and high satisfaction are table stakes. Do not cut them, but do not invest more there either.
When to Use It
Opportunity scoring works best when you already have a customer base large enough to survey (50+ responses per segment). It pairs well with the RICE framework because it gives you the "impact" input that RICE requires. Teams that struggle to estimate impact on their own can use opportunity scores as a data-backed proxy.
Use this method when you are planning quarterly or annual roadmaps and need to decide which problem spaces deserve investment. It is less useful for sprint-level decisions where speed matters more than precision.
Running the Analysis
Start by listing 15-25 outcomes or jobs customers hire your product to do. Survey your user base on importance and satisfaction for each. Plot the results on a 2x2 grid. The upper-left quadrant is your priority zone.
Feed those priorities into a weighted scoring model to layer in effort estimates and strategic alignment. This gives you a ranked backlog grounded in customer data rather than internal opinions.
Common Mistakes
The biggest mistake is surveying on features instead of outcomes. "How important is a Gantt chart?" gets you nowhere. "How important is seeing dependencies between workstreams?" reveals the actual need. Frame questions around the job, not the solution.
Another trap: treating all customer segments equally. Power users and new users have different needs. Segment your survey data before scoring. The prioritization guide covers segmentation strategies in depth.
For comparing this approach against scoring frameworks, see the RICE vs ICE vs MoSCoW comparison to understand the tradeoffs.