Behavioral: A Product Launch You Owned That Missed Its Planned Date

Tell me about a product launch you were responsible for that did not ship on the date you had planned. What caused the slip, how did you handle it, and what did you change afterward? ```hint Center the turning point Choose a slip you were accountable for, and build the story around the moment you realized the date was at risk and the choice you made next. ``` ### Clarifying Questions - Should the launch be one where I owned the date as the product manager, or does a slip caused mainly by another team's dependency also work? - Does a launch that kept its date by shipping reduced scope count, or should it be a launch whose date actually moved? - Would you like me to focus on how I handled the slip at the time, or equally on what I changed in later launches? ### What a Strong Answer Covers - A real slip with clear stakes and a plain statement of the candidate's own role and accountability - How and when the risk surfaced, and the options weighed among moving the date, cutting scope, adding people or a phased release - Communication with engineering, leadership, partners and customers: who heard what, when, and with which new plan - The outcome with concrete results, including what the delay cost, and a specific process change applied afterward - Ownership without blaming other teams or individuals ### Follow-up Questions - Looking back, when could you first have known the date was at risk, and which signal did you miss? - Who made the final call between moving the date and cutting scope, and how did you get agreement? - How did the delay affect trust with the stakeholders who were waiting on the launch, and what did you do to rebuild it?