prioritization-frameworks

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Prioritization Frameworks Reference

优先级框架参考指南

A reference guide to help you select and apply the right prioritization framework for your context.
一份帮助你根据实际场景选择并应用合适优先级框架的参考指南。

Core Principle

核心原则

Never allow customers to design solutions. Prioritize problems (opportunities), not features.
绝不要让客户来设计解决方案。应优先关注问题(机会),而非功能。

Opportunity Score (Dan Olsen, The Lean Product Playbook)

Opportunity Score(Dan Olsen,《精益产品实战》)

The recommended framework for prioritizing customer problems.
Survey customers on Importance and Satisfaction for each need (normalize to 0–1 scale).
Three related formulas:
  • Current value = Importance × Satisfaction
  • Opportunity Score = Importance × (1 − Satisfaction)
  • Customer value created = Importance × (S2 − S1), where S1 = satisfaction before, S2 = satisfaction after
High Importance + low Satisfaction = highest Opportunity Score = best opportunities. Plot on an Importance vs Satisfaction chart — upper-left quadrant is the sweet spot. Prioritizes customer problems, not solutions.
用于客户问题优先级排序的推荐框架。
针对每个需求,调研客户的重要性满意度(归一化至0–1区间)。
三个相关公式:
  • 当前价值 = Importance × Satisfaction
  • Opportunity Score = Importance × (1 − Satisfaction)
  • 创造的客户价值 = Importance × (S2 − S1),其中S1 = 改进前的满意度,S2 = 改进后的满意度
高重要性+低满意度=最高Opportunity Score=最优机会。将数据绘制在‘重要性vs满意度’图表中——左上象限为黄金区域。该框架优先关注客户问题,而非解决方案。

ICE Framework

ICE框架

Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.
  • I (Impact) = Opportunity Score × Number of Customers affected
  • C (Confidence) = How confident are we? (1-10). Accounts for risk.
  • E (Ease) = How easy is it to implement? (1-10). Accounts for economic factors.
Score = I × C × E. Higher = prioritize first.
适用于对项目和创意进行优先级排序。不仅考量价值,还纳入了风险与经济因素。
  • I(Impact,影响范围)= Opportunity Score × 受影响客户数量
  • C(Confidence,置信度)= 我们的置信程度?(1-10分)。用于考量风险。
  • E(Ease,实施难度)= 实施难度如何?(1-10分)。用于考量经济因素。
得分 = I × C × E。得分越高,优先级越高。

RICE Framework

RICE框架

Splits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.
  • R (Reach) = Number of customers affected
  • I (Impact) = Opportunity Score (value per customer)
  • C (Confidence) = How confident are we? (0-100%)
  • E (Effort) = How much effort to implement? (person-months)
Score = (R × I × C) / E
将ICE框架中的Impact拆分为两个独立因素。适用于需要更精细化管理的大型团队。
  • R(Reach,覆盖范围)= 受影响客户数量
  • I(Impact,影响程度)= Opportunity Score(每位客户的价值)
  • C(Confidence,置信度)= 我们的置信程度?(0-100%)
  • E(Effort,投入成本)= 实施所需投入?(人月)
Score = (R × I × C) / E

9 Frameworks Overview

9种框架概览

FrameworkBest ForKey Insight
Eisenhower MatrixPersonal tasksUrgent vs Important — for individual PM task management
Impact vs EffortTasks/initiativesSimple 2×2 — quick triage, not rigorous for strategic decisions
Risk vs RewardInitiativesLike Impact vs Effort but accounts for uncertainty
Opportunity ScoreCustomer problemsRecommended. Importance × (1 − Satisfaction). Normalize to 0–1.
Kano ModelUnderstanding expectationsMust-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing.
Weighted Decision MatrixMulti-factor decisionsAssign weights to criteria, score each option. Useful for stakeholder buy-in.
ICEIdeas/initiativesImpact × Confidence × Ease. Recommended for quick prioritization.
RICEIdeas at scale(Reach × Impact × Confidence) / Effort. Adds Reach to ICE.
MoSCoWRequirementsMust/Should/Could/Won't. Caution: project management origin.
框架适用场景核心要点
Eisenhower Matrix个人任务紧急vs重要——适用于产品经理个人任务管理
Impact vs Effort任务/项目简单的2×2矩阵——快速分类,不适用于严谨的战略决策
Risk vs Reward项目类似Impact vs Effort,但纳入了不确定性考量
Opportunity Score客户问题推荐使用。重要性 × (1 − 满意度)。归一化至0–1区间。
Kano Model需求理解必备型、期望型、兴奋型、无差异型、反向型。用于需求理解,而非优先级排序。
Weighted Decision Matrix多因素决策为各项标准分配权重,对每个选项打分。有助于获取相关方认可。
ICE创意/项目影响范围 × 置信度 × 实施难度。推荐用于快速优先级排序。
RICE规模化创意(覆盖范围 × 影响程度 × 置信度) / 投入成本。在ICE基础上增加了覆盖范围维度。
MoSCoW需求管理Must/Should/Could/Won't(必须/应该/可以/不会)。注意:源自项目管理领域。

Templates

模板

Further Reading

拓展阅读