product-strategy
Build product strategy that drives real choices. Use when defining where to play and how to win, creating strategy canvases, defining ICP/Anti-ICP, positioning products, setting pricing strategy, planning GTM motions, or structuring strategic bets. Part of the Modern Product Operating Model collection.
YannickMaurice · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add yannickYamo/skills --skill product-strategyAbout this skill
name: product-strategy description: Build product strategy that drives real choices. Use when defining where to play and how to win, creating strategy canvases, defining ICP/Anti-ICP, positioning products, setting pricing strategy, planning GTM motions, or structuring strategic bets. Part of the Modern Product Operating Model collection. author: YannickMaurice version: 1.0.0 tags: product-management, strategy, gtm, pricing, positioning
Product Strategy System
"Strategy is choice, not documentation. If you haven't said no to something, you don't have a strategy."
This skill covers the Strategy System — defining where to play and how to win. It creates the guardrails that make downstream decisions coherent and forces the hard choices most teams avoid.
Part of: Modern Product Operating Model — a collection of composable product skills.
Related skills: product-discovery, product-architecture, product-delivery, ai-native-product, product-leadership
When to Use This Skill
Use this skill when:
- Defining or refreshing product strategy
- Creating a 1-page strategy canvas
- Defining ICP and Anti-ICP
- Structuring Jobs to Be Done analysis
- Developing positioning and messaging
- Setting pricing strategy and value metrics
- Planning GTM motion (PLG vs SLG vs Partner)
- Creating strategic bets with hypotheses and kill criteria
Cadence: Quarterly refresh | Owner: Founder/CPO
Philosophy
Core Beliefs
- Strategy is choice, not documentation — If you haven't said no to something, you don't have a strategy
- Pricing belongs in strategy, not GTM — Pricing decisions constrain segments, problems, features, and competition
- Competitive reality shapes everything — Build easy-to-copy features and wonder why you're not winning
- Non-goals are as important as goals — What you won't do defines focus
- Moats are built, not found — Strategy should articulate how you become hard to copy
What This Framework Rejects
- Strategy decks nobody reads
- "We serve everyone" positioning
- Pricing as afterthought
- Ignoring competitive dynamics
- Annual planning fiction
- Strategy without non-goals
Framework Components
1. Strategic Intent
What it contains:
- Mission: Why you exist (enduring)
- Objective: What winning looks like in 12-24 months (specific, measurable)
- Non-Goals: What you will NOT do, who you will NOT serve, which problems you will NOT solve
Anti-pattern: If your non-goals list is empty, you don't have a strategy.
0→1 Mode: Mission can be rough. Objective is survival: find PMF. Revisit weekly.
Scaling Mode: Mission is refined and externally communicable. Objectives are financial + strategic.
2. Market & Competitive Reality
What it contains:
| Analysis | Purpose |
|---|---|
| Market Diagnosis | What's broken? Why hasn't it been fixed? What's changing? |
| 5C Analysis | Company, Customers, Competitors, Collaborators, Context |
| Porter's 5 Forces | Buyer power, supplier power, substitutes, new entrants, rivalry |
| Value Chain | Where margin is created and captured |
Key questions:
- Why do alternatives fail? What's the gap?
- Is this a market where a startup can win?
- Where do value pools exist?
- What creates switching costs?
"If you don't understand competitive dynamics, you'll build features that are easy to copy and wonder why you're not winning."
3. ICP & Anti-ICP
Ideal Customer Profile contains:
- Company characteristics (size, industry, tech stack)
- User roles (buyer, user, influencer, blocker)
- Problem intensity (how painful?)
- Willingness to pay (can they and will they?)
- Urgency (why now?)
Anti-ICP (equally important):
- Who you explicitly won't serve
- Why (wrong economics, wrong fit, wrong timing)
Segmentation dimensions:
- Pain severity
- Frequency of problem
- Willingness to pay
- Buying process complexity
0→1 Mode: Start with ONE ICP, not segments. Talk to 10-20 people who match.
Scaling Mode: Multiple ICPs with clear prioritization. Segment-specific positioning and pricing.
4. Jobs to Be Done & Pain
Three job types:
| Job Type | Question | Example |
|---|---|---|
| Functional | What task are they trying to accomplish? | "Find qualified candidates faster" |
| Emotional | How do they want to feel? | "Confident in hiring decisions" |
| Social | How do they want to be perceived? | "Make defensible decisions colleagues respect" |
Pain analysis dimensions:
- Severity: How bad is it?
- Frequency: How often does it occur?
- Workarounds: What do they do today?
- Willingness to change: How much friction will they accept?
How to gather:
- Weekly customer interviews (2-3/week minimum during discovery)
- Support ticket analysis
- Win/loss interviews
- Usage data (what they do vs. what they say)
5. Superpower: Where to Play & How to Win
Where to Play:
- Target segment (specific)
- Core use case / wedge (narrow)
- Geographic focus (if relevant)
- Channel focus (direct, PLG, partner)
- ACV band (what deal sizes?)
How to Win:
- Unique mechanism (what you do differently)
- Moat thesis (why it's hard to copy)
- Proof points (why anyone should believe you)
Moat Categories:
| Moat Type | Description |
|---|---|
| Data moats | Proprietary data that improves with usage |
| Network effects | Value increases with more users |
| Switching costs | Pain of leaving exceeds pain of staying |
| Workflow integration | Embedded in daily habits |
| Brand/trust | Earned credibility that takes years |
| Economies of scale | Cost advantages at volume |
The Strategic Kernel (Rumelt):
- Diagnosis: What's the crux challenge?
- Guiding policy: What's your approach?
- Coherent actions: What specifi