“We should build the thing the CEO mentioned in the hallway.” 

“Sales promised this feature to close the deal.” 

“The loudest customer gets the roadmap priority.” 

Sound familiar? If you’re prioritizing based on the Highest Paid Person’s Opinion (HiPPO) or whoever yells loudest, you’re not managing products—you’re managing chaos. 

Why Most Prioritization Fails 

I’ve watched hundreds of product managers struggle with prioritization. The problem isn’t that they don’t want to make good decisions. It’s that they don’t have a structured way to evaluate options against what actually matters to the business. 

When everything is a priority, nothing is. And when decisions are made based on gut feel or political pressure rather than strategic logic, you end up with a roadmap that serves no one. 

Enter the Decision Matrix 

A decision matrix is a structured technique for rating opportunities against explicit decision criteria. It’s not complicated, but it forces you to be honest about what matters and why. 

Here’s how it works: 

1. Define your decision criteria. What actually matters for this product’s success? Strategic alignment? Revenue potential? Customer impact? Technical feasibility? Market differentiation? Choose 4-6 criteria that reflect your product strategy. 

2. Weight the criteria. Not all criteria matter equally. Strategic alignment might be worth 30% of the decision. Revenue potential might be 25%. Technical feasibility 20%. And so on. Your weights should add up to 100%. 

3. Score each option. Rate each potential feature, project, or opportunity against each criterion on a simple 1-10 scale. Be objective. Use data where you have it. 

4. Calculate weighted scores. Multiply each score by its weight, add them up, and you have a quantifiable comparison. 

Why This Works 

Decision matrices do three things: 

They force strategic clarity. You can’t weight criteria without knowing what your product strategy actually is. This exercise exposes fuzzy thinking fast. 

They make bias visible. When someone argues for their pet feature, ask them to score it against the criteria. Suddenly, the conversation shifts from opinion to evidence. 

They create defensible decisions. When the CEO asks why you’re not building their hallway idea, you can show exactly how it scored against strategic priorities. Data beats gut feel. 

The Real Power 

The matrix isn’t magic. It’s a tool that makes implicit priorities explicit. It won’t make decisions for you—but it will show you what you’re really optimizing for and whether your roadmap actually reflects your strategy. 

Try this: Take your top 10 feature requests. Define 5 decision criteria based on your product strategy. Score them. See what bubbles to the top. 

You might be surprised what deserves to be on your roadmap—and what doesn’t.