Explaining a product roadmap change you owned: what triggered it and how you carried it out

Describe a time a product roadmap you owned had to change course. What drove the change, and what did you do about it? ```hint Make the reason carry the story The interviewer is listening for the evidence that tipped the decision and for what giving up the original plan cost; choose an example where you can name both. ``` ### Clarifying Questions - Should the example be a change you initiated because of new evidence, or can it be one forced on you by leadership, a dependency or a market event? - Is a shift in one quarter's priorities big enough, or are you looking for a change of strategy or a cancelled initiative? - Should the answer include how the change was explained to engineering and to stakeholders or customers who had been promised the original plan? ### What a Strong Answer Covers - The original plan and the reasoning behind it, so the change has something to be measured against. - The specific trigger (customer data, an experiment, a dependency, a business or competitive shift) and how the candidate checked it was real before acting. - The decision itself: the options weighed, what was dropped or delayed, and the candidate's own role in the call. - How the change was communicated and how existing commitments were handled. - A measurable outcome and what the candidate now does differently when planning. ### Follow-up Questions - What did the team lose because of the change, and how did you handle the work that was set aside? - Someone important disagreed with the change. How did you resolve it? - How do you decide when new information justifies changing a roadmap rather than staying the course?