Guides
Product

Prioritization frameworks (RICE, ICE), and why the framework is the easy part

A prioritization framework turns a messy backlog into a ranked list by scoring each item on a few factors. RICE and ICE are the common ones, and they're genuinely useful for making tradeoffs explicit. But operators who've made the hard calls say the scoring is the easy part: the real skill is choosing the one thing to commit to and saying no to the rest.

Why this matters. Focus paralysis is the single largest founder theme by volume in our corpus. Its exemplar, "you lack priorities, not information," is the most-liked comment in a 300,000-comment dataset.

Ask Gavel, free

No signup for your first answer. See a real cited response before you decide.

4,593

likes on 'You lack priorities, not information', the single most-liked comment across 300,000 founder-channel comments. The bottleneck is choosing, not scoring.

Alex Hormozi 13 Years Of Brutally Honest Business Advice

The short answer

The scoring frameworks, at a glance

Both turn gut feel into a number you can compare. Use them to make tradeoffs explicit, not to outsource the decision.

  1. 1

    RICE

    Reach times Impact times Confidence, divided by Effort. Best when you have rough data and many competing bets to rank.

  2. 2

    ICE

    Impact times Confidence times Ease. A lighter, faster version for early teams with less data.

  3. 3

    Value vs Effort

    The simplest 2x2: plot each item by value and effort, do the high-value, low-effort ones first. Good for a quick sort.

Every one of these depends on numbers you estimate, so they organize judgment; they don't replace it.

The cited playbook

What operators actually do to prioritize

Score if it helps, but here is what the people who've made the call actually rely on, each linked to the source, each something Gavel applies to your real list.

  1. 1

    Score with a framework to make tradeoffs explicit

    Use ICE or RICE to force a number on Impact, Confidence, and Ease or Effort. The value isn't the ranking itself; it's that scoring surfaces the assumptions you were hiding, so a low-confidence bet stops masquerading as an obvious yes.

    Sean Ellis · Hacking Growth (ICE)
  2. 2

    Remember you lack priorities, not information

    The paralysis is rarely a knowledge gap. Anxiety comes from too many options without a priority, so stop gathering more inputs to feed the scoring model and force a single priority instead. The word is singular for a reason.

    Alex Hormozi · Knowledge and Prioritization
  3. 3

    Find the one constraint and put everything against it

    Every business has one primary constraint that limits growth. Strategy is allocating limited resources against unlimited options, so name the single bottleneck and attack it, instead of spreading effort evenly across a scored list.

    Alex Hormozi · Identifying and Solving Business Constraints
  4. 4

    When you can't decide, build what people already pay for

    If two items score the same, break the tie with revealed demand. Look at what customers already spend money on rather than what they say they'd want, and concentrate there. Money already moving beats a high confidence score.

    Y Combinator · Identifying Promising Startup Ideas

Where experts disagree

Where operators disagree: score it or commit to it?

Sean Ellis

leans on scoring frameworks like ICE to rank a pipeline of experiments, so the team runs the highest-expected-value bets first and compounds learning through volume.

Alex Hormozi

treats elaborate scoring as a way to avoid the hard call. Find the single constraint, commit through a season of saying no, and the ranked backlog mostly takes care of itself.

ChatGPT smooths this into 'use a framework and stay flexible.' Gavel shows you both, so you pick the one that fits your stage and how much data you actually have.

FAQ

Prioritization questions, answered

What is the RICE prioritization framework?

RICE scores each initiative on Reach (how many it affects), Impact (how much), and Confidence (how sure you are), divided by Effort. You rank by the resulting score. It's best when you have several bets and enough rough data to estimate each factor.

RICE vs ICE, what's the difference?

ICE is the lighter version: Impact times Confidence times Ease, with no Reach and no explicit effort denominator. Use ICE when you're early and data is thin, and RICE when reach and effort vary enough across items to matter.

Do prioritization frameworks actually work?

They work as a thinking aid, not an oracle. Because every input is an estimate, the score is only as good as your judgment. Operators use them to expose hidden assumptions, then still make the call on conviction and constraint.

What's the best prioritization framework for a small team?

For a small team with little data, ICE or a simple value-vs-effort 2x2 beats a heavier model. The goal is to force one priority quickly, not to build a spreadsheet you'll maintain instead of shipping.

Can ChatGPT prioritize my roadmap?

It can apply a scoring formula to items you paste in, but it can't see your real constraint, your revenue, or your unfair advantage, so it ranks against the generic average. That context is exactly what Gavel asks for before it answers.

Bring your actual numbers. Get a cited answer you can defend.

Try Gavel free

Keep exploring