Behavioral: Walking Away from a Feature You Had Invested Real Work In

In a product manager behavioral interview, you are asked to describe a feature you had put real work into and then had to abandon, whether you made that call yourself or it was made above you. Answer with one real situation. The interviewer wants to hear why the feature was dropped, what you did, how you brought the team and stakeholders along, and what happened afterward. ```hint Make the decision the story Pick a case where you can explain the evidence that made stopping the right call and your part in acting on it. The feature matters less than how you recognized the signal, weighed the effort already spent, and communicated the decision. ``` ### Clarifying Questions - Does it matter whether I made the decision to stop the feature or someone above me did? - Can the feature have been cut before launch, or should it be one that shipped and was later removed? - Should the story come from a product manager role, or is an earlier role acceptable? ### What a Strong Answer Covers - The evidence or change that made stopping right: data, customer feedback, a strategy shift, or cost - The candidate's own role in spotting the signal and making or backing the call, including the pull of effort already spent - How the team, stakeholders and any affected customers were told and supported - What was salvaged (learnings, reusable work, redirected effort) and the measurable outcome - What the candidate now does earlier, such as setting stop criteria before building ### Follow-up Questions - Looking back, could you have stopped sooner? Which signal did you miss or discount? - How did the engineers who built it react, and what did you do about it? - What did you do about customers who had been promised the feature or were already using it?