Product Management Skill

Description

Expertise in product management lifecycle, from ideation to launch. Covers requirements gathering, user story creation, prioritization, and product strategy.

Capabilities

1. Requirements Engineering

• User Interviews & Surveys: Techniques for gathering qualitative and quantitative data.
• Problem Definition: Using "How Might We" statements to frame problems.
• PRD Writing: Structuring comprehensive Product Requirement Documents.
• Functional vs. Non-Functional: Distinguishing between what the system does and how it behaves (performance, security).

2. Feature Prioritization

• RICE Score: Reach, Impact, Confidence, Effort.
• MoSCoW Method: Must have, Should have, Could have, Won't have.
• Kano Model: Delighters, Performance, Basic expectations.
• WSJF: Weighted Shortest Job First (for Agile).

3. User Story Mapping & Definition

• User Story Format: "As a , I want , so that ."
• Acceptance Criteria: Conditions that a software product must satisfy to be accepted by a user.
• INVEST Principle: Independent, Negotiable, Valuable, Estimable, Small, Testable.

4. Product Strategy & Roadmap

• Lean Canvas: 1-page business plan.
• Value Proposition Design: Matching product features to user pains and gains.
• Roadmap Planning: Now, Next, Later frameworks.

Templates

User Story Template

**Title**: [Short description]
**User Story**:
As a [user persona],
I want [action/feature],
So that [benefit/value].

**Acceptance Criteria**:
1. [Criterion 1]
2. [Criterion 2]
3. [Criterion 3]

**Priority**: [High/Medium/Low]
**Notes**: [Additional context]

PRD Structure

1. Introduction: Background, Goals, Scope.
2. User Personas: Details about target users.
3. User Stories: List of features aimed at users.
4. Functional Requirements: Specific system behaviors.
5. Non-Functional Requirements: Performance, Security, etc.
6. UI/UX Guidelines: Wireframes or references.
7. Analytics: Metrics to track success.

Best Practices

• Focus on Outcomes, Not Outputs: Measure success by value delivered, not features shipped.
• Fall in Love with the Problem: Don't get attached to a specific solution too early.
• Validate Early: Use prototypes and mockups to test assumptions before building key features.