Behavioral: Justifying an Unplanned Project Against Committed Roadmap Work

You are interviewing for a product manager role. Describe a project you took on even though it was not part of the planned roadmap. Explain what set it in motion and how you concluded it deserved time that was already promised to other work. ```hint Show the comparison you made The interviewer cares most about how you weighed the unplanned work against commitments already on the roadmap: the evidence you gathered, what you compared it with, and what was pushed out to make room. ``` ### Clarifying Questions - Does the project need to be one I proposed, or does one that came from a customer escalation, a leadership request or an incident also count? - Should I cover what was deprioritized to make room for it and how the owners of that work reacted? - Is a small project, such as a few weeks of one team's time, acceptable as long as it displaced planned work? ### What a Strong Answer Covers - A concrete trigger, such as new data, a customer signal, an incident or a competitor move, and why the work was not on the roadmap originally - An evidence-based decision: sizing the impact or the risk of inaction, estimating the cost, and comparing it with committed work using explicit criteria - The trade-off made, what slipped, and how affected stakeholders were brought along - Execution and a measurable outcome, including whether the bet paid off - What the experience changed about how the candidate handles unplanned requests ### Follow-up Questions - What evidence would have led you to say no to this project? - How did you keep the roadmap from filling up with reactive work afterward? - If the results had come in below expectations, how would you have noticed, and what would you have done?