RICE Will Not Make the Call for You. It Makes You Ask the Question You Are Avoiding.

Say you have ten things sitting in your backlog and no way to do them all at once. Which one goes first? This post is about a simple framework that helps with exactly that call: RICE scoring. But let me say it upfront. The real value of RICE is not the number it hands you. Its value is that it sits you down in front of the questions you have been running from.

Because the real problem in prioritization is not a lack of information. The real problem is a feeling that everyone who builds things knows. An idea lands in your head, and it looks so bright that it dazzles you. “If we add this, everything changes.” A voice inside says “let’s start now,” and your hands are already on the keyboard.

That feeling is innocent on its own. What is dangerous is when it cuts in front of the work that actually matters. Three things the user is genuinely stuck on are sitting right there, and one bright but groundless idea swallows the whole roadmap. A product does not drown in junk. It drowns in the wrong order. Prioritization is the act of pulling up a chair and sitting down across from that bright, loud voice.

RICE does this with four questions. Reach, how many people does it touch. Impact, how much does it change things when it does. Confidence, how sure are you. Effort, what will it cost you. You multiply the first three, divide by effort, and a number is left in your hand. This formula, which came out of Intercom’s product team, looks like a calculator on paper. For the curious, I even wrote a small tool to play with the score, which you can look at here. But the moment you mistake RICE for a calculator, you miss what it is actually for.

”These frameworks are decoration for big companies”

The common belief goes like this: frameworks like RICE exist so that huge product teams can pass the time in meeting rooms. If you are a small team, or even someone working alone, fussing with these tables is a luxury. “I already know what to do, my gut is enough.”

I respect that objection, because it is partly right. Intuition is a real thing, and the intuition of someone who has done a lot of work is not cheap. But the question is set up wrong. It is not “gut or spreadsheet.” It is what your gut is not showing you.

Intuition fails hardest on the thing you want most. When you fall for an idea, your brain becomes that idea’s lawyer, not its judge. What RICE does is call a prosecutor into that courtroom. And a good prosecutor asks the questions you are afraid to answer. Because most of what we call intuition is just an impulse wearing a disguise.

The real work is asking the question, not finding the number

I misread RICE for years. I waited for the score like a prophecy. But each of those four boxes puts a question on the table that you would rather escape.

Reach asks you “how many people, really?” The “everyone wants this” in your head, once you put it into numbers, usually turns into “actually a few hundred, and they use it once a month.”

Impact asks you “what changes when it lands?” Most features, looked at honestly, do not change the user’s day. They only stroke your own “I shipped it” satisfaction.

Confidence is the sneakiest one. “Do you know this, or do you hope it?” If your hand does not shake as you write a high number in that box, either you genuinely have the evidence, or you are fooling yourself. There is not much in between.

Effort is the most honest mirror. Underestimating a task is the national sport of the person doing it. Putting effort into writing breaks the “it will take two days” lie.

As you can see, what is on the table here is not math but confession. What RICE actually gives you is not a score but the obligation to say your assumptions out loud. The number is just the sum of those confessions. There is an old saying that the worth is in the head, not in the crown it wears. The score is the crown, the ornament you show everyone. The real worth is the truth you were forced to tell yourself while filling in those boxes. This is why, when you push a decision through RICE, you usually see the answer before you finish the arithmetic.

Getting ahead of the million-dollar assumption

The most damage comes from the people who speak with the most confidence. I have heard the classic line from an inexperienced product person too many times: “The moment we add this feature, we will make a million dollars.” Under that sentence there is no measured Reach, no calculated Impact, only the sound of an excitement.

That excitement is innocent on its own. What is dangerous is when it cuts in front of the necessary work and pushes a team to spend months polishing something nobody asked for. RICE is made for this moment, because it does not ban the excitement, it just puts it in line. “Fine, your million-dollar idea is on the list too. Now let’s run it through the same four questions.” If the idea is genuinely strong, it comes out strong in the score and nobody can argue. If it is weak, it falls to the bottom of the queue on its own number, without a fight with anyone. You do not make the call, the process does. This also lowers the politics on a team. The argument stops being “whose idea is cooler” and becomes “which assumption is more solid.”

A side benefit is this: RICE often pushes you toward the cheaper path. High Effort drags the score down. So the question “how do I deliver the same value with half the work” comes up on its own. Good prioritization does cost optimization without noticing.

AI Made the Code Cheap, Not the Right Order

Something changed in the last few years. Building software with AI got both cheaper and faster. The distance between imagining a feature and seeing it run has never been this short. It sounds like news that makes prioritization pointless: if everything is this easy, just sit down and build all of it.

The sneaky part is right here. What got cheap is writing a feature. Choosing the right feature did not get cheap, it got more expensive. When production gets easy, the natural brake in front of adding features is lifted, and every bright idea turns into code instantly. Looked at one at a time, each is a few hours, a few tokens. But when they pile up without a plan, those small costs add to each other: tokens spent, context bloated, code no one looks at again, complexity you are forced to carry on your back. As the cost per feature drops, the total cost quietly climbs.

This is exactly why, as the “can I do it” question got cheaper, the “should I do it” question got more valuable. RICE makes you ask that second one. The easier production gets, the more decisive choosing the right order becomes. When the brake is expensive, everyone drives carefully. The real skill is knowing how to slow down when the brake is free.

When No One Is Watching You

I saw this most clearly working alone. As someone who sits on the technical side, project management was never really my job. But when I was building my own things, no one was asking me “is this really a priority.” I was the boss, the developer, and the so-called product manager. And on a team of one, fooling yourself is far easier than on a crowded team. There is no friction holding you back.

RICE stood in for that friction, right there. When I got carried away by an idea, I forced myself to sit in front of those four boxes. Often, because I could not write an honest number in the Confidence box, I gave up on a task that would have eaten weeks before I even started it. What saved me was not the score itself, but the truth I was forced to tell myself while filling in that box.

A small team is not exempt from this method. The opposite. The scarcer your resources, the bigger the price you pay for the wrong order. A big company absorbs a wrong priority, loses a few months, and moves on. In a one-person venture, the wrong priority is a survival question. A working prototype does not make it a product; in the same way, an idea being exciting does not make it a priority. Deciding what comes first is maybe the loneliest part of owning the product.

Do Not Hand the Wheel to a Number

I have defended RICE this far, so now let me trip up my own defense. Because the biggest danger of this method is seeing that it works and trusting it too much.

RICE is a navigation, not a steering wheel. The numbers you write in the four boxes are your guesses, not exact measurements. Confidence especially is the easiest place to inflate, on purpose or not. If you really want to get a task done, you unconsciously bend the other boxes toward that outcome too, and in the end you produce a score that confirms the decision you already made. I call this “the theater of objectivity.” The table looks scientific, but you have filled it with your own bias.

So I never make the score the final word. When the navigation says “turn right,” you do not close your eyes and turn, you first check whether there is a road there. When RICE rejects a decision, I stop and ask too: “Am I wrong, or is the table?” Sometimes the number saves me from my own laziness. Sometimes I sense something the number cannot see and go against the table, but now on purpose, not by accident. The number exists not to hide intuition but to test it. The moment you swap one for the other, RICE turns into one of those bad product managers you have seen, just one hiding behind a table.

What You Are Really Weighing

In the end, what RICE taught me is far older than prioritization. These four boxes look like they are weighing a task, but they are really weighing you: what you actually know, what you are only hoping, which excitement you are hiding behind.

That is why, on a big team and alone, I come back to the same place. Not because I want a calculator. Because I need something that makes lying to myself harder. The score comes out, and I forget it. But the moment I am forced to answer those four questions honestly, I have already made the call.