Why 95% of employees don't know their company strategy

April 22, 2026

·Podcast

Written by

The Product Experience
The Product Experience

Join our podcast hosts Lily Smith and Randy Silver for in-depth conversations with some of the best product people around the world! Every week they chat with people in the know, covering the topics that matter to you - solving real problems, developing awesome products, building successful teams and developing careers. Find out more, subscribe, and access all episodes on The Product Experience homepage.

Martin Eriksson — The Decision Stack | The Product Experience

Martin Eriksson — Product Leader, Co-founder of Mind the Product and ProductTank, and Author — joins us on The Product Experience podcast this week to discuss his new book, The Decision Stack: a mental model for connecting every layer of organisational strategy, from vision all the way down to the decisions teams make every single day.

They get into why 95% of employees cannot name their organisation's strategy, why exec teams are so often reluctant to fill the strategy gap, and how to challenge upwards and surface strategic gaps without putting leadership on the spot.

Plus: why empowering teams without context sends them running in every direction — and how principles, not values, are the tool that eliminates recurring debates.

Chapters

00:00
Introduction
01:11
Martin's background in product
02:19
The origin of The Decision Stack
03:44
The five questions the stack answers
04:27
Why strategy is most often missing or unclear
08:18
Who should be making strategic decisions
09:44
Time horizons: how long should strategy last
11:43
Using the decision stack in practice
13:36
How to surface gaps from lower in the organisation
16:01
Why context is the prerequisite for empowerment
19:32
How the stack reduces decision-making overhead
21:04
Language, frameworks, and avoiding rigidity
23:43
Where to start: top-down or bottom-up
26:34
Fractal stacks and scaling across teams
28:44
Strategy for maintenance work and existing products
31:41
The role of principles at the foundation of the stack
33:38
How principles emerge — top-down and bottom-up
37:07
The "this or that" technique for surfacing trade-offs
39:26
Communicating strategy continuously across the organisation
43:34
The most common mistake when getting started

Key Takeaways

Strategy is the foundation — and it's usually missing. Research cited in the book shows that 95% of employees cannot name their organisation's strategy. Exec teams compound the problem by avoiding the hard choices that real strategy requires, because real strategy means picking winners and losers.

The stack answers five questions. Where are we going? How are we going to get there? What is important right now and how do we measure progress? What actions are we going to take? And how do we choose between them? The tools — vision, strategy, OKRs, opportunities, principles — matter less than whether those questions are genuinely answered and connected.

Empowerment without context is abandonment. Teams given autonomy but no strategic clarity don't make better decisions — they scatter. The decision stack exists to give direction to empowerment, so people know which direction to run before they're given the freedom to run.

Strategy drifts if you don't maintain it. As markets shift, new people join, and AI changes assumptions overnight, the risk isn't that a strategy was wrong at the outset — it's that no one updated it. Martin recommends at minimum a quarterly check-in, even for organisations with a five-year strategy.

Principles eliminate recurring debates. When Monster's CEO declared that building the best experience for job seekers would always come first, the weeks-long internal debate about recruiter versus job seeker priority disappeared overnight. Principles are the tool that makes the right decision obvious — without a meeting.

Communication is never a one-off. A twenty-slide strategy deck shared once at an all-hands is not communication — it's an announcement. Martin references Jeff Weiner's maxim: by the time you're sick of saying something, people are just beginning to hear it. The stack has to live inside existing ceremonies, not sit in a document no one revisits.

Start where you are, not from scratch. The most common mistake is treating the stack as a reason to tear everything down and rebuild from a blank canvas. For most organisations, the better approach is diagnostic — audit what exists, find the connections that are broken or missing, and start there.

Did you find this article helpful?

Rate this article to help us improve

Your unfair advantage in product, delivered weekly.

By subscribing, you agree to our Terms & Privacy Policy

Join 170k+ product pros

Become a better product manager
Learn from product experts and become part of the world’s most engaged community for product managers
Join the community

Free Resources

  • Articles

Popular Content

Company
  • Careers

    HIRING

Follow us
  • LinkedIn

© 2026 Pendo.io, Inc. All rights reserved. Pendo trademarks, product names, logos and other marks and designs are trademarks of Pendo.io, Inc. or its subsidiaries and may not be used without permission.