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.
Product Practice #342 The OKR Trap:Reporting vs. Progress READ ON HERBIG.CO PUBLISHED Nov 12, 2024 READING TIME 3 min & 04 sec Dear Reader, Similar to being focused on Discovery motions, but missing Discovery decisions, simply filling in OKR templates will lead to reporting, but not measuring progress. OKRs that report numbers try to get a template-based Objective right and define a Key Result as something with a number. OKRs that measure progress take care of the hard conversations through...
Product Practice #341 The Context Matrix READ ON HERBIG.CO PUBLISHED Nov 8, 2024 READING TIME 2 min & 11 sec Dear Reader, Every level of product management involves two areas: creating context and making sense of it. While creating the context partially depends on the environment you work in, making sense of the context mainly depends on the hard skills a product team has. For Product Strategy, the context consists of internal and external data points about the market, your capabilities, how...
Product Practice #340 How to Navigate Product Discovery Like a Map READ ON HERBIG.CO PUBLISHED Nov 1, 2024 READING TIME 4 min & 51 sec Dear Reader, βWe need to complete all six Discovery phases in order." "Let's perfect that JTBD statement before we talk to users." "Our process requires detailed one-pagers before any customer interviews." Does this sound familiar? These are examples of dogmatic defaults: Teams cycling through the same tools in the same order, regardless of context. While...