When Feedback Is Met with Denial: How Leaders Keep the Conversation Moving Forward

Part 2 of The Courageous Conversations Series

In the first article of The Courageous Conversations Series, Handling Difficult Conversations in Leadership: Preparing for the Response, we introduced three common reactions leaders may encounter during difficult conversations.

The first is denial. You've prepared for the conversation. You know what needs to be addressed. You sit down with the employee, explain the concern, and expect a discussion about how to resolve it. Let's dive into how to respond to denial during feedback seasons.

Instead, you hear:

"That's not what happened."

"I never did that."

"No one has ever told me there was a problem."

"I don't remember it that way."

Now the conversation has changed. Instead of discussing the issue, you're suddenly debating whether the issue exists at all. How a leader responds in this moment matters. Push too hard, and the conversation can become an argument. Back away, and the employee may leave believing there isn't really a problem.

The answer is neither.

When feedback is met with denial, effective leaders stay focused on clarity, evidence, expectations, and what needs to happen moving forward.

Why Employees Deny Feedback

Denial can be frustrating, particularly when the problem seems obvious to the leader. But before responding, it helps to understand what may be happening. The employee may genuinely remember the situation differently. They may not recognize a pattern the leader has been observing over time. They may be surprised by the feedback. Or the information may conflict with how they see themselves.

Someone who considers themselves a strong communicator may have difficulty hearing that their communication is creating confusion. A dependable employee may be genuinely surprised to learn that others have begun questioning their follow-through.

There is also an important difference in timing. The leader may have been thinking about the issue for weeks. They may have reviewed examples, considered the impact, and decided how to address it.

The employee may be hearing it clearly for the first time. Their immediate response may be:

That's not true."

That doesn't mean the leader should abandon the feedback. But understanding the response can help the leader avoid turning denial into a battle.

How to Respond to Denial During Feedback

Don't Argue with Denial

When someone denies something you believe is clearly true, the natural response is to prove it.

That's where difficult conversations can quickly go wrong.

Employee: "I communicated the change to everyone."

Leader: "No, you didn't."

Employee: "Yes, I did."

Leader: "I know you didn't."

At this point, neither person is talking about the actual leadership concern anymore. They're arguing about who's right. The leader doesn't need to win that argument. Instead, stay curious and specific.

You might say:

"It sounds like we remember this differently. Let me walk you through the information I have."

That small shift changes the tone of the conversation. You're not surrendering your position. You're simply refusing to turn the conversation into a contest.

Bring Examples, Not Accusations

When you anticipate denial, preparation becomes especially important. Don't enter the conversation with a vague statement such as:

"You've had problems communicating lately."

Come prepared with specific examples. If there is a pattern, bring more than one.

For example:

"Last Monday, the client moved the deadline and the project team wasn't notified until Wednesday. The previous week, the scope changed and two team members told me they didn't receive the update until after they had completed the original work."

Specific examples make it much harder for the conversation to become a disagreement about general impressions. They also help the employee see a pattern they may genuinely not have recognized. The purpose of evidence isn't to corner someone or build a case against them. It's to create clarity.

Leadership Language: When Someone Denies the Behavior

Employee: "That's not what happened. I told everyone about the deadline."

Leader: "I hear that you remember it differently. Let me share what I know. The deadline changed Monday afternoon, and the project team received the update Wednesday morning. I've also spoken with team members who weren't aware of the change before then."

Employee: "Well, I know I told someone."

Leader: "You may have. The concern is that the people responsible for completing the work didn't have the information they needed. Moving forward, I need changes like this communicated directly to the entire project team as soon as you receive them."

The leader doesn't accuse the employee of lying. The leader doesn't spend another 20 minutes trying to establish exactly who was told and when. The leader provides the evidence, clarifies the concern, and moves forward.

When One Example Isn't Enough

Denial becomes more difficult when an employee treats every example as an isolated incident.

"That was only one time."

"There was a reason for that."

"That's not normally what happens."

This is why patterns matter. If you're addressing an ongoing performance or behavior issue, prepare multiple examples that demonstrate the pattern you're concerned about. One missed communication may be a mistake. Several missed communications begin to show a pattern.

The conversation becomes much clearer when a leader can say:

"I understand that there were circumstances surrounding each of these situations. My concern is that we've now seen the same issue occur several times."

You're no longer debating one incident. You're addressing a pattern that needs to change.

Lean on Expectations

There may come a point when you've shared the evidence and the employee still doesn't agree. This is where leaders sometimes get stuck.

They believe they need the employee to admit:

"You're right. I did it."

You don't. You can listen to someone's perspective without agreeing with it. You can acknowledge that they see the situation differently without removing the expectation.

At some point, the conversation needs to move from:

What happened?

to:

What is expected?

Established expectations give leaders something objective to return to.

Instead of:

"I need you to agree that you handled this incorrectly."

Try:

"I understand that you see it differently. What I want to make sure is clear today is the expectation going forward."

That's a very different conversation.

The Power of "Moving Forward"

Two simple words can be extremely useful when a conversation becomes stuck in denial:

Moving forward. They don't dismiss the past. They redirect attention toward the future.

"Moving forward, here's what I need to see."

"Moving forward, let's make sure the entire team receives the update at the same time."

"Moving forward, the expectation is that this report is submitted every Friday by 3:00."

The phrase gives both people somewhere to go.

The employee doesn't have to abandon their perspective before the leader can establish what happens next. And the leader doesn't have to spend the entire conversation trying to force agreement.

Leadership Language: When the Employee Still Disagrees

Employee: "I still don't agree that I did anything wrong."

Leader: "I understand that you don't agree with my assessment, and I've heard your perspective. I also want to make sure we're completely clear about the expectation. Moving forward, all client changes need to be communicated directly to the project team the same business day. Can we agree that will happen?"

This is the point where the conversation shifts. The question is no longer:

"Can I make you agree with my version of the past?"

It's:

"Are we clear about what needs to happen in the future?"

That's where accountability begins.

Denial Doesn't Have to Derail the Conversation

A successful feedback conversation doesn't always end with an employee saying:

"You're right."

Sometimes it ends with:

"I still see it differently, but I understand what's expected of me."

That may not feel as satisfying to the leader, but it can still be productive. When feedback is met with denial, resist the temptation to argue. Come prepared with specific examples. Look for patterns. Lean on established expectations. Then use moving forward to shift the conversation toward what needs to change.

The goal isn't to force an admission.

The goal is to create enough clarity that there can be no confusion about the expectation going forward. At Powered by Pera, Executive Coaching helps leaders develop the confidence and communication skills needed to navigate conversations like these while maintaining both accountability and trust.

What's Next?

Denial isn't the only response that can make a difficult conversation challenging.

In the next article in The Courageous Conversations Series, we'll focus specifically on emotion and what happens when feedback is met with anger, frustration, embarrassment, or tears. We'll explore how leaders can acknowledge emotion, give someone space to process, communicate their intention, and know when and how to move the conversation forward.

If difficult conversations are getting in the way of stronger accountability or team performance, explore Executive Coaching or learn more about Powered by Pera's leadership development services.