Feature prioritization guide

RICE, MoSCoW, Kano: the PM frameworks that make prioritization defensible

Prioritization is the PM's most important job. Learn the most effective frameworks — RICE, MoSCoW, Kano, Impact/Effort — and when to use each.

Why prioritization is hard

It is not a time management problem — it is a people problem.

Every stakeholder thinks their request is the most important.

There is always more to build than time to build it.

Saying no to good ideas is as important as saying yes to great ones.

Prioritization frameworks make this defensible and consistent.

RICE Score

A quantitative scoring model that makes it hard to argue with your prioritization.

Reach × Impact × Confidence ÷ Effort

ReachHow many users does this affect per quarter?

ImpactHow much does this move the target metric? (0.25 = minimal, 0.5 = low, 1 = medium, 2 = high, 3 = massive)

ConfidenceHow confident are you in your estimates? (100% = high, 80% = medium, 50% = low)

EffortHow many person-weeks will this take?

Example

Feature A (Reach: 500, Impact: 2, Confidence: 80%, Effort: 5 weeks) → RICE = (500 × 2 × 0.8) / 5 = 160

Best for: Comparing features across a large backlog with quantitative data.

MoSCoW

A simple labeling system that forces explicit scope decisions before a sprint starts.

Must have

Without this, the product is incomplete or the sprint fails.

Should have

Important but the product/sprint delivers value without it.

Could have

Nice-to-have for later if time allows.

Will not have (this time)

Explicitly deferred — not forgotten.

Best for: Sprint scope decisions, MVP scoping, and stakeholder alignment conversations.

Impact / Effort Matrix (2×2)

Plot features on two axes and the right action in each quadrant becomes obvious.

Quick wins

High Impact + Low Effort

Do first.

Major projects

High Impact + High Effort

Plan carefully.

Fill-ins

Low Impact + Low Effort

Do when capacity allows.

Avoid

Low Impact + High Effort

Question whether to do at all.

Best for: Quick backlog triage when you need speed over precision.

Kano Model

Categorizes features by how they affect user satisfaction — not all features are equal.

Basic needs

Expected features — absence causes dissatisfaction, presence is invisible (e.g. login works).

Performance needs

Linear — more = better (e.g. faster loading).

Delighters

Unexpected features that create excitement (e.g. a feature users did not know they needed).

Best for: Product strategy and understanding which features move user sentiment.

How to choose a framework

The right framework depends on what decision you are trying to make.

RICEUse when: You have data and a large backlog

MoSCoWUse when: Sprint planning and stakeholder alignment

Impact / EffortUse when: Quick decisions and team workshops

KanoUse when: Product strategy and new product decisions

Next steps

Master PM skills in the Product Manager track

Prioritization is one skill in a full PM toolkit. The product manager track covers roadmapping, stakeholder communication, user research, and more.

Explore the PM track