The longer a hard conversation waits, the harder it becomes — and the more the team notices you're avoiding it. - Jeff Hill

Key Takeaway: Deferring a hard conversation does not protect anyone; it erodes trust, raises the stakes, and quietly signals to the whole team what is and is not acceptable.

There is usually one conversation sitting in the back of every leader's week. They know who it is with. They know roughly what it is about. And they have been carrying it for longer than they should. Some version of it is in every team meeting, even when the topic never comes up. It is in the pause before a one-on-one. It is in the way the leader phrases things carefully around a particular person.

I know this because I have been that leader. I have found every reasonable justification for waiting. The timing was not right. Things were busy. The situation might resolve on its own. And maybe it would have been fine to wait one more week, except that one week became three, and by then the conversation was carrying the weight of everything that had happened since.

If any part of this sounds familiar, you are not uniquely conflict-averse. You are human. And you are in good company. But there is something worth sitting with: the conversation you are avoiding is not neutral. It is active. It is doing something to your team, to your relationship with that person, and to you, whether you show up for it or not.

Why Leaders Keep Waiting

The Cost of Waiting.

What most leaders do not fully account for is that delay is a message. When a pattern goes unnamed, the person does not assume you have not noticed. They either assume you are fine with it, or they feel the tension without having any information to work with. Neither outcome serves them. Both make the eventual conversation harder.

The team sees it too. Not always clearly, and not always consciously. But the way a leader handles difficulty sets the tone for what everyone else believes is permissible. If a standard is consistently not enforced, it quietly ceases to be a standard. The team adjusts their understanding of what this place actually values, regardless of what is written in any document or said in any meeting.

None of this is intended as pressure. It is just true. And naming it is more useful than pretending the cost is zero.

---

Clarity and Kindness

Clarity and Kindness Are Both Required.

Here is what I have learned, both from my own experience and from working with leaders through this: most people do not avoid hard conversations because they lack courage. They avoid them because they are not sure how to hold two things at once. They want to be kind. They also want to be clear. And somewhere along the way they picked up the idea that those two things are in tension.

They are not. In fact, the most effective hard conversations I have ever witnessed (or had) were the ones where both were fully present. Clarity without kindness lands as punishment. Kindness without clarity lands as ambiguity. The person walks away feeling good about the conversation but not sure what they are supposed to do differently. That is not a conversation. That is a missed opportunity dressed up as one.

The preparation matters more than most leaders think. Before you walk into the room, get clear on two things: what pattern or behavior are you actually naming, and what do you want the outcome of this conversation to be? Not what you want the person to feel. Not what you want them to admit. What outcome, specifically, are you working toward? When leaders walk in with that clarity, the conversation tends to find its own structure.

The Three Moves That Make It Work.

The conversation itself does not need to be complicated. In practice, it usually comes down to three moves: name the pattern, state the standard, and agree the path forward.

Naming the pattern means saying specifically what you have observed, without generalizing or editorializing. "Over the last three weeks, I have noticed X" is a starting point. Not "you always" or "this is becoming a real problem." Just what you saw, described plainly.

Stating the standard means making explicit what the expectation is. This is the part leaders most often skip because they assume the standard is obvious. It rarely is. Saying it out loud is not condescending. It is respectful. It closes the gap between "I thought they knew" and "they actually know."

Agreeing the path forward is where the conversation stops being about the past and starts being about the future. What does the person need from you? What are they committing to? When will you check back in? This is accountability without punishment. It is both people leaving the room with something to work with.

None of this makes the conversation easy. But it makes it doable. And doable is all you need.

---

Leadership Application

The conversation you have been putting off is probably not as catastrophic as it feels at this point. It has grown in weight the way avoided things do. Once it happens, with clarity and with care, most leaders are surprised by two things: how much shorter it was than they expected, and how much lighter they feel when it is done.

The person on the other end usually feels that too. Not because the message was comfortable, but because someone cared enough to say it directly. That is what the JHC Feedback Culture℠ comes back to again and again: feedback is a gift. The giving of it, done well, is an act of respect.

The week you stop carrying that conversation is a different kind of week. I have seen it many times. It is worth it.

If you are ready to explore what that looks like in your specific context, I would enjoy the conversation. Schedule a call here 👉 30 minute introduction

---

Jeff Hill is a leadership coach and the founder of Jeff Hill Consulting, LLC. He works with leaders in nonprofit and for-profit organizations to build the clarity, systems, and behaviors that make sustained leadership possible.