Pushing back on a costly, low-value feature
WHAT IT TESTS: whether you can challenge scope with evidence, not opinion. OUTLINE: estimate cost in engineer-weeks, size the expected value, frame it as cost-per-unit-of-value, then propose a cheap experiment to test the hypothesis first.
WHAT IT TESTS: whether you can turn an engineering gut-feeling into a defensible cost/benefit case and de-risk it before committing. ANSWER OUTLINE: quantify the build cost in engineer-weeks and opportunity cost; estimate the value with the PM using a metric and a reach/impact guess; express the trade-off as cost per expected unit of value so it is comparable to other bets; then propose a cheaper test (fake door, prototype, manual concierge) to validate demand first. RED FLAG: a flat 'no', or building it anyway without surfacing the trade-off.
Read the original → interview
- #product
- #estimation
- #experimentation
- #lean-startup
Get five bites like this every day.
Tezvyn delivers a daily feed of 60-second tech bites with quizzes to lock in what you learn.