Opportunity Scoring (popularized in Outcome-Driven Innovation contexts) helps teams prioritize based on unmet customer needs. Instead of starting with feature ideas, teams begin with desired outcomes and score each outcome by importance and current satisfaction.
A common formula is:
Opportunity Score = Importance + (Importance – Satisfaction)
High-importance, low-satisfaction outcomes are the best opportunity zones for innovation and prioritization. This shifts planning from output-centric roadmaps to problem-centric roadmaps.
Why this matters: many teams build features that are easy to ship rather than outcomes customers struggle with. Opportunity scoring reduces that bias and directs investment toward real pain.
Implementation approach:
- Define clear customer outcomes.
- Collect survey or interview data on importance and satisfaction.
- Compute opportunity scores.
- Map high-opportunity outcomes to candidate solutions.
- Prioritize experiments and delivery around those outcomes.
The method works best when outcome statements are specific and stable. Vague outcomes produce noisy data and weak prioritization.
Example: B2B Analytics Tool
Customer interviews identify outcomes:
- “Quickly identify why weekly revenue changed”
- “Share insights with non-technical teams”
- “Trust data freshness before board reporting”
Survey scores:
- Revenue-change diagnosis: Importance 9, Satisfaction 4 -> Opportunity 14
- Share insights easily: Importance 8, Satisfaction 6 -> Opportunity 10
- Trust freshness: Importance 10, Satisfaction 5 -> Opportunity 15
Roadmap implication:
- Prioritize data freshness visibility and anomaly root-cause workflows.
- Defer cosmetic dashboard enhancements.
- Build lightweight sharing improvements only after top-opportunity pain is reduced.
Opportunity scoring ensures prioritization starts from user struggle, not internal preference.