How to Stop Saying Yes to Everything in Your Product StrategyDear 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 #394 Can an AI Interviewer doYour Concept Testing? PUBLISHED Feb 6, 2026 READ ON HERBIG.CO Dear Reader, What happens when you let an AI do the concept testing of design variations? I used Reforge's AI Concept testing* to find that out. As a prototype, I chose an app idea that lets you document taste notes from brewing specialty coffee. And I need your help exploring how AI-led interviews feel for participants (and improving the app design ☕️). I mostly went with their...
Product Practice #393 How much Money willthis Feature make? PUBLISHED Jan 30, 2026 READ ON HERBIG.CO I'm hosting my first free live webinar in 2026: Go From "We Need a Strategy" to "Here's Exactly What We're Doing and Why" — In 60 Minutes on Feb 11 at 5:00 PM CET (11:00 AM EST | 8:00 AM PT). Bring all your questions, and I will work through them on the spot. Note that there will be no recording - this is about hands-on interaction, not just information transmission. CLAIM YOUR FREE SPOT Dear...
Product Practice #392 From Product Jargonto Plain English READ ON HERBIG.CO PUBLISHED Jan 23, 2026 READING TIME 3 min & 29 sec Dear Reader,I often feel that, somewhere along the way, we, as an industry, started optimizing for sounding like product people instead of speaking like humans in plain English (or any other language). What would happen if we dropped the product lingo and used plain English to describe what's needed? I find it increasingly liberating for product teams to describe...