How to Have Difficult Conversations With Employees: Scripts for Performance, Behavior, Conflict, and Layoffs

The instinct to delay is rational in the moment. Naming a problem out loud feels riskier than hoping it resolves itself, and most managers have never been taught what to actually say. So the performance issue gets a vague comment in passing. The behavior problem gets ignored until it affects someone else. The conflict between two employees gets routed around instead of addressed.

The cost of that delay compounds. A performance gap that would have taken a ten-minute conversation to correct in week one becomes a documented pattern by week six, harder to fix and harder to discuss without the employee feeling blindsided. Teams also notice when a manager avoids the obvious problem in the room, and that erodes trust faster than an awkward but honest conversation ever would.

Difficult conversations with employees stay difficult for exactly as long as they stay unpracticed. Managers who have said the words out loud before, even just once in a low-stakes setting, walk into the real version with noticeably less hesitation. Learning how to have difficult conversations with employees is less about a natural gift for confrontation and more about having a structure to lean on when the room goes quiet and it's your turn to speak first.

Preparation is what separates a conversation that lands from one that spirals into vague back and forth. Most managers who report that a conversation "went badly" walked in without having settled any of the three things below, which is usually the real reason it fell apart, not a lack of courage in the moment.

Performance conversations fail most often because the manager describes the feeling instead of the behavior. "You need to step it up" gives an employee nothing to act on, and it usually gets received as a mood rather than instructions. A conversation that connects a specific situation, the observed behavior, and its impact gives them something concrete to change, and it's the single highest-leverage habit inside how to have difficult conversations with employees about performance specifically.

Behavior conversations, tone in meetings, how someone treats a teammate, how they respond to pushback, are harder than performance conversations because they can feel like a judgment of character rather than a note on a specific action. The fix is to keep the language locked to what was observed.

"In yesterday's planning meeting, when Priya raised a concern about the timeline, you told her she was overreacting in front of the group. I need to talk about that specifically." This names a single moment rather than a pattern of who someone is, which makes it far easier for the employee to hear without getting defensive.

Follow the observation with impact, not accusation: "A couple of people mentioned afterward that they're now hesitant to raise concerns in that meeting." Then be direct about the change you need: "I need disagreements handled without dismissing the other person, even when you think they're wrong." Close with a real question, not a rhetorical one, so the conversation has room to become a two-way exchange instead of a lecture. Something like "What's your read on what happened?" gives the employee a genuine chance to add context you might be missing, and it signals that the conversation is a correction, not a verdict handed down without any input from them.

Leadership difficult conversations shift shape entirely once a third person is in the room. You are no longer delivering a message, you are managing two perspectives at once, and the instinct to referee who is right almost always backfires.

Start by meeting with each person separately before the joint conversation, and ask the same question of both: "What do you need from this to feel resolved?" That question surfaces the actual ask, which is often smaller than the conflict makes it look.

In the joint session, set the frame before either person speaks: "We're here to find a way to work together going forward, not to relitigate who started it." Give each person uninterrupted time to describe their side, reflect back what you heard before moving to the other person, and end with a specific agreement both people say out loud, not one you summarize for them. Agreements that come from the employees themselves hold up better than ones handed down by the manager.

One useful rule when you're the one holding leadership difficult conversations between two people who report to you: stay out of deciding who was more at fault. That role turns you into a judge, and it usually leaves one person feeling like they lost even when the underlying issue gets resolved. Your job is the process, not the verdict.

Workload conversations sit in a gray area between performance and support, and treating them as a pure performance issue usually misses what's actually happening. Start with a genuinely open question: "I've noticed things are landing later than usual. Walk me through what a typical week looks like right now."

That answer tells you whether you're dealing with a prioritization problem, an unrealistic scope, or a skill gap disguised as a time problem. If the workload itself is the issue, say so plainly: "Looking at what's on your plate, I think we've given you more than one person can reasonably carry. Let's figure out what moves off your list." Naming the mismatch directly, rather than letting the employee absorb the blame for missing deadlines under an unreasonable load, is usually the moment trust either strengthens or breaks in this kind of conversation.

If the root cause is closer to a skill or focus issue, be equally direct about that, and set a concrete checkpoint rather than leaving it as a vague "let's see how it goes." Either way, close by asking what would actually help this week, not next quarter. A workload conversation that ends with only a diagnosis and no next step tends to repeat itself within a month.

Layoff conversations carry weight the others don't, and the instinct to soften the message with extra context usually makes it worse, not better. Clarity, delivered with respect, is kinder than a long preamble that keeps the employee guessing what's actually being said. This is also the conversation where a script matters most, because emotion under pressure tends to push people toward exactly the vague, drawn-out delivery that causes the most harm.

Even a well-prepared conversation can land differently than expected. Knowing how to handle difficult conversations at work when the other person pushes back, goes quiet, or gets visibly upset matters as much as the opening script.

If they get defensive, resist the urge to repeat your point louder or add more evidence. Slow down instead: "I hear that this feels unfair. Tell me more about how you're seeing it." This is not conceding the point, it's making room for their perspective before asking them to hear yours again.

If they go quiet, don't fill the silence for them. "Take a second if you need it" gives them room without the conversation stalling out awkwardly. If emotions run high, it is fine to pause: "Let's take a short break and pick this back up in ten minutes" is a legitimate move, not a failure.

This is exactly the kind of moment where rehearsal pays off, because the words that feel natural in your head rarely come out the same way under real pressure. SayNow AI lets managers practice these exact scenarios out loud, performance pushback, a tense conflict mediation, a layoff conversation, before the real one happens, with feedback on pacing, tone, and clarity so the actual conversation doesn't have to be the first time you've said the words.

None of the scripts above are meant to be read verbatim in the room. They're a starting shape. The managers who get better at how to have difficult conversations with employees over time are the ones who adapt that shape to their own voice through repetition, not the ones who memorize a script and hope it survives contact with a real person across the table.