product-manager-toolkit

Product Manager Toolkit

Essential tools and frameworks for modern product management, from discovery to delivery.

Table of Contents

• [Quick Start](#quick-start)
• [Core Workflows](#core-workflows)
• [Feature Prioritization](#feature-prioritization-process)
• [Customer Discovery](#customer-discovery-process)
• [PRD Development](#prd-development-process)
• [Tools Reference](#tools-reference)
• [RICE Prioritizer](#rice-prioritizer)
• [Customer Interview Analyzer](#customer-interview-analyzer)
• [Input/Output Examples](#inputoutput-examples)
• [Integration Points](#integration-points)
• [Common Pitfalls](#common-pitfalls-to-avoid)

Quick Start

For Feature Prioritization

# Create sample data file
python scripts/rice_prioritizer.py sample

# Run prioritization with team capacity
python scripts/rice_prioritizer.py sample_features.csv --capacity 15

For Interview Analysis

python scripts/customer_interview_analyzer.py interview_transcript.txt

For PRD Creation

1. Choose template from references/prd_templates.md
2. Fill sections based on discovery work
3. Review with engineering for feasibility
4. Version control in project management tool

Core Workflows

Feature Prioritization Process

Gather → Score → Analyze → Plan → Validate → Execute

Step 1: Gather Feature Requests

• Customer feedback (support tickets, interviews)
• Sales requests (CRM pipeline blockers)
• Technical debt (engineering input)
• Strategic initiatives (leadership goals)

Step 2: Score with RICE

# Input: CSV with features
python scripts/rice_prioritizer.py features.csv --capacity 20

See references/frameworks.md for RICE formula and scoring guidelines.

Step 3: Analyze Portfolio

Review the tool output for:

• Quick wins vs big bets distribution
• Effort concentration (avoid all XL projects)
• Strategic alignment gaps

Step 4: Generate Roadmap

• Quarterly capacity allocation
• Dependency identification
• Stakeholder communication plan

Step 5: Validate Results

Before finalizing the roadmap:

• [ ] Compare top priorities against strategic goals
• [ ] Run sensitivity analysis (what if estimates are wrong by 2x?)
• [ ] Review with key stakeholders for blind spots
• [ ] Check for missing dependencies between features
• [ ] Validate effort estimates with engineering

Step 6: Execute and Iterate

• Share roadmap with team
• Track actual vs estimated effort
• Revisit priorities quarterly
• Update RICE inputs based on learnings

Customer Discovery Process

Plan → Recruit → Interview → Analyze → Synthesize → Validate

Step 1: Plan Research

• Define research questions
• Identify target segments
• Create interview script (see references/frameworks.md)

Step 2: Recruit Participants

• 5-8 interviews per segment
• Mix of power users and churned users
• Incentivize appropriately

Step 3: Conduct Interviews

• Use semi-structured format
• Focus on problems, not solutions
• Record with permission
• Take minimal notes during interview

Step 4: Analyze Insights

python scripts/customer_interview_analyzer.py transcript.txt

Extracts:

• Pain points with severity
• Feature requests with priority
• Jobs to be done patterns
• Sentiment and key themes
• Notable quotes

Step 5: Synthesize Findings

• Group similar pain points across interviews
• Identify patterns (3+ mentions = pattern)
• Map to opportunity areas using Opportunity Solution Tree
• Prioritize opportunities by frequency and severity

Step 6: Validate Solutions

Before building:

• [ ] Create solution hypotheses (see references/frameworks.md)
• [ ] Test with low-fidelity prototypes
• [ ] Measure actual behavior vs stated preference
• [ ] Iterate based on feedback
• [ ] Document learnings for future research

PRD Development Process

Scope → Draft → Review → Refine → Approve → Track

Step 1: Choose Template

Select from references/prd_templates.md:

| Template | Use Case | Timeline | |----------|----------|----------| | Standard PRD | Complex features, cross-team | 6-8 weeks | | One-Page PRD | Simple features, single team | 2-4 weeks | | Feature Brief | Exploration phase | 1 week | | Agile Epic | Sprint-based delivery | Ongoing |

Step 2: Draft Content

• Lead with problem statement
• Define success metrics upfront
• Explicitly state out-of-scope items
• Include wireframes or mockups

Step 3: Review Cycle

• Engineering: feasibility and effort
• Design: user experience gaps
• Sales: market validation
• Support: operational impact

Step 4: Refine Based on Feedback

• Address technical constraints
• Adjust scope to fit timeline
• Document trade-off decisions

Step 5: Approval and Kickoff

• Stakeholder sign-off
• Sprint planning integration
• Communication to broader team

Step 6: Track Execution

After launch:

• [ ] Compare actual metrics vs targets
• [ ] Conduct user feedback sessions
• [ ] Document what worked and what didn't
• [ ] Update estimation accuracy data
• [ ] Share learnings with team

Positioning Statement Framework

Create a Geoffrey Moore-style positioning statement to clarify product differentiation and value. Use this before writing PRDs, go-to-market plans, or pitch decks.

Core Positioning Template

For [target user/persona]
who [underserved need or painful moment],
[product name] is a [product category]
that [primary outcome delivered].
Unlike [main alternative: competitor, workaround, or status quo],
[product name] [unique differentiation in outcome terms].

One-Sentence Value Proposition

Write a single sentence a PM can reuse in docs and slides.

Differentiation Proof Points

List 3 concrete proof points that support the "unlike" claim. Focus on outcomes and evidence, not adjectives.

Writing Rules

• Use persona-first language.
• Focus on outcomes, not feature lists.
• Keep wording specific and testable.
• "Unlike X" should name the real alternative, including status quo.
• Strong differentiation is about outcomes and evidence, not adjectives.

Optional Variants

• Executive variant: Shorter strategic wording for board decks.
• Customer-facing variant: Clear plain-language wording for marketing.

Next Steps

1. Generate 3 alternate positioning directions (Recommended)
2. Create a competitor comparison message matrix
3. Convert into homepage headline + subheadline options

Recommendation Canvas

Evaluate product opportunities holistically using a structured canvas that connects problem framing to solution evidence. Useful for investment decisions, portfolio reviews, and stakeholder alignment.

Canvas Sections

## Product Name
[Name of the product or service]

## Business Outcome
[Direction] [Metric] [Outcome] [Context] [Acceptance criteria]

## Product Outcome
[Direction] [Metric] [Outcome] [Context] [Acceptance criteria]

## Problem Statement Narrative
[2-3 sentences telling the persona's story from their point-of-view]

## Solution Hypothesis
If we [action/solution] for [target persona],
then we will [desirable outcome].

### Tiny Acts of Discovery
- [Small experiment focused on viability]
- [Small experiment focused on customer value]

### Proof-of-Life
Within [timeframe], we observe:
- [Quantitative measurable outcome]
- [Qualitative measurable outcome]

## Positioning Statement
For [target persona] that need [underserved need],
[product] is a [category] that [benefit].
Unlike [competitor], [product] provides [differentiation].

## Assumptions & Unknowns
- [Assumption 1]
- [Assumption 2]

## Issues/Risks (PESTEL lens)
- Political: [Risk]
- Economic: [Risk]
- Social: [Risk]
- Technological: [Risk]
- Environmental: [Risk]
- Legal: [Risk]

## Value Justification
[Yes/Yes with caveats/No with alternatives/No]
Justification: [Why this is or isn't valuable]

## Success Metrics
1. [SMART metric 1]
2. [SMART metric 2