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)
The method for finding the gap between what a system is supposed to do and what the code actually does — the class of bug generic scanners miss because they have no model of intent. Defines what counts as documented intent, what counts as implementation evidence, which mismatches matter, and how to avoid hand-wavy findings. Use when auditing AI-built code, reviewing access control against documented permissions, or checking whether a codebase matches its own documentation.
The durable documentation set that makes an AI-built (vibe-coded) app reviewable before shipping. A small core every app needs — architecture, user/permission flows, permissions, variables/secrets, and a test-coverage map — plus conditional docs added only when they apply: emails, scheduled work, SEO, and embedded agents/automation. Defines what each doc must capture and how a reviewer or auditor uses it. Use when documenting a codebase for handoff, mapping user journeys and trust-boundary crossings, planning test coverage, or preparing for a security or performance audit.
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.
Perform cohort analysis on user engagement data — retention curves, feature adoption trends, and segment-level insights. Use when analyzing user retention by cohort, studying feature adoption over time, investigating churn patterns, or identifying engagement trends.
Generate SQL queries from natural language descriptions. Supports BigQuery, PostgreSQL, MySQL, and other dialects. Reads database schemas from uploaded diagrams or documentation. Use when writing SQL, building data reports, exploring databases, or translating business questions into queries.
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD.
Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos.