product-lead

name	product-lead
description	Product management skills: strategy, prioritization, stakeholder management, problem framing, outcome definition. Use when: defining product scope, setting priorities, coordinating teams.

Product Lead Skills

Core Competencies

1. Problem Framing & Outcome Definition

Best Practices:

• Start with the problem, not the solution
• Define clear, measurable outcomes (not outputs)
• Use the "Jobs to be Done" framework to understand user needs
• Frame problems from the user's perspective, not the business's

Frameworks:

• Problem Statement Template:

  • Who: [target user]
  • Problem: [specific problem they face]
  • Impact: [why this matters]
  • Success: [how we'll know we solved it]

• Outcome Definition:

  • North Star Metric: single metric that captures product value
  • Supporting metrics: leading indicators that drive North Star
  • Guardrail metrics: ensure we don't break things

Anti-patterns to avoid:

• Defining solutions before understanding problems
• Focusing on features instead of outcomes
• Vanity metrics (metrics that look good but don't drive value)

2. Prioritization

Frameworks:

• RICE Scoring:

  • Reach: how many users affected
  • Impact: how much impact (0.25 to 3.0)
  • Confidence: how confident are we (0% to 100%)
  • Effort: person-months
  • Score = (Reach × Impact × Confidence) / Effort

• ICE Scoring:

  • Impact: how much impact
  • Confidence: how confident
  • Ease: how easy to implement
  • Score = (Impact + Confidence + Ease) / 3

• Value vs Effort Matrix:

  • Quick wins: high value, low effort
  • Major projects: high value, high effort
  • Fill-ins: low value, low effort
  • Time sinks: low value, high effort (avoid)

Best Practices:

• Always include rationale for prioritization
• Consider dependencies and risks
• Revisit priorities regularly (weekly/monthly)
• Balance short-term wins with long-term strategy

3. Stakeholder Management

Best Practices:

• Identify all stakeholders early
• Understand their goals and concerns
• Communicate clearly and regularly
• Build trust through transparency
• Manage expectations (under-promise, over-deliver)

Stakeholder Map:

• High power, high interest: Manage closely (key stakeholders)
• High power, low interest: Keep satisfied (executives)
• Low power, high interest: Keep informed (users, support)
• Low power, low interest: Monitor (minimal effort)

Communication:

• Use the right format for the audience
• Provide context, not just updates
• Make decisions visible and explain rationale
• Create feedback loops

4. Product Strategy & Vision

Best Practices:

• Align product strategy with business goals
• Create a clear product vision (where we're going)
• Define product principles (how we make decisions)
• Balance user needs with business needs

Vision Statement Template:

• For [target users]
• Who [have this problem]
• [Product name] is a [category]
• That [key benefit]
• Unlike [competitors]
• Our product [unique differentiator]

5. Decision Making

Best Practices:

• Make decisions with available information (don't wait for perfect data)
• Document decisions and rationale (ADRs)
• Revisit decisions when context changes
• Accept that some decisions will be wrong (learn and adjust)

Decision Framework:

1. Define the decision clearly
2. Gather relevant information
3. Identify options
4. Evaluate options (pros/cons, risks)
5. Make decision
6. Document decision (ADR)
7. Communicate decision
8. Monitor and adjust

Output Quality Checklist

When producing artifacts, ensure:

• ✅ Problem clearly defined (not solution)
• ✅ Outcome metrics specified (North Star + supporting)
• ✅ Prioritization rationale provided
• ✅ Stakeholders identified and mapped
• ✅ Dependencies and risks noted
• ✅ Assumptions explicitly stated
• ✅ Scope boundaries clear (IN/OUT)

Common Pitfalls

• Solution-first thinking: Starting with features instead of problems
• Feature factory: Shipping features without measuring outcomes
• Analysis paralysis: Waiting for perfect data before deciding
• Stakeholder misalignment: Not getting buy-in early
• Scope creep: Not saying "no" to good ideas that don't fit