Describe a situation where you had to prioritize feature requests. What framework did you use to make the decision?
Model answer
Model answerI had 15 feature requests from customers but could only build 3 that quarter. I used an impact-effort matrix: I plotted each request by potential user impact and engineering effort, then prioritized high-impact low-effort features first. I also considered customer concentration risk. I communicated the decision transparently to stakeholders.
Framework · Impact-Effort Matrix
- DDefine Criteria
Establish how you measure impact (user value, business revenue) and effort (engineering time, complexity) - SScore Each Option
Plot each request on the matrix — high impact, low effort is priority - GGather Input
Consult with engineering leadership and customers - MMake Decision
Select items from the high-impact quadrant - CCommunicate
Share the decision rationale with stakeholders
Related questions
- Tell me about a time you had to deliver a product feature with unclear requirements. How did you handle it?
- Tell me about a time when a metric you were tracking didn't match your intuition about product performance. What did you do?
- Describe a time you had to work with a difficult stakeholder or team member. How did you manage the relationship?
- Tell me about a time you had to gather data to support a product decision. What data did you use and how did it change your approach?
- Tell me about a time you launched a product that initially underperformed. How did you decide whether to pivot or persevere?