The Conversation You Keep Postponing
What I learned from delaying difficult feedback, then delivering it so objectively that I lost the humanity the conversation needed.
The feedback conversation I kept postponing
YouTubeThis article is inspired by real workplace and leadership experiences. I do not use real names, company names or identifying details. Roles, teams, organisational structures, projects and business context may be removed, generalised or combined to protect the people and organisations involved while preserving the underlying leadership reflection. Where conversations are referenced, wording may be edited for clarity and anonymity.
When a strength casts a shadow
There was a conversation I knew I needed to have with one of the strongest performers on a team. The difficult part was that almost every conventional measure told me they were doing well. Their work was strong. They were experienced, dependable and highly regarded. If you looked at their performance in isolation, there was not an obvious performance problem to address.
But I had started hearing something very different from the people working around them. Colleagues described feeling spoken over. Decisions were often taken out of their hands. Problems they might have worked through themselves were solved for them. What one person experienced as helping, protecting and making sure the work succeeded, others experienced as being given less room to think. They were becoming dependent on the strongest person in the group.
That created an uncomfortable leadership problem because I did not think the behaviour came from a bad place. Quite the opposite. I think this person genuinely cared about the people around them. If someone was struggling, they stepped in. If they could see a better answer, they gave it. If something looked as though it might go wrong, they tried to prevent that from happening.
From their perspective, that probably looked like leadership. From the other side, it increasingly felt like a ceiling. People could complete their work, but they were not always being given enough room to build the judgement that would eventually allow them to work without that protection. The same behaviour was being experienced in two completely different ways.
That distinction has stayed with me because I think leadership conversations become much harder when somebody's intent is good. It is relatively easy to challenge behaviour that everybody agrees is inappropriate. It is much more difficult when the behaviour is coming from characteristics that have probably contributed to someone's success: high standards, experience, confidence, care, urgency and a willingness to take responsibility.
The conversation I avoided
I struggled with what to do. Part of that hesitation was because I knew some of the feedback was subjective. There is a fine line between addressing behaviour that genuinely damages a team and penalising someone because their personality is stronger than the people around them. I did not want to confuse discomfort with dysfunction.
I also knew this person had received a lot of positive feedback historically. Some of the people now raising concerns had never said any of this directly to them. They were uncomfortable doing so, which left me holding feedback that would probably come as a surprise.
For a while, I hoped the situation might correct itself. Perhaps they would notice that people were becoming too reliant on them. Perhaps somebody would challenge them. Perhaps they would eventually recognise that constantly helping could have an unintended consequence.
That was an attractive idea because it allowed me to delay an uncomfortable conversation without feeling as though I was avoiding it. I could call it patience. In hindsight, I think some of it was avoidance.
The more I watched, the more I came back to a fairly simple question. What is the value of having one exceptional performer if their success prevents several other capable people from becoming better?
That did not make the individual less talented. It changed the level at which I needed to judge their impact. As an individual contributor, solving the problem might be exactly what success looks like. As your influence grows, that calculation becomes more complicated. Eventually, being the person who can solve everything can become part of the problem if everybody else stops learning how.
I have wrestled with versions of that problem in my own leadership as well. Earlier in my management career, being able to step in felt useful. If I could prevent someone from making a mistake, give them the answer or get something over the line more quickly, why wouldn't I?
The answer, which took me longer than it probably should have, is that efficiency and development sometimes pull in opposite directions. Sometimes the slower route today creates a much stronger team tomorrow.
Being right was not enough
Eventually, I decided I had to have the conversation. And then I made a different mistake. I became so determined to be fair that I became almost robotic.
I wanted to remove emotion from the conversation. I did not want to expose the colleagues who had spoken to me. I did not want it to feel like gossip or a collection of personal complaints. I wanted to stick to observable themes and explain the feedback as objectively as I could.
So that is what I did. I went straight at it. The message, stripped down, was that although their individual performance was strong, the way they were operating was having a negative effect on the development and autonomy of people around them.
It did not land well. Not slightly badly. Terribly.
The response was deeply emotional. I was told, among other things, that I was uncaring and dishonest. The person felt betrayed. From their perspective, they had spent a long time helping people, protecting them and making sure things succeeded, only to suddenly be told that those same actions were causing harm.
I had prepared myself to deliver difficult feedback. I had not prepared the other person to receive it. That difference matters.
For a while afterwards, I focused heavily on whether the feedback itself had been correct. I still believe it was a conversation I needed to have. I still believe there is a point at which the performance of one person cannot be assessed separately from what happens to everybody around them. But being right about the need for a conversation does not make you right about the way you conduct it. That was the part I had to examine.
What I would do differently
In trying not to make the conversation personal, I had removed too much of the context that would have helped explain why I was having it. I should have made the larger picture clearer.
I should have acknowledged much more explicitly that the behaviour I was challenging was connected to qualities I valued in them. Their instinct to protect people was not inherently wrong. Their standards were not the problem. Their willingness to help was not something I wanted them to lose. The issue was that a strength was beginning to cast a shadow. And I should have explained that distinction.
I also relied too heavily on the sentiment I had received from others instead of owning enough of the conclusion myself. There is an important difference between saying, "People are telling me that you do this," and saying, "I have heard this feedback, I have considered it carefully, and here is what I am also seeing."
A leader cannot outsource difficult feedback to an invisible group. Protecting confidentiality matters, but if I am going to bring something into a performance conversation, I have to take responsibility for my own judgement too. Otherwise, the person is effectively arguing with a room of people they cannot see.
I think I also underestimated how destabilising the feedback would be because it challenged something deeper than behaviour. It challenged identity. This was somebody who believed that caring for people was one of the things they did well. I was telling them that some of the behaviour they associated with caring was being experienced by others as restrictive. That is a very different conversation from telling someone to improve a technical skill or hit a deadline.
If I were having the conversation again, I would still be candid. Probably just as candid. But I would not confuse candour with emotional neutrality.
I would start by establishing the contradiction. I would explain that somebody can be an exceptional performer and still unintentionally reduce the performance of the system around them. I would acknowledge that the behaviour may have come from a genuine desire to help. Then I would explain that intent does not remove impact, and that part of becoming more influential is learning to recognise when a strength needs to change shape.
I would probably share more of my own experience too. There have been moments in my career where I have had to learn that being able to solve something does not necessarily mean I should solve it. There are times when giving somebody the answer feels supportive but taking the answer away from them is what actually creates growth.
That lesson is uncomfortable because it requires you to redefine usefulness. You stop measuring your contribution by how many problems you personally fix and start paying attention to how capable people become when you are not there. For a high performer, that can feel like being asked to care less. It isn't. It is learning to care differently.
I would also give the person more opportunity to process what they were hearing rather than expecting an immediate rational response. Difficult feedback can be factual and still hurt. A person can disagree with it, become defensive or react emotionally without that automatically invalidating the underlying issue.
That does not mean avoiding the conversation. It means understanding the weight of what you are putting on the table.
Holding care and challenge together
This experience changed the way I think about empathy in difficult conversations. I used to think there was a risk that too much empathy would weaken the message. You soften it, surround it with reassurance and eventually the person leaves without understanding what you were actually trying to say. That absolutely can happen.
But there is another failure mode. You can become so focused on being clear, factual and defensible that the person on the other side stops feeling like a person.
The standard I am trying to hold now is different. Being clear because you care. That means not hiding something somebody needs to hear simply because the conversation will be unpleasant. But it also means recognising that delivering a difficult truth is not the same as dropping evidence onto a table.
Care and challenge are not opposites. The harder part of leadership is holding both at the same time.
A different measure of performance
There was another lesson in this situation that I have thought about a lot since. We often celebrate the "rockstar" in a team. The person everybody calls when something is difficult. The person who knows the answer. The person who can rescue the situation when things start going wrong. Those people can be enormously valuable.
But leadership requires us to look beyond their output. If one person's excellence creates dependency around them, we have to be willing to ask a harder question about what high performance actually means.
I would rather have a team in which several people are becoming stronger than one person whose brilliance keeps everybody else permanently average. That does not mean diminishing the exceptional person. It means asking something more of them.
The next stage of their contribution may not be solving more problems. It may be creating the space in which other people learn to solve them. And sometimes the conversation a leader keeps postponing is precisely the one that helps somebody make that transition.
Looking back, I do not regret having the conversation. I regret waiting for the problem to somehow explain itself. And I regret believing that the fairest way to deliver difficult feedback was to remove myself emotionally from it.
I would approach it differently now. I would still tell the truth. I would just do more to help the person understand why I believed they were capable of hearing it, what strength I was asking them to evolve, and why the conversation mattered enough that avoiding it would have been the less caring choice.
Continue exploring
- Article
When Good Relationships Get in the Way of Good Leadership - AI Skill
Difficult Conversation Prep - Free resource
The thing you're not saying
