How to Know if Your Product Strategy Has WorkedβDear Reader,β Your Strategy can be perfectly thought-out, based on well-researched insights, co-created by Individual Contributors and Leadership, and contain sustainable advantages over alternatives. But if nobody understands it and you can't integrate it into teams' decision-making processes, the value of Product Strategy will remain locked. The degree to which Product Strategy is executable depends on many factors like your teamβs abilities, organizational structures, and more. But the two aspects I want to focus on in this essay are the following: An executable format: Can you translate the messy work of choosing and connecting components into formats that resonate? As mentioned in the Just Enough Strategy chapter, don't treat canvases or statement structures like the defining guardrails for your strategy. See them as simplified windows into what you're trying to say. β For measuring the execution of Analytico's Product Strategy choices, the key question is: "Twelve months from now, which three metrics would tell us that this Strategy choice has worked?" For a Strategy choice like expanding their market to upstart mobile-first eCommerce shops in the US, their metrics need to go beyond "Total Revenue" or "Number of Clients." These are reactive KPIs, but not proactive measures of strategic progress. Instead, they would use metrics like
Translating your strategy into metrics will feel particularly easy if you approach your strategy creation from the βAtomicβ perspective I discussed before; you assembled and connected strategy components to form the overarching strategy patterns. Here's where you can find the first two parts of this mini-series on the valuable attributes of Product Strategy: βPart 1: How to Stop Saying Yes to Everything in Your Product Strategyβ βPart 2: How to Build a Product Strategy That Fits Your Companyβs Focusβ 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 #381 How to ConnectNorth Star Metrics and OKRs READ ON HERBIG.CO PUBLISHED Oct 23, 2025 READING TIME 5 min & 25 sec Dear Reader, I once worked with a team whose OKRs read like a best of every company's KPI dashboard: user engagement up 15%, conversion rate improved by 10%, feature adoption increased by 20%. When I asked how these connected to the specific intentions they want to pursue to drive long-term customer and business value, they couldn't link them. Their OKRs looked...
Product Practice #380 How to put Real Progressinto Practice READ ON HERBIG.CO PUBLISHED Oct 16, 2025 READING TIME 4 min & 28 sec Dear Reader, When I wrote my book Real Progress, I didn't want it to feel like a light read you browse front-to-back. Instead, I wanted it to feel dense. Dense with practical knowledge. I couldn't finish more than two pages in a row of the best non-fiction books I've ever read. Every two pages brought a new insight, nugget, or practical tip that I wanted to capture...
Product Practice #379 OKRs for MeasuringAI Adoption & Effectiveness READ ON HERBIG.CO PUBLISHED Oct 9, 2025 READING TIME 5 min & 32 sec Dear Reader, In The OKR Parallel Universe Syndrome, I wrote about an interesting cycle: Teams model their OKRs after the company OKRs. The company insists that other things are "also important." So when teams share their roadmap items connected to the OKRs, but get pushback on where the work on these "other important things" is happening. I'm not sure if this...