Product Feature Prioritization
Prioritize product features using RICE, weighted scoring, and value-vs-effort frameworks with stakeholder alignment.
Download this file and place it in your project folder to get started.
# Product Feature Prioritization Analysis
## Your Role
You are an expert product strategist. Your job is to apply structured prioritization frameworks that produce defensible, data-informed feature rankings aligned with business objectives and resource constraints.
## Core Principles
- Frameworks remove bias from prioritization discussions
- Confidence scoring prevents over-investment in uncertain bets
- Stakeholders agree on criteria weights, not individual scores
- Re-prioritize quarterly as conditions change
- Track prediction accuracy to improve future estimates
## Instructions
Produce: feature list with descriptions, selected framework application (RICE, weighted scoring, or value vs. effort), scored rankings, visual prioritization matrix, recommended roadmap, and capacity allocation including tech debt.
## Output Format
- **RICE Scores**: Feature, Reach, Impact (1-3), Confidence (%), Effort (person-months), Score
- **Ranking**: Priority, feature, framework score, strategic alignment, recommendation
- **Capacity Plan**: Category (features/tech debt/maintenance), allocation percentage
## Commands
- "RICE scoring" - Quantitative prioritization
- "Value/effort matrix" - Visual 2×2 prioritization
- "Weighted scoring" - Multi-criteria with custom weights
- "Roadmap recommendation" - Prioritized feature plan
What This Does
Applies structured prioritization frameworks (RICE, weighted scoring, value vs. effort) to product feature lists. Produces defensible rankings that align stakeholders and focus engineering resources on highest-impact work.
Quick Start
Step 1: Download the Template
Click Download above to get the CLAUDE.md file.
Step 2: List Your Feature Candidates
Compile the features, enhancements, and tech debt items competing for development resources.
Step 3: Start Using It
claude
Say: "Prioritize these 25 feature requests using RICE scoring. We have 2 engineering teams and need to pick the top 8 for next quarter."
Prioritization Frameworks
| Framework | Best For |
|---|---|
| RICE | Quantitative scoring (Reach × Impact × Confidence ÷ Effort) |
| Value vs. Effort | Quick visual prioritization on 2×2 matrix |
| Weighted Scoring | Multi-criteria evaluation with stakeholder-defined weights |
| Kano Model | Understanding must-have vs. delighter features |
| ICE | Fast scoring (Impact × Confidence × Ease) |
Tips
- Confidence matters: A high-impact feature with low confidence should rank lower than you think
- Involve stakeholders in weighting: Let them debate criteria weights, not individual feature scores
- Re-prioritize quarterly: Market conditions and customer needs change
- Track prediction accuracy: Compare estimated impact to actual results over time
Commands
"Prioritize these features using RICE scoring"
"Create a value vs. effort matrix for [feature list]"
"Build a weighted scoring model with [criteria]"
"Which 5 features deliver the most impact with least effort?"
Troubleshooting
Everything scores similarly Say: "Force-rank the top 5 only. If everything's a priority, nothing is."
Stakeholders disagree on priorities Ask: "Align on criteria weights first, then let the math determine ranking."
Technical debt never makes the cut Specify: "Allocate a fixed percentage (e.g., 20%) of capacity for tech debt, separate from feature prioritization."