A vision tells the team where you're headed. A strategy is the much harder work of choosing, out of everything you could do to get there, the narrow set of bets you're actually going to make.
1Vision Is Not a Strategy
'Become the default way people manage their finances' is a vision — inspiring, but it tells nobody what to build this quarter. A strategy translates that ambition into a specific position: which segment you're targeting first, what capability you're building an edge in, and just as importantly, what you are deliberately choosing not to pursue yet.
2The Cost of Skipping Straight to Roadmapping
Teams that jump from a vague vision directly into roadmap planning end up prioritizing by whoever argues loudest in the meeting, because there's no strategic filter to weigh requests against. A clear 'where to play, how to win' statement gives every prioritization conversation a shared reference point instead of a debate from first principles every time.
3Step-by-Step Breakdown
Introduction. A product strategy is the approach you commit to for winning with a specific set of users, given real constraints on time, budget, and headcount. It is not the vision (the destination) and it is not the roadmap (the schedule) — it's the reasoning that connects the two.
The Product Strategy Stack. Melissa Perri's Product Strategy Stack lays it out top to bottom: Company Vision, Company Strategy, Product Vision, Product Strategy, then Product Initiatives that finally become roadmap items. Skip a layer and your backlog fills with disconnected feature requests instead of aligned bets.
Where to Play, How to Win. Roger Martin's 'Playing to Win' framework forces two hard choices: where to play (which market, segment, or use case you'll focus on) and how to win (what makes you the better choice there). A strategy that tries to play everywhere and win on everything is really no strategy at all.
Knowledge Check. What is the key difference between a product strategy and a product roadmap?
- →Strategy defines the deliberate bets and tradeoffs; the roadmap sequences the work that results from them
- →A roadmap is just a longer, more detailed version of the strategy document
Summary. Strategy is what gives you a defensible reason to say no. Without it, prioritization becomes a popularity contest between whichever stakeholder spoke last, and the roadmap turns into an unstructured wishlist.
