How to Build a Product Strategy That Fits Your Company’s FocusDear Reader, Besides being decisive, another attribute that can determine the value of your Product Strategy is how layered it is. The best way to think of the interplay between the Company and Product layers is the magnitude of overlap between each of them: Is the audience you chose for your Product part of the prioritized audience by the company? Is the distribution channel you want to leverage mastered by the company? How can you make your offering stand out using the company's existing differentiators? So, a critical attribute of a useful Product Strategy is its ability to fit into the Company Strategy and make coherent choices that inform the intentional delivery of Features. Here's how our exemplary b2b SaaS company, Analytico, can make use of this: As a company, Analytico had established the route of doing one thing really, really well ( web eCommerce tracking) through a fully integrated solution (as opposed to catering to more use cases through integrations). For the new predictive checkout optimization features, this meant not getting lost in all the possibilities of other checkouts: No tiered pricing or subscriptions. While stakeholders suggested other checkouts that could be optimized, the product team could use the established company focus to narrow its perspective on audiences and problems worth solving. Among others, they prioritized GDPR compliance and the ease of use for integrating with web technologies like Progressive Web Apps (PWAs). This way, they could reinforce the company's established strengths and increase the chances of succeeding for Next week, we'll wrap up this miniseries by looking at how Analytico can ensure its Product Strategy is Executable. 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 Join my In-Person Workshops in BerlinI'm excited to bring my beloved in-person workshops back to Berlin in January 2025. You can choose between 1-day workshops on Product Strategy, Product OKRs, or Product Discovery OR get the full 3-day experience for you or your team.
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...