Product Manager Toolkit

/product-manager-toolkit

Essential tools and frameworks for modern product management, from discovery to delivery. Ask the user what they need: feature prioritization (paste the feature list), interview analysis (paste the transcript), or a PRD (describe the feature and its context).

Core Workflows

Feature Prioritization Process

1. Gather Feature Requests

   • Customer feedback
   • Sales requests
   • Technical debt
   • Strategic initiatives

2. Score with RICE Ask the user to list features with reach, impact, confidence, and effort, then compute and rank:

   • Reach: Users affected per quarter
   • Impact: massive/high/medium/low/minimal
   • Confidence: high/medium/low
   • Effort: xl/l/m/s/xs (person-months)

3. Analyze Portfolio

   • Review quick wins vs big bets
   • Check effort distribution
   • Validate against strategy

4. Generate Roadmap

   • Quarterly capacity planning
   • Dependency mapping
   • Stakeholder alignment

Customer Discovery Process

1. Conduct Interviews

   • Use semi-structured format
   • Focus on problems, not solutions
   • Record with permission

2. Analyze Insights Ask the user to paste interview transcripts or notes, then extract:

   • Pain points with severity
   • Feature requests with priority
   • Jobs to be done
   • Sentiment analysis
   • Key themes and quotes

3. Synthesize Findings

   • Group similar pain points
   • Identify patterns across interviews
   • Map to opportunity areas

4. Validate Solutions

   • Create solution hypotheses
   • Test with prototypes
   • Measure actual vs expected behavior

PRD Development Process

1. Choose Template

   • Standard PRD: Complex features (6-8 weeks); comprehensive format with technical specs
   • One-Page PRD: Simple features (2-4 weeks); focus on problem/solution/metrics
   • Feature Brief: Exploration phase (1 week); lightweight, hypothesis-driven, pre-PRD
   • Agile Epic: Sprint-based delivery; user story mapping, acceptance criteria focus

2. Structure Content

   • Problem -> Solution -> Success Metrics
   • Always include out-of-scope
   • Clear acceptance criteria

3. Collaborate

   • Engineering for feasibility
   • Design for experience
   • Sales for market validation
   • Support for operational impact

Prioritization Frameworks

RICE Framework

Score = (Reach x Impact x Confidence) / Effort

Reach: # of users/quarter
Impact:
  - Massive = 3x
  - High = 2x
  - Medium = 1x
  - Low = 0.5x
  - Minimal = 0.25x
Confidence:
  - High = 100%
  - Medium = 80%
  - Low = 50%
Effort: Person-months

Value vs Effort Matrix

                Low Effort      High Effort

High Value      QUICK WINS      BIG BETS
                [Prioritize]    [Strategic]

Low Value       FILL-INS        TIME SINKS
                [Maybe]         [Avoid]

MoSCoW Method

• Must Have: Critical for launch
• Should Have: Important but not critical
• Could Have: Nice to have
• Won't Have: Out of scope

Discovery Frameworks

Customer Interview Guide

1. Context Questions (5 min)
   - Role and responsibilities
   - Current workflow
   - Tools used

2. Problem Exploration (15 min)
   - Pain points
   - Frequency and impact
   - Current workarounds

3. Solution Validation (10 min)
   - Reaction to concepts
   - Value perception
   - Willingness to pay

4. Wrap-up (5 min)
   - Other thoughts
   - Referrals
   - Follow-up permission

Hypothesis Template

We believe that [building this feature]
For [these users]
Will [achieve this outcome]
We'll know we're right when [metric]

Opportunity Solution Tree

Outcome
|- Opportunity 1
|  |- Solution A
|  \- Solution B
\- Opportunity 2
   |- Solution C
   \- Solution D

Metrics & Analytics

North Star Metric Framework

1. Identify Core Value: What's the #1 value to users?
2. Make it Measurable: Quantifiable and trackable
3. Ensure It's Actionable: Teams can influence it
4. Check Leading Indicator: Predicts business success

Funnel Analysis Template

Acquisition -> Activation -> Retention -> Revenue -> Referral

Key Metrics:
- Conversion rate at each step
- Drop-off points
- Time between steps
- Cohort variations

Feature Success Metrics

• Adoption: % of users using feature
• Frequency: Usage per user per time period
• Depth: % of feature capability used
• Retention: Continued usage over time
• Satisfaction: NPS/CSAT for feature

Best Practices

Writing Great PRDs

1. Start with the problem, not solution
2. Include clear success metrics upfront
3. Explicitly state what's out of scope
4. Use visuals (wireframes, flows)
5. Keep technical details in appendix
6. Version control changes

Effective Prioritization

1. Mix quick wins with strategic bets
2. Consider opportunity cost
3. Account for dependencies
4. Buffer for unexpected work (20%)
5. Revisit quarterly
6. Communicate decisions clearly

Customer Discovery Tips

1. Ask "why" 5 times
2. Focus on past behavior, not future intentions
3. Avoid leading questions
4. Interview in their environment
5. Look for emotional reactions
6. Validate with data

Stakeholder Management

1. Identify RACI for decisions
2. Regular async updates
3. Demo over documentation
4. Address concerns early
5. Celebrate wins publicly
6. Learn from failures openly

Common Pitfalls to Avoid

1. Solution-First Thinking: Jumping to features before understanding problems
2. Analysis Paralysis: Over-researching without shipping
3. Feature Factory: Shipping features without measuring impact
4. Ignoring Technical Debt: Not allocating time for platform health
5. Stakeholder Surprise: Not communicating early and often
6. Metric Theater: Optimizing vanity metrics over real value

Usage

/product-manager-toolkit $ARGUMENTS