By Quick answer: What are the main product prioritization frameworks?
- RICE — (reach × impact × confidence) ÷ effort.
- ICE — impact × confidence × ease, for quick calls.
- MoSCoW — must, should, could, won't, for scoping a release.
- Kano — basics, performance, delighters.
- Value vs effort — a quick visual for workshops.
Key takeaways
- Frameworks make assumptions visible; that's their main value.
- Strategy comes first — score only options that serve your goals.
- Scores are estimates; treat close calls as ties and use judgment.
- Confidence should reflect evidence, not enthusiasm.
- Use one framework consistently rather than switching per meeting.
Every product team has more good ideas than capacity. Prioritization frameworks don't make the choice for you — but they force you to state your assumptions, compare options consistently, and argue about evidence instead of opinions. Here are the ones worth knowing, with worked examples.
RICE
Popularised by Intercom1: Score = (Reach × Impact × Confidence) ÷ Effort.
| Idea | Reach (users/quarter) | Impact (0.25–3) | Confidence | Effort (person-months) | Score |
|---|---|---|---|---|---|
| Faster UPI checkout | 40,000 | 2 | 80% | 2 | 32,000 |
| Dark mode | 60,000 | 0.5 | 90% | 1 | 27,000 |
| Referral programme | 15,000 | 2 | 50% | 3 | 5,000 |
Good for: comparing many backlog items. Blind spot: strategic bets with low reach today.
ICE
Impact × Confidence × Ease, each scored 1–10. Fast and rough — useful for growth experiments.
MoSCoW
From the DSDM agile method: Must, Should, Could, Won't (this time)2. Best for agreeing what's in a specific release or MVP.
Must
Without it, the release fails.
Should
Important, but there's a workaround.
Could
Nice to have if time allows.
Won't (this time)
Explicitly out — prevents scope creep.
Kano model
Developed by Noriaki Kano, it classifies features by how they affect satisfaction3:
| Category | If absent | If present | Example |
|---|---|---|---|
| Basic | Strong dissatisfaction | Taken for granted | Secure login |
| Performance | Dissatisfaction | Satisfaction grows with quality | App speed |
| Delighter | No dissatisfaction | Delight | A thoughtful surprise |
Delighters become basics over time — yesterday's surprise is today's expectation. See the Kano model in the SOA Laws of UX.
Value vs effort
A 2×2 grid: high value / low effort first ("quick wins"), high value / high effort as planned bets, low value / low effort as fillers, low value / high effort avoided. Fast for workshops; easy to fool yourself on "value".
Choosing a framework
| Situation | Use |
|---|---|
| Large backlog of comparable items | RICE |
| Rapid growth experiments | ICE |
| Scoping a release or MVP | MoSCoW |
| Deciding what kind of value to build | Kano |
| Workshop with stakeholders | Value vs effort |
Rules that make any framework work
- Start from strategy and goals; score only relevant options
- Agree scales before scoring
- Require evidence for high impact and confidence
- Treat close scores as ties; decide with judgment
- Revisit scores after launch to calibrate your estimates
Prioritised work feeds your roadmap.
Key terms, defined
RICE — reach, impact, confidence, effort. ICE — impact, confidence, ease. MoSCoW — must, should, could, won't. Kano model — basic, performance and delighter features. Backlog — the list of potential work.
Frequently asked questions
What is the RICE framework?
A scoring method popularised by Intercom: Reach (how many users per period), Impact (effect per user, on a scale), Confidence (how sure you are, as a percentage) and Effort (person-months). Score = (Reach × Impact × Confidence) ÷ Effort.
What is the MoSCoW method?
A scoping technique from the DSDM agile method that sorts requirements into Must have, Should have, Could have and Won't have (this time), often used to agree what goes into a release.
What is the Kano model?
A model developed by Noriaki Kano that classifies features by how they affect satisfaction: basic (expected; absence causes dissatisfaction), performance (more is better) and attractive or delighters (unexpected, cause delight). Features can shift categories over time.
What's the difference between RICE and ICE?
ICE drops reach and replaces effort with ease, making it faster but less precise. RICE is better when reach varies a lot between options.
Which prioritization framework is best?
None is best in all cases. RICE suits backlogs with comparable items; MoSCoW suits release scoping; Kano suits deciding what kind of value to build; value-vs-effort suits quick workshops.
How do I avoid gaming prioritization scores?
Agree scales in advance, require evidence for impact and confidence, review scores as a team, and revisit them after launch to calibrate.
Sources
- Intercom — RICE: simple prioritization for product managers
- ProductPlan — MoSCoW prioritization
- Folding Burritos — The complete guide to the Kano model
- Checked October 23, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Where to go from here
- Product roadmap template — where prioritised work goes
- Kano model in the SOA Laws of UX — the psychology of delight
- Templates & toolsRICE prioritization: the formula, a worked calculator table and how to score features honestlyRICE prioritization explained: the Reach × Impact × Confidence ÷ Effort formula, scoring scales, a worked calculator table for five features and common traps.
- Career guidesProduct prioritisation skills employers want in 2027: RICE, Kano, cost of delay, opportunity cost, impact vs effort, saying no and communicating trade-offsProduct prioritisation skills employers want in 2027: RICE, Kano, cost of delay, opportunity cost, impact vs effort, saying no and explaining trade-offs.
- Templates & toolsCompetitor analysis template: how to analyse rival apps, with a scoring grid and a worked exampleA competitor analysis template for apps and startups: who to include, a scoring grid, UX teardown prompts, review mining and a worked example.
- Product managementProduct sense interview: how to answer "design a product for…" questionsHow to crack product sense interviews: a seven-step framework, a worked Indian example, what interviewers score and the mistakes to avoid.
- Product managementJobs to be done: the framework, job statements, interview questions and Indian examplesThe jobs-to-be-done framework explained: the milkshake story, job statements, functional, emotional and social jobs, switch interviews and Indian examples.
- Startups in IndiaStartup valuation: how to value your startup at pre-seed and seed, with methods and worked examplesHow to value a startup at pre-seed and seed: the methods investors use, a worked VC-method example, dilution maths and India's valuation report rules.
Get the ideas, not the noise.
Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.
Bring evidence to your next roadmap debate.
A behavioral UX audit of your app or SaaS product: why users hesitate, stall and leave, and a prioritized fix list. Fixed price, 2–4 weeks.