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
🛠️ How does your Traffic Light Strategy look?
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. |
Product Practice Newsletter
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 #403 Linked Better Practices over Stacked Best Practices PUBLISHED Apr 9, 2026 READ ON HERBIG.CO Dear Reader, During my last webinar on Connect Strategy, Goals, and Discovery with Progress Wheel, I asked people which part of their work is most prone to Alibi Progress. Almost everyone who chimed in named OKRs. And that's because many OKR cycles start the same way for teams: Someone opens a spreadsheet, fills in three to five semi-random metrics, and picks a value that isn't...
Product Practice #402 Product Discovery forInternal Enabler Teams PUBLISHED Apr 2, 2026 READ ON HERBIG.CO Dear Reader, Because the customers of your product just sit three desks away, you might think you can just "talk to them." And that's precisely what often leads to the low adoption of better product practices among product teams working on internal products (also sometimes called Enabler Teams). And why, when a user has a company email address, it is likely nobody's doing discovery on...
Product Practice #401 How to Close Your Confidence Loop PUBLISHED Mar 26, 2026 READ ON HERBIG.CO Dear Reader, Most teams can tell you what they're building. Far fewer can tell you why it matters and how they will know it has worked. And I mean in a connected, defensible way that traces from their next release or discovery back to a company goal. That gap is where confidence lives (or doesn't). The confidence loop describes the critical questions you need to be able to answer and connect to...