Vision vs strategy vs roadmap

Most product teams drown in roadmaps and feature lists while calling the pile a strategy. A strategy is not a wish list, a vision statement or next quarter's OKRs. It is a focused bet on where you will play and how you will win — and an explicit list of what you will ignore so you can concentrate force.

Without strategy, every request looks urgent, every competitor feature looks mandatory and prioritization becomes politics. With strategy, engineers can push back on work that does not move the diagnosis.

The big idea

These four words get used interchangeably. They are not the same layer.

Marty Cagan's framing: vision is the destination, strategy chooses which problems to solve on the way, discovery finds tactics that might work and delivery ships them. Strategy sits between inspiration and backlog.

If your "strategy doc" could be swapped with another company's and still read fine, it is not strategy. Strategy names your constraint and your chosen response.

A mountain-summit poster is vision. The chosen ridge, the season you will not climb and the gear you leave behind are strategy. The analogy breaks when the mountain moves — markets do — so strategy has to be reviewed, not framed.

Walking through it

A team writes: "Become the leading collaboration platform. Delight users. Expand internationally. Invest in AI." That is vision-plus-goals, usable by any company. It does not tell an engineer whether to build on-prem SSO or kill an enterprise integration this quarter.

A strategy-shaped version: "Win mid-market SaaS by owning deploy + observe; refuse on-prem for 18 months." Now a sales request for a custom on-prem build has a clear no, unless leadership revises the diagnosis.

Common mistakes

• Calling the roadmap a strategy. A sequence of bets is execution. Strategy is the argument those bets serve.
• Vision as a substitute for choice. Ambition ("be #1", "delight customers") does not name a constraint.
• OKRs standing in for strategy. Quarterly targets are a scoreboard. They are not a diagnosis.

Check yourself

1. "Grow ARR 40% and invest in AI" — which layer is this, and what is missing?

Goals, not strategy. Missing a diagnosis of the challenge and a policy for how you will get there.

2. Why can a good vision still produce a thrashing backlog?

Vision does not choose. Without strategy, every request looks equally aligned with the destination.

Key takeaways

• Vision is destination; strategy is focused choice under constraint; roadmap and tactics execute.
• If another company could paste your strategy doc, it is not strategy.
• Use the layers to say no: work that does not serve the strategy is a distraction.

Further learning

Vision vs. Strategy — SVPGA partnership dedicated to teaching best practices to product teams and product leadersSilicon Valley Product Group

Next: the test for whether a strategy is real, in Rumelt's kernel.