You have 3 features requested by customers and only 1 sprint. How do you decide?
Model answer
Model answerI'd use a scoring framework, but more importantly I'd make the decision criteria explicit before scoring — not after. RICE works well here: Reach × Impact × Confidence ÷ Effort. But I'd add one question RICE doesn't ask: which feature is most aligned with our current strategic priority? A high-RICE feature that doesn't serve our north star metric this quarter should wait.
Framework · RICE Framework
- RReach
How many users will this affect in a given period? Use real data - IImpact
How much will it move the needle per user? Score 0.25 to 3 - CConfidence
How sure are you about reach and impact estimates? % - EEffort
Person-weeks to build. Include design, QA, PM time — be honest
Related questions
- What is product-market fit and how would you know if you have it?
- How would you communicate a feature delay to stakeholders?
- How do you handle a situation where engineering says a feature is impossible?
- How do you say no to a stakeholder's feature request?
- How would you explain your product roadmap to an engineer who thinks all roadmaps are a waste of time?