Product Manager Toolkit
Essential tools and frameworks for modern product management, from discovery to delivery.
Table of Contents
-
Feature Prioritization
-
Customer Discovery
-
PRD Development
-
RICE Prioritizer
-
Customer Interview Analyzer
Quick Start
For Feature Prioritization
CODEBLOCK0
For Interview Analysis
CODEBLOCK1
For PRD Creation
- 1. Choose template from INLINECODE0
- Fill sections based on discovery work
- Review with engineering for feasibility
- Version control in project management tool
Core Workflows
Feature Prioritization Process
CODEBLOCK2
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
CODEBLOCK3
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
CODEBLOCK4
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
CODEBLOCK5
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
CODEBLOCK6
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
Tools Reference
RICE Prioritizer
Advanced RICE framework implementation with portfolio analysis.
Features:
- - RICE score calculation with configurable weights
- Portfolio balance analysis (quick wins vs big bets)
- Quarterly roadmap generation based on capacity
- Multiple output formats (text, JSON, CSV)
CSV Input Format:
CODEBLOCK7
Commands:
# Create sample data
python scripts/rice_prioritizer.py sample
# Run with default capacity (10 person-months)
python scripts/rice_prioritizer.py features.csv
# Custom capacity
python scripts/rice_prioritizer.py features.csv --capacity 20
# JSON output for integration
python scripts/rice_prioritizer.py features.csv --output json
# CSV output for spreadsheets
python scripts/rice_prioritizer.py features.csv --output csv
Customer Interview Analyzer
NLP-based interview analysis for extracting actionable insights.
Capabilities:
- - Pain point extraction with severity assessment
- Feature request identification and classification
- Jobs-to-be-done pattern recognition
- Sentiment analysis per section
- Theme and quote extraction
- Competitor mention detection
Commands:
# Analyze interview transcript
python scripts/customer_interview_analyzer.py interview.txt
# JSON output for aggregation
python scripts/customer_interview_analyzer.py interview.txt json
Input/Output Examples
→ See references/input-output-examples.md for details
Integration Points
Compatible tools and platforms:
| Category | Platforms |
|---|
| Analytics | Amplitude, Mixpanel, Google Analytics |
| Roadmapping |
ProductBoard, Aha!, Roadmunk, Productplan |
|
Design | Figma, Sketch, Miro |
|
Development | Jira, Linear, GitHub, Asana |
|
Research | Dovetail, UserVoice, Pendo, Maze |
|
Communication | Slack, Notion, Confluence |
JSON export enables integration with most tools:
# Export for Jira import
python scripts/rice_prioritizer.py features.csv --output json > priorities.json
# Export for dashboard
python scripts/customer_interview_analyzer.py interview.txt json > insights.json
Common Pitfalls to Avoid
| Pitfall | Description | Prevention |
|---|
| Solution-First | Jumping to features before understanding problems | Start every PRD with problem statement |
| Analysis Paralysis |
Over-researching without shipping | Set time-boxes for research phases |
|
Feature Factory | Shipping features without measuring impact | Define success metrics before building |
|
Ignoring Tech Debt | Not allocating time for platform health | Reserve 20% capacity for maintenance |
|
Stakeholder Surprise | Not communicating early and often | Weekly async updates, monthly demos |
|
Metric Theater | Optimizing vanity metrics over real value | Tie metrics to user value delivered |
Best Practices
Writing Great PRDs:
- - Start with the problem, not the solution
- Include clear success metrics upfront
- Explicitly state what's out of scope
- Use visuals (wireframes, flows, diagrams)
- Keep technical details in appendix
- Version control all changes
Effective Prioritization:
- - Mix quick wins with strategic bets
- Consider opportunity cost of delays
- Account for dependencies between features
- Buffer 20% for unexpected work
- Revisit priorities quarterly
- Communicate decisions with context
Customer Discovery:
- - Ask "why" five times to find root cause
- Focus on past behavior, not future intentions
- Avoid leading questions ("Wouldn't you love...")
- Interview in the user's natural environment
- Watch for emotional reactions (pain = opportunity)
- Validate qualitative with quantitative data
Quick Reference
CODEBLOCK11
Reference Documents
- -
references/prd_templates.md - PRD templates for different contexts - INLINECODE6 - Detailed framework documentation (RICE, MoSCoW, Kano, JTBD, etc.)
产品经理工具包
从发现到交付,现代产品管理必备工具与框架。
目录
-
功能优先级排序
-
客户发现
-
PRD开发
-
RICE优先级排序器
-
客户访谈分析器
快速入门
功能优先级排序
bash
创建示例数据文件
python scripts/rice_prioritizer.py sample
结合团队容量运行优先级排序
python scripts/rice
prioritizer.py samplefeatures.csv --capacity 15
访谈分析
bash
python scripts/customer
interviewanalyzer.py interview_transcript.txt
PRD创建
- 1. 从 references/prd_templates.md 选择模板
- 基于发现工作填写各部分内容
- 与工程团队评审可行性
- 在项目管理工具中进行版本控制
核心工作流
功能优先级排序流程
收集 → 评分 → 分析 → 规划 → 验证 → 执行
第1步:收集功能需求
- - 客户反馈(支持工单、访谈)
- 销售需求(CRM管道阻塞点)
- 技术债务(工程团队输入)
- 战略举措(领导层目标)
第2步:使用RICE评分
bash
输入:包含功能的CSV文件
python scripts/rice_prioritizer.py features.csv --capacity 20
RICE公式和评分指南请参见 references/frameworks.md。
第3步:分析组合
审查工具输出,关注:
- - 速赢与重大投入的分布
- 工作量集中度(避免全部为超大型项目)
- 战略对齐差距
第4步:生成路线图
第5步:验证结果
在最终确定路线图之前:
- - [ ] 将最高优先级与战略目标进行对比
- [ ] 进行敏感性分析(如果估算偏差2倍会怎样?)
- [ ] 与关键干系人评审以发现盲点
- [ ] 检查功能间是否存在遗漏的依赖关系
- [ ] 与工程团队验证工作量估算
第6步:执行与迭代
- - 与团队分享路线图
- 跟踪实际与估算工作量
- 每季度重新审视优先级
- 根据经验更新RICE输入
客户发现流程
规划 → 招募 → 访谈 → 分析 → 综合 → 验证
第1步:规划研究
- - 定义研究问题
- 确定目标细分群体
- 创建访谈脚本(参见 references/frameworks.md)
第2步:招募参与者
- - 每个细分群体5-8次访谈
- 混合核心用户与流失用户
- 给予适当激励
第3步:进行访谈
- - 采用半结构化形式
- 聚焦问题而非解决方案
- 经许可后录音
- 访谈期间尽量少做笔记
第4步:分析洞察
bash
python scripts/customer
interviewanalyzer.py transcript.txt
提取内容:
- - 痛点及其严重程度
- 功能请求及其优先级
- 待完成工作任务模式
- 情感倾向与关键主题
- 重要引述
第5步:综合发现
- - 跨访谈归类相似痛点
- 识别模式(3次以上提及即为模式)
- 使用机会解决方案树映射到机会领域
- 按频率和严重程度对机会排序
第6步:验证解决方案
在开始构建之前:
- - [ ] 创建解决方案假设(参见 references/frameworks.md)
- [ ] 使用低保真原型进行测试
- [ ] 衡量实际行为与陈述偏好的差异
- [ ] 根据反馈进行迭代
- [ ] 记录经验以供未来研究参考
PRD开发流程
范围界定 → 起草 → 评审 → 完善 → 批准 → 跟踪
第1步:选择模板
从 references/prd_templates.md 中选择:
| 模板 | 适用场景 | 时间线 |
|---|
| 标准PRD | 复杂功能、跨团队 | 6-8周 |
| 单页PRD |
简单功能、单团队 | 2-4周 |
| 功能简报 | 探索阶段 | 1周 |
| 敏捷史诗 | 基于冲刺交付 | 持续进行 |
第2步:起草内容
- - 以问题陈述开头
- 预先定义成功指标
- 明确说明范围外事项
- 包含线框图或原型图
第3步:评审周期
- - 工程团队:可行性和工作量
- 设计团队:用户体验差距
- 销售团队:市场验证
- 支持团队:运营影响
第4步:根据反馈完善
第5步:批准与启动
第6步:跟踪执行
上线后:
- - [ ] 对比实际指标与目标
- [ ] 开展用户反馈会议
- [ ] 记录有效与无效的做法
- [ ] 更新估算准确度数据
- [ ] 与团队分享经验
工具参考
RICE优先级排序器
结合组合分析的高级RICE框架实现。
功能特性:
- - 支持可配置权重的RICE分数计算
- 组合平衡分析(速赢 vs 重大投入)
- 基于容量的季度路线图生成
- 多种输出格式(文本、JSON、CSV)
CSV输入格式:
csv
name,reach,impact,confidence,effort,description
用户仪表盘重新设计,5000,high,high,l,完全重新设计
移动端推送通知,10000,massive,medium,m,添加推送支持
深色模式,8000,medium,high,s,深色主题选项
命令:
bash
创建示例数据
python scripts/rice_prioritizer.py sample
使用默认容量运行(10人月)
python scripts/rice_prioritizer.py features.csv
自定义容量
python scripts/rice_prioritizer.py features.csv --capacity 20
JSON输出用于集成
python scripts/rice_prioritizer.py features.csv --output json
CSV输出用于电子表格
python scripts/rice_prioritizer.py features.csv --output csv
客户访谈分析器
基于NLP的访谈分析工具,用于提取可执行洞察。
能力:
- - 痛点提取及严重程度评估
- 功能请求识别与分类
- 待完成工作任务模式识别
- 各部分情感分析
- 主题与引述提取
- 竞品提及检测
命令:
bash
分析访谈记录
python scripts/customer
interviewanalyzer.py interview.txt
JSON输出用于汇总
python scripts/customer
interviewanalyzer.py interview.txt json
输入/输出示例
→ 详情请参见 references/input-output-examples.md
集成点
兼容工具与平台:
| 类别 | 平台 |
|---|
| 分析 | Amplitude, Mixpanel, Google Analytics |
| 路线图 |
ProductBoard, Aha!, Roadmunk, Productplan |
|
设计 | Figma, Sketch, Miro |
|
开发 | Jira, Linear, GitHub, Asana |
|
研究 | Dovetail, UserVoice, Pendo, Maze |
|
沟通 | Slack, Notion, Confluence |
JSON导出支持与大多数工具集成:
bash
导出用于Jira导入
python scripts/rice_prioritizer.py features.csv --output json > priorities.json
导出用于仪表盘
python scripts/customer
interviewanalyzer.py interview.txt json > insights.json
常见陷阱需避免
| 陷阱 | 描述 | 预防措施 |
|---|
| 解决方案优先 | 在理解问题前就跳到功能 | 每个PRD以问题陈述开头 |
| 分析瘫痪 |
过度研究而不交付 | 为研究阶段设定时间盒 |
|
功能工厂 | 交付功能而不衡量影响 | 在构建前定义成功指标 |
|
忽视技术债务 | 不为平台健康分配时间 | 预留20%容量用于维护 |
|
干系人意外 | 不进行早期和频繁沟通 | 每周