◀ Stage Select World 2 · Stage 2-03

Opportunity Analysis

Find problems worth solving before writing a line of code

The most common product mistake is falling in love with a feature idea instead of the user problem behind it. This guide teaches you to spot real opportunities, size them, and prioritize them with simple, repeatable frameworks.

Ready?

Step-by-step lessons

Master Opportunity Analysis

Four short lessons: what an opportunity is, how to map it, how to size it, and how to prioritize it.

1

Opportunities vs. Solutions

The classic beginner trap: falling in love with a solution (a specific feature idea) instead of the opportunity, the unmet pain, need, or desire behind it. Staying in the problem space first saves you from building things nobody needs.

Everyday example, "a faster horse"

There's a famous line attributed to Henry Ford: "If I'd asked people what they wanted, they'd have said a faster horse." A faster horse is a solution. The real opportunity underneath it was "I need to get places quicker and more comfortably", and the car served that far better than any horse could. When users ask for a specific feature, they're handing you their guessed solution. Your job is to dig out the opportunity beneath it, because a better solution than the one they named often exists.

The doctor analogy

A patient walks in with severe muscle cramps and demands a specific pill they saw in an advertisement, that's the solution.

A good doctor doesn't just hand it over. They ask questions, run tests, and discover the patient is severely dehydrated, that's the opportunity. Treating dehydration fixes the problem for good; the pill alone would fix nothing.

Rule: never prescribe a feature without diagnosing the opportunity first.

Quick check

You work on a fitness app. Which of these is an opportunity, not a solution?

2

The Opportunity Solution Tree

To keep problems and solutions organized, product discovery expert Teresa Torres created the Opportunity Solution Tree, a simple map that flows top-down in four levels:

Everyday example, planning to save money

Imagine a tree for "save $200 a month" (the outcome, at the top). Branch into the reasons you're not: "eating out too much," "forgotten subscriptions," "impulse shopping" (the opportunities). Under each, list ideas: for eating out, "meal-prep Sundays," "a lunch budget app" (the solutions). Then try one for two weeks and see if it sticks (the experiment). The tree keeps you from jumping straight to a random idea ("download a budgeting app!") before you even know which problem is costing you the most.

1

Desired outcome

A measurable business target. "Increase food-delivery retention by 10%."

2

Opportunities

Unmet user needs blocking that outcome. "Food arrives cold."

3

Solutions

Feature ideas that might resolve each opportunity. "Text directions, 3D maps."

4

Experiments

Cheap tests, A/B tests, interviews, to find which solution actually works.

Quick check

Your tree's outcome is "Boost user retention by 12%." Where does the task "Run an A/B test comparing two checkout layouts" sit?

3

Sizing Up Opportunities

Not all user problems deserve your team's time. Before committing resources, score each opportunity on three questions:

Everyday example, which pothole to fix

A city can't fix every pothole at once, so it picks wisely. A deep crater on a busy main road that wrecks tires (many people hit it, and it hurts a lot) gets fixed first. A small crack on a quiet dead-end street waits. The opportunity score does the same math for user problems: a pain that's important to many users and badly served today is your main-road crater, the sweet spot. A pain that's minor, or that competitors already solve well, is the quiet-street crack. Fix the craters first.

How many?

User demand

What share of your users hit this problem, 70% or 5%?

How bad?

Pain severity

Is it a workflow-breaking blocker causing uninstalls, or a minor annoyance?

Who else?

Market gap

Can users solve it elsewhere easily, or would fixing it set you apart?

The opportunity score

The sweet spot is a need with high importance but low satisfaction with today's alternatives:

Score = Importance + Max(Importance − Satisfaction, 0)

Quick check

A problem is very important to users (importance = 9/10), but competitors already solve it brilliantly (satisfaction = 9/10). What's its opportunity score?

4

Prioritizing with RICE

To take emotion and politics out of roadmap debates, many teams score every idea with the RICE framework. It's just a way of turning gut feelings into a number everyone can compare fairly.

Everyday example, picking a home project

Deciding between home improvements, you weigh four things. Reach: how many rooms does it affect? (Rewiring the whole house vs. one closet.) Impact: how much nicer will life be? Confidence: how sure are you it'll actually work out? Effort: a weekend or three months? A project that helps every room, a lot, reliably, in a weekend beats one that helps one closet, slightly, maybe, over months. RICE literally divides the payoff (reach × impact × confidence) by the effort, so quick wins with wide, confident benefit rise to the top, and expensive gut-feel bets sink.

The formula

RICE Score = (Reach × Impact × Confidence) ÷ Effort

Reach, how many users it touches in a given period.

Impact, how much each user gains (scored 0.25 to 3).

Confidence, how solid your evidence is (100% = strong data, 50% = educated guess).

Effort, the cost to build, in person-months.

Quick check

A riddle: "I am the truth-teller of the RICE formula. When a stakeholder overhypes a feature's reach and impact on pure gut feeling, scoring me honestly, based on verified research only, drags the final score back down to reality. Who am I?"

Review the concepts

Opportunity Analysis Flashcards

Four cards covering the vocabulary, the tree, and the two scoring formulas. Click to flip.

Click to flip

Tip: say the answer out loud before flipping.

Explanation

In practice

1 / 4
Did you recall it?
Apply what you learned

Practice Scenarios

15 situations that test whether you can stay in the problem space, size opportunities, and prioritize with RICE. Pick the strongest move, then read why the others fall short.

Scenario 1easy

A high-value enterprise customer threatens to churn unless you build a custom 'PDF Export' feature that isn't on your roadmap.

What is your first step?

Scenario 2easy

Food-delivery users complain their food arrives cold because drivers get lost inside large apartment complexes. You start an Opportunity Solution Tree with the outcome 'raise delivery satisfaction to 95%'.

Where does 'drivers lose time in the final 100 meters' belong on the tree?

Scenario 3easy

A stakeholder proposes a Bluetooth smart-water-bottle integration to boost activity logging in your fitness app.

What does a RICE evaluation most likely reveal?

Scenario 4easy

You must choose between two opportunities. Opportunity A: importance 8, satisfaction 7. Opportunity B: importance 7, satisfaction 2.

Which scores higher, and why?

Scenario 5easy

Two features have similar Reach, Impact, and Effort. But one is backed by solid usage data and interviews; the other is a hunch from a single loud meeting.

How does RICE separate them?

Scenario 6medium

A PM writes this "opportunity" on the tree: "Build an AI recommendation engine."

What's wrong with it as an opportunity?

Scenario 7medium

Your team found a real, painful problem that only affects about 0.5% of users — but for those few it's a total blocker.

How should you weigh it?

Scenario 8medium

A stakeholder games the RICE scores: they quietly inflate Reach and Impact and lowball Effort for their pet feature so it tops the list.

What's the right way to protect the process?

Scenario 9medium

During research you uncover 15 distinct user pains for one outcome. Leadership wants you to tackle all 15 this quarter.

What does the Opportunity Solution Tree encourage instead?

Scenario 10medium

You have a promising opportunity and three candidate solutions. A teammate wants to fully build the most exciting one right away.

What does the tree's 'experiments' layer suggest?

Scenario 11hard

Sales relays that "customers keep asking for a dark mode." You investigate and find the underlying complaint is eye strain during long night shifts.

Why does distinguishing these matter?

Scenario 12hard

An opportunity scores high on importance and low on satisfaction — a jackpot. But when you size the effort, any real solution would take 18 months and a new team.

How should this affect your decision?

Scenario 13hard

A leader says: "RICE scores are just made-up numbers — they give false precision. Let's not bother."

What's the balanced defense of RICE?

Scenario 14hard

You're comparing two features. Feature X: Reach 1000, Impact 1, Confidence 100%, Effort 2. Feature Y: Reach 500, Impact 3, Confidence 80%, Effort 5.

Which has the higher RICE score?

Scenario 15hard

Your opportunity tree has an outcome ("increase retention 10%") but a teammate keeps adding opportunities like "users on Android" and "enterprise customers."

What's the confusion, and how do you fix the tree?

Lock it in

Guess the Term

Read the clues and name the concept. The fewer clues you need, the more points you score.

Round 1 Score 0
Keep it handy

Opportunity Analysis Quick Reference

The formulas and the tree on one screen, perfect for a two-minute refresher.

Sizing & Scoring

Quantify the size of the prize before committing your team.

Opportunity score

Score = Importance + Max(Importance − Satisfaction, 0). Jackpot: high importance, low satisfaction.

1

User demand

What percentage of active users hit this problem?

2

Pain severity

Minor annoyance or core workflow blocker?

3

Market gap

How well do competitors already solve it?

The Opportunity Solution Tree

Teresa Torres's map keeps discovery tied to metrics. Always read top-to-bottom.

1

Outcome

The measurable north-star target. "Boost checkout conversion 12% in Q4."

2

Opportunities

Human pains blocking the outcome. Never phrased as features.

3

Solutions & experiments

Feature ideas per opportunity, validated with cheap tests before big builds.

RICE formula

(Reach × Impact × Confidence) ÷ Effort, confidence is your honesty gate.

RICE, Factor by Factor

Score each honestly, the formula is only as good as the inputs.

R

Reach

How many users per period? Count them from real data.

I

Impact

How much per user? Use a scale: 3 = massive, 1 = medium, 0.25 = minimal.

C

Confidence

How solid is the evidence? 100% = data, 80% = some, 50% = a guess.

E

Effort

Person-months to build. The divider, cheap wins rise.

Example

(1000 × 1 × 1.0) ÷ 2 = 500 beats (500 × 3 × 0.8) ÷ 5 = 240.

Traps to Avoid

Where opportunity work goes wrong.

Falling for a solution

A feature request is a guessed answer. Find the pain beneath it first.

Segments as opportunities

"Android users" is a group, not a need. Phrase opportunities as pains.

Gaming the numbers

Inflated inputs kill RICE. Demand evidence; score openly as a team.

Severity without reach

A total blocker for 0.5% of users is usually a low-priority fix.

Notification