Day 255 of the Daily · Product Management

RICE

5 min read · 4 principles · apply it by lunch

Nobody in the room is short of opinions about what to build next. What’s scarce is a way to disagree in public.

The question

When your team last settled what to build next, could anyone in that room have said out loud how sure they were — not whether the idea was good, but how much of the case rested on a figure somebody had actually gone and looked up? I’ll give you the answer: nobody was asked, because nothing on the list carried a number anyone could argue with.

The idea

Sean McBride was a product manager at Intercom when the company’s backlog outgrew the arguments it could hold. In 2016 he set out on the Inside Intercom blog the scoring model his team had built from first principles, and RICE has been in general use ever since. It rests on four numbers, written where anyone can see them. Reach is how many people or events the work touches in a stated period, taken from analytics rather than from the room. Impact is how much it moves things for each of them, on a fixed menu running from 3 for massive down to 0.25 for minimal. Confidence is the discount you apply for not knowing — 1.0 when data sits behind the reach, the impact and the effort, 0.8 when it sits behind two of them, 0.5 when all three are informed guesses. Effort is total person-months across every function the work touches. Multiply the first three, divide by the fourth. The dividing is the least interesting part of it, and Day 90’s cost of delay already sequences a queue the same way; reach for that one when the waiting itself has a price, and for RICE when the population is countable but your belief about it isn’t. Where you point it matters as much as how you run it: the opportunity solution tree was right that a mixed feature list can’t be ranked, so this is scoring inside one branch — several solutions to the opportunity you have already chosen, ordered once the choosing is done. What RICE adds is the confidence multiplier, and four written assumptions that the most junior person in the room can dispute by name.

In the Daily · 4 principles and a template

RICE is Day 255 of 365.

In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.

$29 a month · cancel any time · 7-day money-back guarantee

More from Product Management

The next four in the course.

All 22 Product Management frameworks
Day 264 · Product Management

Working Backwards

Your team is building something right now that nobody outside the building has heard of yet — so on the day it ships, when the announcement goes out with the customer named, the problem stated and the reason anyone should care in two plain sentences, will a stranger read that and want the thing, or read a list of capabilities and feel nothing at all?

See the framework →
Day 274 · Product Management

User Story Mapping

Your team has committed to a release next: could one real customer start at the very beginning and get all the way through to the thing they actually came for using only what’s above the line — or does it stop somewhere in the middle, polished at step one and missing entirely at step four? A backlog sorted by priority almost always slices the wrong way.

See the framework →
Day 283 · Product Management

Brooks’s Law

Think about the last project that ran late on you: when the extra people arrived, who stopped doing their own work in order to bring them up to speed, how many weeks went by before the newcomers were producing more than they were consuming, and did anyone put either of those two costs on paper before the decision got made?

See the framework →
Day 293 · Product Management

The Five-User Test

Have you ever sat behind someone who’d never seen your product, handed them a real task and then stayed silent while they failed at it — or is everything you believe about how the thing gets used assembled entirely from your own hands on your own keyboard?

See the framework →