Product Strategy

Product Strategy

Strategic product planning covering vision articulation, roadmap development, prioritization frameworks, and go-to-market execution. Evaluates features through customer value, business impact, and strategic alignment lenses.

When to Use This Skill

• Evaluating and prioritizing a feature backlog
• Defining product vision or strategic direction
• Planning roadmaps for releases or product launches
• Assessing product-market fit for new concepts
• Setting OKRs and success metrics for product goals
• Analyzing competitive positioning and market opportunities
• Balancing technical debt against feature delivery

Quick Reference

Workflow

1. Understand the goal: What outcome are we seeking? 2. Assess alignment: Does this fit the product vision? 3. Select a framework: Choose the right prioritization method for the context. 4. Evaluate trade-offs: What are we not building instead? What is the opportunity cost? 5. Define success: How will we measure impact? Identify the north star metric. 6. Plan execution: What is the MVP and iteration path?

Domain Vocabulary

product vision, roadmap, prioritization, OKRs, value proposition, product-market fit, MVP, feature backlog, user stories, RICE scoring, jobs-to-be-done, north star metric, opportunity cost, technical debt

Guiding Questions

Ask these at every decision point:

1. "What customer problem does this solve?" 2. "What's the opportunity cost of building this?" 3. "How does this align with our product vision?"

Capabilities

Vision and Strategy

• Product vision articulation and communication
• Strategic roadmap development
• Competitive landscape analysis
• Market opportunity identification
• Product positioning and differentiation

Prioritization and Planning

• RICE, MoSCoW, and Kano model prioritization
• Jobs-to-be-done framework application
• OKR definition and tracking
• Sprint planning and capacity management
• Technical debt prioritization

Stakeholder Management

• Cross-functional alignment facilitation
• Executive communication and buy-in
• Customer feedback synthesis
• Engineering partnership optimization
• Go-to-market coordination

Metrics and Analytics

• North star metric identification
• Product analytics interpretation
• Funnel analysis and optimization
• Cohort analysis for retention
• A/B test result interpretation

Response Approach

1. Understand the goal: What outcome are we seeking? 2. Assess alignment: Does this fit our product vision? 3. Evaluate trade-offs: What are we not building instead? 4. Define success: How will we measure impact? 5. Plan execution: What is the MVP and iteration path?

Example Interactions

• "Prioritize this feature backlog for Q1"
• "Define OKRs for user engagement improvement"
• "Evaluate market fit for this new product concept"
• "Create a roadmap for mobile app launch"
• "Analyze competitive positioning against market leaders"

Prioritization Frameworks

Practical reference for selecting and applying product prioritization methods. Each framework includes when to use it, how to score, and a worked example.

RICE Scoring

When to use: Comparing features objectively across a shared backlog.

Formula

RICE Score = (Reach x Impact x Confidence) / Effort

Definitions

Worked Example

Tips

• Re-estimate Reach quarterly; do not reuse stale numbers.
• Use Confidence to penalize guesswork, not to inflate pet projects.
• Effort should reflect total team effort, not just engineering.

---

MoSCoW Method

When to use: Time-boxed releases where you need to draw a firm scope line.

Categories

Process

1. List all candidate items. 2. Stakeholders assign each item a category (force a decision; "maybe" is not a category). 3. Validate that Must Haves fit within capacity. If not, something is mis-categorized. 4. Fill remaining capacity with Should Haves, then Could Haves. 5. Move overflow to Won't Have with a clear reason.

Anti-patterns

• Everything is a Must Have: capacity math will expose this.
• No Won't Haves: you are not making real trade-offs.
• Skipping stakeholder alignment: categories should be consensus, not dictated.

---

Jobs-to-be-Done (JTBD)

When to use: Understanding why customers switch products or adopt features, beyond surface-level requests.

Core Concept

Customers "hire" products to do a job. The job statement follows a structured format:

When [situation], I want to [motivation], so I can [expected outcome].

Job Mapping Steps

1. Define the job: What is the functional, emotional, and social job? 2. Map the process: Break the job into steps (locate, prepare, confirm, execute, monitor, modify, conclude). 3. Find underserved needs: Where is the current solution slow, error-prone, or missing? 4. Prioritize opportunities: Score each unmet need by importance and satisfaction gap.

Opportunity Score

Opportunity = Importance + max(Importance - Satisfaction, 0)

High-opportunity scores indicate underserved needs worth building for.

Tips

• Interview customers about their last real purchase decision, not hypothetical preferences.
• Jobs are stable over time; solutions change. Focus on the job, not the feature.
• Combine JTBD with RICE to filter what to build first.

---

OKR Alignment

When to use: Connecting feature work to measurable business outcomes.

Structure

Objective: [Qualitative, inspiring goal]
  KR1: [Metric] from [baseline] to [target] by [date]
  KR2: [Metric] from [baseline] to [target] by [date]
  KR3: [Metric] from [baseline] to [target] by [date]

Good OKR Checklist

• [ ] Objective is ambitious but achievable (aim for ~70% hit rate).
• [ ] Key Results are measurable, not tasks.
• [ ] Each KR has a baseline and a target.
• [ ] KRs are leading indicators, not lagging (prefer activation rate over annual revenue).
• [ ] No more than 3-5 KRs per Objective.

Linking Features to OKRs

Features that do not connect to any OKR should be questioned or deprioritized.

---

Impact/Effort Matrix

When to use: Quick visual triage during planning sessions or brainstorms.

Quadrants

          High Impact
              |
  Quick Wins  |  Big Bets
  (Do First)  |  (Plan Carefully)
--------------+--------------
  Fill-Ins    |  Money Pits
  (Do If Idle)|  (Avoid)
              |
          Low Impact
   Low Effort      High Effort

Process

1. List candidate items on sticky notes or a shared board. 2. Each item gets a rough Impact score (1-5) and Effort score (1-5). 3. Place on the matrix. Discuss disagreements. 4. Sequence: Quick Wins first, then Big Bets with proper planning, Fill-Ins as capacity allows, Money Pits last or never.

Common Mistakes

• Underestimating effort by ignoring testing, docs, and rollout.
• Conflating "loud stakeholder" with "high impact."
• Using the matrix once and never revisiting as context changes.

---

Feature Scoring Template

A combined template for when you want to evaluate features across multiple dimensions.

Scoring Rubric

Calculation

Weighted Score = Sum(Dimension Score x Weight)

Template Row

---

Roadmap Planning Patterns

Time Horizons

Theme-Based Roadmap

Group features under themes rather than dates:

Theme: "Frictionless Onboarding"
  - Onboarding wizard (Now)
  - Progressive profiling (Next)
  - Personalized templates (Later)

Theme: "Power User Retention"
  - Keyboard shortcuts (Now)
  - Custom dashboards (Next)
  - API access (Later)

Roadmap Review Cadence

Anti-patterns

• Date-driven roadmaps with no flexibility: prefer outcome-driven.
• Roadmap as a promise: it is a plan, not a contract.
• No explicit "not doing" list: makes it impossible to say no.