prioritization-frameworks
This Claude Code skill provides a structured reference guide to nine prioritization frameworks including Opportunity Score, ICE, RICE, and others, with formulas, scoring methods, and guidance on when each applies. Use it to select the appropriate prioritization method for your context, compare frameworks like RICE versus ICE, understand the mechanics behind different approaches, or learn how to apply frameworks like Opportunity Score to prioritize customer problems over proposed solutions.
git clone --depth 1 https://github.com/phuryn/pm-skills /tmp/prioritization-frameworks && cp -r /tmp/prioritization-frameworks/pm-execution/skills/prioritization-frameworks ~/.claude/skills/prioritization-frameworksSKILL.md
## 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 | 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. | ### Templates - [Opportunity Score intro (PDF)](https://drive.google.com/file/d/1ENbYPmk1i1AKO7UnfyTuULL5GucTVufW/view) - [Importance vs Satisfaction Template — Dan Olsen (Google Slides)](https://docs.google.com/presentation/d/1jg-LuF_3QHsf6f1nE1f98i4C0aulnRNMOO1jftgti8M/edit#slide=id.g796641d975_0_3) - [ICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1LUfnsPolhZgm7X2oij-7EUe0CJT-Dwr-/edit?usp=share_link&ouid=111307342557889008106&rtpof=true&sd=true) - [RICE Template (Google Sheets)](https://docs.google.com/spreadsheets/d/1S-6QpyOz5MCrV7B67LUWdZkAzn38Eahv/edit?usp=sharing&ouid=111307342557889008106&rtpof=true&sd=true) --- ### Further Reading - [The Product Management Frameworks Compendium + Templates](https://www.productcompass.pm/p/the-product-frameworks-compendium) - [Kano Model: How to Delight Your Customers Without Becoming a Feature Factory](https://www.productcompass.pm/p/kano-model-how-to-delight-your-customers) - [Continuous Product Discovery Masterclass (CPDM)](https://www.productcompass.pm/p/cpdm) (video course)
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.
Brainstorm product ideas for an existing product using multi-perspective ideation from PM, Designer, and Engineer viewpoints. Use when generating new feature ideas, brainstorming solutions for an identified opportunity, or ideating with a product trio.
Brainstorm feature ideas for a new product in initial discovery from PM, Designer, and Engineer perspectives. Use when starting product discovery for a new product, exploring features for a startup idea, or doing initial ideation.