Prioritisation for Product Managers
Prioritisation is how a product manager chooses what to work on first when time and people are limited. Frameworks such as RICE, MoSCoW, Kano and impact-effort scoring structure the discussion, and roadmaps then communicate the chosen sequence and its reasons to the team and stakeholders.
Stage: Strategy and Prioritisation · Part of the Product Manager roadmap · Last reviewed 19 November 2026
What to learn in Prioritisation
- Score features with RICE using reach, impact, confidence and effort
- Classify requests using MoSCoW and the Kano model
- Build an outcome-based roadmap with themes rather than dates
- Explain a prioritisation decision to a stakeholder who disagrees
- Know the limits of scoring models and when to override them
Prioritisation interview questions
How is the RICE score calculated?
RICE equals reach times impact times confidence, divided by effort. Reach is how many users in a period, impact is a scaled estimate per user, confidence is a percentage and effort is person-time. It ranks ideas but depends on honest inputs.
Why do many teams prefer outcome-based roadmaps over date-based ones?
Dates imply certainty the team rarely has, and a feature list encourages shipping output. A roadmap of problems and goals by now, next and later keeps flexibility, invites discussion of outcomes and avoids broken promises.
Where Prioritisation fits in the Product Manager roadmap
Prioritisation belongs to the Strategy and Prioritisation stage (beginner level), which takes about 4 hours. Decide with clarity.
Other units in this stage
Back to the full Product Manager roadmap