You Brought a RICE Score. They Brought an Opinion.

The spreadsheet was perfect. You spent hours on it. Every proposed feature was neatly scored on Reach, Impact, Confidence, and Effort. The final RICE score, calculated to a clean decimal, was in column F. You walked into the prioritization meeting feeling like you had brought math to a knife fight.

Then the VP of Sales cleared his throat.

"I don't see the 'ACME Corp' feature on top," he said, ignoring your beautiful grid. "My top salesperson says we'll lose the deal without it. It needs to be number one."

Just like that, your objective framework was steamrolled by a single anecdote. Your data-driven process collapsed into a debate about one customer. The meeting ended with a messy, re-ordered list based on the loudest voice in the room.

Frameworks like RICE are supposed to save us from this. They promise an objective, rational way to make trade-offs. But they have a fatal flaw: a spreadsheet can't argue back. A framework is a tool for structuring a conversation, not a machine for making a decision. When you present a score, you’re presenting a conclusion. Your stakeholders want to be part of the thinking.

The problem isn't the framework. The problem is how you use it. Stop presenting the final score and start pressure-testing the inputs.

Separate the Inputs from the Output

Your RICE score is an output. The R, I, C, and E are inputs. The real conversation, the one that builds alignment, happens at the input level. Before the big meeting, your job is to build a shared understanding of those inputs with your key stakeholders.

Don't just show them the final list. Go to that VP of Sales a day before the meeting.

Don't say: "Here's the prioritized list. The ACME feature scored a 6.8."

Instead, say: "I'm working on our prioritization for Q3. I want to make sure I'm scoring the ACME feature correctly. Right now, I have the Reach estimated at one major customer. Is that right? For Impact, I have it as a major revenue driver for that deal. For Confidence, I'm at 50% because we haven't validated the problem with other enterprise customers. Does that feel right to you?"

This changes everything. You are no longer defending a number. You are inviting them to co-create the inputs. You’re turning their opinion into a variable in your equation. They might tell you the feature would unlock five other similar deals, immediately changing your Reach score. They might give you data that boosts your Confidence. Now, it's their score, too.

Turn Opinions into Trade-offs

When you get into the group meeting and a new opinion emerges, don't treat it as an attack on your spreadsheet. Treat it as a new piece of data about one of the inputs.

When the Head of Marketing says, "We really need to prioritize the re-branding project," use the framework to clarify the trade-off.

Don't say: "But the re-branding project has a low RICE score."

Instead, say: "That's a good flag. In the scoring, we estimated the Impact on new user acquisition as medium. Do you have a different perspective on its impact?" Or, "To prioritize that, it would mean pushing back Project X, which we scored as having a much higher Reach. Are we comfortable with that trade-off?"

This forces the conversation back to the variables. It makes the cost of a decision explicit. You're not shutting