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 #404 Linked Better Practices over Stacked Best Practices PUBLISHED Apr 16, 2026 READ ON HERBIG.CO Dear Reader, During a recent webinar, someone asked a question I had to think about a bit longer: "What do you do when your strategy is still early, and you're not sure if it's right?" The answer that popped into my head was based on an incredible piece of advice (or admission) I received from a former boss 10+ years ago: No one knows if their strategy is right in the beginning,...
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...