Product Manager Toolkit

Essential frameworks and templates for modern product management—from discovery to delivery.

When to Use This Skill

Use when:

• Prioritizing features using data-driven frameworks (RICE)
• Conducting customer discovery interviews
• Creating Product Requirements Documents (PRDs)
• Defining and tracking product metrics
• Building product roadmaps and strategies
• Analyzing user behavior and engagement
• Aligning teams on product direction

Core Capabilities

1. RICE Prioritization - Feature scoring and portfolio analysis
2. Customer Discovery - Interview frameworks and insight synthesis
3. PRD Templates - Multiple PRD formats for different contexts
4. Product Metrics - North Star metrics, funnels, cohort analysis
5. Roadmap Planning - Capacity planning and quarterly planning
6. Stakeholder Alignment - Cross-functional communication

Reference Guides

For detailed guidance, see:

RICE Prioritization Framework

Use when: Prioritizing features and building roadmaps

Covers:

• RICE scoring formula (Reach, Impact, Confidence, Effort)
• Portfolio analysis (quick wins vs big bets)
• Score calculation and ranking
• Process and tools

Customer Interview & Discovery

Use when: Conducting customer research and validating problems

Covers:

• Customer interview framework and guide
• Interview best practices
• Analysis and synthesis process
• Pattern extraction and affinity mapping

PRD Templates & Development

Use when: Creating Product Requirements Documents

Covers:

• Feature Brief (lightweight)
• One-Page PRD (simple features)
• Standard PRD (11-section detailed)
• Agile Epic template
• PRD best practices

Product Metrics & Analytics

Use when: Defining success metrics and analyzing product health

Covers:

• North Star metric framework
• Funnel analysis and optimization
• Feature success metrics (adoption, engagement, quality)
• Cohort analysis and retention curves
• Unit economics (for SaaS/Marketplace)

Quick Decision Guide

Core Workflows

Feature Prioritization

1. Gather all feature requests and initiatives
2. Estimate Reach, Impact, Confidence, Effort for each
3. Calculate RICE scores
4. Rank by score, verify ranking feels right
5. Allocate quarterly capacity based on prioritization
6. Validate results post-launch

Customer Discovery

1. Define interview goals (not leading questions)
2. Recruit right mix of users (customers, prospects, churned)
3. Conduct interviews using framework
4. Analyze key patterns, pain points, features
5. Synthesize findings across interviews
6. Validate patterns in next round

PRD Development

1. Choose right PRD format (brief, one-page, standard, epic)
2. Problem-first articulation (who, what, why)
3. Solution overview and requirements
4. Acceptance criteria (engineering knows done)
5. Stakeholder alignment (eng, design, sales review)
6. Version control as requirements evolve

Metrics Setup

1. Define North Star metric (core user value)
2. Build success metrics (adoption, engagement, quality)
3. Set targets and thresholds
4. Create dashboard for monitoring
5. Establish review cadence (weekly/monthly)
6. Share metrics with team

Templates & Resources

All templates are in the references/ folder:

• RICE calculation templates and examples
• Customer interview guide and analysis checklist
• PRD templates (4 formats for different needs)
• Metrics framework and dashboard examples

Best Practices

Prioritization

• ✅ Use data: Back up reach/impact with evidence
• ✅ Include effort: Don't forget design, QA, documentation
• ✅ Be honest on confidence: Admit uncertainty
• ✅ Review quarterly: Rescore as situation changes
• ✅ Validate results: Did features deliver expected impact?

Discovery

• ✅ Listen more: 70% user, 30% you
• ✅ Avoid leading: Don't suggest solutions
• ✅ Ask why 3 times: Get to root cause
• ✅ Diverse participants: Include power users, casual users, non-users
• ✅ Synthesize patterns: Don't just list findings

PRD Writing

• ✅ Problem-first: Start with problem, not solution
• ✅ Clear criteria: Engineering knows definition of done
• ✅ Get alignment: Review with eng/design early
• ✅ Out of scope: Explicit bounds prevent creep
• ✅ Version control: Track changes over time

Metrics

• ✅ One North Star: Single metric representing core value
• ✅ Actionable: Teams can influence the metric
• ✅ Segment users: Different cohorts behave differently
• ✅ Compare trends: Week-over-week, month-over-month
• ✅ Alert on anomalies: Investigate drops and spikes

Dependencies

• brainstorming - For ideation and exploration
• concise-planning - For roadmap and planning