How to Stop Saying Yes to Everything in Your Product Strategy​Dear Reader,​ Three weeks ago, I shared with you Why you don’t get Value from your Product Strategy. Today, we're going to talk about the How. Making your Product Strategy decisive means making choices that help answer "What does this allow us to say no to?" Imagine a b2b SaaS Analytics software called Analytico. If your Product Strategy says you target "Companies building Digital Products," every stakeholder conversation will go like this: "We need customizable dashboards to meet a company's branding." - "That sounds reasonable." "We need a data import from Shopify" - "I guess we could do that." "We need native Android and iOS SDKs" - "Sure, companies might need that." You don't have a basis for saying no to any of these. But if you break down your audience into comically narrow segments, you shift the conversation. You can break "Companies building Digital Products" down by many criteria: Business model, industry, revenue, number of employees, geography, technology used, etc. This might lead you to a segment like "European Web-first eCommerce companies making 10-50M€ per Year in Revenue." Nobody knows exactly if this is the right segment. It's an informed assumption. But at least this choice shifts the priorities: "We need customizable dashboards to meet a company's branding." - "No, our customers are scrappy and don't represent their data to the outside." "We need a data import from Shopify" - "Yes, 75% of our target customers run on Shopify." "We need native Android and iOS SDKs." - "No, there are only 100 native eCommerce apps in the European App Store, and none of them fall within our target segment." Other possible tentpoles you can establish to make your Strategy conversation more decisive are:
Next week, we talk about how Analytico can ensure its Product Strategy is Layered. Did you enjoy this one or have feedback? Let me know and reply. Hearing from you is what motivates me whenever I sit down to write this newsletter. If this newsletter isn't for you anymore, you can unsubscribe here. Thank you for Practicing Product, ​Tim​ Good News!There are a few tickets available for my 1-day Product Strategy workshop in Cologne on November 14. Learn how to navigate the practices of Product Strategy with confidence.
What did you think of this week's newsletter? 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 #408 How to Spot and StopDiscovery Slop PUBLISHED May 15, 2026 READ ON HERBIG.CO From Strategy to Derisked Assumptions Workshop Make clear strategy choices, translate them into leading product goals, and understand needed Discovery actions before deciding what to build (with and without AI Assistance). Next 3x 4h Workshop Cohort: Jun 15/16/17 Claim your Free Spot Dear Reader, The first time I heard Julia mention the idea of Discovery slop, I knew she was onto...
Product Practice #407 Your Goal Depends on Another Team — Now What? PUBLISHED May 7, 2026 READ ON HERBIG.CO Dear Reader, Your Key Result says to "Improve Conversion Rate by 7%," but you only control on-site search. You want to drive customer retention, but the marketing team is focused on new acquisition. Most teams respond in one of two ways: they water down the goal until it fits their scope (and lose the ambition), or they keep the big goal and quietly accept they can't move it. Both lead...
Product Practice #406 Why your Company's POV on OKRs matters more than Processes PUBLISHED Apr 30, 2026 READ ON HERBIG.CO Dear Reader, Before I talk with companies about OKR cadences, templates, or tools, I ask them: "What do you expect to change by using OKRs?" The answers take a bit of time. Not because they don't exist, but because OKRs have been treated as a solution without a problem to solve. OKRs haven't been treated as a product, but as a process without purpose. They've chosen a...