RICE Scoring and Kano Model
Level 4 · Choosing what goes first
How to rank product ideas with RICE scoring, and how the Kano model sorts features by feeling. When MoSCoW is enough on its own.
Course contentsLesson 9 of 13
Level 1 · The job
Level 2 · Where the product is going
Level 3 · Finding the right problem
Level 4 · Choosing what goes first
Level 5 · Shipping and measuring
After this lesson you can
- Work out a RICE score from four numbers
- Sort features into Kano groups
- Pick a method that fits the choice
14 mincovers 5 glossary entries
Worth reading first: User Feedback and Requests
How RICE and Kano rank ideas
Feature prioritization is deciding which ideas to build first. RICE scoring gives each idea four numbers: reach, impact, confidence and effort. Multiply the first three and divide by effort. An idea that reaches 2,000 users, with impact 2 and confidence 80%, taking 4 person-months, scores 2,000 × 2 × 0.8 ÷ 4 = 800.
Each number has a set scale. Reach is how many people the idea touches in a set time, such as a quarter. Impact runs 3 for massive, 2 for high, 1 for medium, 0.5 for low and 0.25 for minimal. Confidence is 100% for high, 80% for medium and 50% for low. Effort is counted in person-months.
Confidence is the part people skip, and it matters most. It lowers the score of an idea backed by a hunch and no data. It is a polite way to say the exciting idea has no proof yet. RICE came from the product team at a firm that makes chat software for support teams.
The Kano model asks a different question: how will a feature make people feel? Basic features are expected. Having them earns no praise, but missing them makes people angry. Performance features please people more the better they get, like speed. A delighter is a surprise nobody asked for. A Japanese professor of quality set out the model in 1984.
Kano groups drift over time. A delighter today becomes a basic in a few years, once every rival has copied it. Free next-day shipping once surprised shoppers. Now its absence annoys them. So a Kano sort needs redoing every year or so, or it tells you about last year's market.
Some choices do not need numbers at all. MoSCoW sorts a fixed release into must have, should have, could have and won't have this time. It works when the date is fixed and the list is short. RICE suits a long list of rival ideas. Kano suits checking that the basics are covered first.
Every score is an estimate built on guesses. Scores of 800 and 750 are a tie, not a ranking. Use the method to start the talk and to show your reasons, then use judgement. The real win is that everyone argues about the same four numbers instead of whose idea is loudest.
Three ways to choose, side by side
| Method | What it asks | Best for |
|---|---|---|
| RICE scoring | How much value per month of work? | A long list of rival ideas |
| Kano model | How will this make users feel? | Checking the basics are covered |
| MoSCoW | What must ship on this date? | A fixed date and a short list |
Which one to pick
Worked example
Jack scores three ideas
Jack's onboarding tour would reach 3,000 users with impact 1, but his confidence is only 50%. It takes 5 months: 3,000 × 1 × 0.5 ÷ 5 = 300.
Saved carts reaches fewer people, 2,000, but scores 800 because it has impact 2 and 80% confidence. Jack builds saved carts first.
The words for this lesson5
Check yourself
An idea reaches 1,000 users, has impact 3, confidence 50% and takes 2 person-months. What is its RICE score?
Finished this lesson?
Marking it complete also marks its 5 glossary entries learned, which updates your roadmap and your saved page. 0 are already marked.