**1) One concise, high-authority answer** “I cut a feature that had strong internal support because the data said it would slow our core funnel. Design and sales both wanted it live. Early tests showed higher engagement but worse activation. Shipping it would have made our roadmap look ambitious and our metrics look worse. So we froze it, reallocated two engineers to the funnel fix, and took the internal hit. Three weeks later activation was up 18%. Then we rebuilt the feature in a narrower form and shipped it without harming conversion.” --- **2) The hidden signal this answer sends** “I optimize for business impact over internal harmony, and I’m willing to absorb short-term friction to protect long-term outcomes.” --- **3) One alternative phrasing that signals a different trade-off** “I let a feature ship even though I wasn’t fully convinced by the upside. The team needed momentum, and blocking it would’ve cost trust. I time-boxed it to two weeks, defined a kill metric, and pre-committed to rolling it back if it hurt activation. It did. We pulled it within 48 hours and focused the team on the funnel instead.” *(Signals: bias toward team morale and speed, with guardrails rather than hard vetoes.)* --- **4) Why this answer outperforms typical responses** * It centers the decision on **business risk**, not feelings or process. * It shows a **clear trade-off** (team friction vs. core metrics). * It demonstrates **second-order thinking** (short-term engagement vs. long-term activation). * It avoids consensus theater and positions the PM as the owner of outcomes, not alignment.