The Product Strategy Stack
Separate mission, strategy, product strategy, roadmap, and goals into five layers you can define top-down and debug bottom-up.
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 95%
A five-layer system that untangles the terms teams routinely conflate: company mission, company strategy, product strategy, product roadmap, and product goals. You define strategy by working from the top down, and you debug a failing product by working from the bottom up. Most prioritization confusion traces back to a strategy layer that was never clearly articulated.
Origin
Created by Ravi Mehta (CPO at Tinder, product director at Facebook, VP product at TripAdvisor) and taught in the Reforge product strategy program. He developed it after repeatedly seeing PMs unable to choose between two similarly-sized features, and tracing that paralysis back to gaps in the underlying strategy.
Core principles
- 01Mission is aspirational and qualitative; strategy is rigorously logical.
- 02Product strategy is the connective tissue between what the company is trying to accomplish and the team's day-to-day work.
- 03Define top-to-bottom, debug bottom-to-top.
- 04A prioritization problem is usually a strategy problem in disguise.
- 05Vision can be folded into mission — don't get stuck perfecting the distinction.
How to run it
- 1
Write the company mission
State the change the company wants to bring to the world — a qualitative, inspirational statement of purpose. This can be scoped to a team or subsidiary if that fits your environment.
Pro tip Fold vision into mission rather than agonizing over the difference: mission is what you're trying to do, vision is what the world looks like once you've done it — one statement can hold both.
- 2
Define the company strategy
Lay out the rigorously logical, specific plan the company will use to bring the mission into being. Where mission is aspirational, strategy must be concrete and defensible.
Watch out Strategy that stays vague pushes ambiguity downstream — every layer below inherits the fuzziness.
- 3
Set the product strategy
Articulate how the product specifically advances the company strategy — the bridge between company ambition and product execution.
- 4
Build the roadmap, then the goals
The product strategy informs the roadmap, and the roadmap ultimately informs the goals — in that order. Goals measure progress toward a destination the strategy has already chosen.
- 5
Debug bottom-up when things break
If you're missing goals, check whether the roadmap supports them; if the roadmap is wrong, check whether the product strategy is clear; if that's unclear, check the team's grasp of company strategy and mission.
Pro tip Use the failing layer as a diagnostic: symptoms in day-to-day tactics almost always trace back to a higher, under-defined layer.
In the wild
Two dating apps with near-identical use cases diverge at every layer. Missions differ: Hinge is 'designed to be deleted' (temporary use case) while Tinder aims 'to make single life more fun' (continuous use case). Strategies differ on acquisition: Hinge leans on television ads, Tinder on influencer and event-based marketing. Product strategies differ: Tinder is built around fast swiping; Hinge is a post-swipe app built around profile prompts and deeper conversation. Roadmaps overlap (both invested in video chat post-pandemic) and top-line goals converge (both measure meaningful conversations).
→ The stack shows exactly where two comparables should look alike and where they must diverge, turning 'copy the competitor or not' into a layer-by-layer decision.
Common mistakes
Treating a prioritization problem as a prioritization problem
When a PM can't decide between two similarly-sized features, the real gap is usually an undefined strategy layer — no framework exists to inform the choice. Fixing the tactic without fixing the strategy just reproduces the paralysis.
Over-engineering the mission/vision distinction
Teams get stuck trying to perfect and separate mission and vision. Mehta advises not overthinking it — put something people are excited about and move on to strategy, because the strategy work is where value is created.
Is it for you?
Best for
Product managers and founders who feel their team is busy but directionless, and can't explain why one feature beats another.
Not ideal for
Solo makers in pure execution mode on a validated product where the strategy is already obvious and unchanging.
From the transcript
“the goal of the product strategy stack is to help people take a set of terms that are normally conflated together like goals roadmap strategy…”
“so the top of the stack is the company Mission and the company Mission is the change the company wants to bring to the world”
“whereas a mission is aspirational strategy is rigorously logical”
“if a PM is looking to Define strategy they can work top to bottom and if they're looking to debug strategy they can actually work…”
From the episode
Building your product strategy stack
Ravi Mehta (Tinder, Facebook, Tripadvisor, Outpace)