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 #399 How to Connect Strategy,Goals and Discovery PUBLISHED Mar 12, 2026 READ ON HERBIG.CO Most product teams don't have a strategy or OKR problem. They have a connection problem. My new Progress Wheel Intensive is a full-day working session for ambitious product teams where we fix that together — using your actual product context, not hypotheticals. Book a call to talk about it. Dear Reader, Often, the core concepts I share on how teams can make real progress by connecting...
Product Practice #398 The AI-Assisted ProductDiscovery Cheatsheet PUBLISHED Mar 6, 2026 READ ON HERBIG.CO Dear Reader, I'll cut to the chase: A few weeks ago, I thought about synthesizing high-level guidance on what stays the same and what needs to change in Product Discovery with AI - beyond the ever-changing tool details. So, I reached out to one of my favorite Product AI-thinkers right now, Julia Bastian (who's knowledgeable, pragmatic, and practical), and we compiled this graphic for you....
Product Practice #397 3 Things to Put into YourNext Strategy Document PUBLISHED Feb 27, 2026 READ ON HERBIG.CO Dear Reader, The most effective strategy document I've seen doesn't worry about the looks or format. Whether it's a scrappy Google Doc or a fancy Miro template, what matters is the quality and cohesiveness of the information it contains. Make sure what you cover aligns with your company's expected standards to ensure stakeholder understanding and, consequently, buy-in. But make sure...