home / skills / coowoolf / insighthunt-skills / product-strategy-stack
This skill helps align product initiatives with a top-down strategy, translating mission into roadmap and measurable goals for clear execution.
npx playbooks add skill coowoolf/insighthunt-skills --skill product-strategy-stackReview the files below or copy the command above to add this skill to your agents.
---
name: Product Strategy Stack
description: A hierarchical framework forcing alignment from top down—Mission, Company Strategy, Product Strategy, Roadmap, Goals. Strategy precedes goals; goals measure progress against a strategy.
---
# The Product Strategy Stack
> "If you're going to take a road trip, you first decide where you want to drive to... our destination is Vegas, and we'll know whether or not we reach there if we've driven 250 miles." — Ravi Mehta
## What It Is
A hierarchical framework that forces alignment from **top down**. It separates mission (aspirational) from strategy (logical plan) and ensures the roadmap and goals are **derivatives** of the strategy, not the drivers.
## When To Use
- Teams are confused about **prioritization**
- "Goals" are being used as a **substitute for strategy**
- Debating Feature A vs. Feature B with **no clear answer**
- Annual/quarterly **planning kickoffs**
## The Stack
```
┌─────────────────────────────────────────────────────────┐
│ MISSION │
│ The change you want to bring to the world │
│ (Aspirational, enduring) │
├─────────────────────────────────────────────────────────┤
│ COMPANY STRATEGY │
│ The logical plan to achieve the mission │
│ (Multi-year, company-wide) │
├─────────────────────────────────────────────────────────┤
│ PRODUCT STRATEGY │
│ Connective tissue between company and product │
│ (How product specifically contributes) │
├─────────────────────────────────────────────────────────┤
│ PRODUCT ROADMAP │
│ Sequence of features/outcomes to execute strategy │
│ (Quarterly/annual priorities) │
├─────────────────────────────────────────────────────────┤
│ PRODUCT GOALS │
│ Metrics that measure progress against roadmap │
│ (Lagging indicators of strategy execution) │
└─────────────────────────────────────────────────────────┘
```
## Core Principles
### 1. Strategy Precedes Goals
Goals measure progress against a strategy. Without strategy, goals are arbitrary numbers.
### 2. Alignment Flows Down
Each layer must clearly derive from the one above.
### 3. Include Wireframes
Prevent misalignment by including visuals in strategy docs. Ambiguous text causes drift.
### 4. Mission is Aspirational
Mission doesn't change often. Strategy is how you achieve it in current conditions.
## How To Apply
```
STEP 1: Articulate Mission
└── What change do we want in the world?
└── Why does this company exist?
STEP 2: Define Company Strategy
└── What is our logical plan?
└── What are we betting on?
STEP 3: Translate to Product Strategy
└── How does product specifically contribute?
└── What capabilities must we build?
STEP 4: Build Roadmap from Strategy
└── What features execute this strategy?
└── What's the sequence?
STEP 5: Set Goals to Measure
└── What metrics indicate strategy is working?
└── Goals are outputs, not inputs
```
## Common Mistakes
❌ Starting with goals ("increase retention by 5%") and building **backward**
❌ Conflating roadmap with strategy
❌ Using goals as **substitute for strategy**
## Real-World Example
Tinder vs. Hinge: Both are dating apps. Tinder's mission is "Make single life fun" (Product Strategy: fast swiping, serendipity). Hinge's mission is "Designed to be deleted" (Product Strategy: anti-swipe, rich profiles). Their features differ because their Strategy Stacks differ.
---
*Source: Ravi Mehta, Former CPO of Tinder, Lenny's Podcast*
This skill codifies a hierarchical Product Strategy Stack that forces alignment from mission down through goals. It clarifies the difference between aspirational mission, multi-year company strategy, product strategy, roadmap sequencing, and measurable goals. The aim is to ensure strategy drives goals and roadmaps, not the other way around.
The skill inspects each layer of your planning artifacts to verify top-down derivation: mission → company strategy → product strategy → roadmap → goals. It checks for mismatches where goals precede strategy, roadmaps masquerade as strategy, or features lack strategic rationale. It also recommends including visuals or wireframes in strategy docs to reduce ambiguity and drift.
What if my company has no clear mission?
Start by drafting a concise aspirational statement that explains the change you want to make; use it to guide the company strategy and product decisions.
Can goals ever inform strategy?
Goals should measure progress, not create strategy. Use evidence from goals to iterate strategy, but avoid treating target numbers as the strategic plan.