The backlog argument, settled with arithmetic. Score every feature on Reach, Impact, Confidence, and Effort — then watch the ranking move as your assumptions change. Preloaded with the kind of ops-platform bets I used to evaluate at BlackRock. Edit them, break them, add your own.
The product thinking behind this tool
- Confidence is the honesty lever. Reach gets inflated, effort gets underestimated — but confidence is where stakeholders smuggle optimism. Making it an explicit input, visible next to the score, is the real feature. That's why the demo invites you to break it.
- Why one editable table, not a form + results page: prioritization is iterative. You don't fill in RICE once — you argue with it. Keeping inputs and ranking on one screen matches the actual workflow: tweak, re-rank, discuss.
- What RICE deliberately ignores: dependencies, strategic bets, regulatory must-dos, and team morale. In practice I'd pair this with a "must-do" lane outside the scoring. A tool that pretends one formula decides everything teaches bad PM habits.
- Grounding in my own work: at BlackRock I ran this logic without the acronym — weighing Aladdin enhancement requests by users affected, STP impact, certainty of the estimate, and engineering cost, then defending the order in front of stakeholders. The write-ups and UAT plans were the deliverables; this is the thinking underneath.
- What I'd measure: forecast accuracy — what share of shipped roadmap came from the top quartile, and how estimated effort compared to actuals. A prioritization tool earns trust when its predictions check out.
Why this is on my portfolio: this is the artifact hiring managers ask about in PM interviews. Now I don't describe how I'd prioritize — I hand them the tool and let them try to break my ranking.