Module 5: Prioritization Frameworks
- Apply the RICE scoring framework to rank features
- Use the Impact/Effort matrix to make quick prioritization calls
- Say no to good ideas that don't serve the current strategy
Every product team has more good ideas than time to build them, so prioritization is one of a PM's most consequential skills. RICE scores each potential feature on Reach (how many users it affects), Impact (how much it helps them), Confidence (how sure you are about the first two), and Effort (how much work it takes), then ranks ideas by (Reach x Impact x Confidence) / Effort, turning a gut-feel debate into a structured comparison. A simpler alternative, the Impact/Effort matrix, plots ideas on two axes to quickly surface "quick wins" (high impact, low effort) and flag "time sinks" (low impact, high effort) worth avoiding. Crucially, this module also covers the harder skill underneath any framework: saying no, clearly and respectfully, to ideas that may be good in isolation but don't serve the current strategy or timeline.
1. On an Impact/Effort matrix, a 'quick win' is typically defined as:
2. In the RICE framework, which factor represents how confident the team is in their Reach and Impact estimates?
3. A core, often underrated skill in prioritization is: