45:15
strategy
Most organizations' strategy is functionally invisible to their own employees (the video cites an HBR figure that 95% don't know it), and Martin Eriksson's 'Decision Stack' — a five-layer model of vision, strategy, OKRs, opportunities, and principles, mapped to five questions every org must answer — is offered as a way to diagnose, build, and continuously maintain that clarity so strategy actually gets executed.
Every organization has to be able to answer five questions: where are we going, how are we going to get there, what's important right now and how do we measure progress, what actions will we take, and how do we choose between those actions.
The Decision Stack maps these questions to five layers: vision, strategy, objectives and key results, opportunities, and principles.
Strategy is presented as the most important and most often missing or poorly done layer, because real strategy requires tough trade-offs that exec teams often avoid in favor of optionality.
Big strategic bets should be set top-down by leadership for organization-wide consistency; bottom-up insight from product, marketing, sales, and customer service should validate or challenge that strategy.
Time horizons for vision and strategy should scale to business maturity — long for established companies, only as long as the runway for a startup — and the strategy must be reviewed at least quarterly rather than set once and left alone.
'Laddering' (asking 'how' top-down, 'why' bottom-up) is offered as a diagnostic for finding where the stack is disconnected.
People without authority to set strategy can use a 'straw man' approach — proposing a tentative reading of the strategy and checking it with others — to surface gaps without appearing to challenge leadership.
The stack's layers work like interlocking blocks: each higher-level decision narrows the options below it, so a clear vision/strategy lets teams filter opportunities without re-deciding from scratch each time.
Martin deliberately avoids calling the stack a 'framework' so it isn't applied rigidly; any tool (OKRs, NCTs, VMOs) can fill a layer as long as it connects up and down.
Established organizations shouldn't discard existing strategy artifacts; the stack can be used diagnostically to find, connect, and then refine what already exists.
The stack is described as fractal — teams have their own 'mini stacks' that should ladder into the company's 'macro stack,' splitting into sub-stacks only where answers to the stack's questions diverge between teams.
Strategy is commonly misunderstood as only 'what's next' (new bets); the video argues it must also explicitly address maintaining existing offerings, described as 'the core to protect.'
Principles, the foundation layer, codify recurring trade-off decisions, emerging both top-down from well-articulated strategy and bottom-up from teams hitting the same decision repeatedly.
Named techniques for surfacing and testing trade-offs include a Miro 'decisions made / said no to' board, the 'this or that' trade-off game, and physically ranking roadmap items on a wall.
Communicating the stack is described as working best through continuous co-creation woven into existing ceremonies (all-hands, standups, planning, quarterly kickoffs), not a one-off strategy-offsite reveal.
The biggest failure modes cited for adopting the stack are trying to build the whole thing at once instead of starting small, and failing to first get organizational agreement that clarity is actually missing.
The Decision Stack — Martin Eriksson's five-layer model — vision, strategy, objectives and key results, opportunities, and principles — mapped one-to-one onto five questions every organization must answer: where are we going, how do we get there, what's important now, what actions do we take, and how do we choose between them. Apply: Use it to check whether an organization has actually answered all five questions, and whether the answers connect coherently from vision down to daily decisions.
Vision (Decision Stack layer) — The top layer, answering 'where are we going'; for an established business it can sit far out in time and possibly never be fully achieved, with Google's 'organizing the world's information' given as an example. Apply: Write it as a document or even a simple phrase, and make sure every team's own vision ladders up into this one shared organizational vision rather than drifting into slightly different versions.
Strategy (Decision Stack layer) — The second layer, answering 'how are we going to get there'; called the most important layer and the one most often missing or poorly done because it requires tough trade-off choices rather than optionality. Apply: Set the big bets (which markets, positioning, how to win) top-down from leadership, explicitly include maintaining existing offerings ('the core to protect') alongside new bets, and review it at least quarterly.
Objectives and Key Results (OKRs) — A specific tool named for the third layer of the stack, answering 'what's important right now and how do we measure progress' — presented as one option, not mandatory. Apply: Adopt OKRs (or a substitute like NCTs or VMOs) only after the team agrees what the term concretely means for them, ensuring objectives connect up to strategy and down to opportunities.
Opportunities (Decision Stack layer) — The fourth layer, answering 'what actions are we actually going to take to move forward'; opportunities that don't connect back to stated strategy are meant to be dropped. Apply: List candidate opportunities, filter out any not connected to strategy, and focus discovery/experimentation on the ones that remain (the video's example: 10 options down to 4).
Principles (Decision Stack layer) — The bottom/foundation layer, answering 'how do we choose between those actions' — a strong reflection of strategy articulated as a concrete trade-off, arising both top-down from well-articulated strategy and bottom-up from teams hitting the same decision repeatedly. Apply: When a team faces the same decision repeatedly, escalate it, debate it with data, then codify the resolution as a principle instead of re-deciding it from scratch each time, as in Monster's CEO ruling to build for job seekers first.
Laddering (top-down 'how' / bottom-up 'why') — A diagnostic technique: reading the stack top-to-bottom should chain 'how' (vision → strategy → objectives), while reading it bottom-to-top should chain 'why' back up. Apply: Ask 'why' about a piece of work; if it reaches goals/OKRs but the next 'why' gets a blank stare, that signals a missing or disconnected strategy layer.
Individual exec-interview diagnostic — Martin's practice of asking each member of an executive team, one-on-one, what the organization's strategy is. Apply: Compare the divergent answers as concrete evidence to the exec team that strategic alignment is missing.
Straw man approach — A technique for people without authority to set strategy to surface a missing or unclear strategy without appearing to challenge leadership, by proposing a tentative version and checking it. Apply: Say something like 'I'm not sure what our strategy is, so I think it's this — does that make sense?' and socialize it broadly, treating both agreement and challenge as useful signal.
Quarterly strategy check-in cadence — A recommended minimum review rhythm for strategy, replacing the old habit (vision at 3–5 years, strategy at 1–3 years) of setting it once and never revisiting it. Apply: Re-test strategic assumptions and direction at least every quarter, reacting sooner to major shifts such as AI.
NCTs (Narratives, Commitments, Tasks) — An alternative tool to OKRs for the 'what's important now' layer of the stack. Apply: Substitute NCTs for OKRs where an org prefers narrative-based planning, as long as the layer still connects to strategy above and opportunities below.
VMOs — Another named tool mentioned alongside OKRs and NCTs as an option for the objectives layer; not further defined in the source. Apply: Use it as a possible substitute for OKRs if it's the org's existing convention, subject to the same connect-up/connect-down requirement.
Decision Stack as diagnostic for existing orgs — Using the stack to audit an established company's existing strategy artifacts rather than starting from a blank page. Apply: Pull in old documents (e.g., an unused strategy doc from an offsite), check whether they still connect to current objectives, and only then challenge or refine them.
Mini stacks / macro stack (fractal stacking) — The idea that a team's own local decision stack should ladder up into the company's overall 'macro' stack, becoming more fractal as the company scales. Apply: Let sub-teams define their own objectives, opportunities and principles, while keeping vision and strategy shared at the business-line level to avoid drift.
Splitting rule for sub-stacks — A rubric for deciding where to break one decision stack into separate sub-stacks: split at the point where different teams' answers to the stack's questions start diverging. Apply: Give each business line one shared strategy but allow the teams within it to have different objectives, rather than running a full independent stack for every team.
Opportunity Solution Tree — A comparable strategy-documentation approach mentioned alongside the decision stack, noted in the conversation as tending to emphasize a small number of 'sexy' big bets. Apply: Referenced only as a point of comparison in this source, not elaborated as a technique to apply.
Product Requirement Documents (PRDs) — The old-style, multi-month specification documents Martin describes writing at Monster starting in 1999, thrown 'over the wall' to engineering. Apply: Cited as historical context for how strategic debates used to get resolved slowly, not offered as a technique to adopt today.
Miro 'decisions made / said no to' board — A practice of keeping a dedicated area on a Miro board that visualizes decisions a team has made and options it has said no to. Apply: Use it to make trade-off conversations and rejected options visible and comparable across different teams.
'This or that' game — An exercise credited to Adam War Burton that puts stark trade-off pairs (new customers vs. recurring revenue, retention vs. growth, mobile vs. desktop) in front of a team to observe reactions. Apply: Run it to surface disagreement and prompt people to articulate why they favor one side of a trade-off, revealing unstated assumptions that could otherwise pull the team in different directions.
Physical/tangible prioritization (post-it wall ranking) — A technique of writing roadmap items on post-it notes and physically ranking them on a wall, forcing a single order rather than declaring items 'equally important.'. Apply: Use with CEOs and exec teams who resist trade-offs, to force an honest single ranking instead of an 'AND' list.
thedecisionstack.com 'This or That' app — A web app/poll tool the guest built at thedecisionstack.com for teams to register their views on trade-offs. Apply: Use it to run the 'this or that' exercise digitally/remotely with a team.
'OR organization vs. AND organization' framing — A framing, quoted from a CEO's objection, describing an org that resists trade-offs by trying to pursue everything ('AND') versus one that accepts forced prioritization ('OR'). Apply: Recognize this objection as the mechanism by which exec teams avoid real strategic trade-offs, and counter it with tools like physical ranking or the 'this or that' game.
Co-creation as communication strategy — The claim that involving broad, cross-functional representation in building the strategy/objectives is itself the most effective way to communicate them afterward. Apply: At scale, include representatives from different departments and functions in the strategy-creation process so clarity spreads outward naturally.
Embedding communication into existing ceremonies — A recommendation to repeat strategic context inside all-hands, standups, planning sessions and quarterly kickoffs rather than relying on a single reveal. Apply: Add a brief strategy/objective reminder into existing recurring meetings instead of a one-off strategy-offsite announcement with a slide deck that's never mentioned again.
Rule of seven (marketing heuristic, referenced) — A marketing repetition heuristic referenced as an analogy, paired with a paraphrase of LinkedIn CEO Jeff Weiner ('once you are sick of saying it, people are starting to hear it'), for how many times a message must repeat before it lands. Apply: Use it to justify deliberately over-communicating strategy well past the point where it feels repetitive to the person saying it.
'Think big, start small' rollout principle — A change-management/innovation principle applied to introducing the decision stack, cautioning against trying to build the whole stack at once (e.g., in a single offsite). Apply: Start with whichever single layer is weakest — e.g., just improve objectives first — check that it ladders to the rest of the stack, and expand from there.
'Ask everyone in the company' diagnostic — Martin's closing recommendation ('my trick') to ask people across the whole company, not just the exec team, what they think the strategy is. Apply: Use the breadth and divergence of the answers as visible proof to the organization that action is needed on strategic clarity.
Missing strategy is framed as often not a case of leadership never setting one at all, but of a lack of ongoing maintenance as the company, team, and market change — the stack silently decays even after being done well once.
Asking each executive individually (rather than as a group) is diagnostic precisely because a group setting lets people nod along without actually holding the same mental model, which is why Martin gets a different answer from almost everyone he asks.
Company values are described as failing as decision tools specifically because they don't specify a trade-off; a principle only becomes useful once articulated as a concrete choice, as in Monster's CEO ruling to build for job seekers first and let recruiters follow.
Placing 'principles' at the bottom of the stack rather than near the top next to strategy (where they logically originate) is presented as a deliberate design choice: it makes proposing or challenging a principle feel psychologically safer for teams than challenging strategy directly, even though principles are described as a strong reflection of strategy.
A CEO's objection that 'we're an AND organization' is treated as naming the actual mechanism by which exec teams dodge trade-offs — declaring priorities 'equally important' avoids the discomfort of a forced ranking, which is why physically ranking sticky notes on a wall (no ties allowed) is offered as an effective counter.
For mature, multi-line businesses, the video suggests the real strategic decision is often about pruning (e.g., cutting a large but non-growing, costly-to-maintain business line) rather than adding new bets — something that stays invisible if strategy is framed only as 'what's next.'
Overcommunication that feels repetitive to the leader saying it is framed as the point at which it actually starts landing with the organization, echoed via a paraphrase of LinkedIn CEO Jeff Weiner and marketing's 'rule of seven.'
«95% of employees do not know their organization strategy. If you have a great strategy, if your team doesn't know what it is, how the hell are they going to execute it?»
— 00:00
«I think every company or every organization has to be able to answer these questions. One, where are we going? Two, how are we going to get there? Three, what's important right now and how do we measure progress? Four, what actions are we actually going to take to move forward? And five, how do we choose between those actions.»
— 00:08
«I will go and ask the exec team individually what the strategy is. And you might not be surprised that I get a different answer from just about everyone I talk to.»
— 07:12
«Exec teams don't really want to make strategy sometimes. They don't want to do what is real strategy, which is making really tough choices cuz they like optionality.»
— 07:41
«...that X turned out to be, you know, 80% of the benefit for 20% of the effort.»
— 17:00
«And that's what real empowerment feels like to me.»
— 17:26
«If you want like the one-word summary of that book, it is empowerment.»
— 17:42
«If you empower teams without context, they just start running in every single direction.»
— 18:03
«It's almost like Jenga blocks or Lego blocks that lock together.»
— 19:44
«I'm so kind of cautious about trying to call it a framework cuz I don't want it to be applied as like, 'Oh, well, we have to like follow the stack.'»
— 21:55
«It does become fractal a little bit as you kind of scale the company.»
— 27:00
«Part of the strategy is are we maintaining the thing that we already have.»
— 30:06
«If we build the best possible experience for job seekers, then recruiters have to follow.»
— 32:41
«We have values which can be amazing, right? But they're not really helping us make decisions.»
— 33:19
«It's the challenge of whenever you're trying to come up with one of these mental models... how do we simplify an end-dimensional complex world into two dimensions that fit on a page and make sense mentally?»
— 35:36
«I once had a CEO say to me, the problem with you guys is that you're an OR organization and we're an AND organization.»
— 37:49
«Once you are sick of saying it, people are starting to hear it.»
— 40:44
«Think big, but start small.»
— 43:55
«Copy my trick, right? Go talk to everyone in your company about like, what do you think our strategy is?»
— 44:24
Reception
No comments are available to gauge audience reception.
This is a practitioner's synthesis rather than empirical research — the central 95% statistic is attributed to a single HBR article, and the supporting cases (Monster, an anonymized client, a junior-developer anecdote) are illustrative stories from Martin's own career rather than independently sourced data; its value lies in the reusable diagnostic techniques (laddering, the exec-interview diagnostic, straw man, this-or-that) more than in novel theory.
45:15