← All questions
Metricsstandard
Engineering can either cut app load time in half or build the top-requested feature this quarter. How do you choose?
How to approach it
Estimate the impact of each on the same metric, so you are comparing like with like rather than gut feel.
How a strong answer opens
“To compare these fairly, I'd estimate both on the same metric, probably retention, using past data for speed and request data for the feature.”
Outline of a strong answer
Try answering out loud for a few minutes before you open this.
- Pick a common goal metric, such as retention
- Estimate impact of faster load time using past data
- Estimate impact of the feature: who asked, how many, how often
- Compare cost, risk and time to value
- Consider whether one can be split into smaller parts
- Make the call and say what would change your mind
Where this question usually goes wrong
Choosing by gut feel or by whoever asks loudest instead of estimating both options' impact on one common metric.
Learn the method
Making trade-off decisions in Module 2, Metrics and execution.
The full kit has worked answers in full, start to finish, for every round type. $129 once.
More metrics questions
- A feature increases engagement but also increases reports of harassment. Do you keep it?
- Ads revenue would rise 5% if you added one more ad to the feed. Should you?
- Notifications drive 30% of daily opens, but the uninstall rate is rising. What do you do?
- A feature in your app is used by only 2% of users. What would you look at before deciding to remove it?
- Which would you rather increase for a dating app: matches or conversations? Why?