Staying close to users and turning their input into product decisions

How do you engage with your product's users in your day-to-day work as a PM? Describe your approach and give an example of how it changed a product decision. ```hint Trace one case end to end A list of research methods says little on its own. Pick one case and follow it from how you chose whom to talk to, through what you learned, to the decision it changed and what happened next. ``` ### Clarifying Questions - Does the interviewer want your ongoing practice (how often you talk to users, which methods, whom you talk to), one specific story, or both? - Which users are in scope: consumers of the product, business customers and the admins who buy for them, or internal teams using a platform? - Should the answer include people who are hard to reach, such as users who tried the product once and left? ### What a Strong Answer Covers - A concrete, repeatable practice: cadence, methods matched to the question being asked, and how participants are chosen. - How what users say is combined with what usage data shows, so neither decides alone. - One specific example where user input changed scope, priority or design, with a measured outcome. - How engineers and designers hear from users directly, and how users learn what was done with their feedback. - Judgment about when not to build what users ask for. ### Follow-up Questions - Tell me about a request from users that you chose not to build. How did you explain that to them? - How do you make sure you are not hearing only from your loudest or most loyal users? - When interviews and usage data point in different directions, how do you decide which to act on?