Prioritization
RICE, value-vs-effort, and the conversation the framework forces.
The short version
The value of a prioritization framework isn't the number it produces — it's the conversation it forces. RICE, value-vs-effort, and weighted scoring all work; what matters is making the trade-offs explicit and shared, so the decision survives the next stakeholder who disagrees with it.
Why it matters
Prioritization is where strategy becomes real. Anyone can list good ideas; the job is sequencing them against finite capacity. A team without a shared method prioritizes by whoever argued last, or loudest.
The framework is a forcing function, not an oracle. Its job is to make you state the inputs — reach, impact, effort, confidence — out loud, where they can be challenged. The score is the artifact; the alignment is the point.
The approach
Common mistakes
Treating the score as truth instead of as a structured opinion.
Ignoring confidence, so a wild guess outranks a sure bet on paper.
Letting effort estimates come from PMs instead of the engineers who will build it.
Never revisiting the list, so it ossifies while reality moves.
In a startup
Lean on speed and learning value. The highest-priority item is often the one that resolves the biggest unknown, not the one with the best ROI on paper.
In an enterprise
Prioritization is partly negotiation across teams with their own goals. The framework gives you a neutral, defensible language for saying no.