Impact Score (1-5)
How much value does this feature add? Consider revenue potential, user satisfaction, strategic importance, and how many users it affects. A feature that solves a critical pain point for most users scores higher than a nice-to-have for a few.
Effort Score (1-5)
How much work does this feature require? Include development time, complexity, dependencies, testing, and maintenance. A simple UI tweak scores low; a major infrastructure change scores high.
Simple mode: Impact / Effort = Priority
Divide impact by effort to get your priority score. Higher scores mean better return on investment. This surfaces your quick wins (high impact, low effort) at the top while pushing time sinks (low impact, high effort) to the bottom. The matrix above plots the same data as four quadrants: quick wins, big bets, fill-ins, and time sinks.
When to use which framework
Impact/effort works well for quick backlog triage: it takes seconds per feature and gets a team aligned fast. RICE adds two more inputs, how many people each feature reaches and how sure you are, which helps when stakeholders disagree about audience size. For the full breakdown with a worked example, see the RICE score calculator.
Best practices for both: score features as a team to reduce individual bias. Revisit scores quarterly as circumstances change. Use scores as input to decisions, not the final word. Strategic features may still win with lower scores.
Every number in these formulas is an estimate. For ongoing prioritization, the strongest signal is actual users telling you what they want. That is what feature voting is for.