How would you prioritize between three equally important features?

What They’re Really Asking

Can you make tough trade-off decisions using a framework rather than gut feeling?

Strong Sample Answer

When features seem equally important, 'importance' is usually subjective. I move the conversation to objective criteria using the RICE framework (Reach, Impact, Confidence, Effort). First, I quantify 'Reach': how many users does each affect? Second, 'Impact': which drives the core strategic metric (e.g., revenue vs. retention) most? Third, 'Confidence': do we have data backing these estimates, or is it a guess? Finally, 'Effort': what is the engineering cost? Often, two features have high impact but one requires 10x the effort, lowering its priority. If scores remain close, I apply a strategic lens: which feature aligns with our quarterly theme or creates a defensible moat? I also consider dependency; does Feature A unlock Future Feature B? I present this analysis to stakeholders, not as my decision, but as a data-driven recommendation. If still tied, I advocate for the smallest viable experiment to de-risk the biggest assumption. This ensures we deliver value incrementally rather than betting everything on one 'perfect' feature.

Common Mistake to Avoid

Company-Specific Variants