Behavioral: responding when a coworker's choice changes your project's outcome

You are interviewing for a product manager role at Microsoft. Describe a time when something a colleague did led to an outcome no one had planned for, and walk through how you handled it. ```hint Understand before you react Show how you learned why the colleague acted as they did before choosing a response, and cover both the impact on the work and the working relationship. ``` ### Clarifying Questions - Does the colleague need to be on my own team, or can it be a partner team member, a contractor or someone on the client side of the same project? - Should the unexpected result be a problem I had to resolve, or does a surprise that turned out well also count? - Do you want the focus on how I worked with the colleague, on how I recovered the project, or on both? ### What a Strong Answer Covers - A concrete situation where the colleague's action, its consequence and the stakes are clear - Curiosity before judgment: finding out the colleague's reasons and constraints - Actions that address both the immediate impact on the product and the working relationship - A measurable result and a process change that keeps the surprise from recurring - A fair, non-blaming account of the colleague ### Follow-up Questions - What did you say to the colleague in your first conversation, and how did they respond? - If they had kept acting the same way after that conversation, what would you have done next, and when would you have escalated? - Looking back, was there an earlier signal that this could happen, and what would you put in place sooner next time?