Lesson 19: Opportunity Identification

Module 2 has built an entire research and synthesis pipeline: interviews and surveys (Lessons 12–13), personas and journey maps (Lessons 14–15), pain points characterized by severity and frequency (Lesson 16), problem statements written without solutions (Lesson 17), and validated segments (Lesson 18). At this point, a team typically has more validated problems, pain points, and segment insights than it could possibly act on simultaneously. This lesson answers the natural next question: given a genuinely large pool of validated candidates, how do you systematically identify and size which ones represent the biggest actual opportunities — before committing to solve any particular one?

Opportunity identification is the practice of surfacing, characterizing, and comparatively sizing candidate problems or unmet needs, so that a team can make a deliberate choice about where to focus limited discovery and delivery resources, rather than defaulting to whichever problem statement was written most recently or championed most persuasively. This lesson sits at the seam between research (which surfaces raw material) and strategy (Lesson 10) and prioritization (Lesson 29, still ahead) — it is the disciplined practice of turning a pile of validated findings into a ranked, comparable set of genuine opportunities.

Learning Objectives

1
Define an opportunity and distinguish it from a raw pain point, a problem statement, and a solution.
2
Apply the Opportunity Solution Tree as a technique for organizing multiple candidate opportunities beneath a shared outcome.
3
Size an opportunity using both qualitative importance/satisfaction data and quantitative segment-based prevalence (Lesson 18).
4
Identify the "opportunity sprawl" failure pattern and explain why an unbounded list of opportunities is as unusable as no list at all.
5
Distinguish a genuine opportunity from a restated business goal, and explain why the latter provides no real direction for discovery.

Lesson 16 (Pain Points), Lesson 17 (Problem Statements), and Lesson 18 (Customer Segmentation). This lesson assumes you can characterize a pain point's severity and frequency, write a solution-free problem statement, and validate a segment — an opportunity, in this lesson's sense, is what emerges when these three prior artifacts are organized and compared against each other systematically.

The Core Definition, and Distinguishing an Opportunity from Its Neighbors

An opportunity is a validated, sized candidate for where a team could focus its next discovery and delivery effort — sitting conceptually between a raw pain point (Lesson 16) and a fully specified solution. It is useful to place these concepts on a single continuum:

A pain point tells you something hurts. A problem statement tells you precisely what hurts, for whom, and why it matters, without committing to a fix. An opportunity adds the comparative dimension: how does this specific, validated problem compare in size and value to every other validated problem currently competing for the same limited discovery and delivery capacity? Skipping straight from a problem statement to a solution, without ever explicitly sizing and comparing it against alternatives, means a team may invest heavily in solving a real, validated problem that turns out to be far smaller in impact than several other, equally real, validated problems that were never seriously considered.

The Opportunity Solution Tree

A widely used technique for organizing multiple candidate opportunities is the Opportunity Solution Tree (closely associated with Teresa Torres's continuous discovery methodology), which structures a team's discovery work as a tree with a single desired outcome at the root, multiple opportunities as branches beneath it, and, eventually, multiple candidate solutions beneath each opportunity:

This structure enforces a specific, valuable discipline: multiple opportunities are laid out side by side, beneath a single shared outcome, before any solution work begins for any of them. This prevents a team from tunneling into deep solution work on the first opportunity that happened to surface, without ever seeing it alongside the full set of alternatives that might have delivered more value toward the same desired outcome. The tree also visually enforces Lesson 17's discipline at the opportunity level: a genuine opportunity, like a genuine problem statement, should sit at the level of a validated user problem, with candidate solutions kept as distinct child nodes underneath it — not merged into the opportunity itself.

Sizing an Opportunity: Combining Importance/Satisfaction and Prevalence

A practical technique for sizing and comparing opportunities combines two dimensions, directly extending this module's qualitative and quantitative methods:

Importance and satisfaction gap (often gathered via a structured survey technique, sometimes called an "outcome-driven" or "importance-satisfaction" survey): asking a representative sample how important a specific job or outcome is to them, and how satisfied they currently are with existing solutions for it. A large gap between high importance and low satisfaction indicates a genuinely underserved opportunity; a job rated as unimportant, or one where satisfaction is already high, indicates a comparatively weaker opportunity regardless of how vividly it was described in a single interview.
Segment-validated prevalence (Lesson 18): how large is the validated segment experiencing this specific gap, and how does that segment's overall strategic or commercial value compare to other segments experiencing different gaps?

An opportunity that scores well on both dimensions — a large importance-satisfaction gap affecting a large, strategically valuable, validated segment — represents the clearest, highest-value candidate. An opportunity strong on only one dimension (a severe gap affecting a small, low-value segment, or a modest gap affecting a very large segment) requires the same kind of deliberate, explicit judgment Lesson 16 described for off-diagonal severity/frequency cases, rather than either automatic prioritization or automatic dismissal.

The "Opportunity Sprawl" Failure Pattern

A specific, recurring failure — closely related to Lesson 14's "too many personas" and Lesson 18's "segmentation for its own sake" patterns — is opportunity sprawl: generating an ever-growing, unbounded list of candidate opportunities from ongoing research, without ever consolidating, comparing, or pruning the list down to a manageable set the team can actually reason about and act on. A list of forty loosely characterized "opportunities," none of which have been sized or compared against each other using the importance-satisfaction and prevalence dimensions above, provides essentially the same lack of direction as having identified no opportunities at all — the volume of raw material creates an illusion of thoroughness while actually obscuring which few items genuinely deserve the team's limited attention.

The corrective discipline, directly parallel to Lesson 10's exclusion principle, is periodic, deliberate pruning: consolidating overlapping or redundant opportunities, explicitly deprioritizing (not merely ignoring) low-scoring candidates, and maintaining a genuinely short, actively reasoned-about list rather than an ever-growing backlog of undifferentiated possibilities.

Distinguishing a Genuine Opportunity from a Restated Business Goal

A final, important distinction, directly echoing Lesson 10's "mistaking goals for strategy" failure: a genuine opportunity names a specific, validated user problem or unmet need (echoing Lesson 17's problem statement discipline), while a restated business goal simply names a desired business outcome without identifying any specific underlying user-side driver. "Increase revenue by 15%" is a goal, not an opportunity — it says nothing about which validated user problem, if solved, would plausibly move that number. A genuine opportunity, sitting beneath a desired outcome in the Opportunity Solution Tree, must be specific enough to be evaluated using the importance-satisfaction and prevalence dimensions above; a restated goal cannot be evaluated this way at all, because it isn't yet a hypothesis about a specific underlying cause.

Common Mistakes to Avoid

Moving directly from a single problem statement to a solution, without comparing it against alternative opportunities

This risks investing heavily in a real, validated problem that turns out to be smaller in impact than several other equally real problems that were never seriously considered side by side.

Merging a candidate solution into the opportunity itself within an Opportunity Solution Tree

An opportunity should remain at the level of a validated user problem; folding a specific solution into the same node prematurely forecloses the comparison of multiple candidate solutions later, echoing Lesson 17's solution-contamination warning.

Sizing an opportunity using only vivid anecdote or a single interview, without importance-satisfaction or prevalence data

This repeats Lesson 16's "vivid but rare" distortion at the level of opportunity comparison, rather than pain point comparison specifically.

Allowing an opportunity list to grow indefinitely without consolidation or pruning

Opportunity sprawl produces an illusion of thoroughness while actually obscuring which few candidates genuinely deserve focused attention, echoing Lesson 14's "too many personas" pattern.

Treating a restated business goal as if it were a genuine opportunity

"Increase revenue" or "reduce churn" names a desired outcome, not a specific, validated user-side driver that could be sized and compared using this lesson's framework.

Mental Model

The Opportunity Comparison Grid

This lesson's mental model is the Opportunity Comparison Grid, plotting candidate opportunities by importance-satisfaction gap and segment prevalence/value, directly parallel to Lesson 16's Severity/Frequency Grid but operating one level up, at the opportunity-comparison stage rather than the individual pain-point stage.

Use this grid whenever more than a small handful of validated problem statements exist simultaneously: rather than defaulting to whichever one is freshest in memory or most forcefully argued, plot each candidate explicitly and let the comparison, not the loudest voice, guide where the team focuses next.

Quick Reflection Checkpoint

Key Takeaway: How will you apply "The Opportunity Comparison Grid" when evaluating trade-offs in your product decisions?

Opportunity Identification