How to have a difficult performance conversation

A difficult conversation with an employee goes badly when it's vague, late, and emotional. It goes well when it's specific, timely, and calm. Here is how to prepare for one and get through it without either of you leaving worse off.

Prepare before you say a word

Most difficult conversations fail before they start, because the manager walks in with a feeling instead of a fact. Before you schedule anything, get clear on three things:

• The specific behavior or result — what actually happened, with dates and examples. "The last two reports were a week late" is something you can discuss. "You seem checked out" is not.
• The impact — why it matters. Who was affected, what it cost, what risk it created. This is what turns a complaint into a reason.
• What good looks like — the change you actually want, concretely enough that both of you would recognize it.

Pick a private time when neither of you is rushed, and never the end of a Friday. Tell them roughly what it's about so they're not blindsided. Surprise breeds defensiveness.

Open it without triggering defensiveness

The first thirty seconds set the tone. Lead with the specific issue plainly, not with a long warm-up that makes the person brace for impact. Avoid the "compliment sandwich" — burying the real message between two pieces of praise teaches people to distrust your praise and miss your point.

State what you've observed, name the impact, and then stop talking. A simple opener: "I want to talk about the last two project deadlines, both of which slipped about a week. It put the launch at risk and the team had to scramble. I want to understand what's going on." That is direct without being an attack, and it ends with a genuine question.

Stick to specifics and evidence

The moment the conversation drifts to "you always" or "people feel that you," you've lost. Generalizations invite the person to find the one exception and argue it, and they feel like character judgments rather than fixable problems. Stay on the documented, the dated, the observable.

Describe behavior, not character. "The report was late three times this quarter" is a fact you can solve together. "You're unreliable" is a verdict that leaves nowhere to go.

This is exactly why keeping notes through the year matters: in the moment you can point to specifics instead of reaching for adjectives.

Then actually listen

You delivered your part in under a minute. Now give them real space. There is often a reason you don't know — an overload, a blocker, something happening at home, a misunderstanding about priorities. Ask an open question and let silence do its work; do not rush to fill it.

Listening is not agreeing. You can fully hear someone's explanation and still hold the standard. But people accept hard feedback far more readily when they feel they were understood first.

Agree on next steps, then write them down

A conversation without a concrete next step is just a bad afternoon for both of you. Before you part, agree on:

• What specifically will change, in observable terms.
• By when, and how you'll both know it happened.
• What support you'll provide to make it possible.
• When you'll check in next.

Afterward, write a short, factual summary — what you discussed, what you agreed, the date. Send it to the person so there's a shared record. This is not building a case; it's making sure you both remember the same conversation, and it protects them as much as you.

Follow up — or it didn't count

The follow-up is where trust is won or lost. If you raised something seriously and then never mentioned it again, you've taught the person it didn't really matter. Check in at the date you agreed. Name the improvement when you see it — sincerely, because effort to change is hard and worth acknowledging. If nothing has changed, the next conversation is shorter and clearer, and the earlier record makes it fair.

A short worked example

Situation: A capable engineer has missed two sprint commitments and gone quiet in standups.

Prep: The manager notes the two specific dates, the impact (a dependent team was blocked), and what good looks like (commitments met or flagged early).

Opening: "I want to talk about the last two sprints — the API work slipped both times and the mobile team was stuck waiting. That's not like your usual work, so I wanted to understand what's happening."

Listening: Turns out the engineer was pulled into firefighting for another team and didn't feel they could say no. New information that changes the problem entirely.

Next steps: They agree the engineer will flag conflicting demands in their 1:1 immediately, the manager will handle the cross-team pull, and they'll review at the next sprint boundary.

Follow-up: Two weeks later commitments are back on track; the manager says so directly. The "difficult" conversation turned out to be a solvable logistics problem — which is true far more often than managers expect, and a good reason to have the conversation early and calmly.