Product Improvement: Find a Gap in a Product You Love and Propose One New Capability

Pick a product you like and use often. Point to one capability it lacks today that would make your everyday life simpler, and argue for adding it as if you were the product manager responsible for it. The choice of product is yours; the interviewer wants to see how you move from a real frustration to one well-reasoned feature. ```hint Root cause first Before naming the feature, describe the moment where the product lets you down and why that moment happens. A feature that removes the cause beats one that hides the symptom. ``` ### Clarifying Questions - May the product be physical as well as digital, and should it be one I use regularly so the pain is first-hand? - Should the missing capability be something the current team could build in the near term, or can it depend on new partners or hardware? - Should I weigh the effect on the business and on other parties the product serves, such as sellers or drivers on a marketplace, or focus on my own experience as a user? - Do you want me to estimate how many users share the pain, or is a qualitative case enough? ### What a Strong Answer Covers - A specific product, user segment and moment of friction, described from real use. - A diagnosis of why the friction happens, separating root causes from symptoms. - At least two candidate features compared on user impact, effort and side effects, with one chosen and the choice defended. - A concrete description of how the user would experience the chosen feature. - Success metrics with at least one guardrail for the users or partners who might bear the cost of the change. ### Follow-up Questions - How would you confirm that the feature does not already exist, or was not tried and dropped? - What is the smallest version you could ship to learn whether users want it? - In the experiment your main metric improves but a guardrail moves the wrong way. How do you decide whether to launch?