Why opportunity discovery is important
If you work on internal products or in an IT setting, you may think of discovery as a cooler term for eliciting requirements
I know I was guilty of that line of thinking in the past. And I’m pretty sure I came to that conclusion because I worked in contexts where my product team was assigned a solution to deliver.
But as I found myself in situations where my product team had to achieve an outcome, we needed to figure out how to make that happen.
We were in a position where we could make a more informed decision. In order to do that, we needed to gather information about our customers, their problems, and constraints we faced. We also needed to organize all the information we collected and the ideas we generated.
This is where opportunity discovery comes into play. When you have an intentional approach to opportunity discovery, you’re able to focus your research efforts so you’re collecting information that will guide you in the right direction.
Once you have that information and need to identify your actions, you need some ways to organize those thoughts. I’m aware of two different tools to help you do that – opportunity solution trees, and impact maps.
Read on to find out an approach to opportunity discovery and to find out more about those two tools.
Product Opportunity Discovery
Opportunity discovery is an often misunderstood concept – an enigma even within the product management community. Without a ubiquitous definition, Product professionals seem to sense a need to figure out what to build and we eventually end up with a roadmap, but Neal Cabage hasn’t seen a clear articulation of exactly what’s required or how to get from strategy to planning. To that end, Neal came up with this approach to opportunity discovery.
 |
Opportunity Solution Trees
As Teresa Torres worked with teams to encourage them to do continuous discovery, she kept running into teams that understood the techniques involved in discovery, but had trouble tying all the activities together. She eventually realized that product discovery has two dimensions – discovering opportunities and discovering solutions.
To help teams organize their thoughts around discovering opportunities, Teresa created the opportunity solution tree. In this article she explains why she came up with the opportunity solution tree and how you can use it to guide your opportunity discovery efforts.
 |
If you’d like an idea of how teams use opportunity solution trees Melissa Suzuno shares three stories of people using opportunity solution trees in a variety of contexts.
Impact Mapping
A primary way of making progress toward a particular outcome is influencing the behaviors that drive progress toward (or prevent progress toward) that outcome. Impact mapping combines mind mapping and strategic planning to help you do that. I put together an overview of Impact Mapping to introduce you to what it is and how you can use impact maps to guide your discovery efforts.
 |
Isabelle Andrews shared her experiences using impact mapping to meet policy intent and user needs at the same time in the UK Department for Education.