All frameworks and cheat sheets

Guide

Five common opportunity solution tree mistakes

List of five common opportunity solution tree mistakes, from putting solutions in the opportunity layer to treating experiments like features.
If an opportunity names something you would build, it belongs one layer down.
Download PNGRead the full guide

Five mistakes teams make with an opportunity solution tree: writing solutions where opportunities belong, interviewing only one kind of customer, letting the tree go stale, chasing several opportunities at once and building full features when a small experiment would do. Use it as a review list when your product trio updates the tree. Regular Koji interviews help keep the opportunity layer current.

Where this appears

What's in this guide

  1. Solutions in the opportunity layer: Users need a dashboard is a solution. Ask if a customer could have the problem without your product.
  2. Interviewing one customer type: Talk only to power users and you miss what blocks casual users from getting value.
  3. Treating the tree as static: Update it after every batch of interviews, or solutions drift away from what customers say now.
  4. Chasing too many opportunities: Pick one, test it, ship a solution, then move to the next.
  5. Confusing experiments with features: An experiment tests one assumption. Build the least you need to learn.

Use this image

Free to use in your docs, decks and posts under CC BY 4.0, as long as you credit Koji with a link to this page. To embed it, paste this into your page:

html
<a href="https://www.koji.so/visuals/opportunity-solution-tree-common-mistakes"><img src="https://www.koji.so/visuals/opportunity-solution-tree-common-mistakes/opportunity-solution-tree-common-mistakes.png" alt="List of five common opportunity solution tree mistakes, from putting solutions in the opportunity layer to treating experiments like features." width="1080" height="1080" /></a>
<p>Source: <a href="https://www.koji.so/visuals/opportunity-solution-tree-common-mistakes">Five common opportunity solution tree mistakes</a>, Koji</p>

Related

Table comparing a traditional product roadmap with an opportunity solution tree on focus, update rhythm, decision basis, risk and customer voice.

Opportunity solution tree vs traditional roadmap

Framework showing the four layers of an opportunity solution tree: one outcome, customer opportunities, solutions and the experiments that test them.

The four layers of an opportunity solution tree

List of seven disadvantages of focus groups, from groupthink and dominant voices to small samples, cost, moderator bias and slow results.

Seven disadvantages of focus groups