Product Management: Foundations to Practice · Prioritization Frameworks
MoSCoW and Value vs Effort
Not every prioritization decision needs a numeric scoring model. This chapter covers two lightweight alternatives suited to fast, visual, low-overhead prioritization conversations.
MoSCoW sorts requirements into Must have, Should have, Could have, and Won't have this time, a lightweight approach that works well for quickly aligning a team on scope for a single release without the numerical estimation that frameworks like RICE require. It is particularly effective in a time-boxed context, such as scoping what genuinely must ship before a fixed launch date, since it forces an explicit, binary conversation about what is truly non-negotiable versus merely desirable.
Key Takeaways
- MoSCoW forces an explicit must/should/could/won't conversation, well suited to scoping a single fixed-deadline release.
- The Value vs Effort matrix sorts ideas into four quadrants; quick wins, major projects, fill-ins, and ideas to avoid.
- Visual matrices are faster for group discussion; numeric scores like RICE resolve close calls within the same quadrant.
- Match the rigor of the prioritization method to the size of the bet, not apply the same process to every decision.