Product Strategist Expert

A Claude Code skill for Head of Product and senior product leaders to drive product vision, organizational alignment, and strategic excellence. Covers OKR cascade generation, market analysis, product vision articulation, and cross-functional strategy frameworks.

When to Use This Skill

Choose Product Strategist Expert when:

• You're defining or refining product vision and strategy
• You need to cascade OKRs from company goals to team objectives
• You're conducting market and competitive analysis
• You need to align multiple teams around a shared product direction
• You're preparing strategy presentations for leadership or board meetings

Consider alternatives when:

• You need tactical feature prioritization (use a product manager toolkit)
• You want marketing positioning and GTM strategy (use a PMM skill)
• You need specific UX design guidance (use a UX design skill)

Quick Start

Copy
# Install the skill
claude install product-strategist-expert

# Define product vision
claude "Help me articulate a product vision for our developer platform that serves both indie developers and enterprise teams"

# Cascade OKRs
claude "Our company objective is to reach $10M ARR by Q4. Create product OKRs that cascade to the platform, growth, and enterprise teams"

# Competitive strategy
claude "Analyze the competitive landscape for API monitoring tools. Key players: Datadog, New Relic, Grafana, our product"

Core Concepts

Strategy Framework Layers

Layer	Focus	Horizon	Owner
Vision	Where we're going and why	3-5 years	CEO / CPO
Strategy	How we'll get there	1-2 years	VP Product
Roadmap	What we'll build and when	Quarterly	Product Directors
Execution	How we'll build it	Sprint	Product Managers

OKR Cascade Model

Company Objective: "Become the leading developer platform in APAC"
  ├── Product KR: "Achieve 15K monthly active developers in APAC"
  │   ├── Platform Team OKR: "Launch localized docs in 3 APAC languages"
  │   ├── Growth Team OKR: "Increase APAC signup-to-active conversion to 40%"
  │   └── Enterprise Team OKR: "Close 5 enterprise deals in APAC market"
  └── Product KR: "Reach 60 NPS among APAC developers"
      ├── Platform Team OKR: "Reduce API latency from APAC regions to <100ms"
      └── Growth Team OKR: "Launch APAC developer community with 500 members"

Strategic Analysis Tools

Tool	Purpose	Output
Porter's Five Forces	Industry attractiveness analysis	Competitive intensity map
SWOT	Internal/external position assessment	2x2 strengths/weaknesses matrix
Jobs-To-Be-Done	Customer motivation analysis	Job statements and outcome metrics
Blue Ocean	Finding uncontested market space	Strategy canvas showing differentiation
Wardley Mapping	Understanding value chain evolution	Component evolution map

Configuration

Parameter	Type	Default	Description
planning_horizon	string	"annual"	Strategy horizon: quarterly, annual, multi_year
org_size	string	"mid"	Organization: startup, mid (50-200), large (200+)
framework	string	"okr"	Goal framework: okr, kpi, north_star, all
audience	string	"leadership"	Output audience: team, leadership, board
include_templates	boolean	true	Include document templates in output

Best Practices

1. Vision before strategy, strategy before roadmap — Don't skip to the roadmap. A roadmap without strategy is a random collection of features. A strategy without vision has no destination. Work top-down through each layer.

2. OKRs should be uncomfortable — If you're confident you'll hit 100% of your key results, they're not ambitious enough. Aim for 70% achievement on stretch OKRs. This applies to product OKRs especially — safe goals lead to incremental thinking.

3. Review competitive landscape quarterly — Markets shift fast. Schedule quarterly competitive reviews that cover new entrants, feature launches, pricing changes, and positioning shifts. Feed findings back into your strategy.

4. Align metrics across teams — If the growth team measures signups and the platform team measures retention, they'll optimize in conflicting directions. Establish shared metrics that force collaboration.

5. Strategy is about saying no — The most important strategic decisions are what you won't do. Document deliberate trade-offs and communicate them clearly so teams don't constantly relitigate settled decisions.

Common Issues

Vision is too vague to be useful — A good product vision should be specific enough to guide decisions. "Be the best platform" is useless. "Enable every developer to deploy production APIs in under 5 minutes" is actionable and testable.

OKRs become a to-do list — Key Results should be outcomes, not outputs. "Launch feature X" is a task. "Increase activation rate to 40%" is a key result. If your KRs read like a project plan, rewrite them as measurable outcomes.

Strategy doesn't survive contact with reality — Build quarterly strategy reviews into your calendar. Assess what's changed in the market, what you've learned, and whether your bets are paying off. Adjust without abandoning the vision.