# Opportunity Scoring

Opportunity scoring compares the importance of customer outcomes with satisfaction with current solutions to identify underserved needs.

- Type: method
- Domain: Data, experimentation & growth
- Level: Intermediate
- Last reviewed: 2026-10-20
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/opportunity-scoring/>)

## What it means

Anthony Ulwick’s opportunity algorithm, used in Outcome-Driven Innovation, scores desired outcomes as importance + max\(importance − satisfaction, 0\). Inputs must use a consistent scale and method. It prioritizes unmet outcomes, rather than ranking proposed features by delivery effort or predicting business return.

## Why it matters

Teams can confuse frequent requests with important unmet needs. Comparing importance and satisfaction helps distinguish a crucial task that is already well served from one where improvement could create meaningful value.

## When to use it

Use this method when well-defined customer outcomes can be researched quantitatively with relevant respondents. It is premature when the outcomes are vague or solution-laden. Delivery sequencing still needs feasibility, cost, strategic, and dependency considerations.

## How it works

1. Identify the job and write solution-independent desired outcomes.
2. Recruit people who perform that job and understand current alternatives.
3. Ask separately about outcome importance and satisfaction.
4. Calculate comparable input scores using a documented method, such as top-two-box proportions on the same scale.
5. Apply the algorithm and inspect segment differences and uncertainty.
6. Investigate the strongest unmet outcomes before selecting solutions.

## A practical example

A reporting team uses a 0–10 scaling of survey proportions. An outcome with importance 9 and satisfaction 4 scores 14; another with importance 7 and satisfaction 8 scores 7. The team investigates the first outcome’s causes rather than automatically building its most requested feature.

## Where it breaks

The formula cannot rescue weak outcome wording or unrepresentative sampling. Aggregate scores hide segment differences and are sensitive to measurement choices. High opportunity does not establish that a proposed solution works or that serving the need will be profitable.

## Common mistakes

- Scoring feature ideas instead of customer outcomes.
- Mixing rating averages and percentage inputs on different scales.
- Treating the output as a complete delivery roadmap.

## Sources

1. [How To Discover Hidden Market Opportunities](<https://strategyn.com/outcome-driven-innovation/market-opportunity/>) — Strategyn · Original author guidance
2. [Quantify Your Customers’ Unmet Needs](<https://strategyn.com/quantify-your-customers-unmet-needs/>) — Strategyn · Original author guidance

## Related topics

- [Jobs to Be Done](<https://wiki.soroush.uk/topic/jobs-to-be-done/>)
- [Opportunity](<https://wiki.soroush.uk/topic/opportunity/>)
- [RICE Prioritization](<https://wiki.soroush.uk/topic/rice-prioritization/>)
