product-management

产品管理专家

涵盖战略、路线图、优先级排序和产品市场契合度的综合产品框架。

产品战略

产品愿景框架

VISION COMPONENTS:

TARGET CUSTOMER:
- Who are we building for?
- What segments? What personas?

CUSTOMER NEED:
- What problem are we solving?
- What job to be done?

KEY BENEFIT:
- Primary value proposition
- Why customers will choose us

DIFFERENTIATOR:
- What makes us unique?
- Competitive advantage

AMAZON PRESS RELEASE FORMAT:
- Headline
- Summary (who, what, when, where, why)
- Problem statement
- Solution description
- Customer quote
- How to get started

产品市场契合度

PMF INDICATORS:

QUANTITATIVE:
- 40%+ would be "very disappointed" without product (Sean Ellis)
- Strong organic growth/referrals
- Low churn, high retention
- Improving unit economics

QUALITATIVE:
- Customers actively advocating
- Word of mouth driving acquisition
- Pull from market (not push)
- Customers expanding usage

PMF SURVEY:
"How would you feel if you could no longer use [product]?"
- Very disappointed → Target 40%+
- Somewhat disappointed
- Not disappointed

PMF STAGES:
1. Problem-Solution Fit: Validated problem worth solving
2. Product-Market Fit: Solution resonates with market
3. Business Model Fit: Sustainable economics
4. Scale: Growth mechanics work

待完成的任务（JTBD）

JOB STATEMENT:
When [situation], I want to [motivation], so I can [expected outcome].

FORCES OF PROGRESS:
Push: Current pain/frustration
Pull: Attraction to new solution
Anxiety: Concerns about switching
Habit: Comfort with status quo

有关详细的 JTBD 方法论和访谈技巧，请参阅客户研究方法。

路线图规划

路线图类型

类型	时间范围	受众	详细程度
愿景	2-5 年	董事会、高管	主题
战略	1-2 年	领导层	倡议
发布	3-6 个月	团队、利益相关者	功能
迭代	2-4 周	开发团队	用户故事

面向产品的 OKR 框架

PRODUCT OKR STRUCTURE:

OBJECTIVE: [Qualitative goal]

KEY RESULT 1: [Metric] from [X] to [Y]
KEY RESULT 2: [Metric] from [X] to [Y]
KEY RESULT 3: [Metric] from [X] to [Y]

EXAMPLE:
O: Become the preferred solution for enterprise customers
KR1: Increase enterprise NPS from 40 to 60
KR2: Reduce enterprise churn from 8% to 4%
KR3: Increase enterprise ACV from $50K to $75K

功能优先级排序

RICE 框架

RICE SCORE = (Reach x Impact x Confidence) / Effort

REACH: How many customers affected per quarter
- Count: Number of users, customers, transactions

IMPACT: Effect on individual customer
- 3 = Massive
- 2 = High
- 1 = Medium
- 0.5 = Low
- 0.25 = Minimal

CONFIDENCE: How sure are we
- 100% = High confidence
- 80% = Medium
- 50% = Low

EFFORT: Person-months of work
- Engineering time
- Design time
- PM time

EXAMPLE:
| Feature | Reach | Impact | Conf | Effort | RICE |
|---------|-------|--------|------|--------|------|
| A | 5000 | 2 | 80% | 3 | 2667 |
| B | 1000 | 3 | 100% | 1 | 3000 |
| C | 10000 | 1 | 50% | 5 | 1000 |

ICE 框架

ICE SCORE = Impact x Confidence x Ease

IMPACT (1-10):
How much will this move our key metric?

CONFIDENCE (1-10):
How sure are we about impact estimate?

EASE (1-10):
How easy to implement?

Note: Simpler than RICE, good for quick decisions

MoSCoW 方法

类别	定义	指引
必须有	发布时不可或缺	核心功能
应该有	重要但不关键	价值高，可推迟
可以有	有了更好	时间允许时
不会有	不在范围内（本次发布）	留待未来考虑

Kano 模型

CATEGORIES:

BASIC (Must-be):
- Expected features
- Absence causes dissatisfaction
- Example: Login functionality

PERFORMANCE (Linear):
- More is better
- Satisfaction proportional to fulfillment
- Example: Speed, capacity

DELIGHTERS (Excitement):
- Unexpected features
- Absence doesn't cause dissatisfaction
- Presence greatly increases satisfaction
- Example: Innovative features

客户研究

研究方法

方法	适用场景	样本量	时间
用户访谈	深入理解	5-15	2-4 周
问卷调查	量化发现	100-1000+	1-2 周
可用性测试	验证设计	5-8	1-2 周
A/B 测试	比较选项	1000+	2-4 周
分析	理解行为	不适用	持续进行
卡片分类	信息架构	15-30	1 周
日记研究	长期行为	10-20	2-4 周

有关详细的访谈框架、人物角色模板和可用性测试方案，请参阅客户研究方法。

产品分析

关键指标框架

PIRATE METRICS (AARRR):

ACQUISITION:
- How do users find us?
- Metrics: Traffic, signups, installs

ACTIVATION:
- First positive experience
- Metrics: Onboarding completion, first value

RETENTION:
- Do they come back?
- Metrics: DAU/MAU, cohort retention

REVENUE:
- Do they pay?
- Metrics: Conversion, ARPU, LTV

REFERRAL:
- Do they tell others?
- Metrics: NPS, referral rate, viral coefficient

产品健康度指标

指标	公式	目标
DAU/MAU	日活跃用户 / 月活跃用户	20-50%+
激活率	完成设置的用户 / 注册用户	40-60%+
功能采用率	使用该功能的用户 / 总用户数	因情况而异
价值实现时间	首次获得价值所需天数	尽可能缩短
高活跃用户	重度用户 / 总用户数	15-25%

有关详细的群组分析、留存基准和事件跟踪策略，请参阅分析与实验。

A/B 测试

实验框架

EXPERIMENT DESIGN:

HYPOTHESIS:
If we [change], then [metric] will [improve/decrease] because [rationale].

METRICS:
- Primary: The metric you're trying to move
- Secondary: Other metrics to monitor
- Guardrails: Metrics that shouldn't degrade

SAMPLE SIZE:
Use calculator based on:
- Baseline conversion rate
- Minimum detectable effect (MDE)
- Statistical significance (usually 95%)
- Power (usually 80%)

DURATION:
- At least 1 business cycle
- Adequate sample size
- Account for novelty effects

决策框架

• 发布：统计显著 + 实际显著 + 无负面护栏指标
• 迭代：结果方向积极但未达到统计显著，或结果不一致
• 终止：没有效果或产生负面影响
• 调查：结果出乎意料、差异较大或不同细分群体间存在差异

有关详细的统计概念、常见陷阱和细分分析，请参阅分析与实验。

产品发布

发布检查清单

PRE-LAUNCH:
- [ ] Feature complete and tested
- [ ] Documentation ready
- [ ] Support team trained
- [ ] Marketing materials prepared
- [ ] Sales team enabled
- [ ] Beta feedback incorporated
- [ ] Success metrics defined

LAUNCH:
- [ ] Staged rollout plan
- [ ] Monitoring dashboards live
- [ ] War room established
- [ ] Communication sent
- [ ] Feature flags enabled

POST-LAUNCH:
- [ ] Monitor metrics and feedback
- [ ] Address critical issues
- [ ] Gather early learnings
- [ ] Celebrate wins
- [ ] Retrospective scheduled

上市计划

要素	描述
目标细分市场	面向哪些人？
价值主张	他们为什么会关注？
定价	我们如何收费？
分发	他们如何获取？
信息传达	我们要传达什么？
赋能	团队如何销售／提供支持？
衡量	我们如何跟踪成效？

产品探索

探索技巧

技巧	目的	适用时机
机会地图	识别问题	探索初期
故事地图	将用户历程可视化	规划发布
设计冲刺	快速制作原型	重大赌注
虚假入口测试	验证需求	开发前
绿野仙踪法	测试概念	复杂功能
礼宾式 MVP	先提供人工服务	新市场

机会评估

OPPORTUNITY CANVAS:

PROBLEM:
What problem are we solving?
Who has this problem?
How do they solve it today?

EVIDENCE:
What data supports this?
Customer quotes/feedback?
Market research?

SOLUTION:
What are we proposing?
Why will it work?
What's the MVP?

ASSUMPTIONS:
What must be true?
What risks exist?
How will we validate?

OUTCOME:
Success metrics?
Business impact?
Customer impact?

交付物模板

PRD 结构（单页版）

1. EXECUTIVE SUMMARY (3-4 sentences)
- What: One-line description
- Why: Core problem being solved
- Who: Target users
- Success: How we'll measure it

2. BACKGROUND & CONTEXT
- Current situation and pain points
- Supporting data
- Strategic alignment

3. GOALS & SUCCESS METRICS
- Primary goal and success metric
- Secondary goals and metrics
- Guardrail metrics

4. USER STORIES
Format: "As a [persona], I want to [action], so that [benefit]"
- Acceptance criteria
- Priority (Must/Should/Could Have)

5. SOLUTION OVERVIEW
- High-level description
- Key user flows
- Out of scope

6. DESIGN & TECHNICAL CONSIDERATIONS
- Mockups/wireframes
- Dependencies
- Scalability

7. LAUNCH PLAN
- Rollout strategy
- Success criteria
- Risk mitigation

8. OPEN QUESTIONS
- Unresolved decisions
- Areas needing research

其他资源

如需全面了解产品管理框架和方法：

• 产品战略专家 - 完整的 PM 参考指南
• 客户研究方法 - 访谈框架、用户画像、可用性测试
• 分析与实验 - 留存率分析、A/B 测试、事件跟踪

另请参阅

• 数据科学 - 分析与 ML
• 营销 - 上市策略
• 商业战略 - 战略规划