vibe.prioritizationlisted
Install: claude install-skill su-record/vibe
# Prioritization Frameworks Reference
## Done Criteria
- [ ] 선택한 framework와 선택 근거가 기록되어 있다.
- [ ] 모든 평가 대상에 framework의 필수 입력값이 있다.
- [ ] 정의된 산식으로 점수가 계산되어 있다.
- [ ] 최종 정렬 순서와 동점 처리 기준이 명시되어 있다.
> Based on the Product Frameworks Compendium from [Product Compass](https://www.productcompass.pm/p/the-product-frameworks-compendium) by Pawel Huryn (MIT License).
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 x Satisfaction
- **Opportunity Score** = Importance x (1 - Satisfaction)
- **Customer value created** = Importance x (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.
## ICE Framework
Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.
- **I** (Impact) = Opportunity Score x Number of Customers affected
- **C** (Confidence) = How confident are we? (1-10). Accounts for risk.
- **E** (Ease)