Prioritization Frameworks

作者 phuryn8607e3b07781無授權條款26K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫3 週前更新

Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.

AI 產生的概覽

介紹九種優先順序排序框架的參考指南,包含公式、適用時機說明與範本。

功能
此技能是一份參考指南,涵蓋九種優先順序排序框架,包括機會分數、ICE、RICE、Kano、MoSCoW、艾森豪矩陣、影響與投入、風險與報酬以及加權決策矩陣。它說明每種框架的公式、評分輸入與最適合的使用情境,並指向機會分數、ICE 和 RICE 的外部範本。它產出的是選擇與套用框架的指引,而非產出檔案或分析結果。
適用情境
適用於為產品或專案決策挑選優先順序排序方法、比較 RICE 與 ICE 等框架,或了解不同優先順序排序方法的運作方式。主要對象是產品經理與需要決定優先事項的團隊。
執行需求
不需要指令碼或執行環境相依項目,僅為說明與參考內容。它連結到外部的 Google Drive、Slides 與 Sheets 範本及延伸閱讀頁面,存取這些連結需要網路連線。

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)

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.

ICE Framework

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.

RICE Framework

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

9 Frameworks Overview

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.

Templates


Further Reading

來源與署名

來源:phuryn/pm-skills位於pm-execution/skills/prioritization-frameworks提交8607e3b

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架