Giving Difficult Feedback
Describe a situation where you had to provide difficult or negative feedback to a high-performing colleague. What was the context and how did you frame the conversation?
Why Interviewers Ask This
Interviewers at Adobe ask this to evaluate your ability to balance high performance with accountability, reflecting their 'Conscious Culture' values. They want to see if you can deliver tough messages without damaging relationships or demotivating top talent. The focus is on your emotional intelligence, courage to address issues directly, and skill in framing feedback as growth rather than criticism.
How to Answer This Question
1. Select a specific scenario involving a high-performer whose behavior threatened team dynamics or project quality, ensuring the stakes were real.
2. Apply the STAR method: Set the Context clearly by describing the employee's usual success versus the specific new issue.
3. Detail the Action using the SBI model (Situation-Behavior-Impact) to describe exactly what happened, how it affected the team, and why it mattered.
4. Explain how you framed the conversation with empathy, acknowledging their past wins before addressing the gap, aligning with Adobe's collaborative spirit.
5. Conclude with the Result, highlighting immediate behavioral changes or long-term improvements, proving the feedback was constructive rather than destructive.
Key Points to Cover
- Demonstrating the ability to separate the person from the problem while maintaining respect for their past contributions
- Using data-driven examples like defect rates or missed deadlines to make the feedback objective rather than subjective
- Showing active listening by inviting the colleague to propose solutions rather than just dictating corrections
- Highlighting a positive outcome where the relationship improved or the team process became stronger after the conversation
- Aligning the feedback style with Adobe's value of being authentic and creating a culture of open communication
Sample Answer
In my previous role, I worked with a senior developer who consistently delivered code ahead of schedule but frequently skipped peer reviews to meet aggressive deadlines. This became critical when a major bug slipped into production due to a lack of oversight, delaying our launch by two days. Although he was a top performer, his individual speed was compromising our collective quality standards.
I requested a private meeting, starting by explicitly acknowledging his exceptional velocity and technical skills. I then transitioned to the specific incident, using the SBI framework: the situation was the production delay, the behavior was bypassing the review process, and the impact was a loss of client trust and team morale. I explained that while speed was valued, reliability was non-negotiable for our engineering culture.
I asked him how we could maintain his efficiency while ensuring compliance with our quality gates. He realized his approach was unsustainable and agreed to a trial period where he would dedicate time for mandatory reviews. Within a month, our defect rate dropped by 40%, and he became an advocate for the review process, mentoring others on balancing speed with quality. This experience reinforced that true high performance requires both output and adherence to shared standards.
Common Mistakes to Avoid
- Focusing too much on the negative behavior without first validating the employee's high performance, which can feel like a personal attack
- Being vague about the specific impact of the behavior, making the feedback seem like a personality clash rather than a business necessity
- Taking a confrontational tone instead of a collaborative one, failing to invite the colleague into the problem-solving process
- Skipping the resolution phase, leaving the interviewer unsure if the difficult conversation actually led to any tangible improvement
Practice This Question with AI
Answer this question orally or via text and get instant AI-powered feedback on your response quality, structure, and delivery.