Data PM behavioral: a surprise at work, how you checked it and what you changed

You are interviewing at Disney for a product manager role. Describe a moment in your work as a product manager for data products when something caught you off guard. What was the surprise, and what did you do about it? ```hint Make the response the story Choose a surprise where your first reading of the data, or of how people used a data product, turned out to be wrong or incomplete, and spend most of the answer on how you handled it rather than on the surprise itself. ``` ### Clarifying Questions - Would you like a surprise that turned out well, such as unexpected adoption or an insight, or one that went badly, such as a broken pipeline or a metric that misled a decision? - Should the example come from an internal data platform or analytics product, or from a customer-facing feature powered by data? - How much technical detail do you want about the data issue itself, versus the product and stakeholder decisions that followed? ### What a Strong Answer Covers - A genuine, specific surprise rooted in data or in how a data product was used, with the stakes made clear - How the candidate verified the surprise before acting: data quality, sizing, and ruling out artifacts - Concrete actions with stakeholders, including how uncertainty was communicated and what changed in the plan or product - A measurable result and an honest reflection on what could have been caught earlier - The lasting process, check or mechanism the candidate put in place afterward ### Follow-up Questions - Looking back, which early signal should have warned you, and why did you miss it? - How did you explain the surprise to leaders who had already acted on the earlier picture? - What monitoring or review step did you add so a similar surprise would be caught sooner?