🛠️ How to Navigate Product Discovery Like a Map


How to Navigate Product Discovery Like a Map

READ ON

​HERBIG.CO​

PUBLISHED

Nov 1, 2024

READING TIME

4 min & 51 sec

​Dear Reader,​

“We need to complete all six Discovery phases in order." "Let's perfect that JTBD statement before we talk to users." "Our process requires detailed one-pagers before any customer interviews."

Does this sound familiar? These are examples of dogmatic defaults: Teams cycling through the same tools in the same order, regardless of context. While these practices aren't harmful, blindly following them as processed often means missing faster paths to reducing uncertainty.

Instead of rigid processes, think of Discovery as a path you navigate. It consists of:

Entry Points: Where you begin. Shaped through (new) business goals, changes in market conditions, or other triggers.

Crossroads: Pivotal „What do we need to learn next“ moments that determine the direction of a team’s moves. Articulated through research intent questions (problem space) or assumptions (solution space).

Moves: The distinct methods you use to progress.Typically in the shape of qualitative or quantitative methods linked to the specific research intent question or assumption

Commitments: States of informed conviction leading to clear decisions. Conviction about additional needed work to reduce uncertainty, discarding a problem or solution, or committing to and implementing a solution

The key is not which method you use but how you choose your next move based on what you need to learn. When navigating Discovery Paths, constantly ask yourself: What activity maximizes uncertainty reduction while shortening the lead time to the next viable insight as much as possible?

Here are the paths of a Product Team working on a financial trading app:

Product Discovery isn't about following prescribed steps. It's about using evidence to reduce uncertainty about what problems are worth solving and what solutions are worth delivering.

Stop waiting for perfect conditions. Start reducing uncertainty from whatever entry point you find yourself at.

Did you enjoy this newsletter or have feedback? Do reply. It's motivating. I'm not a robot; I read and respond to every subscriber email I get (just ask around). If this newsletter isn't for you anymore, you can unsubscribe here.

Thank you for Practicing Product,

​Tim​

PS: Thanks to Paulius Tuzikas for contributing to the "accidental" shaping of the idea of Product Discovery Paths derived from our conversation.

PPS: Join me on Nov 12 for an in-person deep dive on Product Discovery practices at Product Tank Cologne.

Join my In-Person Workshops in Berlin

I'm excited to bring my beloved in-person workshops back to Berlin in January 2025. You can choose between 1-day workshops on Product Strategy, Product OKRs, or Product Discovery OR get the full 3-day experience for you or your team.

(reach out for custom team quotes)

Content I found Practical This Week

You’re Not Just Solving User Problems

Lastly, even if you develop ideas that successfully address important user needs, that doesn’t mean that you will necessarily achieve your goals. The connection between user needs and company goals has its own set of assumptions. For example, we may add an elaborate “find parking” feature to our GPS navigation system, but still not improve customer churn, simply because customers are switching to car brands with whom we didn’t partner yet (this would be uncovered by market research or data analysis, but not necessarily by interviewing existing customers).

The benefits of building a user segmentation matrix

To be truly powerful ONE user segmentation matrix should be used across the organization, from Marketing to Business, Product, Data & Insight etc. allowing you to build user-centred value propositions fit for each user segment and ensuring that the services and products offered for each segment are full-rounded and strategically relevant. Sharing this information and gathering it from across your organization, is also incredibly useful for all conversations between Product, Business and Sales - because you know you’re referencing the same issues and sharing the same mental model.

The Interview Snapshot: How to Synthesize and Share What You Learned from a Single Customer Interview

What did you think of this week's newsletter?

Who is Tim Herbig?

As a Product Management Coach, I guide Product Teams to measure the real progress of their evidence-informed decisions.

I focus on better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.

Enjoy the newsletter? Please forward it. It only takes 2 clicks. Coming up with this one took 2 hours.

Product Practice Newsletter

1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.

Read more from Product Practice Newsletter

Product Practice #345 Four Decision Tree Frameworks Product Managers Need to Know READ ON HERBIG.CO PUBLISHED Dec 6, 2024 READING TIME 2 min & 54 sec Dear Reader, As a highly visual thinker, decision trees are one of my favorite ways to support product teams in making real progress and bringing structure to my thinking. Today, I want to share four of my favorite tree structures and use an outside-in view on Eventbrite to illustrate their usage. MECE Trees The MECE tree structure, invented by...

Product Practice #344 Product Strategy Stackvs. Decision Stack (Part 2) READ ON HERBIG.CO PUBLISHED Nov 29, 2024 READING TIME 4 min & 49 sec Dear Reader, This is part 2 in my mini-series on putting the Product Strategy Stack and Decision Stack side-by-side. You can read part 1 here. Measuring Progress Here's where the frameworks diverge more significantly. The Decision Stack uses "Objectives" as its connecting measuring element between "the work" and Strategy. At the same time, the Product...

Product Practice #343 Product Strategy Stackvs. Decision Stack (Part 1) READ ON HERBIG.CO PUBLISHED Nov 22, 2024 READING TIME 3 min & 01 sec Dear Reader, Everyone loves a Product Strategy framework. But choosing between the Product Strategy Stack and Decision Stack isn't straightforward. Both put long-term artifacts like a Vision and Mission at the top and link their different elements. But knowing which works best for you requires decoding their layers. Long-term Ambitions Both stacks agree:...