Tell me about a time you received critical feedback about your work. How did you respond and what did you change?
Model answer
Model answerAfter launching a major feature, a stakeholder gave me harsh feedback that my roadmap prioritization had missed market signals and hurt adoption. My first instinct was to defend my methodology, but I paused. I asked them to walk me through the specific signals I missed and reviewed 6 months of customer feedback I hadn't fully connected. They were right. I adjusted my prioritization framework to include earlier market sensitivity checks and brought them into monthly roadmap reviews. Six months later, the adoption curves of subsequent features improved significantly. The key was hearing the feedback without ego and treating it as valuable input.
Framework · Feedback Receptivity Framework
- LListen Without Defending
Resist the urge to explain or justify immediately - AAsk Clarifying Questions
Understand the specific situations and evidence behind the feedback - IIdentify the Root Insight
Look past the tone and find what's actually true about your approach - CMake Concrete Changes
Don't just acknowledge — actually adjust your process or methodology
Related questions
- Tell me about a time you launched a product that initially underperformed. How did you decide whether to pivot or persevere?
- Describe a time you had to make a product decision that conflicted with what the data showed. What was the outcome?
- Tell me about a time you had to influence a group without direct authority. How did you build consensus?
- Describe a time you had to influence a critical decision where stakeholders had conflicting interests. How did you navigate the politics?
- Tell me about a time you had to deliver a product feature with unclear requirements. How did you handle it?