prioritization-frameworks

oleh phuryn

Panduan referensi untuk 9 kerangka kerja prioritas dengan rumus, panduan kapan digunakan, dan templat — RICE, ICE, Kano, MoSCoW, Opportunity Score, dan lainnya. Gunakan saat memilih metode prioritas, membandingkan kerangka kerja seperti RICE vs ICE, atau mempelajari cara kerja berbagai pendekatan prioritas.

npx skills add https://github.com/phuryn/pm-skills --skill prioritization-frameworks
Unduh ZIPGitHub
25.7k
Coba skill iniDisponsori

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

Lebih banyak skill dari phuryn

create-prd
phuryn
Buat Dokumen Requirements Produk menggunakan template komprehensif 8 bagian yang mencakup masalah, tujuan, segmen, proposisi nilai, solusi, dan perencanaan rilis. Gunakan saat menulis PRD, mendokumentasikan requirements produk, menyiapkan spesifikasi fitur, atau meninjau PRD yang sudah ada.
outcome-roadmap
phuryn
Ubah roadmap yang berfokus pada keluaran menjadi roadmap yang berfokus pada hasil untuk mengomunikasikan maksud strategis. Tulis ulang inisiatif sebagai pernyataan hasil yang mencerminkan dampak bagi pengguna dan bisnis. Gunakan saat beralih ke roadmap hasil, membuat roadmap lebih strategis, atau menulis ulang daftar fitur sebagai hasil.
project-managementcommunication
strategy-red-team
phuryn
Lakukan red-team terhadap PRD, roadmap, atau strategi dengan menyerang asumsi penopangnya sebelum realitas melakukannya. Steelman setiap klaim lalu serang, rangking mode kegagalan berdasarkan dampak × kemungkinan × murahnya pengujian, dan kembalikan tes termurah serta kriteria penghentian untuk masing-masing. Gunakan saat menguji ketahanan sebuah rencana, menguji tekanan sebuah strategi, menantang asumsi, atau menyiapkan dokumen untuk tinjauan eksekutif.
pre-mortem
phuryn
Jalankan analisis risiko pre-mortem pada PRD atau rencana peluncuran. Mengategorikan risiko sebagai Tigers (masalah nyata), Paper Tigers (kekhawatiran berlebihan), dan Elephants (kekhawatiran yang tidak diungkapkan), lalu mengklasifikasikan sebagai launch-blocking, fast-follow, atau track. Gunakan saat mempersiapkan peluncuran, menguji ketahanan rencana produk, atau mengidentifikasi hal-hal yang bisa salah.