Opportunity Scoring Explained
A framework explainer for measuring unmet customer needs and spotting product opportunities worth validating.
Product walkthrough
Watch how Feedbackly brings product feedback into a shared board for review and prioritization.
Watch the product walkthroughSee the Feedbackly product walkthrough
Practical context for Opportunity Scoring Explained
Opportunity scoring helps teams find important customer outcomes that existing solutions satisfy poorly. It ranks unmet needs before the team chooses a feature or implementation. Define the outcome in customer terms and keep importance and satisfaction on compatible scales.
Score the customer outcome
Strategyn describes its opportunity algorithm as importance + max(0, importance − satisfaction). Its survey-based method derives importance and satisfaction from the proportion of respondents giving high ratings. Keep the measurement method explicit rather than silently substituting a different scale.
For an arithmetic illustration using a consistent 0–10 scale, importance 9 and satisfaction 4 produce 14. Importance 6 and satisfaction 7 produce 6 because the unmet-need term cannot be negative. These are hypothetical inputs, not customer research results.
Source: Strategyn: Opportunity algorithm
- +Specify the target audience.
- +Describe an outcome rather than a feature.
- +Use the same rating and aggregation method for every outcome.
Turn a score into a research priority
An outcome such as reducing the time needed to identify an incorrect invoice is more useful than a request to add an AI button. Ask how important the task is and how well the current approach works for the intended users.
Compare outcomes within relevant segments. An average across unrelated roles may conceal a strong unmet need. Keep respondent counts and uncertainty beside the score.
- +Check segment coverage.
- +Review the comments behind extreme ratings.
- +Investigate important outcomes with weak satisfaction.
Evaluate solutions separately
A high opportunity score does not establish feasibility or prove that a proposed feature will solve the need. Explore possible responses, test the strongest assumptions, and estimate delivery cost before committing.
After release, revisit the same outcome with comparable users. Check whether satisfaction with completing the task improved, not only whether people clicked the new feature.
- +Separate unmet need from implementation choice.
- +Keep effort and risk in the delivery decision.
- +Recheck the original outcome after a change.
Keep exploring this topic
These next reads help you move from the concept on this page to a framework, tool, template, or deeper comparison you can apply right away.
Questions teams usually ask
Is opportunity scoring the same as RICE?
No. Opportunity scoring focuses on important unmet outcomes. RICE compares initiatives using reach, impact, confidence, and effort. The two can support different stages of a decision.
Can we use estimated scores?
You can label them as provisional hypotheses, but do not present team estimates as customer research or apply survey-based thresholds to an incompatible scale.
Put customer feedback into practice
Use Feedbackly to collect requests, discuss customer problems, and make product status visible. Bring that evidence into your team's review process.