glossary · general
Prioritization product management definition
The act of ordering what to build next against a specific outcome, using evidence and judgment, not just a framework score.
Prioritization is a communication and decision act, not an arithmetic exercise. The output is a defensible rationale that a skeptical engineer, executive, or stakeholder can challenge and you can hold. Every framework (RICE, ICE, MoSCoW, Value-vs-Effort) is a shared vocabulary for that conversation, not a substitute for the judgment behind it. The most common interview failure: a candidate produces a framework score without anchoring to the company’s north-star metric or strategic bet. The number is correct; the answer is wrong.
Frameworks: which one and when
- RICE (Reach x Impact x Confidence / Effort): originated at Intercom. Use when comparing unlike items on one scoreboard: a feature, a reliability investment, and an experiment in the same stack rank. Reach in real units (users/month). Confidence is the most important input: 50% confidence halves the rank and forces you to name what you do not know.
- ICE (Impact x Confidence x Ease): Sean Ellis coined it for growth experiments. Fast enough for weekly triage; not precise enough for high-stakes roadmap decisions.
- MoSCoW (Must / Should / Could / Won’t): from DSDM agile, designed for fixed-timebox releases where you negotiate scope publicly with non-technical stakeholders. The “Won’t” column makes commitments explicit. Poor fit for continuous discovery.
- Value-vs-Effort (2x2): fastest visual alignment tool. Use in discovery workshops to cull obvious no-gos, then switch to a more precise lens before committing capacity.
- WSJF (Weighted Shortest Job First): Cost of Delay / Job Duration. Relevant at enterprise B2B companies running SAFe where delay has a real, quantifiable cost.
Know when to skip the framework. MoSCoW for a time-boxed release: yes. RICE for a one-person startup with three backlog items: no.
The 2026 shift: feasibility is no longer the filter
Prioritization used to include a feasibility screen: you scored items and engineering told you which were realistic. AI has collapsed that constraint. Almost anything is buildable faster than before. The hard work has shifted to two questions: Is this problem viable (will people pay, is the market big enough)? Is the solution lovable (will users integrate it and return without prompting)? A feature users try once and forget is not a win regardless of its RICE score.
For AI-specific backlogs, add a mitigation feasibility gate: if the model is wrong, is the user harmed, and is the harm reversible? High-impact items with irreversible error consequences should wait for guardrails. At OpenAI and Anthropic, interviewers probe whether candidates can separate model-layer from application-layer problems when stack-ranking: reciting RICE without addressing inference cost or error-recovery reads as underprepared.
What clears the bar
weak
"I use RICE scoring. Reach times Impact times Confidence divided by Effort. I'd score each feature and pick the highest number." This treats the framework as the answer. The interviewer has no evidence the candidate can source real inputs, defend assumptions under pressure, or recognize when RICE is the wrong tool. It also skips strategy: a feature can top the RICE chart and still be wrong if it does not advance the current company priority.
strong
"I start with the strategic goal: the metric the team is accountable for this quarter. Which items most directly move it, and what is the cost of each in engineering time, inference cost if it is an AI product, and opportunity cost of what we defer? I reach for RICE to compare unlike items on one scoreboard, MoSCoW when the deadline is fixed and scope is negotiated publicly, Value-vs-Effort for fast discovery alignment. I am explicit about assumptions throughout: what 'impact' means here, how confident I am in the reach estimate, and whether there is a risk floor. For an AI feature, irreversible model error consequences move something off the list regardless of the RICE score. The output is a rationale a skeptical engineer or executive can challenge and I can defend."
The seniority signal: does the candidate start with the item list or with the outcome? Starting with a framework before defining the strategic goal is the clearest tell that someone manages a list rather than shapes a direction.
For the full question and follow-up pressure tests, see how do you prioritize your backlog? and prioritize backlog with two conflicting executives. For individual frameworks, see RICE and MoSCoW. For the viability frame, see feasibility is free.