---
title: "Product Vision vs Strategy vs Roadmap"
description: "Product vision vs strategy vs roadmap: how mission, vision, objectives, opportunities and solutions connect as one chain, with a worked example and a test."
canonical_url: "https://builderscamp.com/guides/other/product-vision-vs-strategy-vs-roadmap"
date_published: "2026-09-26"
date_modified: "2026-09-26"
author: "Andre Albuquerque"
publisher: "Builders Camp"
guide_class: "other"
---

# Product Vision vs Strategy vs Roadmap

**TL;DR:** A product vision is the future state you are building toward, usually 2 to 5 years out; the strategy is the few opportunities most likely to grow your North Star metric on the way there; the roadmap is the sequence of solutions you will build or test to pursue those opportunities. Mission sits above all three, and objectives sit between vision and strategy.

## What is the difference between product vision, strategy and roadmap?

The vision is the destination, the strategy is the choice of which problems to solve to get there, and the roadmap is the order in which you will build or test solutions to those problems. Shreyas Doshi, a startup advisor whose LinkedIn profile lists past roles at Stripe, Twitter, Google and Yahoo, compressed the whole stack into one [LinkedIn post](https://www.linkedin.com/posts/shreyasdoshi_mission-why-vision-what-strategy-how-activity-6866621883920601088-J9Ok): "Mission: Why Vision: What Strategy: How Segmentation: Who Positioning: Where Roadmap: When Goals: What's next". Marty Cagan of SVPG gives the vision a time frame in [Vision vs. Strategy](https://www.svpg.com/vision-vs-strategy/): "The product vision describes the future we are trying to create, typically somewhere between 2 and 5 years out."

Cagan's range is a norm drawn from software companies, and he gives 5 to 10 years for hardware or device-centric companies in the same article. What it still shows is the gap in scale between the layers: a vision measured in years cannot be delivered by one quarter's roadmap, which is why something has to sit in between.

| Layer | Question it answers | What it looks like | How often it changes |
|---|---|---|---|
| Mission | Why do we exist? | One sentence about the change you want in the world | Almost never |
| Vision | What future are we creating? | A persuasive picture of the customer's world a few years out | Rarely, when the mission needs a new route |
| Objectives | What outcome proves progress now? | A target on the North Star metric or one of its inputs | Each planning cycle |
| Strategy (opportunities) | Which problems will move that outcome most? | Three or so chosen customer problems, with the ones you rejected | When evidence says an opportunity is smaller or bigger than thought |
| Roadmap (solutions) | When do we build or test what? | Sequenced solutions and experiments, each tied to an opportunity | Continuously, as experiments land |

## How do mission, vision, objectives, opportunities and solutions form one chain?

Mission, vision, objectives, opportunities and solutions form one chain when each layer answers the layer above it. The mission says why; the vision makes that why concrete as a future state; the objectives pick the measurable outcome that shows progress toward the vision now; the opportunities are the customer problems most likely to move that outcome; the solutions are the specific things you build or test to address each opportunity.

Cagan draws the same line between the middle layers: "the product vision describes where we ultimately want to go; the product strategy helps us decide what problems to solve in order to get to our vision; product discovery helps us figure out the tactics that can actually solve the problems." Read that way, the strategy is a set of problems, not a set of features, and the roadmap is where the features finally appear.

The chain also explains the most common confusion. Many teams skip straight from a goal to a list of features. Cagan describes exactly this in his [Product Strategy Overview](https://www.svpg.com/product-strategy-overview/): companies that "have a goal (like doubling revenue), and they have a product roadmap (the tactics), yet no product strategy to be found."

## Why define strategy as the opportunities most likely to grow the North Star metric?

A product strategy defined as opportunities is testable in a way a strategy defined as themes or ambitions is not. Start from the [North Star metric](https://builderscamp.com/guides/other/north-star-metric-examples), the one number that best captures the value your product delivers, then ask which customer problems, if solved, would move it most. The handful you choose is the strategy. The ones you consciously reject belong in the strategy document too, because saying no is the part stakeholders need to see.

Three sources feed the list of candidate opportunities: what customers tell you and do, what stakeholders and the market signal, and where you can open a gap on competitors. The [opportunity space](https://builderscamp.com/guides/glossary/opportunity-space) is where those candidates get collected and filtered, an [opportunity solution tree](https://builderscamp.com/guides/glossary/opportunity-solution-tree) links each chosen opportunity to its candidate solutions, and the [Four Actions Framework](https://builderscamp.com/guides/glossary/four-actions-framework) is a reliable way to find opportunities that differ from what competitors already offer.

## What does the chain look like for a real product?

Take a hypothetical inventory app for independent restaurants. Here is the whole chain, top to bottom:

- **Mission:** Help independent restaurants waste less food and money.
- **Vision:** In three years, a head chef finishes the weekly stock order on a phone in the walk-in, from suggestions that already account for the menu, the bookings and supplier prices.
- **Objective (this half-year):** Grow the North Star metric, weekly orders placed from the app's suggestions, from its current level to a set target.
- **Strategy (three chosen opportunities):** stock counts take too long, so chefs skip them; supplier price changes go unnoticed until the invoice arrives; menu changes are not reflected in order quantities. **Rejected for now:** detailed sales analytics, because owners asked for it but interviews showed it would not change what gets ordered.
- **Roadmap (solutions, sequenced):** a scan-to-count mode for the walk-in first, since counts feed every suggestion; supplier price alerts second; menu-linked par levels third, starting as a prototype with five restaurants.

Every roadmap item names the opportunity it serves, and every opportunity names the North Star it is meant to move. The rejected opportunity is on the page, which is what lets the product manager say no to the analytics request with a reason instead of a delay.

## How is a roadmap different from a strategy?

A roadmap is a sequence of solutions; a strategy is the choice of problems those solutions exist to solve. Shreyas Doshi's [post on whether roadmaps are useful](https://www.linkedin.com/posts/shreyasdoshi_are-product-roadmaps-useful-or-useless-activity-6976365908474683392-DzYG) puts the dependency plainly: "If you do not know where you are headed, a roadmap will take you everywhere, and therefore, nowhere." A roadmap without a strategy above it still looks busy, because every item has a requester and a reason, but nothing on it adds up.

The practical difference shows up in how each one changes. Roadmap items should change often, as discovery kills weak solutions and experiments return results. The strategy should change only when evidence shows an opportunity is bigger or smaller than you thought. If your strategy changes every time your roadmap does, you have one document with two names.

## How do you test whether your roadmap traces back to your strategy?

Take your current roadmap and, for each item, write the opportunity it serves and the objective that opportunity is meant to move. Three outcomes are possible for each item:

- **It traces cleanly.** Item, opportunity and objective line up. Keep it.
- **It traces to an opportunity you never chose.** Either add that opportunity to the strategy on purpose, with the evidence, or cut the item.
- **It traces to nothing.** It is a request, not strategy. Park it or say no, and point to the chain when you explain why.

The same exercise works across time frames. Sorting the surviving items by the [three horizons model](https://builderscamp.com/guides/glossary/three-horizons-of-growth) shows whether the roadmap is all core improvements or whether any capacity goes to extending or reinventing the product.

## When does the layered model break down?

The layered model breaks down when a team treats it as paperwork rather than a set of choices. A pre-product-market-fit startup can write every layer and still be guessing at most of them; there, the vision is a hypothesis and the strategy is the list of riskiest assumptions to test first. Cagan admits as much in Vision vs. Strategy, calling buying into a vision "a bit of a leap of faith." Large companies hit the opposite problem: layers written by different groups that never reference each other. In both cases the fix is the trace test above, run every planning cycle. Doshi's own caption on his mission-to-goals list is the fair summary of the effort involved: "Always simple, rarely easy."

## How is this page different from the product vision definition?

The [product vision](https://builderscamp.com/guides/glossary/product-vision) glossary entry defines one layer in depth: what a vision is, how long it should be, and who should write it. This page covers how that vision connects downward to objectives, opportunities and roadmap items, and how to check that the connection holds. Read the glossary entry when you are writing or rewriting the vision itself; use the chain here when the vision exists but the roadmap does not seem to follow from it.

## Where can you practice building the full chain?

Builders Camp's Product Strategy bootcamp, 2 weeks with 4 live sessions and 8 microlessons taught by Andre Albuquerque, covers strategic choices and trade-offs, using the roadmap as a strategy execution tool, and writing and presenting strategy so it earns commitment, and its practical challenge asks for a board-ready strategy memo with one North Star metric. It is part of the Product Leadership Track. [See the Product Strategy bootcamp](https://builderscamp.com/bootcamps/product-strategy?utm_source=guide&utm_medium=organic&utm_campaign=product-vision-vs-strategy-vs-roadmap) for the full curriculum and challenge.

## Frequently asked questions

### What is the difference between a product vision and a product strategy?

The vision describes the future the product is trying to create; the strategy is the small set of problems or opportunities the team chooses to work on to get there. Marty Cagan of SVPG puts it as the vision describing where we ultimately want to go and the strategy helping decide what problems to solve to reach it.

### What is the difference between a product strategy and a product roadmap?

The strategy names which opportunities matter most; the roadmap sequences the solutions the team will build or test to pursue them. If a roadmap item cannot name the opportunity it serves, it is not part of the strategy, whatever its priority label says.

### How far ahead should a product vision look?

Marty Cagan writes that a product vision typically describes the future somewhere between 2 and 5 years out, and 5 to 10 years for hardware or device-centric companies. A vision short enough to finish in a quarter is really an objective.

### Where does the mission fit relative to the vision?

The mission is the why: the reason the company or product exists, which rarely changes. The vision is the what: the concrete future state that would show the mission is being delivered. Shreyas Doshi's shorthand lists mission as why, vision as what, strategy as how and roadmap as when.

### Should the strategy change when the roadmap changes?

Not usually. Roadmap items change as experiments succeed or fail; the strategy should only change when evidence shows a chosen opportunity is smaller than expected or a new one is clearly bigger. Frequent strategy changes driven by roadmap churn mean the strategy was a feature list.

### Where do OKRs fit in the chain?

OKRs sit at the objectives layer, between vision and strategy. The objective states the outcome the team is chasing this period, usually movement in the North Star metric or one of its inputs, and the strategy is the set of opportunities chosen to hit it.

### Is this the same as the product vision glossary entry?

No. The product vision glossary entry defines one layer, the vision, in depth. This page is about how all five layers connect, and how to test that a roadmap actually traces back to them.

## Sources

- [Marty Cagan, SVPG: Vision vs. Strategy](https://www.svpg.com/vision-vs-strategy/)
- [Marty Cagan, SVPG: Product Strategy Overview](https://www.svpg.com/product-strategy-overview/)
- [Shreyas Doshi on LinkedIn: Mission: Why, Vision: What, Strategy: How](https://www.linkedin.com/posts/shreyasdoshi_mission-why-vision-what-strategy-how-activity-6866621883920601088-J9Ok)
- [Shreyas Doshi on LinkedIn: Are product roadmaps useful or useless?](https://www.linkedin.com/posts/shreyasdoshi_are-product-roadmaps-useful-or-useless-activity-6976365908474683392-DzYG)

## How this guide was made

Researched from Builders Camp's bootcamp, track and masterclass material and the sources listed on this page, drafted with AI, and fact-checked against every source cited.