ChannelPulse
Prioritisation that survives scrutiny
RICE is not an answer, it is a spreadsheet. This lesson prioritises four real candidates by expected value per engineer-week, shows that the top item's lead is robust while the middle of the list is noise, then handles the parts a scoring framework cannot — opportunity cost, dependencies, the strategic item with no measurable value, and the stakeholder you have to say no to.
What you'll be able to do
- Estimate the value of a candidate project in a unit you can defend, and divide by its cost
- Distinguish a ranking that is robust to estimation error from one that is noise
- Handle the items a score cannot rank — platform work, strategic bets, and compliance
- Say no to a stakeholder in a way that survives the escalation
Before this: metrics-you-can-defend
Log in to read the rest of this lesson
RICE is not an answer, it is a spreadsheet. This lesson prioritises four real candidates by expected value per engineer-week, shows that the top item's lead is robust while the middle of the list is noise, then handles the parts a scoring framework cannot — opportunity cost, dependencies, the strategic item with no measurable value, and the stakeholder you have to say no to. This walkthrough runs about 24 minutes, with runnable code you can edit and re-run as you read. A new account gets 7 days of Pro free, no card required.
Log in to continueThe first module of every track is free to read on the web: see what's open in Product management.