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 #430 How to Think About Product Strategy in the Age of AI PUBLISHED Oct 16, 2026 READ ON HERBIG.CO Dear Reader, Two weeks ago, I had the incredible opportunity to be on Akash's Product Growth Podcast. Now that the episode is out, I can finally share it with you as well. I typically don't put podcast episodes front and center in this newsletter, but since this is more of a 1-hour AI Product Strategy Masterclass than an audio-only podcast, I think it's one of the best pieces of...
Product Practice #429 Linked Better Practices over Stacked Best Practices PUBLISHED Oct 11, 2026 READ ON HERBIG.CO Meet Me Next Week at Just Product 2026 Get your Ticket Dear Reader, When a leadership team wants to introduce OKRs, it can be tempting to start by turning every bullet point of your strategy into an OKR. But a long list of priorities will still compete for the same time and attention, even when it gets repackaged. Before moving into OKR drafting, I like to work through this...
Product Practice #428 Linked Better Practices over Stacked Best Practices PUBLISHED Oct 5, 2026 READ ON HERBIG.CO Dear Reader, Sorry for the slip in sending this one out on Friday. To make up for it, there will be (for the first time ever) two newsletters going out this week. Recently, a CPO told me about an engineer who had used AI to develop a proposal. But when the decisions in it were questioned, the engineer kept referring him back to the output. The CPO wondered how that conversation...