MODULE 1 · VISION & STRATEGY · TOOL 02

Mission · Vision · Strategy · Roadmap Ladder

The hierarchy that ends the ‘is this strategy or roadmap?’ argument — five rungs, each answering a different question on a different time horizon.

Category · Vision & Strategy Complexity · Beginner–Intermediate Time to apply · 60–120 min Pairs with · OKRs · Vision

A WHAT IT IS

The framework

The Mission / Vision / Strategy / Roadmap Ladder maps the relationship between four terms product teams routinely confuse or collapse into one another. Each rung answers a different question, operates on a different time horizon, and changes at a different cadence.

The power isn't in the definitions — any PM can memorise those in five minutes. It's in the discipline of knowing which level a conversation is happening at and anchoring the debate there. When a CEO says "strategy" and a PM hears "roadmap," the result isn't a misunderstanding — it's misaligned work, wasted quarters, and features that serve no strategic purpose.

THE FIVE RUNGS

MISSION → why we exist (timeless, never changes)
VISION → what the future looks like if we win (3–10 yrs, rarely changes)
STRATEGY → how we'll get there (1–3 yrs, changes with the market)
ROADMAP → what we'll build and when (quarterly, changes often)
OKRs / KPIs → how we measure progress at every level (quarterly, resets)

B WHY IT MATTERS

What conflation costs

Most "strategy debates" are really arguments happening at the wrong rung. The ladder makes the level explicit so the debate can resolve.

Without the ladder…	The damage	The fix it provides
Mission gets treated as strategy "Make the world better" becomes the plan.	The roadmap has no filter — every idea passes, because any idea can be tied to a vague mission.	Each rung must answer a different question, making conflation impossible.
Roadmap and strategy get swapped	Engineers get a feature list called "the strategy" and optimise for shipping speed, not direction. Features ship that don't compound.	Strategy sets direction; roadmap sets sequence. The separation makes the difference visible.
Every priority debate is a backlog debate	Hours spent arguing tickets instead of asking which strategic bet they serve. Debates never end because they're at the wrong abstraction.	Anchor the argument one rung up: which bet does this serve?
The "strategy" changes every quarter	Presenting a roadmap as strategy signals instability to investors and erodes trust — real strategy shouldn't churn every 12 weeks.	Strategy lives above the roadmap and changes far less often.

C HOW TO RUN IT

Building the ladder top-down

Work from the top rung down. Each level must be derivable from the one above it — if a roadmap item can't be traced up to a strategic bet, it doesn't belong.

Establish the mission — why you exist

One timeless sentence about the change you're trying to make in the world. Test it: a mission with a date or a number ("reach $10M ARR by 2026") is a goal, not a mission. A real mission could still be true in twenty years.

Define the vision — what winning looks like

A concrete picture of the world 3–10 years out if you succeed. Inspiring, customer-centric, and stable. This is where the Product Vision Template (Tool 01) plugs in as the articulated form.

Set the strategy — how you'll get there

The hard one. Strategy is a small set of choices and trade-offs — usually two to four "bets" over 12–18 months. The test: does your strategy say no to something? If everyone can agree without giving anything up, it's a vision, not a strategy.

Build the roadmap — what ships, and when

The sequence of work that delivers each strategic bet, mapped to quarters. Every roadmap item names the bet it serves. Items that serve no bet are the first to cut when capacity is tight.

Set OKRs — how you measure progress

Objectives and Key Results that track whether each rung is working. They reset quarterly and connect the abstract (strategy) to the concrete (did the roadmap move the number?). Covered in depth in Tool 20.

D IN PRACTICE

When the "strategy" was really a roadmap

IN PRACTICEboard prep · early-stage SaaS

A PM was asked to present "the product strategy" to the board and arrived with a slide listing fourteen upcoming features. A reviewer stopped them: "That's a roadmap. What are the two or three bets those features serve?"

Forced up a rung, the team found the fourteen features collapsed into three actual bets — prove value to buyers, deepen activation, build a referral loop. Several pet features served no bet at all and were quietly dropped. The board conversation shifted from "why these features?" to "are these the right bets?" — a far more useful discussion, and one that didn't need to change every quarter.

The lesson: if your strategy changes as often as your roadmap, you don't have a strategy — you have a roadmap wearing a strategy's name tag.

E THE ARTIFACT

The ladder, filled in

The deliverable is a single one-page ladder anyone can read top-to-bottom and see how the daily work traces to the reason the company exists.

Rung	Answers	Horizon	Changes when…
Mission	Why we exist	Timeless	Almost never — only if the company fundamentally redefines itself.
Vision	What winning looks like	3–10 years	Rarely — when the destination itself shifts.
Strategy	How we'll get there	1–3 years	With major market or competitive shifts — not every planning cycle.
Roadmap	What & when	Quarterly / annual	Often — as discovery and capacity change.
OKRs / KPIs	How we measure	Quarterly	Every quarter — they reset by design.

F THE SO-WHAT

The discipline is the value

THE KEY INSIGHT

The ladder doesn't make better strategy — it makes you notice which rung you're standing on. Most wasted quarters come from arguing roadmap when the real disagreement is about strategy.

When a debate stalls, the move is to ask: "Which rung is this argument actually about?" A feature fight is usually a strategy disagreement in disguise. Naming the rung relocates the conversation to where it can be resolved — and stops the team from re-litigating settled questions at the wrong altitude.

G MISTAKES & LIMITS

Common mistakes

⚠Confusing strategy with vision

"Become the go-to platform for X globally" is a vision, not a strategy — it contains no trade-off. Test: does it say no to anything? If everyone can agree without sacrificing something, it's not strategy.

⚠Treating the roadmap as the strategy

Presenting a feature list as "the strategy" is the most common exec-setting PM mistake. Roadmaps change quarterly; strategy shouldn't. Always show the roadmap one rung below strategy.

⚠Writing a mission that expires

"Grow ARR to $10M by 2026" is a business goal, not a mission. A mission has no finish line. Goals belong in OKRs, not on the top rung.

⚠Skipping rungs

Jumping from mission straight to roadmap leaves no strategy to filter against — so every feature looks justified. The middle rungs are exactly where prioritisation lives.

When not to use it

You're in pure execution mode on a settled plan. If strategy is agreed and stable, you don't need to rebuild the ladder every sprint — reference it, don't re-derive it.
The company is pre-product and pre-customer. With nothing to learn from yet, lower rungs are guesses. Establish mission and a rough vision, then let discovery fill in strategy.
As a substitute for the actual thinking. The ladder organises strategic choices; it doesn't make them. A neat ladder with empty bets is still no strategy.

H CONNECTS TO

Where this sits in the toolkit

Contains → Product Vision Template

The Vision rung is exactly the sentence Tool 01 produces. The ladder shows what sits above it (mission) and below it (strategy, roadmap).

Feeds into → OKRs

The bottom rung is OKRs (Tool 20). Each strategic bet gets objectives; each roadmap item gets key results that tell you if the bet is working.

Filters → Prioritisation frameworks

RICE, ICE, and MoSCoW all assume a strategy to score against. The ladder's strategy rung is the "strategic fit" input those scores depend on.

Extends into → Module 2 strategy tools

The Strategy Stack, Good Strategy vs Bad Strategy, and the strategy checklist go deep on the rung this ladder only sketches.

TRY IT YOURSELF

Audit a product you work on

Write one line for each rung — mission, vision, strategy, roadmap, OKRs — for a product you know. Don't look anything up; write what the team actually behaves as if it believes.

Now check two things: does the mission have a date or number in it (if so, it's a goal)? And does the strategy say no to anything (if not, it's a vision)?

Most teams discover their "strategy" is really a vision and their "mission" is really a goal. Fixing which rung each statement belongs on is often the whole exercise.