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.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
A reference guide to help you select and apply the right prioritization framework for your context.
Never allow customers to design solutions. Prioritize problems (opportunities), not features.
The recommended framework for prioritizing customer problems.
Survey customers on Importance and Satisfaction for each need (normalize to 0–1 scale).
Three related formulas:
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.
Useful for prioritizing initiatives and ideas. Considers not only value but also risk and economic factors.
Score = I × C × E. Higher = prioritize first.
Splits ICE's Impact into two separate factors. Useful for larger teams that need more granularity.
Score = (R × I × C) / E
| Framework | Best For | Key Insight |
|---|---|---|
| Eisenhower Matrix | Personal tasks | Urgent vs Important — for individual PM task management |
| Impact vs Effort | Tasks/initiatives | Simple 2×2 — quick triage, not rigorous for strategic decisions |
| Risk vs Reward | Initiatives | Like Impact vs Effort but accounts for uncertainty |
| Opportunity Score | Customer problems | Recommended. Importance × (1 − Satisfaction). Normalize to 0–1. |
| Kano Model | Understanding expectations | Must-be, Performance, Attractive, Indifferent, Reverse. For understanding, not prioritizing. |
| Weighted Decision Matrix | Multi-factor decisions | Assign weights to criteria, score each option. Useful for stakeholder buy-in. |
| ICE | Ideas/initiatives | Impact × Confidence × Ease. Recommended for quick prioritization. |
| RICE | Ideas at scale | (Reach × Impact × Confidence) / Effort. Adds Reach to ICE. |
| MoSCoW | Requirements | Must/Should/Could/Won't. Caution: project management origin. |
まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Analyze A/B test results with statistical significance, sample size validation, confidence intervals, and ship/extend/stop recommendations. Use when evaluating experiment results, checking if a test reached significance, interpreting split test data, or deciding whether to ship a variant.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze and prioritize a list of feature requests by theme, strategic alignment, impact, effort, and risk. Use when reviewing customer feature requests, triaging a backlog, or making prioritization decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Generate an Ansoff Matrix analysis mapping growth strategies across market penetration, market development, product development, and diversification. Use when considering growth options, planning market expansion, or evaluating strategic growth paths.
日本語の概要は準備中です。原文の説明を表示しています。
Identify the first beachhead market segment for a product launch. Evaluates segments against burning pain, willingness to pay, winnable market share, and referral potential. Use when choosing a first market, targeting an initial customer segment, or planning market entry strategy.
日本語の概要は準備中です。原文の説明を表示しています。
Design experiments to test assumptions for an existing product — prototypes, A/B tests, spikes, and other low-effort validation methods. Use when validating assumptions, testing feature ideas cheaply, or planning product experiments.
日本語の概要は準備中です。原文の説明を表示しています。
Design lean startup experiments (pretotypes) for a new product. Creates XYZ hypotheses and suggests low-effort validation methods like landing pages, explainer videos, and pre-orders. Use when validating a new product idea, creating pretotypes, or testing market demand.
日本語の概要は準備中です。原文の説明を表示しています。