Prioritize a Roadmap with Limited Resources

What interviewers evaluate

• Do you anchor prioritization on a goal/strategy, not just stakeholder volume?
• Do you use an explicit framework (RICE, impact vs effort) rather than gut feel?
• Do you account for effort/cost and dependencies, not just upside?
• Do you handle stakeholder management and saying no?
• Do you revisit/sequence rather than treating it as one-and-done?

A framework to structure your answer

1. Align on the goal - what's the quarter's objective (growth, retention, revenue, reducing a risk)? Priorities flow from it.
2. Score with a framework - RICE (Reach × Impact × Confidence ÷ Effort) or a 2x2 of impact vs effort for each feature.
3. Check dependencies & risk - some features unblock others or carry technical/compliance risk that changes ordering.
4. Decide & sequence - pick the top items by score, and sequence (quick wins early to build momentum/learning).
5. Communicate the no - explain to stakeholders why their item didn't make it and when it might.

Try structuring your own answer first, then reveal a strong worked example.

Common variants

• How do you say no to a senior stakeholder's pet feature?
• Walk me through how you'd build next quarter's roadmap.
• Two features have equal impact - how do you break the tie?

Pitfalls to avoid

• Prioritizing by who asked (HiPPO) instead of by goal-driven impact.
• Considering only upside and ignoring effort and dependencies.
• Using no explicit framework - 'I'd just pick the important ones.'
• Not addressing stakeholder communication / saying no.
• Treating it as permanent rather than sequenced and revisitable.

Likely follow-ups

• The CEO insists on the feature your framework ranked last. What do you do?
• How do you estimate Impact when you have no data yet?
• When would you deliberately build a low-RICE feature anyway?