← Product Management from Scratch
Lesson
Lesson 4.1 — Why prioritize, and an overview of the frameworks
Understand why prioritization is necessary and recognize the main frameworks — RICE, ICE, Kano, and MoSCoW — and what each is good for.
Why prioritization matters and the four main frameworks
Finite resources, infinite ideas
Every product team faces the same mismatch: there are always more ideas, features, and requests than time or people to build them. Prioritization is the discipline of making trade-offs explicit and defensible — instead of building whatever is loudest or most recent, you decide what matters most and why.
Without a framework, decisions default to whoever shouts loudest (HiPPO — Highest Paid Person's Opinion), or to gut feel that is hard to revisit or explain. A prioritization framework does not replace judgment; it structures the decision so the team can align, communicate the rationale to stakeholders, and revisit choices with new data.
Here are the four frameworks this unit covers. RICE (Reach × Impact × Confidence ÷ Effort) gives a numerical score per feature — useful when you have rough estimates and want to rank a long backlog quickly. ICE (Impact, Confidence, Ease) is a lighter, faster cousin — three factors scored 1–10, summed or averaged — good for early-stage or hackathon-style triage. Kano classifies features by how they affect user satisfaction: Must-be (basics that cause dissatisfaction if absent), Performance (more = better), and Attractive/Delighters (nice surprises that please but are not missed if absent), plus Indifferent and Reverse. MoSCoW (Must-have / Should-have / Could-have / Won't-have) maps features to a specific release, making scope decisions visible.
A practical insight: the same list of ten features can rank very differently depending on which framework you apply, because each one measures something different. RICE rewards broad reach and high confidence; Kano surfaces table-stakes; MoSCoW locks scope to a deadline. Choosing the right lens for the situation is itself a key PM skill.
Lesson notes
Finite resources, infinite ideas
Every product team faces the same mismatch: there are always more ideas, features, and requests than time or people to build them. Prioritization is the discipline of making trade-offs explicit and defensible — instead of building whatever is loudest or most recent, you decide what matters most and why.
Without a framework, decisions default to whoever shouts loudest (HiPPO — Highest Paid Person's Opinion), or to gut feel that is hard to revisit or explain. A prioritization framework does not replace judgment; it structures the decision so the team can align, communicate the rationale to stakeholders, and revisit choices with new data.
Here are the four frameworks this unit covers. RICE (Reach × Impact × Confidence ÷ Effort) gives a numerical score per feature — useful when you have rough estimates and want to rank a long backlog quickly. ICE (Impact, Confidence, Ease) is a lighter, faster cousin — three factors scored 1–10, summed or averaged — good for early-stage or hackathon-style triage. Kano classifies features by how they affect user satisfaction: Must-be (basics that cause dissatisfaction if absent), Performance (more = better), and Attractive/Delighters (nice surprises that please but are not missed if absent), plus Indifferent and Reverse. MoSCoW (Must-have / Should-have / Could-have / Won't-have) maps features to a specific release, making scope decisions visible.
A practical insight: the same list of ten features can rank very differently depending on which framework you apply, because each one measures something different. RICE rewards broad reach and high confidence; Kano surfaces table-stakes; MoSCoW locks scope to a deadline. Choosing the right lens for the situation is itself a key PM skill.