Prioritization Playbook

Play around with the RICE framework to see how different inputs affect feature priority.

RICE Score 0.0

Reach 1000

Impact 2

Confidence 80%

Effort 2

RICE Score 0.0

Reach 5000

Impact 0.5

Confidence 100%

Effort 1

RICE Score 0.0

Reach 2000

Impact 2

Confidence 50%

Effort 4

My Approach

In B2B SaaS, a bad feature wastes engineering resources and can cause you to fall out of product-market fit. That's why I naturally overweight Confidence in my model and carefully tune Effort to avoid deep technical debt. You can have massive Reach, but if your Confidence is low, it's safer to run a painted-door test than ship half-baked code to high-value clients."