How to Build a Product Strategy That Fits Your Company’s Focus​Dear 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.
Product Practice #353 How Duolingo Approaches Strategy, OKRs, and Discovery READ ON HERBIG.CO PUBLISHED Mar 7, 2025 READING TIME 4 min & 24 sec Dear Reader, Many Product Managers were in awe of the ways of working shared in The Duolingo Handbook a few weeks ago. While it’s an inspiring read, I used this as a reason to revisit some of my all-time favorite reads about how this company operates (or at least used to operate) and extract my takeaways with you. Duolingo focuses on “Movable” Metrics...
Product Practice #352 My Digitale Leute Summit 2024 Keynote Recording and Slides READ ON HERBIG.CO PUBLISHED Feb 28, 2025 READING TIME 1 min & 40 sec Dear Reader, I'm excited to share the full recording of my talk on How Product Teams Can Connect the Dots of Strategy, OKRs, and Discovery from last year's Digitale Leute Summit. You can think of it as the naturally progressing chapter (hint hint) that would follow my talk from Product at Heart 2024. As always, I won't require you, as an...
Product Practice #351 The Post-it trap: Why Strategy needs more than Workshops READ ON HERBIG.CO PUBLISHED Feb 21, 2025 READING TIME 5 min & 19 sec Dear Reader, 'Product Strategy by Post-it' occurs when teams prioritize filling out frameworks over making real strategic choices. It's a common symptom of treating strategy as a checkbox exercise rather than a tool for decision-making. John Cutler even suggests that most frameworks should feature a warning label like this: "This framework is...