product-strategist

---
name: product-strategist
description: Use when creating quarterly OKRs, defining strategic goals, building product roadmaps, running competitive analysis, or cascading company objectives to team level.
category: Product
version: 1.0.0
tools: []
---

# Product Strategy & OKR Cascade

Define and cascade strategic OKRs from company through product to team level with automated alignment scoring.

## Strategic Focus Options

- **Growth**: scaling user base, market expansion
- **Retention**: reducing churn, improving LTV, engagement
- **Revenue**: increasing ARPU, new monetization, expansion
- **Innovation**: market differentiation, new capabilities, moonshots
- **Operational**: improving efficiency, scaling infrastructure, process automation

## Quarterly Planning Workflow

1. **Define Strategic Focus** — Select one of five strategy types based on primary business objective

2. **Gather Input Metrics**
   - Growth: current MAU, target MAU, current growth %, target growth %
   - Retention: current churn %, target churn %, current LTV, target LTV
   - Revenue: current ARPU, target ARPU, expansion rate targets
   - Innovation: market positioning goals, capability gaps to close
   - Operational: efficiency metrics (cost per transaction), throughput targets

3. **Configure Team Structure**
   - Default teams: Growth, Platform, Mobile, Data
   - Custom team names supported
   - Specify product contribution % to company OKRs (typical: 20-40%)
   - Platform teams: support all objectives
   - Specialized teams (ML, Data): support relevant objectives only

4. **Run OKR Generator**
   - Generates aligned objectives company → product → team
   - Each level: 3-5 objectives with 3-5 key results
   - Key results include current state and target value
   - Outputs: dashboard or JSON export

5. **Review Alignment Scores**
   - Vertical Alignment: >90% (objectives link to parent)
   - Horizontal Alignment: >75% (team coordination, no conflicts)
   - Coverage: >80% (all company OKRs have product/team support)
   - Balance: >80% (no team overloaded relative to capacity)
   - Overall: target >80%; investigate <60% for restructuring

6. **Refine and Validate**
   - Review with stakeholders
   - Adjust team assignments by capacity
   - Validate contribution percentages realistic
   - Ensure no conflicting cross-team objectives
   - Set tracking cadence (bi-weekly check-ins)

7. **Export and Track**
   - JSON export for Lattice, Ally, Workboard
   - Dashboard for internal team use
   - Weekly/bi-weekly progress reviews

## OKR Framework Standards

- **Cascade Structure**: Company OKRs → Product OKRs (supported subset) → Team OKRs
- **Measurability**: every key result has baseline (current) and target value
- **Dependency Mapping**: identify cross-team dependencies; resolve conflicts
- **Sizing**: 3-5 objectives per level (not 10+); 3-5 key results per objective
- **Versioning**: changelog tracking additions, modifications, removals

## Configuration Options

| Parameter | Description | Default |
|-----------|-------------|----------|
| Strategy | Growth / Retention / Revenue / Innovation / Operational | growth |
| Teams | Comma-separated team names | Growth, Platform, Mobile, Data |
| Contribution | Product contribution % to company goals | 0.3 (30%) |

## Best Practices

- Start with clear company strategic focus (one per quarter)
- Ensure vertical alignment: every product OKR supports ≥1 company OKR
- Balance contributions across teams (no team >40% of overall scope)
- Use contribution percentages to weight team priorities
- Recalibrate quarterly as business conditions change
- Integrate with tracking tools for live progress updates

## Anti-Patterns to Avoid

- Top-down dictation without team input → low commitment
- Every function gets separate OKRs → silos emerge, misalignment
- Too many OKRs per team → diffusion, low achievement rates
- Contribution percentages don't match capacity → missed targets
- Quarterly cascade without mid-quarter review → drift from strategy