Behavioral: winning a spot on the roadmap for a feature and seeing it to launch

Walk me through a feature you launched where you had to change how highly it was prioritized. How did you win that priority, and what happened after it shipped? ```hint Show what it was competing with The interviewer needs to see what else wanted the same people and time, who owned the priority call, and what evidence or argument changed their mind. ``` ### Clarifying Questions - Does it have to be a feature I proposed, or can it be one I championed after someone else raised it? - Should the influence be on my own team's roadmap, or can it be on another team's roadmap that my feature depended on? - Is a story acceptable where I secured only a smaller first version rather than the whole feature? ### What a Strong Answer Covers - The starting position: what the feature was, where it sat in the priorities and why, and who made the call - The case the candidate built, with evidence suited to each decision maker, and how the candidate's own view was tested along the way - How the trade-off was handled: what moved down, and how the owners of that work were brought along - What shipped and its measured result, including an honest judgment on whether the priority call was right ### Follow-up Questions - What got pushed down to make room, and how did the people who owned it react? - Was there a moment when you nearly lost the argument, and what did you change? - If the feature had underperformed after launch, what would that have meant for your next prioritization argument?