How Do I Have a Difficult Conversation With an Employee?

Stop trying to win the conversation

Leadership isn't about winning. It isn't about controlling somebody else's thinking. And it isn't about carefully arranging a conversation so that the other person reaches the conclusion you've already chosen for them. Sometimes they will agree with you. Sometimes they won't.

Sometimes they'll tell you something you hadn't considered. Sometimes they'll walk away still thinking. Sometimes they'll come back tomorrow having changed their mind. That isn't necessarily failure. That's what a genuine conversation can look like.

The question I would rather you ask yourself beforehand is: Can I explain clearly what I think and why I think it? Can I put the important information in front of them? Can I make sure they genuinely understand my point of view? Can I listen properly when they respond?

And can I remain calm if they disagree? If you can do those things, you've done the part of the job you actually control. After that, the outcome belongs to the conversation.

Difficult conversations often start much earlier than we think

Sometimes the real problem isn't how we deliver the difficult conversation. It's what happened before it. Perhaps you've tolerated something for too long. Perhaps the expectation was implied rather than explicitly agreed.

Perhaps somebody has been missing a standard for months and nobody has said anything. Perhaps you've relied on memory rather than evidence. Perhaps everybody knew there was a problem, but nobody actually addressed it. Perhaps you've simply been hoping it would sort itself out.

And then suddenly you're sitting across from somebody trying to have a "difficult conversation." So before you search the internet for the perfect script, ask yourself: What am I tolerating today that a confident manager would address directly?

That may be where the difficult conversation really begins. Start with: what did we actually agree? I am a great believer in making clear what success looks like before there's a problem. Because when expectations are vague, performance conversations quickly become: "My opinion." versus:

"Your opinion." That is not a particularly useful place to manage from. Instead, start with something more concrete. What did we agree? What was expected? What actually happened? What is the gap? Why does it matter? Those questions change the quality of the conversation.

Now you aren't trying to persuade somebody that you have a feeling they aren't doing very well. You have something tangible to discuss. That is why clear expectations matter. Not because I particularly love paperwork. I don't. They matter because they make expectations visible.

And managers need something real to manage.

Use evidence, not a collection of frustrations

Imagine saying: "You're always late." The natural response might be: "No I'm not." Now you have an argument. Instead: "Over the last six weeks, you arrived after the agreed start time on these four dates." Now you have evidence. Or:

"You keep missing deadlines." "When?" Instead: "We agreed these four actions would be completed by Friday. Three weren't completed by the agreed date." Again, now you have something real to discuss. Evidence doesn't mean becoming prosecutorial or trying to trap someone.

It means reducing the space for arguments about recollection. Memory is a terrible management system. Evidence changes conversations.

Prepare your case

I spent nearly twenty years practising as a courtroom lawyer in the UK before becoming a business coach. So perhaps unsurprisingly, I often think about important business conversations in terms of presenting a case. In court, you prepare. You understand your facts. You understand your argument.

Often written submissions have been provided beforehand. The other side knows the broad case they need to answer. Then the hearing is where the arguments can actually be explored. You present your case. Then you sit down. What does the other side say? What questions arise?

What evidence changes the picture? What decision follows? Business conversations can benefit from exactly the same discipline. Before an important meeting, ask yourself: What is my case? Not "How do I make them agree?" What am I trying to explain? What evidence supports it?

What do I need them to understand before we begin discussing what happens next? For particularly important issues, there may even be value in giving the other person your thoughts beforehand rather than ambushing them in the room. That gives them time to think too.

Then the meeting can be used for the actual discussion.

Preparation is not scripting every sentence

There is a difference between preparation and control. Preparation means knowing:

• the issue; the relevant facts;
• what was expected;
• what happened;
• why the gap matters;
• what you think;
• and what outcome or next step needs to be discussed.

Control means trying to predict and rehearse every possible response from the other person. That is usually impossible. You don't know what they are going to say. Perhaps they have information you don't have. Perhaps their explanation is better than you expected. Perhaps their explanation is worse.

Perhaps they'll agree immediately. Perhaps they'll challenge your facts. Perhaps they'll become upset. Perhaps they'll surprise you. That's why over-scripting can actually make you worse at the conversation.

You're so busy waiting to deliver line three of your prepared speech that you're no longer listening to what the other person is actually saying. Prepare the case. Then participate in the conversation.

Say what needs to be said in full

One reason difficult conversations fail is that managers become so uncomfortable that they soften the message until nobody can work out what was actually being discussed. They hint. They circle. They say: "There are just a few things we might need to work on."

when what they actually mean is: "You are repeatedly missing an agreed performance standard and we need to address it." Courtesy matters. Respect matters. But clarity matters too. The other person deserves to understand the real issue.

If you leave the conversation relieved because you technically "raised it," but the employee walks away with no idea that there was a serious problem, you haven't really done either of you a favour.

Don't launch into a lecture

Once you've explained the issue, stop talking. Ask: What do you think is going on? That question matters. You may know a lot. But you do not know everything. Then ask: What do you think needs to change? What are you going to do about it? What support do you need? By when?

Now the person isn't merely being talked at. They're being asked to think, take ownership and respond. That is a much more useful leadership conversation.

A red dashboard isn't accountability

Sometimes leaders think their systems are doing the management for them. A KPI goes red. A deadline is missed. A dashboard shows a poor result. Fine. But a dashboard going red isn't accountability. It's just a dashboard going red. Accountability is what happens next. Do we discuss it?

Do we understand why? Do we establish whether the expectation was reasonable? Do we decide what needs to change? Does somebody take ownership? Is there a commitment? By when? And then, crucially: Do we follow up?

If nothing happens when somebody repeatedly misses an agreed standard, then you don't really have a standard. You have a suggestion. Your team will work that out remarkably quickly.

Don't save everything up for one enormous conversation

Another reason performance conversations become terrifying is that managers avoid the small conversations. They tolerate. They postpone. They hope. They make mental notes. Then eventually six months of frustration comes pouring out in one enormous conversation. No wonder it feels difficult.

Address issues nearer to when they happen. If an expectation isn't being met, discuss it. If there is a misunderstanding, clear it up. If there is a pattern developing, point to the pattern. Small, clear conversations prevent many huge, emotionally loaded ones later.

Don't confuse discomfort with harm

Some conversations are uncomfortable. That doesn't mean they shouldn't happen. The fact that somebody may not enjoy hearing something is not, by itself, a reason to avoid saying it. Your responsibility is to be fair. Prepared. Clear. Respectful. Evidence-based. Open to hearing their side.

You are not responsible for making sure they enjoy every part of the conversation. That distinction can be very freeing.

Listen for information that changes your view

A difficult conversation should not merely be an exercise in delivering your verdict. The other person may tell you something material. Perhaps they genuinely weren't clear about the expectation. Perhaps they didn't have the authority you thought they had.

Perhaps something else in the business has been blocking them. Perhaps another manager has been giving conflicting instructions. Perhaps they have misunderstood. Or perhaps the evidence confirms exactly what you thought. Either way, listen.

Good leadership judgement includes being willing to change your view when the facts change. The purpose is not to prove yourself right. The purpose is to understand the situation well enough to make a good decision about what happens next.

End with clarity

A conversation should eventually land somewhere. Perhaps the standard has been clarified. Perhaps the person has agreed to change something. Perhaps additional support is required. Perhaps a formal performance process needs to begin. Perhaps you discovered that your original assumption was wrong.

Whatever the outcome, don't let the meeting simply dissolve. Ask: What have we agreed? Who will do what? By when? When will we come back to this? Then record anything important. Because if the same issue returns in six weeks, you do not want to begin again with:

"I think we talked about this before."

A practical structure for a difficult conversation

You do not need a clever script. Try this instead.

Before the conversation

Ask yourself: What is the issue? What did we agree? What evidence do I have? What is the gap? Why does it matter? What am I currently tolerating? What do I need to communicate clearly?

At the beginning

Explain the issue calmly and clearly. Put the relevant facts on the table. Avoid vague accusations. Avoid theatrical openings. Say what needs to be said.

Then ask

What do you think is going on? Listen. Explore What happened? What information am I missing? Is there a capability issue? A clarity issue? An authority issue? A behaviour issue? A motivation issue? Something else?