Scenario Overview

Feedback is one of the most powerful tools a leader has — but it only works when the receiver is open to it. In every IT delivery team, you will eventually encounter a team member who consistently resists feedback. They may interrupt, become defensive, justify every issue, blame others, dismiss observations, or become emotionally upset whenever feedback is shared. This behavior, if unaddressed, blocks personal growth, damages team dynamics, and weakens the leader’s ability to coach the team.

A weak leader avoids giving feedback to such members, hoping things will improve on their own. A reactive leader becomes harsh or escalates quickly. A skilled leader stays calm, separates the behavior from the person, builds psychological safety, adjusts the communication style, and gradually creates a space where even resistant members start accepting and acting on feedback. This scenario teaches you exactly how to lead that transformation.

Typical Real-World Situation

Understanding the Scenario in Depth

Feedback resistance is a behavior pattern — not a character flaw. It usually has deeper roots: past experiences where feedback felt like attack, fear of being judged, perfectionism, ego protection, lack of trust in the giver, or simply not knowing how to receive feedback gracefully. A great leader does not label the person as "difficult." Instead, they investigate the why, adjust their approach, and slowly help the member build a healthier relationship with feedback.

Why This Issue Cannot Be Ignored

Leader’s Core Objectives

Step-by-Step Leadership Approach

Applying the F.A.I.R. Feedback Framework

Sample Conversation – Addressing the Resistance Pattern

Leader: Hi [Name], thanks for joining. I wanted to have an honest, 
respectful conversation with you — and I want to make sure we both 
feel comfortable while doing it.

I genuinely value your technical strength and the contribution you bring 
to this team. So this conversation comes from care, not criticism.

I’ve been noticing a pattern over the last few weeks — 
in code reviews, retros, and our 1:1s, when feedback is shared, 
the response often becomes defensive or dismissive quickly. 
I want to understand it better, from your side first.

Do you feel that feedback in this team is being shared the right way? 
Is there a particular style or moment that feels uncomfortable for you?

(Pause and listen…)

Thank you for sharing. I really appreciate your honesty. 
I want to be transparent — my goal isn’t to "win" a discussion or 
to make you feel wrong. My goal is for both of us to be able to share 
honest input with each other without it feeling personal.

Can we agree on a simple way of working going forward — 
where feedback feels like coaching, not confrontation? 
I’d like to co-create that with you, not impose it.

Sample Conversation – Using F.A.I.R. on a Specific Incident

Leader: I wanted to discuss something specific from yesterday’s code review.

[FACTS]
During the review, when [Reviewer Name] flagged the missing error handling 
in the payment module, the response was, "It’s not a big deal, it works fine."

[ACKNOWLEDGE]
I know you’ve put real effort into that module, and I appreciate the speed 
and ownership you’ve shown.

[IMPACT]
However, when feedback is met with a dismissive response, two things happen:
1. The reviewer hesitates to share input in the future.
2. The team starts feeling that feedback is not safe to give.

[REQUEST]
What I’d like going forward is — even if you disagree, can we pause, 
acknowledge the concern, and discuss it technically? 
Disagreement is welcome. Dismissal is what we need to change.

Sample Conversation – When They Push Back Strongly

Team Member: I’m not being defensive. People just don’t understand 
the context of my work. Their feedback is often wrong.

Leader: I hear you, and I want to acknowledge that sometimes feedback 
can lack full context. That’s a fair point.

At the same time, the team is sharing their honest perspective. 
Even if 50% of the feedback isn’t fully accurate, the other 50% 
could still help you grow.

The challenge isn’t whether feedback is right or wrong. 
The challenge is — when our response always defends, others stop sharing. 
And once they stop sharing, we lose a powerful growth tool.

So instead of debating who is right, can we agree on a simple rule? 
Whenever feedback comes — pause, reflect, ask one clarifying question, 
and then respond. That small habit will change everything for you.

Sample Conversation – When Resistance Is Rooted in Past Experiences

Team Member: Honestly, in my previous team, feedback was used to humiliate me 
in front of others. So I built a wall over time.

Leader: Thank you for sharing that — it takes courage, and it helps me 
understand much better.

I’m really sorry you went through that experience. 
That kind of feedback culture is exactly what I want this team to never become.

In this team, you have my commitment: 
Feedback will be private, respectful, and growth-focused. 
You will never be embarrassed in front of others — that’s a promise.

Let’s rebuild your relationship with feedback at your pace. 
We’ll go slow. I’ll be patient. 
And the moment you feel something is off, you can tell me directly.

Sample Conversation – Boundary-Setting When Behavior Becomes Unprofessional

Leader: I want to be direct with you — with full respect.

There is a clear difference between disagreeing with feedback 
and dismissing the person giving feedback. 
In yesterday’s review, the tone toward [Reviewer Name] was not professional.

I will always create space for honest disagreement. 
But the way feedback is rejected matters as much as the disagreement itself.

Going forward, I expect three things from you in such moments:
1. Acknowledge the input before responding.
2. Use a professional, respectful tone, no matter how technical the disagreement is.
3. Take the discussion offline if it becomes long or emotional.

I’m on your side. But I will hold this standard for everyone in the team — 
including you.

Weak vs Effective Leadership Response

Good vs Bad Communication Examples

Failure vs Success Outcomes

Leadership Principles Demonstrated

Common Root Causes of Feedback Resistance

Action Plan After the Conversation

What a Leader Should NEVER Do

Coaching Tip for Team Leads

Reflection Activity for Learners

Imagine you are the Team Lead. Reflect on the following questions and write down your answers:

1. How would you observe and document feedback resistance patterns over time?
2. What would you check first in your own feedback style before addressing theirs?
3. How would you start the conversation without making them feel attacked?
4. How would you use the F.A.I.R. model on a specific incident?
5. What questions would you ask to uncover the real root cause of resistance?
6. How would you respond if they blame peers or the system instead of reflecting?
7. How would you set boundaries if behavior crosses into unprofessional territory?
8. How would you measure progress over the next 4–6 weeks?

Key Takeaways