The Conversation You’re Avoiding Is Already Affecting the Work

How to have difficult conversations with your boss, your peers, and the people you lead before avoidance becomes the larger problem.

You know which conversation you need to have.

You noticed the problem a few weeks ago, perhaps longer. Since then, you have rehearsed the conversation in the car, decided the timing was wrong, and found small ways to keep the work moving without addressing it. You rewrite the document yourself. You leave someone off an email because including them will slow things down. You schedule around a colleague instead of asking them to change how they work.

For a while, this can look like patience. The work still gets done, nobody becomes defensive, and the relationship stays pleasant. But really, you are adding to the problem and beginning to carry more of it yourself. You take on work that belongs to someone else. You lower an expectation without saying that it changed. Eventually, you start resenting someone who may not know there is a problem.

The conversation is already affecting the relationship and the work. Avoiding it only means that the other person is not participating in what happens next.

This article explains why leaders avoid difficult conversations, the mistakes they make when giving feedback, and how the conversation needs to change depending on whether you are speaking to your boss, a peer, or someone you lead.

Why leaders avoid difficult conversations at work

Most leaders do not avoid these conversations because they lack courage. They are usually trying to protect something.

You may be protecting a relationship that matters to you. You may know the other person is already under pressure and not want to add to it. You may be concerned that the conversation will become emotional, particularly when there is history between you. Sometimes you are protecting yourself from the possibility that the person will disagree, become angry, or force you to make a decision you would rather delay.

Avoidance works in the short term. Nobody gets upset today, and you leave the meeting without the discomfort you were anticipating.

The cost becomes visible later. You begin doing more of the work yourself. Standards change without being discussed. Projects take longer because the process has been built around one person’s behavior. Your frustration starts coming through in meetings, even though you have never explained what is causing it.

That is usually when the relationship becomes harder to repair. The other person can tell that something has changed, but they have not been given enough information to address it. You start acting differently toward them because you feel differently, and the relationship changes even without the conversation.

Having the conversation earlier gives both of you more options.

The common mistakes leaders make when giving feedback

The first mistake is waiting for the right time.

You tell yourself that you will raise the issue after the deadline, when the person is under less pressure, or when you have another example to confirm the pattern. Sometimes a short delay is reasonable. More often, you are waiting for the conversation to feel easier, and it will not.

The longer you wait, the less likely you are to discuss only what happened. By then you have accumulated frustration, made assumptions about why the person behaved that way, and changed how you work around them. A conversation that could have addressed one problem now has to carry several weeks of resentment with it.

The second mistake is making the feedback about the person.

“You are not paying attention” is a conclusion about someone’s character. “The presentation came back with errors after the first review” describes something the person can examine and correct.

You may believe the character judgment. It still does not help you understand what produced the result. The person may lack a review process. They may not understand the standard. The work may have been delegated to someone you did not know was involved. They may also be careless, but you will learn more by beginning with what happened than by telling them who you think they are.

The third mistake is correcting the work yourself.

One of my clients hired an architect who sent him a presentation with several errors, including the company’s name spelled incorrectly. My client pointed out the mistakes. The architect apologized, corrected some of them, and returned a presentation that still contained errors.

My client corrected the document himself.

That resolved the immediate problem, but it changed his role in the relationship. He became the quality-control process for someone he was paying to provide completed work. It also left him wondering what else the architect might be missing that he could not see.

Before joining his family’s business, another client worked for a company that hired outside consultants to build financial models. The models repeatedly came back with errors. He corrected them quietly because raising the issue felt like creating unnecessary conflict.

Eventually, his CEO pulled him aside and told him, “You need to be harder on these people. Their work is making you look bad.”

My client believed he had contained the problem. His CEO saw the repeated errors as evidence of his judgment, standards, and ability to manage the engagement.

When you repeatedly absorb someone else’s work, the correction may be invisible, but the result is not. Other people see the missed deadline, the weak document, or the incorrect analysis and assume you accepted the standard.

The fourth mistake is giving feedback without reaching an agreement.

You explain what went wrong. The other person apologizes. Both of you leave relieved that the conversation is over, but neither of you has said what will happen differently.

An apology may repair the moment. It does not change the process that produced the problem. Without a specific agreement, the next mistake begins the same conversation again.

The fifth mistake is treating unclear direction as a performance problem.

A founder I coached gave two junior employees an instruction the same way he would have given it to someone with thirty years of experience. They followed what they understood, and confidential material was distributed to far more people than the founder intended.

The employees had not ignored the instruction. The founder had assumed knowledge they did not have, and neither side stopped to confirm the purpose, audience, or limits of the assignment.

Before holding someone accountable for missing an expectation, make sure the expectation was clear enough to meet.

How to give feedback that produces a change

Begin with the specific work, decision, or behavior you need to address. Describe what happened without adding a conclusion about the person’s intent.

“The presentation came back with errors after the first review” gives you somewhere to begin.

“You do not care about the quality of your work” gives the other person something to defend.

Then explain the effect. The error may have delayed a decision, created work for someone else, damaged a customer relationship, or increased risk for the company. This is often the part leaders leave out, which means the other person hears criticism without understanding why the issue matters.

Have the conversation privately. Public feedback introduces embarrassment and turns part of the person’s attention toward how they appear in front of everyone else. If the goal is understanding and correction, give them the room to respond without an audience.

Ask what happened from their perspective. You know the result, but you may not know how it was produced. Listening helps you determine whether the problem came from unclear expectations, a weak process, insufficient skill, a lack of attention, or an unwillingness to do the work.

Once you understand the cause, agree on what will happen differently.

“We’ll be more careful” is not specific enough to evaluate later.

“The project lead will complete a second review before anything is sent to the client” is.

The commitment matters because it gives the next conversation a different starting point. If the problem happens again, you are no longer introducing the issue for the second or third time. You are discussing an agreement the person made and determining why it did not happen.

Finally, make sure the person has a reasonable way to meet the expectation. That may require clearer ownership, training, a checklist, another reviewer, or a different deadline. Support does not remove accountability. It makes the standard possible to meet.

The structure is straightforward: describe what happened, explain the effect, ask for their perspective, agree on what changes, and make sure they can follow through.

What changes is how you use that structure with people who have different relationships to your authority.

How the conversation changes with your boss, a peer, or an employee

Having a difficult conversation with your boss or business partner

When the other person has more authority than you, you cannot simply set an expectation and hold them to it. You can explain what their behavior is producing, make a direct request, and reach an agreement about what happens next.

I work with a leader whose business partner does not use the company’s software. He did not refuse to learn it. He had avoided it long enough that starting now felt embarrassing.

The company gradually reorganized around him. Documents were printed because he did not work inside the shared files. His edits remained in email threads. He could not see the shared calendar, so meetings were scheduled over one another. The leader working beside him spent several hours each week reconciling information that everyone else could access immediately.

This continued for four months without either person asking the direct question.

The frustration still became visible. It appeared in the leader’s tone during meetings, in comments about the technology, and in the way he responded when another scheduling problem occurred. His partner could feel the frustration but did not know exactly what was being asked of him.

The conversation needed to begin with the consequences.

“The documents are being recreated in several places. Meetings are being scheduled over one another. I am spending three hours each week reconciling information. Would you be willing to start using the system with the rest of us?”

If the answer is yes, they can agree on the support required to make the change.

If the answer is no, they still need to decide how the company will operate. Information may arrive later. Files may not be available on demand. Scheduling conflicts will continue unless another process is created.

You cannot always require a change from someone above you. You can stop silently absorbing the consequences of a choice nobody has discussed.

This becomes more complicated when the authority is also familial. I worked with a CEO whose mother and aunt were drawing substantial distributions from a company that was losing money. He knew the distributions could not continue, but he did not believe he was allowed to challenge them.

The company absorbed the cost for years. Eventually, the money ran out and the family had the conversation anyway, with fewer options available than they had at the beginning.

Some conversations can be held while there are still several possible outcomes, or delayed until circumstances choose the outcome for you.

Giving difficult feedback to a peer, vendor, or outside partner

A peer, vendor, or outside partner does not report to you, so the conversation rests on the strength of the relationship, the standard you agreed to, and whether the relationship can continue to meet it.

That relationship needs to exist before something goes wrong. Get to know the person beyond the work immediately in front of you. Understand what matters to them, how they prefer to communicate, and what they are trying to build. People are more willing to help, hear difficult feedback, and make an extra effort when they know the person asking and believe the relationship matters in both directions.

It also helps to name something positive and true about who they are. If you know them as thoughtful, thorough, responsive, or committed to the work, say so. This is not praise added to make criticism easier to accept. You are reminding them of the standard they have already shown you and asking them to act consistently with it.

With the architect, the conversation could begin this way:

“You've been thoughtful about this project, and I know the quality of the work matters to you. The presentation came back with several errors, including some that remained after the first review. What is your review process before something is sent to us, and what needs to change so the next version is ready to use?”

The positive statement does not soften the standard or cancel the feedback. It gives the person a clear picture of the behavior you want to see and connects that behavior to a quality they already recognize in themselves.

The process question then gives both people a way to determine what needs to change. Perhaps the architect has no second review. Perhaps the work is being delegated. Perhaps the deadlines are incompatible with the expected quality. Once my client understands what is producing the errors, he can decide whether the process can be repaired.

With a peer or outside partner, you cannot rely on formal authority. You have to build enough trust that the person wants to help, reinforce the qualities you want to see from them, name the standard clearly, and decide what you will do if the relationship can no longer meet it.

Holding an employee accountable

With someone who reports to you, you have the authority to define the expectation and the responsibility to make it clear.

That does not mean beginning with discipline. Start by determining whether the person understood the assignment, had the skill and resources to complete it, and knew how the result would be evaluated.

If those conditions were present and the work still fell short, address it directly. Explain the standard, discuss what prevented the person from meeting it, and agree on what changes before the next attempt.

Your responsibility also includes following up. Leaders sometimes believe they have held someone accountable because they had one difficult conversation. Accountability is what happens after the conversation, when you review the commitment and respond consistently to whether it was met.

Correcting the work yourself may feel faster, but it teaches the organization to depend on you rather than improve without you. It is also how leaders fall into the operator trap.

What to do when the problem keeps happening

Not every mistake deserves the same response. The importance of the work, the consequences of the error, and the person’s response should determine how quickly you escalate.

A minor mistake followed by an honest correction may require nothing more than clarification. If the same problem happens again, examine the process and agree on a specific change.

If it happens after that agreement, the conversation is no longer only about the original mistake. You now need to ask why the commitment was not kept.

The person may lack the skill to meet the expectation. They may need additional support. They may not be giving the work enough attention. They may disagree with the standard and have avoided saying so. They may also be in the wrong role.

These are different problems and require different decisions. You cannot diagnose them accurately if every conversation begins and ends with the most recent mistake.

Severity also determines the pace. Repeated typographical errors may justify several rounds of correction. An error in a financial model being used for a major decision may justify immediate escalation. Responding proportionately does not mean treating every mistake gently. It means matching the response to what is at risk.

The goal is not to repeat the same feedback indefinitely. It is to determine whether the person can meet the standard and what you need to do if they cannot.

Have the conversation while there is still time to change the outcome

The conversation you are avoiding is already affecting the work. You are carrying more of it, changing how you interact with the person, or allowing a standard to move without discussing it.

Having the conversation does not guarantee that the other person will agree or change. It gives both of you the opportunity to understand the problem, repair what is not working, and make a different choice while there is still time for that choice to matter.

Describe what happened. Explain the effect. Ask for their perspective. Agree on what changes, give them a reasonable way to succeed, and follow up on the commitment.

Then adjust the conversation to the relationship. With someone above you, make a request and agree on the consequences of their answer. With a peer or partner, build the relationship, reinforce the qualities you want to see, and decide whether the work can still meet the standard. With an employee, make the expectation clear and hold them accountable for what happens next.

The choice is rarely between having an uncomfortable conversation and avoiding one altogether. It is between having an uncomfortable conversation now, while it can still help everyone succeed, and having a much harder conversation later, after the deadline has passed, the relationship has deteriorated, or there are no longer enough options to fix the problem.

Frequently asked questions