Product management can feel like navigating a jungle with a constantly spinning compass. You’re bombarded with feature requests, user feedback is stored and forgotten, and stakeholders have conflicting visions of success. It’s easy to get lost in the weeds, building features that don’t move the needle and leaving both your users and your business wanting more.

The truth is that many product teams fall into the trap of solution-first thinking. Someone suggests a “cool” new feature, and everyone jumps on the bandwagon without truly understanding the problem it solves or the value it provides. This leads to a bloated product, confused users, and a whole lot of wasted effort.

Opportunity Solution Tree (OST) offers a better approach to product discovery that keeps you focused on the outcome you are trying to achieve and the problems that are in the way of reaching that outcome. This concept was introduced by product discovery expert Teresa Torres. We recommend visiting her free blog at ProductTalk or reading her outstanding book, Continuous Discovery Habits, for a deeper understanding of how OSTs function.

Opportunity Solution Trees in 4 steps

The Opportunity Solution Tree (OST) is a visual framework that guides you through a structured process of:

1. Define the outcome: Define clear, measurable, desired outcomes for your users and your business. These can be OKRs, and we recommend following the S.M.A.R.T. framework for setting goals that are specific, measurable, achievable, relevant, and time-bound.
2. Identifying opportunities: Once you have your outcome defined, work backward to uncover the underlying opportunities that, if addressed, will drive those outcomes. Opportunities are user needs, challenges, or desires, that if solved, will move you toward the desired outcome.
3. Exploring potential solutions: For each opportunity, brainstorm various solutions. Don’t settle for the first solution that comes to mind. Dare to explore! This encourages you to think broadly and avoid fixating on a single idea too early. We recommend that you don’t sit alone doing this. Bring your team and relevant stakeholders for this.
4. Assumption testing: Don’t just assume you have the correct answer! The OST encourages continuous experimentation and learning. Test the underlying assumptions that must be true for your solution to be successful. Do this early and repeatedly based on user and stakeholder feedback and user analytics, and iterate using real-world data.

However, structuring the OST can be challenging. It is tough to keep it up-to-date, connected to all your user feedback, and to keep the layout accessible for you and your team. OppFlow makes this as easy as possible and helps you and your organization achieve your business and product outcomes. Think of the OST as a roadmap. It helps you navigate the complex terrain of product development by:

• Prioritizing user needs: By focusing on opportunities that address real user pain points, you ensure you’re building the right things.
• Aligning teams around a visual map: The OST’s visual nature facilitates communication and collaboration, ensuring everyone is on the same page.
• Reducing risk: By testing assumptions early and often, you avoid wasting time and resources on solutions that don’t work.