The one conversation most managers avoid and why it costs them everything

Most managers know, usually quite precisely, which conversation they are not having.

There is almost always one. The underperformer who has been underperforming for months. The team member whose attitude is affecting everyone around them. The behaviour that started small and has now become a pattern. The colleague whose work keeps landing on someone else's desk. The person who has been told something once, twice, and is still not doing it.

The conversation is clear in the manager's head. The avoidance of it is taking up significant mental energy. Every week it does not happen, the situation gets a little harder to address.

Why managers avoid it

Avoidance is rarely laziness. It is usually a calculation, often an unconscious one, about what the conversation will cost.

It might damage the relationship. The other person might react badly. There might be conflict, tears, defensiveness. The team dynamic might shift. HR might need to get involved. It will be uncomfortable and the discomfort will linger.

These are real concerns. Difficult conversations are uncomfortable. They do not always go well. The other person's reaction is not fully within your control.

But the alternative is its own cost, and it tends to be higher. Problems that are not addressed directly do not resolve themselves. They calcify. The behaviour continues. The team notices. Other people adjust their own behaviour around it, often picking up slack or walking on eggshells in ways that affect morale and output. The manager's credibility quietly erodes because people can see they are not dealing with something they clearly need to deal with.

Avoidance is not neutral. It is a choice with consequences.

What avoidance looks like in practice

Not all avoidance looks like silence. Some of the most common forms are much more subtle.

Giving feedback so softly wrapped in positive framing that the core message does not land. Addressing the symptom rather than the cause. Having the conversation but not following up when nothing changes. Delegating the issue sideways to HR or a more senior colleague to avoid having to own it directly. Rewriting someone's work rather than talking to them about why it keeps needing to be rewritten.

These are avoidance strategies dressed up as management. They feel more comfortable in the short term. In the long term they achieve the same result as saying nothing.

What the conversation actually requires

The conversations that work tend to have a few things in common.

They are specific. Not "your attitude needs to improve" but a description of a particular behaviour in a particular situation and what effect that behaviour had. Vague feedback gives the other person nowhere to go. Specific feedback gives them something to respond to and, if they are willing, something to change.

They are timely. The longer you wait, the more the conversation carries the weight of everything that has accumulated in the meantime. Addressing something close to when it happened, when both people can recall the specifics clearly, is almost always more productive than addressing it weeks later when it has built into something bigger.

They separate the behaviour from the person. What someone did, what effect it had and what needs to change is a very different conversation from what kind of person you think they are. The first is addressable. The second is just an attack.

They leave room for the other person. The best version of a difficult conversation is not a monologue. Once you have said what you need to say, asking what the other person's experience was, what was going on for them, what they need, often produces information that changes the picture. Not always. But often enough that skipping this step is a mistake.

The conversation you have with yourself first

There is a conversation that needs to happen before the one with your team member, and it is the one you have with yourself.

What outcome do you actually want? Is this about the relationship, about performance, about both? Are you going into this conversation willing to hear something that might shift your view, or have you already decided how it ends?

Managers who go into difficult conversations with the genuine intention of solving a problem together tend to get better outcomes than those who go in to deliver a verdict. The internal starting point shapes almost everything about how the conversation unfolds.

When the conversation goes badly

Sometimes it does. The other person reacts defensively, or denies the problem, or gets upset in a way you were not prepared for.

This does not mean the conversation was a mistake. It means the first conversation was not the last one. Most significant issues require more than one exchange. Progress is rarely linear.

The managers who handle this well are the ones who can stay relatively calm when the other person is not, who can acknowledge the other person's feelings without backing away from what they said, and who can agree to continue the conversation rather than letting it blow up or fizzle out.

That takes practice. Most managers have had very little.

The cost of the conversation you are not having

Whatever the conversation is that you have been putting off, it is already affecting your team. They almost certainly know something is being left unaddressed. They may not know the specifics but they can feel the absence of it in the way things work, or do not work, around them.

Dealing with it does not guarantee an easy outcome. Not dealing with it guarantees a slow one.