What prioritization frameworks should a PM use in interviews?
The most commonly expected frameworks are RICE (Reach, Impact, Confidence, Effort), ICE (Impact, Confidence, Ease), and the Value vs. Effort 2x2 matrix. For strategic prioritization, the Opportunity Scoring and Jobs-to-be-Done frameworks demonstrate more sophisticated thinking. The best answers combine a framework with explicit reasoning about the specific goals and constraints of the situation.
Prioritization is central to the PM role. With limited engineering time, infinite possible features, and competing stakeholder interests, PMs make prioritization decisions daily. Interview questions about prioritization test whether you have a systematic, defensible approach — not whether you arrive at the "correct" answer.
Why Prioritization Questions Are Asked
Interviewers use prioritization questions to assess several PM competencies simultaneously:
- Strategic alignment: Do you prioritize based on goals, or based on who asks loudest?
- Analytical rigor: Do you apply a framework, or do you make gut-feel decisions?
- Stakeholder management: How do you handle competing requests from different stakeholders?
- Communication: Can you explain your prioritization logic clearly to engineering, design, and leadership?
The Core Prioritization Frameworks
RICE Framework
RICE stands for Reach, Impact, Confidence, Effort. Each feature is scored on each dimension and a final RICE score is calculated.
Reach: How many users will this feature affect per time period?
- Measured in users/month or percentage of active users
Impact: How much will this feature move your target metric per user who experiences it?
- Scored: 3 = massive, 2 = high, 1 = medium, 0.5 = low, 0.25 = minimal
Confidence: How confident are you in your Reach and Impact estimates?
- Scored as a percentage: 100% = very confident based on data, 50% = moderate confidence
Effort: How much work is required in person-months?
- Higher effort means lower RICE score
RICE Score = (Reach × Impact × Confidence) / Effort
Higher RICE scores suggest higher priority. This framework is excellent for comparing many features systematically and making the prioritization logic visible and auditable.
ICE Framework
Simpler than RICE and faster to calculate. Each dimension is scored 1-10.
Impact: How much will this move the goal metric? Confidence: How confident are you in the Impact estimate? Ease: How easy is this to implement?
ICE Score = Impact × Confidence × Ease
ICE is better for rapid prioritization in early-stage contexts or when you need a quick first-pass ranking.
Value vs. Effort 2x2
The simplest framework: place each feature on a two-dimensional matrix.
Y-axis: Business/user value (high to low) X-axis: Implementation effort (low to high)
Quadrants:
- High value, low effort: Quick wins — do first
- High value, high effort: Strategic investments — plan carefully
- Low value, low effort: Fill-in work — do if bandwidth exists
- Low value, high effort: Avoid or deprioritize
This framework is excellent for communicating priorities visually to stakeholders who do not want to engage with numerical scoring.
MoSCoW Method
Categorizes requirements by necessity.
- Must have: Non-negotiable for the release
- Should have: Important but not critical
- Could have: Nice to have if time permits
- Won't have (this time): Explicitly out of scope for this release
Useful for release scoping conversations with engineering and for setting clear stakeholder expectations.
Applying Frameworks in Interviews
When Given a List of Features to Prioritize
The question: "You have these five features. Rank them and explain your reasoning."
Approach:
- "Before I rank, I want to clarify what goal we're optimizing for in the current quarter."
- Apply a framework explicitly: "I'll use a quick value vs. effort assessment."
- Score each feature on both dimensions.
- Explain your rankings based on the scores.
- Acknowledge where uncertainty exists.
When Facing Stakeholder Conflict
The question: "Engineering wants to focus on tech debt, sales wants a specific feature for a big deal, and your CEO wants a new initiative. How do you prioritize?"
Approach:
- Understand the business context: what is the current strategy priority?
- Quantify the impact of each request where possible
- Apply a framework to make the comparison explicit
- Make a recommendation with explicit tradeoff acknowledgment
- Communicate the decision and its rationale transparently
"The PM who tells me 'we should do all three sequentially' without explaining the order and reasoning has not answered the question. The PM who says 'given that our Q3 priority is retention, and tech debt is causing user-facing reliability issues, I would prioritize tech debt first because it is causal to our primary metric' has answered it." — VP of Product, SaaS company
Common Prioritization Mistakes in Interviews
| Mistake | Better Approach |
|---|---|
| Prioritizing without clarifying the goal | Always clarify what outcome you are optimizing for |
| Using only one framework dogmatically | Choose the framework that fits the context |
| Ignoring effort entirely | Always consider effort alongside value |
| Treating all stakeholders equally | Prioritize based on strategic alignment, not stakeholder seniority |
| Not acknowledging uncertainty | Be explicit about what you know and what you are assuming |
Frequently Asked Questions
Should I memorize RICE scores or calculate them live in an interview? In an interview context, applying the RICE framework conceptually — acknowledging each dimension and reasoning through relative values — is more impressive than performing arithmetic. Interviewers want to see your thinking, not your calculation speed.
What if two features score identically on the framework? Use secondary criteria to break ties: which aligns better with company strategy, which has higher user research confidence, which has more stakeholders advocating for it, which is on the critical path for another initiative. Document your secondary criteria explicitly.
How do I handle a stakeholder who disagrees with my prioritization? Make the framework visible. "Here is why I scored it this way — here are my assumptions. If you think the impact score should be higher, let me understand why and what data you are basing that on." This moves the conversation from "my opinion vs. your opinion" to "let's evaluate the assumptions."
References
- Cagan, M. (2017). Inspired: How to Create Tech Products Customers Love (2nd ed.). Wiley.
- Patton, J. (2014). User Story Mapping: Discover the Whole Story, Build the Right Product. O'Reilly Media.
- Demarco, T., & Lister, T. (2013). Waltzing with Bears: Managing Risk on Software Projects. Addison-Wesley.
- Kano, N. (1984). Attractive quality and must-be quality. Journal of the Japanese Society for Quality Control, 14(2), 39-48.
- Ulwick, A. W. (2016). Jobs to Be Done: Theory to Practice. Idea Bite Press.