Google PM Behavioral: A Product Call Made on Incomplete Data

In a product manager interview at Google, you are asked to describe a product decision you made using data at a time when much of the information you wanted was missing or unreliable. Answer with one real example. The interviewer expects to hear what was at stake, which data you had and what was missing, how you reasoned from partial evidence, what you decided, and what happened afterward. ```hint Make the gap explicit Be ready to name the specific information you lacked, why waiting for it would have been costly, and what you did to limit the damage if your call turned out wrong. ``` ### Clarifying Questions - Does "limited information" mean too little data, such as a new product or a small sample, or data that was noisy, conflicting or missing a key measurement? - Should it be a decision I made and owned, or can it be a recommendation that a leader approved? - Is a decision that turned out wrong acceptable if I can show how I caught and corrected it? ### What a Strong Answer Covers - A decision with real stakes and a clear reason it could not wait for complete data - An honest inventory of the data available and missing, and how each piece shaped the decision - Cheap ways of reducing uncertainty, such as proxies, small tests or qualitative signals, and an explicit statement of the risk accepted - A staged or reversible decision with signals defined in advance for changing course - A measured outcome and what the candidate would repeat or do differently ### Follow-up Questions - Which missing data point, had you had it, would most likely have changed your decision? - How did you persuade stakeholders who wanted to wait for more data? - What would you have done if the first signals after launch had pointed the other way?