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 #404 Linked Better Practices over Stacked Best Practices PUBLISHED Apr 16, 2026 READ ON HERBIG.CO Dear Reader, During a recent webinar, someone asked a question I had to think about a bit longer: "What do you do when your strategy is still early, and you're not sure if it's right?" The answer that popped into my head was based on an incredible piece of advice (or admission) I received from a former boss 10+ years ago: No one knows if their strategy is right in the beginning,...
Product Practice #403 Linked Better Practices over Stacked Best Practices PUBLISHED Apr 9, 2026 READ ON HERBIG.CO Dear Reader, During my last webinar on Connect Strategy, Goals, and Discovery with Progress Wheel, I asked people which part of their work is most prone to Alibi Progress. Almost everyone who chimed in named OKRs. And that's because many OKR cycles start the same way for teams: Someone opens a spreadsheet, fills in three to five semi-random metrics, and picks a value that isn't...
Product Practice #402 Product Discovery forInternal Enabler Teams PUBLISHED Apr 2, 2026 READ ON HERBIG.CO Dear Reader, Because the customers of your product just sit three desks away, you might think you can just "talk to them." And that's precisely what often leads to the low adoption of better product practices among product teams working on internal products (also sometimes called Enabler Teams). And why, when a user has a company email address, it is likely nobody's doing discovery on...