Practices and tools for opportunity discovery


Before I dive into opportunity discovery, here’s a quick update on my current discovery efforts to find my next adventure.


Many thanks to all of you who responded to my email with suggestions. I got a few significant leads out of those connections that I’m pursuing. There were certainly some very interesting opportunities you helped me find.


And a word of advice to everyone - the best time to nurture your network is when you’re not looking for your next gig. With one interesting exception, all the opportunities I’m pursuing came about because of a recommendation or reference from my network.


Blindly applying to job ads rarely works. Getting help from and giving help to your network almost always does.


Now on to the topic at hand…

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.


Recommended Reads

Want to raise the value of your inbox? Here are a couple of additional newsletters I’d recommend. When you signup you get some great info in your inbox, and I get a small referral fee, at no cost to you.

NoCode This

Looking for comprehensive coverage of the latest product updates, trends, and events in the no-code realm? Subscribe to NoCode This and get rich insights and practical takeaways that help you leverage no-code platforms in your professional and personal endeavors. Sign up today!

Chartr

Get the data and visuals you need to understand today's world and take your office small talk to the next level. Join 300,000+ data-driven professionals who love the #1 visual newsletter from our friends at Chartr, filled with snackable charts on business, tech entertainment and society. Sign up today.


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.


Thanks for Reading

Thanks again for reading InsideProduct.

If you have any comments or questions about the newsletter, or there’s anything you’d like me to cover, just reply to this email.

Talk to you in a couple of weeks,

Kent J. McDonald
Founder | KBP.Media

InsideProduct

Hand-picked resources for product owners, business analysts, and product managers working in tech-enabled organizations. Check out the resources I offer below and sign up for my newsletter!

Read more from InsideProduct

I try not to overuse click bait titles, too much. For this particular topic, however, it was just too tempting. As I mentioned in a previous newsletter, there were several reasons I went to Agile2024 after a six year hiatus. One was to get a sense of the current state of agile. There’s been a bit of chatter about the decline in agile coaching opportunities as well as trends in agile transformations in general. I certainly caught some inklings about what’s going on, but I didn’t want to rush...

I’m back from Agile2024, and it was good to be back after a 6 year hiatus. I caught up with some old friends, made some new acquaintances, and had some great discussions along the way. Some of those discussions will influence future issues of InsideProduct, and others will go down as obnoxiously long running inside jokes. If you're wondering about the latter, ask me about retractable stairs or comic sans the next time you see me. While I’m not going to talk about those topics here, I did want...

For the last few weeks, I’ve explored what prioritization looks like in a variety of different scenarios. This week finished up that series with a look at how you can go about prioritizing a bunch of stakeholder requests. This is a common scenario when you’ve already built software for your company (ie internal product) and you’re trying to optimize or maintain it. A unique aspect for internal products is that most requests for changes come from other people inside your company who may, or...