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 #417 User Outcomes are Positively Flipped User Problems PUBLISHED Jul 17, 2026 READ ON HERBIG.CO Dear Reader, Last week, I mapped how OKRs connect to the layers of an Opportunity Solution Tree. But especially the Outcome layer deserves its own issue: turning a customer problem into a team-level Key Result. I first wrote about it in 2023, before I had a name for it. Since then, the positivity flip has become one of the most-used tools in my OKR and Discovery workshops, so...
Product Practice #416 How to Connect OKRs to OSTs PUBLISHED Jul 10, 2026 READ ON HERBIG.CO Dear Reader, OKRs (Objectives and Key Results) help you measure strategic progress. OSTs (Opportunity Solution Trees) are a visual structure for connecting solution and problem spaces to business goals. Let me break down how the layers of an OST connect to the practices of OKR drafting and execution: Layer 1: The Outcome Teresa differentiates between business outcomes, product outcomes, traction metrics...
Product Practice #415 Accelerated Context and the Validation Sparring Partner PUBLISHED Jul 3, 2026 READ ON HERBIG.CO Dear Reader, Most of the AI conversation in product management right now is either describing doomsday scenarios, exaggerated improvements, or warning about what might go wrong. But I am more interested in what changes for product teams doing real work. When a product team adopts an AI tool, what specifically changes about their day? What benefit do they keep coming back for,...