Product Strategy Stack
A layered model connecting purpose, strategic choices, product goals, bets, and delivery evidence so decisions remain coherent across horizons.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/product-strategy-stack/
01What it means
A product strategy stack is a hierarchy of linked decisions, typically moving from durable purpose and vision through market or product strategy, goals, bets, and execution. The exact labels vary; the essential idea is traceability. Each lower layer should explain how it advances the layer above, while evidence from execution can challenge assumptions higher in the stack.[1][2][3]
- Purpose + visionDurable direction
- StrategyCustomers, problems, advantage
- GoalsTime-bounded outcomes
- BetsHow outcomes might happen
- Initiatives + experimentsWork and evidence
Labels vary; traceability and evidence in both directions are essential.
02Why it matters
Organizations frequently mix aspirations, strategies, metrics, initiatives, and tasks in one plan. A stack separates their roles and exposes missing logic: a goal with no strategic choice, a roadmap item with no outcome, or a vision that cannot constrain investment. It also supports autonomy because teams can adapt lower-level actions without reopening every durable decision.
03When to use it
Use the framework when aligning several product teams, translating enterprise strategy into product direction, diagnosing a crowded roadmap, or clarifying which decisions require executive versus team ownership. Keep the stack lightweight for a single small team with limited strategic scope.
04How it works
- Define the durable purpose or vision and the boundaries it implies.
- State strategic choices about customers, problems, advantage, and what not to pursue.
- Translate choices into a few time-bounded product goals with guardrails.
- Form product bets that explain how those outcomes might be produced.
- Connect initiatives and experiments to each bet, including evidence thresholds.
- Review upward and downward: check alignment, then let new evidence revise the appropriate layer.
05A practical example
A mobility company’s vision is accessible urban movement. Its strategy prioritizes riders with unreliable transit access and an advantage in multimodal routing. A yearly goal improves successful late-night journeys; bets cover safety-aware transfers and demand partnerships. Experiments test pickup guidance. A failed interface test changes the initiative, not automatically the vision.
06Where it breaks
A neat hierarchy can misrepresent strategy as linear and stable. Real decisions interact across layers, and labels may become bureaucratic approval gates. Teams should use the stack as a reasoning aid, record uncertainty, and avoid forcing every operational task into a grand strategic lineage.
Common mistakes
- Using different names for layers without clarifying their decision function.
- Treating the stack as one-way decomposition with no learning upward.
- Adding initiatives directly beneath vision while skipping strategic choices.
- Rewriting durable layers to justify short-term delivery changes.
07Sources
- Vision vs. StrategySilicon Valley Product Group · Product strategy articleVision vs. Strategy
- Coaching – Strategic ContextSilicon Valley Product Group · Product leadership articleCoaching – Strategic Context
- Business Strategy vs. Product StrategySilicon Valley Product Group · Product strategy articleBusiness Strategy vs. Product Strategy