Every Conversation We Avoid Creates Work Somewhere Else

There is a particular kind of difficult conversation that I hear about all the time.

Except, often, it doesn't begin as a difficult conversation at all.

It begins with a document landing in your inbox later than you expected. Again.

You need it tomorrow, so you stay late to review it.

You make the changes yourself because it will be quicker, send it back edited and ready to go, and quietly add this to your growing list of frustrations. They know you've changed quite a lot, but they don't really know why.

Neither of you says anything.

Next time, it happens again.

Or perhaps there is someone in your team whose work you don't entirely trust, so you start checking it more carefully. Then checking it before it goes anywhere important. Then quietly giving some of the more complex work to somebody else; probably that very reliable person who is consequently becoming even more overloaded.

You talk about your frustration with another manager. Or your manager. Or your partner over dinner. You keep finding ways to make the situation work.

Until eventually it doesn't.

And now you have a difficult conversation.

Except by this point, the conversation isn't really the beginning of the problem. It's somewhere near the end.

Every conversation we avoid creates work somewhere else.

What Are You Working Around?

When we're thinking about difficult conversations, we tend to focus on the conversation itself.

What should I say? How do I raise it? What if they get defensive? What if I upset them? What if this all sounds terribly petty? What if they think I'm micromanaging?

All useful questions.

And before we get anywhere near the words to use, I often want to ask something else:

What are you currently working around?

Because when we haven't talked clearly about something, the issue rarely sits politely in a corner waiting for us. We compensate for it.

We recheck work, edit it ourselves, move tasks around, stay late, become increasingly careful about how we communicate with someone, complain sideways rather than talking directly. Or we catch yet another piece of work from above without saying what will now need to move.

The work has to go somewhere.

You could think of it as a kind of clarity debt. Every time something important stays unclear, somebody carries a little more of the cost. And there can be interest: rework, frustration, confusion, uneven workloads, slowly eroding trust, hours spent thinking about a situation that we aren't actually addressing.

Eventually, a conversation that could have been relatively small has become considerably harder.

Avoidance Doesn't Always Look Like Avoidance

Most managers I work with aren't ignoring things because they don't care. Quite the opposite.

Usually there is a perfectly reasonable explanation.

They've got a lot on at the moment.
I'll follow up when things are quieter.
There are lots of little things, but individually they sound petty.
I don't want them to feel like I'm micromanaging.

Sometimes we're trying to be patient or generous. Sometimes we don't yet know whether something is a one-off or a pattern. And sometimes, if we're honest, we just don't particularly want to have the conversation.

All very human.

I'm not suggesting we pounce on every tiny irritation the moment it occurs. Nobody wants to work for that person.

What I do want is for us to give ourselves permission to name what we're noticing, and then make a conscious choice about how and when we engage with it.

Because there is a lot of leadership territory between saying nothing and calling a formal performance meeting.

We can check in, clarify an expectation, ask what somebody understood, name a pattern we are beginning to notice, talk about how the work is getting done, not only whether it eventually gets done.

Accountability doesn't begin when something has gone badly enough to require a Difficult Conversation. It's built through the ongoing conversations we have about the work.

Sometimes Clarity Is Kinder Than Patience

Avoiding a conversation can feel like the kinder option.

We don't want someone to feel criticised. We know they have a lot going on. We don't want to knock their confidence.

So we protect them from the feedback.

Except I'm not convinced it necessarily feels like protection from the other side.

People notice when something shifts.

They notice their manager checking their work more closely.
Documents come back heavily edited with no explanation.
Certain tasks quietly stop coming their way.
The relationship feels different, but nobody has explained why.

So now they have to fill in the gaps themselves.

I know I'm not doing this properly, but I don't know what I'm meant to do differently.
My manager has lost confidence in me.
I'm probably going to get caught out eventually.

When we withhold useful clarity, we can leave someone alone with the uncertainty. And we take away their opportunity to grow.

There is a cost elsewhere in the team too. When one person isn't delivering and the work keeps quietly moving to the people who are, trust starts to erode there as well.

The reliable people become more reliable, which, in many workplaces, appears to be rewarded with the exciting opportunity to do everybody else's work too.

Meanwhile, the manager is becoming counsellor, buffer, fixer, checker and increasingly frustrated keeper of unfinished work. Eventually their own confidence can start to take a hit: Why can't I get this person performing? Am I actually any good at managing this team?

A conversation we avoid because we're worried about someone else's confidence can quietly start undermining our own.

Is the Expectation Actually Clear?

Let's go back to that document arriving late.

A manager tells me their people always send things through at the last minute. They're staying late to review documents, turning around rushed edits, getting increasingly frustrated that nobody gives them enough time.

So we unpack it.

When have you told them you need it?
What does "enough time" actually mean?
Have you explained how much review time you need before the final deadline?

And sometimes the answer is... not really.

The team knows the final deadline. The manager knows they need the draft two working days before that deadline. Nobody has actually joined those two pieces of information together out loud.

There isn't an agreed expectation being ignored. There is an expectation sitting very clearly inside the manager's head, which isn't quite the same thing.

"I need the first draft with me by Tuesday afternoon, so I have enough time to review it properly before Friday."

That's not much of a Difficult Conversation.

And yet that two-minute clarification might resolve something that has been generating frustration for months.

Sometimes the difficult conversation is simply the small conversation we didn't have six weeks ago.

And this isn't only about conversations with our teams.

Middle managers do exactly the same thing upwards.

Another priority arrives, and we catch it. Something urgent appears, and we move everything around and catch that too. Our manager may have no idea what is happening underneath because, from where they sit, everything keeps getting done.

Until suddenly it doesn't.

The first they hear about the conflict is when we're overwhelmed, furious, depleted, taking leave or wondering whether we can continue in the role. What feels to them like a sudden difficult conversation may actually have been building quietly for months.

We don't necessarily need to dramatically refuse the work. Sometimes we simply need to make the trade-off visible:

"I can pick this up today. It will mean the other piece moves into next week. Are you comfortable with that?"

That's leading upwards. Not complaining, not refusing, not somehow proving ourselves less capable. Just creating clarity about the consequences of the decision.

The first time your manager hears about the workload conflict shouldn't have to be when you're already at breaking point.

Say the Thing Before You Coach the Thing

There is another pattern I see when managers are trying really hard to have these conversations well.

They start with questions. Lots of questions. They're trying to coach, which I love, and sometimes the thing that actually needs to be said still hasn't been said.

If I've noticed something important, I want to start there: name what I'm observing and name the impact. Then I can be curious about the other person's perspective.

Their perspective might change my understanding completely. There may be information I don't have, or I may have misunderstood what happened. Great. That's why this needs to be a conversation rather than a talking-to.

And sometimes their perspective doesn't change the expectation. The work still needs to meet the standard. The behaviour still needs to change. The deadline is still the deadline.

In those situations, I'm not trying to ask enough clever coaching questions that the person eventually guesses what I need them to know.

We've named what needs to change.

Now let's work together on how.

What would help?
What might get in the way?
What will you do differently?
What support do you need?
How will we check progress?

Curiosity isn't a substitute for clarity. Say the thing, then coach the how.

Follow the Work

So perhaps, rather than beginning with Which difficult conversation am I avoiding?, start smaller.

Notice where you're working around something.

What are you repeatedly checking?
What are you fixing yourself?
What are you complaining about to everyone except the person involved?
Where are your most reliable people quietly picking up the cost?
What are you continuing to catch from above without making the trade-offs visible?

Then ask:

What's the cost of this workaround?
Who is actually holding the impact of it?
What's the smallest thing I need to say to bring more clarity to this situation?

Maybe it's naming an expectation, specifying a timeline, explaining the edits you've made, checking whether you've both understood something in the same way, naming a pattern you're beginning to notice, or making a competing priority visible.

Maybe it's simply having the quick conversation while it can still be a quick conversation.

Not every issue requires a difficult conversation.

In fact, that's partly the point.

Many of the difficult conversations we find ourselves having as managers could have been a series of smaller, clearer conversations earlier.

The work will happen somewhere. We get to choose whether some of that work goes into a timely conversation now, or into rework, resentment, confusion and repair later.