Opportunity Solution Tree Template
Visualise your opportunities and the decisions you're making along the way
Trusted by 65M+ users and leading companies
About the Opportunity Solution Tree template
The Opportunity Solution Tree template helps product teams to improve the way they solve problems and reach their desired outcomes. Designed by Teresa Torres, a product discovery coach, this tree aims to methodically move teams through the steps needed to reach a final solution. Teresa Torres's opportunity solution tree breaks down a desired outcome into opportunities for the product to meet user needs and then suggests potential solutions to meet these needs.
Why use an opportunity solution tree?
Product teams may find this template useful if they are able to produce a lot of ideas, but can’t prioritize which ideas are actually of quality. An opportunity solution tree is a tool that product teams can use to assess if they are considering all potential solutions to reach their desired end. It then provides clear solutions at the end of the exercise that can be compared and contrasted for most value.
What is an opportunity in the opportunity solution tree?
Brainstorms tend to lead to a lot of solutions off the bat without any clear logic to whether the solution is a valuable one. Opportunities are a way for product teams to add in the layer of customer needs in order to better connect solutions to what will really help a user. By adding in the step of identifying opportunities, the ideas your team generates will be based on identified needs rather than an arbitrary solution.
What is product discovery?
Product discovery is a framework to help teams create useful, usable products that don’t overlook true user need. Using the Opportunity Solution Tree template is one way to start improving your product discovery.
How do I build an Opportunity Solution Tree?
Creating an opportunity solution tree is easy with Miro's tree diagram maker or ready-made template. Simply follow these steps.
Step 1: Define your outcome or measurable result
Simply put, what does success look like? If you use OKRs, then you can use one of your Key Results to answer this question. If you don’t, then you’ll need to pick a metric that you’d like to improve. Of course, many teams are striving to achieve many goals each quarter, but it helps to create a separate tree for each goal.
It’s important for your team to agree on this goal before you proceed to the next step. If you’re misaligned from the beginning, then it’s going to be harder to build the rest of the tree.
Step 2: Identify possible opportunities
For goal-oriented people, the temptation to jump from “problem” to “solution” is sizable. But resist that temptation. Instead, it’s time to pause and do some research.
Building an Opportunity Solution Tree is all about identifying key opportunities in your market. That means learning: about customers, about what they need, about the problems that they are trying to solve. Focus on answering these questions before you fill out this portion of the tree.
Armed with insights about your customers, you can begin to find opportunities. Use your research to fill out this second branch of the tree. Don’t be fooled: although this branch isn’t about your solutions, it’s still vitally important. Each branch of the tree builds on the previous, so if your research isn’t robust, your opportunities and solutions won’t be robust either.
Step 3: Generate solutions
Now it’s time to think of solutions. This is where the Opportunity Solution Tree template really comes to life for your team. When you go around the room to share ideas during a meeting, myriad dynamics are in play. People might be more or less likely to share based on their rank, role, or who’s in the room. The Opportunity Solutions Tree is an unbiased, agreed-upon source of truth that everyone can own and contribute to.
Invite cross-functional partners to contribute to this part of the tree. Let the ideas flow! However, be wary of including anything that doesn’t fit in the tree. It’s important to stay focused so you don’t end up with more ideas than resources. Write down those extraneous ideas and save them for later. If your team gets lost or stuck, return to the tree to ground you.
Step 4: Iterate and experiment
Choose one solution and once you have some ideas, you can start testing them out. Build a row on the tree specifically for experiments. Start brainstorming experiments that will enable you to test the chosen solution.
How do you use a solution tree?
The opportunity solution tree helps you to visualize the best path to your desired outcome. Use the solution tree to map out the possible opportunities to solve your problem and keep track of the actionable experiments that will lead to your desired outcome.
Get started with this template right now.
Flowchart Template
Works best for:
Flowcharts, Mapping, Diagrams
Trying to explain a process or workflow to your team — or just wrap your head around it yourself? Sometimes the best way is to see it, and that’s when you create a flowchart. Using common shapes (generally just ovals, rectangles, diamonds, and arrows), a flowchart shows you the direction a process or workflow goes and the order of steps. Beyond giving you a clear understanding, you’ll also be able to see potential flaws and bottlenecks, which helps you refine and improve your process and create a better product more efficiently.
Status Report Template
Works best for:
Project Management, Documentation, Strategic Planning
A status report provides a snapshot of how something is going at a given time. You can provide a status report for a project, a team, or a situation, as long as it emphasizes and maps out a project’s chain of events. If you’re a project manager, you can use this report to keep historical records of project timelines. Ideally, any project stakeholder should be able to look at a status report and answer the question, “Where are we, and how did we get here?” Use this template as a starting point to summarize how something is progressing against a projected plan or outcome.
Risk Matrix Template
Works best for:
Leadership, Decision Making, Strategic Planning
A risk matrix--also known as a probability matrix, risk assessment matrix, or impact matrix--is a tool that allows you to evaluate overall risk by visualizing potential risks in a diagram. The tool allows you to weigh the severity of a potential risk against the probability that the risk might occur. Risk matrices are useful for risk management because they visually represent the risks involved in a decision. This empowers you to avoid worst-case scenarios by preparing contingencies or mitigation plans.
Website Flowchart Template
Works best for:
Flowcharts, Mapping, User Experience
A website flowchart, also known as a sitemap, maps out the structure and complexity of any current or future website. The flowchart can also help your team identify knowledge gaps for future content. When you’re building a website, you want to ensure that each piece of content gives users accurate research results based on keywords associated with your web content. Product, UX, and content teams can use flowcharts or sitemaps to understand everything contained in a website, and plan to add or restructure content to improve a website’s user experience.
DMAIC Analysis Template
Works best for:
Agile Methodology, Design Thinking, Operations
Processes might not seem like the funnest thing to dive into and examine, but wow can it pay off—a more efficient process can lead to serious cost savings and a better product. That’s what DMAIC analysis does. Developed as part of the Six Sigma initiative, DMAIC is a data-driven quality strategy for streamlining processes and resolving issues. The technique is broken into five fundamental steps that are followed in order: Define, Measure, Analyze, Improve, and Control.
Fishbone Diagram Template
Works best for:
Operations, Diagrams, Workflows
What is the best way to solve any problem your team faces? Go straight to the root. That means identifying the root causes of the problem, and fishbone diagrams are designed to help you do it best. Also known as the Ishikawa Diagram (named after Japanese quality control expert Kaoru Ishikawa), fishbone diagrams allow teams to visualize all possible causes of a problem, to explore and understand how they fit together holistically. Teams can also use fishbone diagrams as a starting point for thinking about what the root cause of a future problem might be.