Why your Discovery Insights
|
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 discussed how split-test results had an expiration date. If I remember correctly, it was 6 months. Meaning, if you had an idea that was tested less than 6 months ago, it might not be worth retesting right now. But if it was more than 6 months ago, the changes that have occurred in the meantime justify re-testing.
Many people get hung up on how "horrible" booking.com's UI looks or how "6 months doesn't work for us." But I believe there's a more universal practice in that anecdote, that applies to you, no matter the industry, company size, or maturity: It's that what was true in the past might no longer be true because of context changes. In simpler terms, your insights could benefit from an expiration date.
In the context of Product Discovery, this doesn't necessarily mean you have to re-do generative research or evaluative testing every six months. What it means instead is to run planned decisions and activities through a mental checklist:
Having researched or tested something in the past isn't a reason not to do it again, any more than it's a reason to start all over every time. What it is is an insight from a specific context you need to check for its applicability right now.
So, take this with you into your day:
What is an activity or decision you have recently dismissed because there was an effort around it in the past? How long was that ago? What has changed since then that might yield different, more actionable results?
Then, please reply to this email and let me know what came up for you.
Thank you for Practicing Product,
Tim
I'm excited to bring my beloved in-person workshops back to Berlin in January 2026. You can choose between 1-day workshops on Product Strategy, Product OKRs, or Product Discovery, or opt for the full 3-day experience for you or your team.
| LEARN MORE |
(reach out for custom team quotes)
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 #425 What Part of YouIs Making the Decision? PUBLISHED Sep 11, 2026 READ ON HERBIG.CO Dear Reader, For much of my career, I’ve helped product teams work through uncertainty. Chilling with my buddy King Arthur at Tintagel Castle I challenged assumptions, introduced frameworks, and helped people make better decisions when there was no obvious answer. While I still love doing that work, I’ve become increasingly interested in a deeper question over the past six years: From where...
Product Practice #424 Linked Better Practices over Stacked Best Practices PUBLISHED Sep 4, 2026 READ ON HERBIG.CO Dear Reader, “Let’s prioritize by value.” Value for whom? That was the question I explored in last week's essay Business Value, Customer Value, and Team Value Are Different Arguments. Today, let's demystify the term value even further. Nothing is inherently valuable. The same opportunity can have different value under different strategies. For that narrative to check out, we need...
Product Practice #423 Business Value, Customer Value, and Team Value Are Different Arguments PUBLISHED Aug 27, 2026 READ ON HERBIG.CO Dear Reader, As long as everyone focused on Value you can't do the wrong work, right? RIGHT? Well, as lovely as that sounds, I believe there's a tremendous amount of misdirected focus on value going on in teams. Let's dive into it. Three questions hide behind "value" in most conversations: Did this move a number the business gets paid on. Did customers change...