🛠️ Product Strategy Stack vs. Decision Stack: What's the Difference (Part 1)


Product Strategy Stack
vs. Decision Stack (Part 1)

READ ON

​HERBIG.CO​

PUBLISHED

Nov 22, 2024

READING TIME

3 min & 01 sec

​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.

Long-term Ambitions

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.

Strategic Choices

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.

1 Question For You To Put This Idea Into Practice

What's one strategic decision you're facing where the line between company and product strategy feels blurry? How could these frameworks help you navigate it?

Reply and let me know your answer.

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​

Join my In-Person Workshops in Berlin

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.

(reach out for custom team quotes)

Content I found Practical This Week

Product Strategy: Why You Don’t Always Need One

Process is not the product: the shadow of rituals

As a PM, I think it’s easy to fall into this trap. You write a great doc that everyone agrees upon. You lead a great brainstorm that gets everyone excited. You make it through a tough product review to get the team aligned. That’s all really important. And it’s great to feel a sense of pride when part of the process has been executed well. But, it’s not shipping... Progress in the process should not be confused with getting valuable improvements in the hands of customers.

Level, Depth, Time, and Frame

Who is Tim Herbig?

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.

Enjoy the newsletter? Please forward it. It only takes 2 clicks. Coming up with this one took 2 hours.

Product Practice Newsletter

1 tip & 3 resources per week to improve your Strategy, OKRs, and Discovery practices in less than 5 minutes.

Read more from Product Practice Newsletter

Product Practice #360 Why your Product DiscoveryFeels too Theoretical READ ON HERBIG.CO PUBLISHED Apr 25, 2025 READING TIME 4 min & 17 sec Dear Reader, Over the past two weeks, I've explored treating Product Strategy and OKRs like products to avoid Alibi Progress. Today, let's tackle the practice that often gets dismissed as "good in theory, impossible in practice" — Product Discovery. When teams tell me "we don't have time for proper Discovery," they're usually stuck in Alibi Progress —...

Product Practice #359 Make OKRs Drive Decisions,not Spreadsheets READ ON HERBIG.CO PUBLISHED Apr 18, 2025 READING TIME 5 min & 32 sec Dear Reader, Last week, we explored how treating Product Strategy like a product helps you avoid "Alibi Progress" — prioritizing correctness over value. Today, let's apply this same thinking to OKRs. If you've ever found yourself more relieved that the quarterly OKR-setting theater is over than excited about the OKRs themselves, you've experienced the symptoms...

Product Practice #358 Why your Users don't careabout your Product Strategy READ ON HERBIG.CO PUBLISHED Apr 11, 2025 READING TIME 3 min & 24 sec Dear Reader, One of the most powerful ways to spot and stop Alibi Progress is to start treating our practices like products. This means clearly defining three elements: Audience: For whom is this practice meant? Problem: What core problem does this practice aim to solve? Success: How would we know this practice has delivered value? The question then...