The Problem With Everything Being Priority 1

Every stakeholder you interact with will believe their request is the most important thing the team should be working on. Sales says the enterprise deal depends on this feature. Marketing says they can't launch without that integration. The CEO saw a competitor demo and wants parity by next sprint.

If everything is priority 1, nothing is priority 1. Your job is to make hard calls with incomplete information, and frameworks help you do that in a way that's defensible and repeatable.

Framework 1: RICE Scoring

RICE stands for Reach, Impact, Confidence, Effort. It produces a numeric score that lets you compare items across different types.

Formula: (Reach × Impact × Confidence) / Effort

• Reach: How many users will this affect per period?
• Impact: How much will it impact those users? (3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal)
• Confidence: How confident are you in your estimates? (100% = high, 80% = medium, 50% = low)
• Effort: How many person-months of work is this?

Example: - Feature A: Reach 500, Impact 2, Confidence 80%, Effort 2 months → Score: 400 - Feature B: Reach 2000, Impact 1, Confidence 50%, Effort 1 month → Score: 1000

Feature B wins. The high reach and low effort outweigh Feature A's higher per-user impact.

Framework 2: ICE Scoring

A lighter version of RICE. Stands for Impact, Confidence, Ease — each scored 1–10, averaged.

ICE is faster and less rigorous than RICE. It's good for early-stage teams or for quickly sorting a long backlog.

Framework 3: The Kano Model

The Kano model categorizes features by how they affect user satisfaction:

• Must-Haves: Features users expect. If absent, they're furious. If present, they're not particularly happy. (e.g., a password reset flow)
• Performance / Linear: The more you have, the happier users are. Linear relationship. (e.g., page load speed)
• Delighters / Attractive: Unexpected features that create delight. Users don't know they want them until they have them. (e.g., Spotify's Discover Weekly)

How to use it: Must-Haves should almost always come first. Delighters are risky without the basics done.

Framework 4: The 2×2 Impact/Effort Matrix

Draw a grid — X-axis: Effort (Low → High), Y-axis: Impact (Low → High):

• High Impact, Low Effort → Quick Wins: Do these first
• High Impact, High Effort → Major Projects: Plan carefully
• Low Impact, Low Effort → Fill-Ins: Do when there's slack
• Low Impact, High Effort → Thankless Tasks: Avoid or eliminate

The Real Secret to Prioritization

Frameworks are not decision machines. They're conversation tools. Their real value is in forcing you and your stakeholders to make your assumptions explicit:

• "You think this will reach 2,000 users? Here's the data that says it's 300."
• "You think this is low effort? Engineering estimates three months."

The framework doesn't make the decision — it structures the argument so the decision is made on the right grounds.

Key Takeaway: RICE and ICE score features quantitatively. The Kano model helps you understand what kind of value a feature creates. The 2×2 matrix helps you move fast on obvious decisions. Use them as conversation tools, not as decision machines.