Product Strategy Stack
|
​Dear Reader,​
Everyone loves a Product Strategy framework.
But choosing between the Product Strategy Stack and Decision Stack isn't straightforward. Both put long-term artifacts like a Vision and Mission at the top and link their different elements. But knowing which works best for you requires decoding their layers.
Both stacks agree: you need an inspiring "roof" that transcends mere business goals. Mission, Strategy, and Goals fulfill different human needs. Mission is emotional, Strategy is logical, and Goals are measurable. Whether you call it Vision (Decision Stack) or Mission (Strategy Stack) matters less than using what resonates in your company.
You're looking for elements that create inspiration and motivation and describe the change you want to bring to your customers. "Be the change" is generic BS and neither a good Vision nor a Mission. Martin Eriksson's Mind the Product example "To make product people more successful by coming together to further our craft." is a great example.
The wording of your Mission or Vision doesn’t have to be unique - but its motivational force on team members should be.
Let's be clear: Strategy is about making (and communicating) choices that move you from status quo to vision within your market context. Importantly, neither stack prescribes how to do Strategy - they first and foremost focus on the value Strategy needs to create for you. Martin's curated Strategy toolkit shows how the actual strategic work happens outside the stack, with the stack capturing only the essence of choices made.
Where the stacks differ most is in their scope: The Decision Stack uses broader language applicable across any domain to make it applicable at a company/organization level, while the Product Strategy Stack explicitly focuses how product strategy nests within company strategy.
Here's where it gets practical: this scope difference shapes how you'll use each stack for strategy choices. While the Decision Stack keeps options open for any strategic decision, Ravi's Product Strategy Stack drives towards specific product choices - like how Slack and Discord make different strategic choices about third-party integrations to serve their respective markets.
Next week, I will work through both stacks' measurement and action layers and their real-life usage.
If you have ever benefited from my content, I'd appreciate it if you would share​ this newsletter on LinkedIn. It truly helps.
Thank you for Practicing Product,
​Tim​
I'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.
| LEARN MORE |
(reach out for custom team quotes)
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 #417 User Outcomes are Positively Flipped User Problems PUBLISHED Jul 17, 2026 READ ON HERBIG.CO Dear Reader, Last week, I mapped how OKRs connect to the layers of an Opportunity Solution Tree. But especially the Outcome layer deserves its own issue: turning a customer problem into a team-level Key Result. I first wrote about it in 2023, before I had a name for it. Since then, the positivity flip has become one of the most-used tools in my OKR and Discovery workshops, so...
Product Practice #416 How to Connect OKRs to OSTs PUBLISHED Jul 10, 2026 READ ON HERBIG.CO Dear Reader, OKRs (Objectives and Key Results) help you measure strategic progress. OSTs (Opportunity Solution Trees) are a visual structure for connecting solution and problem spaces to business goals. Let me break down how the layers of an OST connect to the practices of OKR drafting and execution: Layer 1: The Outcome Teresa differentiates between business outcomes, product outcomes, traction metrics...
Product Practice #415 Accelerated Context and the Validation Sparring Partner PUBLISHED Jul 3, 2026 READ ON HERBIG.CO Dear Reader, Most of the AI conversation in product management right now is either describing doomsday scenarios, exaggerated improvements, or warning about what might go wrong. But I am more interested in what changes for product teams doing real work. When a product team adopts an AI tool, what specifically changes about their day? What benefit do they keep coming back for,...