Behavioral: Turning User Feedback Into a Shipped App Improvement

You are interviewing for a product manager role at Apple. Describe a specific time when what users told you about an app you were responsible for led you to change it. Walk through how the feedback reached you, how you decided what was worth acting on, what you changed, and what happened afterward. ```hint Show the judgment behind the change The interviewer cares less about the fix than about how you got there. Explain how you confirmed the feedback reflected a real and widespread problem, why you acted on some requests and not others, and bring a number that shows the result. ``` ### Clarifying Questions - Does the example need to involve a mobile app, or does any software product you owned count? - Should the feedback come directly from users (reviews, support tickets, interviews, beta testers), or can it include usage data that revealed a problem? - Should I focus on one change, or can the story cover several fixes that came out of the same round of feedback? ### What a Strong Answer Covers - A specific situation with clear stakes, and your own role and decisions kept separate from the team's. - How the feedback was gathered, and how it was checked against other evidence before acting. - A clear rationale for what to change and what not to change. - The change itself, how it shipped, and how users learned that their feedback had been acted on. - A measured result and a lesson that has shaped how you handle feedback since. ### Follow-up Questions - Tell me about feedback you chose not to act on. How did you explain that decision, and to whom? - What would you have done if the loudest feedback contradicted what your usage data showed? - How did you make sure the same problem did not return in later releases?