Feature Prioritization
Template
Stop guessing what to build. This template combines RICE scoring with customer feedback data to produce a ranked, defensible feature priority list.
Turn customer signals into a ranked priority list
Prioritization is the hardest part of product management. This template gives you a framework that's simple enough to use weekly and rigorous enough to defend to stakeholders.
Feature/idea name
A clear, 3-7 word label. Avoid internal codenames — use language customers would understand.
Reach score (1-10)
How many customers does this affect? 1 = a single user, 10 = your entire customer base. Use actual data, not guesses.
Impact score (1-10)
How much will this move the needle for those customers? 1 = barely noticeable, 10 = transformational change to their workflow.
Confidence score (1-10)
How sure are you about your reach and impact scores? 1 = pure guess, 5 = some customer input, 10 = validated by multiple data sources.
Effort score (1-10)
How much work is this? 1 = hours, 5 = days/weeks, 10 = months. Include design, engineering, testing, and rollout effort.
RICE score
(Reach × Impact × Confidence) / Effort. Higher score = higher priority. Use this as an input to prioritization — not a dictator.
Customer evidence
Link to the specific feedback, votes, and customers requesting this feature. Every score should be traceable to evidence.
Pro tips
Score features independently first, then compare. If you score relative to each other, you'll get anchoring bias.
Re-score quarterly. A feature that was 'Impact 9' last quarter might be 'Impact 5' now because customer needs evolved.
Use the RICE score as a starting point for discussion — not the final answer. Strategic bets might have low RICE scores but high long-term value.
Frequently asked questions
What if I don't have enough data for confidence scores?
Start with low confidence (3-4) and note it. This flags the feature for additional customer research. Over time, your confidence scores should improve as you gather more data.
How do I handle 'must-do' items (security, compliance) that would score low on RICE?
Non-negotiable items (security patches, legal compliance, platform upgrades) bypass the RICE framework entirely. They go on the roadmap regardless of score.
More free templates
Put the template into practice
FeatureSay gives you all the tools to collect, prioritize, and act on feedback. Free to start.
Get started free