Day 236 of the Daily · Product Management

The Opportunity Solution Tree

5 min read · 4 principles · apply it by lunch

Morning. Your roadmap lists what you’ll build. It doesn’t say what any of it is a bet on.

The question

Pick any item on the roadmap you’re working to right now and say out loud which outcome it’s meant to move and which customer need it addresses — then work down the list item by item, and how far do you get before the honest answer becomes ‘because it was already on the roadmap’?

The idea

Teresa Torres is a product discovery coach who has spent a decade teaching teams to interview customers on a weekly rhythm rather than in occasional bursts. She introduced the opportunity solution tree on her site Product Talk in 2016 and built her 2021 book, Continuous Discovery Habits, around it. The tree has four layers. At the root sits one desired outcome — a change in customer behaviour you’re trying to produce, not a feature you’re trying to ship. Beneath it hangs the opportunity space: the needs, pain points and desires you’ve actually heard in interviews, structured so that broad ones branch into narrower ones. Under a chosen opportunity sit the solutions that might address it, and under those the assumption tests that would tell you whether any of them holds. Read upwards, every item can now answer the question a feature list never can — what is this a bet on. The trap is prioritising in the solution space. Teams rank features against each other when the features serve different customers, different problems and wildly different sizes of prize; the comparison that carries information is between opportunities first, and only then between several solutions to the same one.

In the Daily · 4 principles and a template

The Opportunity Solution Tree is Day 236 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Product Management

The next four in the course.

All 22 Product Management frameworks
Day 245 · Product Management

The House of Quality

Your customers keep asking for the same vague thing — that it feel faster, or simpler, or more solid — and delivering it means moving one measurable characteristic inside the product: can you say which one, and in what unit? Most teams can’t. So the unit gets chosen by whoever writes the code, at the moment they write it.

See the framework →
Day 255 · Product Management

RICE

When your team last settled what to build next, could anyone in that room have said out loud how sure they were — not whether the idea was good, but how much of the case rested on a figure somebody had actually gone and looked up? I’ll give you the answer: nobody was asked, because nothing on the list carried a number anyone could argue with.

See the framework →
Day 264 · Product Management

Working Backwards

Your team is building something right now that nobody outside the building has heard of yet — so on the day it ships, when the announcement goes out with the customer named, the problem stated and the reason anyone should care in two plain sentences, will a stranger read that and want the thing, or read a list of capabilities and feel nothing at all?

See the framework →
Day 274 · Product Management

User Story Mapping

Your team has committed to a release next: could one real customer start at the very beginning and get all the way through to the thing they actually came for using only what’s above the line — or does it stop somewhere in the middle, polished at step one and missing entirely at step four? A backlog sorted by priority almost always slices the wrong way.

See the framework →