Product discovery, structured
Opportunity Solution Trees that stay alive
Connect the outcome you are chasing to the opportunities you have heard, the solutions you are considering and the experiments that decide between them. One living tree instead of a whiteboard nobody has opened since the workshop.
Free plan, no credit card. Desktop browser. Pro from €19 per seat.
The tree is easy to draw and hard to keep
Almost every team that adopts the format hits the same three problems, and none of them are about drawing.
It drifts
The board from the offsite is three months stale. Nobody is sure which branch reflects the current plan, so people stop trusting it and go back to the backlog.
The evidence goes missing
The interview that justified a branch lives in a doc, the experiment result in a Slack thread. When someone asks why you chose this, the answer is a shrug.
Solutions creep upward
Features quietly appear in the opportunity layer. Once that happens the tree stops showing a problem space and starts being a roadmap with extra steps.
How it works
Four node types, one structure
Start with the change you want
One measurable outcome sits at the root. Everything below it has to earn its place by plausibly moving that number.
What counts as outcome? →Map what customers actually said
Needs, pains and desires in the customer's words. Nest them until each one is small enough to attack, and keep solutions out of this layer.
What counts as opportunity? →Compare options instead of defending one
Several candidate solutions per opportunity, so there is a real decision to make rather than an idea to justify.
What counts as solution? →Test the assumption that would sink it
Attach experiments to the solution they check, record what came back, and let the evidence decide whether the branch advances.
What counts as experiment? →What you get
Built for the months after the workshop
The first version of a tree takes an afternoon. Keeping it true takes a tool that understands what a tree is.
Automatic layout
Add a branch and the tree rearranges itself. No dragging boxes to make room.
Evidence on the node
Interview quotes, experiment results and signals attach to the opportunity or solution they speak to, not to a folder somewhere else.
Confidence scoring
See at a glance which branches rest on evidence and which are still assumption.
Experiments with todos
Each experiment carries its own checklist and result, so a test is a piece of work rather than a sticky note.
Tree and list view
Think spatially when you are exploring, switch to a list when you are working through items.
Shared workspaces
Team workspaces with separate decision spaces, so several outcomes can run side by side without colliding.
New to the format?
The Opportunity Solution Tree was created by Teresa Torres as part of her work on continuous discovery. Our guide explains the structure, the common mistakes and how to build your first one, with a worked example you can copy.
Frequently asked questions
What is TreeFlow?
TreeFlow is a collaborative web tool for building and maintaining Opportunity Solution Trees. It models outcomes, opportunities, solutions and experiments as a structured tree, keeps the evidence behind each node attached to it, and lays the tree out automatically as it changes.
Who is TreeFlow for?
Product teams practising continuous discovery: product managers, designers and engineers who run customer conversations regularly and need somewhere for the reasoning to live. It suits product trios and small product organisations more than large feature-request triage operations.
Do I need to know the Opportunity Solution Tree method already?
No. The guide on this site explains the format from scratch, and the product walks you through creating your first outcome, opportunity, solution and experiment. Teams familiar with Teresa Torres's continuous discovery work will recognise the structure immediately.
How is this different from using a whiteboard?
A whiteboard stores shapes; TreeFlow stores the tree. Because the relationships are real, layout is automatic, evidence attaches to specific nodes, and you can see which branches lack support. Whiteboards are better for the first workshop, structured tools for the months after it.
Map your first tree today
Free to start, no credit card. Bring one outcome and the last three customer conversations you had.