Prioritization Frameworks

A practical reference that walks you through nine prioritization methods with actual formulas and when to use each one. It pushes Opportunity Score (Importance times one minus Satisfaction) for ranking customer problems, ICE for quick initiative scoring, and RICE when you need more granularity at scale. Includes templates for each framework and a comparison table. The core advice is solid: prioritize problems, not features, and don't let customers design solutions. Good for PMs who want to move past gut feel or need to justify their stack rank to stakeholders with something more rigorous than a two by two matrix.

skills.sh installs: 10.2K
GitHub stars: 27.8K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add phuryn/pm-skills --skill prioritization-frameworks --agent claude-code

Installs into .claude/skills of the current project.

Files

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.

When a group scores or ranks items together, collect the votes independently before the discussion, so the most senior opinion doesn't anchor everyone else (the live-polls skill covers dot voting and confidence votes).

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.