post

B2B product management

Artificial Intelligence (AI) & Machine Learning (ML)

Building Product Teams

Business Strategy

Data Driven Product Management

Digital Transformation

Diversity and Inclusion

Minimum Viable Product

OKRs

Prioritisation

Product Design

Product Research

Product Development Process

Product Ethics

Product Discovery

Product Leadership

Product Management Career

Product Strategy

Stakeholder Management

🌎 <a href="https://www.mindtheproduct.com/world-product-day/" style="color:#FFFFFF;text-decoration:underline;">Happy World Product Day!</a> Be sure to celebrate product, yourself, and your peers today! 🎉

Can product operations and innovation be friends?

Why can’t we get accessibility right? Claire Bauden (SVP Global Product Design, Global Payments Inc.)

Ditch the PRD template and embrace the PRD checklist

How to price your subscription product: insights and examples

International strategy with a 360 view by Chris Butler

Footer About

Footer Contribute

Footer Get Involved

Footer Links

Mind the Product

Sunday Rewind: The good, bad, and ugly of OKRs by Jenny Herald

Product Management

Ferdinand Goetzen

<p><em>In this post, startup CEO Ferdinand Goetzen relates how product discovery led him and his team to adjust their thinking, pivot and change their product </em></p>
<hr />
<h2>Overview</h2>
<p>We started Reveall in 2021 as a platform to empower UX teams to do more with their customer research insights. As we sought to navigate some of the most volatile market conditions startups have ever faced, we realized that we really couldn’t afford to make any wrong decisions about we would build next.</p>
<p>We were very aware that many companies spend a lot of time and resources building products and features that don’t create enough customer value. We knew we couldn’t afford to do that, so in the summer of 2022, we set out to understand why this occurred and how we could make product decisions that consistently delivered value for customers.</p>
<p>Throughout our exploration, we kept coming back to product discovery – the process of deeply understanding your customers&#8217; problems, needs and desires so that you can create compelling features for them. We felt that product discovery perfectly matched our company mission of empowering teams to build products their customers really need.</p>
<p>Through our own product discovery, we learned that every product team we spoke to was dealing with similar issues. The opportunity to support teams in their product discovery was huge, so we decided to pivot and turn Reveall into the first product management platform dedicated to product discovery.</p>
<p>As a startup with limited runway, we were pressed for time and we needed to work efficiently to ensure the new version of our platform actually solved the core problems we’d identified. We rallied the whole company around our own discovery process, led by our very own ‘product trio’ consisting of our CPO, our CTO and our product designer.</p>
<figure style="width: 1600px" class="wp-caption alignnone"><img loading="lazy" decoding="async" src="//wp-content/uploads/2023/02/13e13190-12c3-4436-a83d-3e862089eec0_pasted20image200.png" alt="" width="1600" height="592" /><figcaption class="wp-caption-text">Our own discovery process</figcaption></figure>
<p>Our goal? To relaunch Reveall as a product discovery platform in January 2023.</p>
<h2>Our Approach</h2>
<p>For clarity, I&#8217;ve broken down our approach into four phases, though please note that these weren’t clear-cut chronological phases – there was a lot of overlap and the process was continuous and iterative. Often we did things in parallel, going back and forth between phases as needed.</p>
<h3>Phase 1: Research</h3>
<p>In June 2022 we started to focus on our own product discovery. Our first goal was to truly understand the problems and needs of product teams. To gain this deeper understanding, we relied on four approaches:</p>
<ol>
<li>Interviewing with our existing customers – a mix of UX and product teams</li>
<li>Interviews with over 50 product teams that didn’t use Reveall</li>
<li>An extensive survey run with over 150 product teams</li>
<li>A year’s worth of insights we had already gathered in our own ‘Reveall repository’</li>
</ol>
<p>We ended up drawing insights from over 250 different product teams, learning that product discovery was both a priority and a challenge for them.</p>
<figure style="width: 1600px" class="wp-caption alignnone"><img loading="lazy" decoding="async" src="//wp-content/uploads/2023/02/b530dd9c-bca7-4cee-b69f-472c6b19f9b6_pasted20image200.png" alt="" width="1600" height="989" /><figcaption class="wp-caption-text">Product discovery emerged as one of the main challenges teams faced in our survey</figcaption></figure>
<p>Doing our own product discovery <span style="font-style: italic;">about</span> product discovery was an interesting experience. We not only learned from product teams how they struggled with doing discovery well, but experienced first-hand what the challenges were.</p>
<p>One takeaway was that the tools available were not designed to really facilitate the discovery process. Most focused on adding ideas to already unmanageable backlogs and building roadmaps that rarely get met – essentially, they <span style="font-style: italic;">encourage</span> the natural tendency to jump straight to solutions, whereas product discovery is all about focusing instead on the core customer problems that can be effectively solved.</p>
<p>Once it became clear to us that we wanted to turn Reveall into a platform that helped simplify the entire process of  product discovery, we needed to figure out what exactly that would entail.</p>
<h3>Phase 2: Mapping our opportunity tree</h3>
<p>Like every product team, we had lots of ideas. And with all the research we had done, we had lots of insights. Fully aware that this is a recipe for confirmation bias, we decided to clearly map out and break down our main opportunities.</p>
<p>The idea for mapping opportunities in the form of a tree came from <a href="https://www.linkedin.com/in/teresatorres/" target="_blank" rel="noopener">Teresa Torres</a>’ opportunity solution tree. The high-level problems we had identified were huge and impossible to solve head-on, so we needed to break them down into problems that were solvable, especially given our timeline.</p>
<figure style="width: 1600px" class="wp-caption alignnone"><img loading="lazy" decoding="async" src="//wp-content/uploads/2023/02/73c26e6e-ce77-4e1d-8064-8c2d17eef459_pasted20image200.png" alt="" width="1600" height="524" /><figcaption class="wp-caption-text">The tip of our opportunity tree</figcaption></figure>
<p>At the  highest level, the single, big problem we aimed to solve was that <span style="font-weight: bold;">teams spend too much time and resources building things that don’t have the desired impact.</span></p>
<p>We broke this down into three sub-problems (which in turn were broken down into further sub-problems, and so on):</p>
<ol>
<li>Teams don’t understand their customers&#8217; problems and needs</li>
<li>Teams prioritize based on solutions and not on opportunities</li>
<li>Teams and stakeholders lack alignment</li>
</ol>
<p>We worked on this tree as a team, pulling in ideas and suggestions from different departments.</p>
<p>Once the tree was mapped, we began validating and prioritizing the problems with the insights from our research, continuously collecting data as needed to further validate and prioritize.</p>
<p>We had the insights, we had the opportunities and we had lots of ideas. It was finally time to start thinking about solutions. But where to get started?</p>
<h3>Phase 3: Reverse Discovery</h3>
<p>One thing we realized was that getting started with proper discovery isn’t easy and isn’t always a top-down process. As humans, we naturally gravitate to details which leads us to focus on solutions &#8211; but a premature focus on solutions is what we’re trying to avoid. So instead of fighting that instinct by railroading people into a single way of working, we wanted our process to work <span style="font-style: italic;">with </span>that tendency and turn it into a positive, while still connecting to the validated opportunities that we identified would lead to business outcomes.</p>
<p>With this in mind, we used our existing backlog as a source of inspiration and, staying true to doing discovery properly, our CPO <a href="https://www.linkedin.com/in/marcelhagedoorn/" target="_blank" rel="noopener">Marcel Hagedoorn</a> proposed what he called ‘reverse discovery’. The idea was to essentially start with products or features (i.e. solutions) we had already defined and reverse-engineer the connecting points in the discovery process from there &#8211; going back and linking them to opportunities and outcomes along the way.</p>
<figure style="width: 1600px" class="wp-caption alignnone"><img loading="lazy" decoding="async" src="//wp-content/uploads/2023/02/311b1486-7e20-4b96-8fd8-3ed46aa597b1_Untitled.png" alt="" width="1600" height="899" /><figcaption class="wp-caption-text">Reverse discovery</figcaption></figure>
<p>Essentially, we took the ideas we had already come up with and attempted to map them where relevant to our opportunity tree. The process also inspired the idea for a new onboarding flow, where we help new customers do their own <span style="font-style: italic;">reverse engineering</span> of the discovery process using existing items from their backlog or roadmap.  Working both top-down and bottom-up in this way, we found an increased flow of ideas and information, helping us more quickly and easily fill out our opportunity tree.</p>
<figure style="width: 1600px" class="wp-caption alignnone"><img loading="lazy" decoding="async" src="//wp-content/uploads/2023/02/54ca1e51-d614-40aa-96cb-69f633043f3e_pasted20image200.png" alt="" width="1600" height="884" /><figcaption class="wp-caption-text">Our ‘getting started’ onboarding tutorial. We ask users to add solutions from their backlog and in the next steps have them link the solutions to opportunities and outcomes.</figcaption></figure>
<p>Of course, where existing ideas did not solve our main opportunities, we discarded or changed them. This also helped reduce our endlessly growing backlog of ideas.</p>
<h3>Phase 4: Delivery</h3>
<p>Our rigorous focus on discovery made delivery a lot easier for us. With clear ideas on what problem we needed to solve, we could easily adjust scope based on the core user stories we identified for each problem and the resources we had available.</p>
<p>At the end of December, we essentially released our product discovery feature set. This included three new features we added to the platform:</p>
<ul>
<li><span style="font-weight: bold;">Outcomes</span> – identify goals and OKRs</li>
<li><span style="font-weight: bold;">Opportunities</span> &#8211; list customer problems, needs and desires, validate with insights from the Reveall Repository, prioritize based on ‘impact’ and ‘confidence’</li>
<li><span style="font-weight: bold;">Solutions</span> &#8211; define features and product ideas, validate with insights, and prioritize based on effort.</li>
</ul>
<p>We also spent a lot of time understanding how to link these all together.  In one click, users  can list the range of opportunities that exist to impact a specific business outcome AND dive deeper into the set of possible solutions for any specific opportunity.</p>
<p>We had previously found that product discovery and insights management really go hand-in-hand and have plenty of overlap. Therefore, many of our previous features such as our insights repository and journey mapping functionality made perfect sense in a product discovery process, providing context for the customer problems we identified. This did present a challenge though as we had to work around the existing platform as we made changes.</p>
<p>To better manage the insight management and product discovery use cases we serve, we split the platform into two feature sets that are seamlessly interconnected:</p>
<ul>
<li><span style="font-weight: bold;">Reveall Discovery</span> (outcomes, opportunities, solutions, journeys)</li>
<li><span style="font-weight: bold;">Reveall Repository</span> (themes, data, findings, insights)</li>
</ul>
<figure style="width: 1600px" class="wp-caption alignnone"><img loading="lazy" decoding="async" src="//wp-content/uploads/2023/02/e3e759d8-1e74-4053-bc2b-2fdd9dbfb5c9_pasted20image200.png" alt="" width="1600" height="886" /><figcaption class="wp-caption-text">Reveall as a product discovery platform</figcaption></figure>
<h2>Results</h2>
<p>Within just a couple of months we managed to revamp Reveall completely. We started as a platform that helped teams do more with their UX research insights and successfully shifted to a platform dedicated to product discovery.</p>
<p>Most importantly, we managed to establish features that fundamentally address some of the biggest problems product teams face. That said, there’s a lot more work that needs doing. Our goal is to make product discovery simple and effective, but every team does product discovery differently. We’re still learning, but we’re excited to rework our opportunity tree based on the feedback we get and identify the next set of <span style="font-style: italic;">problems </span>that we can focus on.</p>
<p>If you want to see what the end result (although there never really is an ‘end’) you can check it out yourself at <span style="text-decoration: underline;"><a href="http://reveall.co" target="_blank" rel="noopener">Reveall.co</a></span>. One thing we can guarantee is that if you share feedback, it will end up in our own Reveall workspace and become a part of our ongoing product discovery.</p>
<h1>Conclusion</h1>
<p>Product discovery is a fundamental process for teams wanting to reduce risk in their product decisions. Through our own discovery process we realized that there is an opportunity for us to support product teams in their discovery efforts. Using our own product to scratch our own itch was incredibly helpful in guiding us through our research.</p>
<p>Our main learning is that the product discovery really helped to rally the whole company behind the same priorities. Knowing what our desired outcomes are and what opportunities lay within them made it easier to research, plan, scope and deliver features that have impact.</p>
<p>The full extent of the results remains to be seen, but the process in itself was hugely valuable.</p>
<div>
<p>&nbsp;</p>
</div>
<div class="g g-21"><div class="g-single a-170"><a class="gofollow" data-track="MTcwLDIxLDEsNjA=" href="https://www.pendo.io/pendomonium/"><img decoding="async" src="https://www.mindtheproduct.com/wp-content/uploads/2024/06/MTP-Footer_ad.png" /></a></div></div>

core/freeform

Reduce risk, fail faster: Experimenting across the product development lifecycle

Experiment like a boss by Merissa Silk

How to find out what your customers want by Janet Bumpas

Why does my product suck? by Jen Dante

Driving customer adoption and retention as a product manager by Karen Adie

Mastering the art of the big bet by Alice Newton Rex

The magic of thinking big by Lenny Rachitsky

Making magic with balanced teams by Becki Hyde

Tools for agile product teams by Gavan Moule

Building Products for Bharat by Arpit Maheshwari and Smriti Pant

A case study: How our own product discovery made us pivot Reveall towards product discovery

A case study: How our own product discovery made us pivot Reveall towards product discovery

Ferdinand Goetzen

Comments

Read next