How does your Traffic Light Strategy look?​Dear Reader,​ Here’s the good news: Your Product Strategy doesn’t have to be 100% proven and watertight based on evidence before you can start sharing and working on it. Instead of trying to hide the assumptions present in your strategy, embrace them by using what I like to call the “Traffic Light Strategy.” This ties in with the idea that your Strategy consists of individual but coherent components that fill universal strategy patterns with life. Once articulated, you can color-code the individual components according to their degree of “unprovenness.” Green - Let’s go. Your green strategy components are rock-solid foundations for decision-making. This applies to things you can fully control (like the definition of your Vision) or components that are really well-proven, like the choice of user segments based on the strong qualitative and quantitative signal you received. Yellow - Just enough Conviction. Don’t hold back on making decisions based on these components, but be clear about how proven these are. Maybe you have a hunch about the buyer segment you need to serve to reach your target user segment, but not more. Or your strategy metrics sort of tie in with where you want to go, but they lack specificity. Derisking these components shouldn’t be your first priority, but be aware of their somewhat shaky substance. Red - Beware the Assumption. Whether due to a lack of data or the high degree of HiPPO decisions, Some components making up your Product Strategy are just wild guesses. These can either be the assumed reasons why customers will pick you over an alternative (no, a nice UI isn’t a strong moat) or how you will reach users to deliver your value proposition. Making these components explicit has two advantages: First, you get your next Discovery priorities “for free.” Second, you avoid working on your strategy for too long in the ivory tower by being upfront about what has to be clarified further by doing the work instead of thinking about doing the work. Did you enjoy this one 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​ How to Dive Deeper into Product StrategyLearn how I helped companies like Chrono24 and ausbildung.de hone their Product Strategy practices. I closely work with product organizations through workshops and coaching to introduce and adapt Product Strategy.
What did you think of this week's newsletter? As a Product Management Coach, I guide Product Teams to measure the progress of their evidence-informed decisions. I identify and share the patterns among 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 #384 Pragmatic OKRsKeynote Recording READ ON HERBIG.CO PUBLISHED Nov 13, 2025 READING TIME 2 min & 16 sec Dear Reader, Possibilities to Connect with me in the Next Two Weeks Nov 13: Product Owner Day (Online, German) Nov 18: UXCam Live Workshop (Online, English) Nov 18: Scrum Event (Online, English) Nov 20: ProductTank FFM (In-person, English) I hope to see you there. This week, I want to share the recording from my talk on Pragmatic OKRs from this year's World OKR Summit:...
Product Practice #383 When to recognizeYour OKR Planning takes too long READ ON HERBIG.CO PUBLISHED Nov 6, 2025 READING TIME 5 min & 37 sec Dear Reader, It's week three of Q4 planning. Your team has revised the OKRs five times. Leadership wants one more alignment session. The quarter starts in a week, but you haven't actually begun working toward the goals yet. The moment you're tweaking wording instead of committing to a strategic goal, you've crossed from Real Progress into Alibi Progress....
Product Practice #382 Discovery Activitiesover The Discovery READ ON HERBIG.CO PUBLISHED Oct 30, 2025 READING TIME 3 min & 52 sec Dear Reader, Most teams treat Discovery like a season: "We'll do Discovery for Q1, then build in Q2." This creates a problem. It separates learning from building, makes stakeholders impatient, and turns Discovery into something you have to defend rather than a practical way to reduce uncertainty. The real question isn't "Are we doing Discovery?" It's "Are we...