3 Universal Truths to Cut
|
Dear Reader,
"We need more user research!" "Let's run a design sprint!" "Have you tried jobs-to-be-done?" Product Discovery can feel like drowning in an ocean of frameworks and methods. But after coaching dozens of product teams, I've found that successful Discovery isn't about following perfect processes—it's about understanding three fundamental truths that cut through the noise.
Truth #1: Evidence Beats Process
The strength of your evidence matters more than the steps you took to get it. Teams frequently get caught up in following the "right" process, but what truly drives progress is gathering reliable evidence about customer problems and potential solutions. Real, observed behavior will always trump reported feedback, and evidence showing meaningful commitment beats casual interest every time.
Truth #2: Context Beats Convention
There is no one-size-fits-all approach to Discovery. What works for a B2B enterprise product won't necessarily work for a consumer mobile app. The key is matching your method to what you need to learn next. Sometimes, that means running quick experiments instead of extensive research. Other times, it means conducting deep customer interviews before prototyping. Your context—including your customer type, business model, and constraints—should guide your choice of methods.
Truth #3: Focus Beats Completeness
Not every customer problem needs to be solved, and not every feature idea is worth pursuing. Valuable Discovery means choosing which problems matter most to your strategic goals. Teams need to evaluate the reliability of their customer insights and use that information to decide what to work on. This means being deliberate about which customer segments to focus on and which problems to prioritize.
The most successful teams I've worked with embrace these truths by:
Remember: The goal isn't perfect certainty—it's gathering enough reliable evidence to make confident decisions about what to (or not to) build next. When teams focus on these fundamentals instead of getting lost in the process, they consistently deliver solutions that matter for both users and the business.
Did you enjoy the newsletter? Please forward it. It only takes two clicks. Creating this one took two hours.
Thank you for Practicing Product,
Tim
There is ONE last ticket available for my in-person Product Discovery workshop on March 10 in London (as part of Mind the Product conference).
| GET THE TICKET! |
(In case it's gone already,
check out one of the other amazing workshops)
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.
1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes. Explore my new book on realprogressbook.com
Product Practice #387 Can We Drive the Same Outcome for Different Customer Segments? READ ON HERBIG.CO PUBLISHED Dec 5, 2025 READING TIME 4 min & 40 sec Dear Reader, "An outcome is a measurable change in human behavior that creates business value." (via Josh Seiden). But what if different customer segments share the same problem? Should you repeat the outcome on your impact map? The answer: Yes—when it forces clarity. From the chapter "Targeted Discovery" in my Book Real Progress Let me give...
Product Practice #386 Why your Discovery Insightsneed an Expiration Date READ ON HERBIG.CO PUBLISHED Dec 29, 2025 READING TIME 5 min & 32 sec Dear Reader, "I believe we should split-test this change to the funnel." "No, we tried that 3 years ago. Didn't work." End of story...right? 9-ish years ago, I got to listen to Willem Isbrucker sharing his insights from running experiments at booking.com (famous for their quantitative data-first approach) at ProductTank Hamburg. Among other things, he...
Product Practice #385 Why Strategic THINKINGmatters more than THE Strategy READ ON HERBIG.CO PUBLISHED Nov 20, 2025 READING TIME 4 min & 5 sec Dear Reader, Will I meet you later today in Frankfurt? "We can't move forward until leadership finishes the strategy." I've heard this from countless product teams. Roadmap planning is on hold. OKRs feel arbitrary. Discovery lacks direction. Everything hinges on THE strategy document, which is perpetually "almost done." Here's what nobody wants to...