Commit to One Improvement for a Google Product and Defend the Choice

You are interviewing for a product manager role at Google. The interviewer asks: if you could make just one recommendation to improve the product or its experience, what would it be, and why? ```hint Earn the single pick Before you name your recommendation, lay out where it came from: one user segment, its most painful moment in the product, and two or three ways to fix it. One idea is convincing only when the interviewer can see the options you passed over and why. ``` ### Clarifying Questions - Which product does "the product" mean here: the one this interviewer's team owns, or any Google product I choose? - Should the recommendation fix the experience for people who already use the product, or may it aim at a segment the product serves poorly today? - Are you looking for something one team could ship in the near term, or can it be a larger, multi-quarter bet? ### What a Strong Answer Covers - A deliberate choice of product and user segment, with the reason that segment matters to the product's goals - A concrete pain point grounded in how that segment uses the product, checked against what the product already offers - A short set of candidate improvements and an explicit rationale for committing to one (reach, frequency, severity, Google's advantage, effort) - How the recommendation would work, including a small first version - Success metrics with guardrails, and the main risks with mitigations ### Follow-up Questions - The interviewer tells you the feature you proposed already exists. How do you respond, and what does that suggest about the real problem? - How would you validate this recommendation before a team commits engineering time to it? - Six months after launch you may track only one number. Which one, and why?