• Home
  • BVSSH
  • C4E
  • Playbooks
  • Frameworks
  • Good Reads
Search

What are you looking for?

Standard : Opportunity Validation Rate

Description

Opportunity Validation Rate measures the percentage of identified opportunities that are validated with evidence before being committed to the roadmap. It reflects the maturity of a team’s discovery process and their ability to focus on high-value problems.

A high rate indicates a disciplined approach to validating assumptions and reducing waste from building low-impact solutions.

How to Use

What to Measure

  • Total opportunities identified in a given period (problem statements, ideas, or feature requests).
  • Opportunities that have been validated with user research, data analysis, or experimentation.

Formula

Opportunity Validation Rate (%) = (Number of Validated Opportunities ÷ Total Opportunities Identified) × 100

Example: 20 opportunities identified, 15 validated → 75% validation rate.

Instrumentation Tips

  • Maintain a discovery backlog or opportunity register.
  • Track validation activities (interviews, surveys, data analysis).
  • Define a clear “validated” state with acceptance criteria.

Why It Matters

  • Focus: Reduces time spent on low-impact initiatives.
  • Confidence: Ensures roadmap items are backed by data.
  • Efficiency: Minimises delivery rework due to poor problem framing.

Best Practices

  • Use structured frameworks like Opportunity Solution Trees.
  • Validate with both qualitative and quantitative evidence.
  • Involve cross-functional teams in validation activities.

Common Pitfalls

  • Counting partially explored ideas as validated.
  • Skipping validation under delivery pressure.
  • Treating stakeholder opinion as sufficient evidence.

Signals of Success

  • Increased proportion of validated opportunities on the roadmap.
  • Fewer late-stage pivots or feature rollbacks.
  • Stronger alignment between roadmap items and customer outcomes.

Related Measures

  • [[CoE/Product/Measures/Discovery Effectiveness/Experiment Success Rate]]
  • [[Outcome vs Output Ratio]]
  • [[Customer Retention Rate]]

Technical debt is like junk food - easy now, painful later.

Awesome Blogs
  • LinkedIn Engineering
  • Github Engineering
  • Uber Engineering
  • Code as Craft
  • Medium.engineering