How do you start a difficult conversation at work?

Start with the specific behavior you observed, not the conclusion you've drawn. 'I want to talk about the last three sprints — each one had a deliverable that slipped on Friday with no warning' is a starting point. 'We need to talk about your performance' is not — it signals a verdict before the conversation has begun. The first sentence should name what you saw, not what you think it means.

What do you say when you have to confront a difficult employee?

Name the pattern in plain language and connect it to the impact on the team or work. 'When the sprint closes without flagging a slip — even a small one — the engineering team has to scramble, and I'm fielding calls I'm not equipped for. I want to understand what's happening on your side.' You're not confronting — you're naming shared reality and making space for their perspective before asking for change.

How do you have a hard conversation with someone who gets defensive?

Slow down and go more specific. Defensiveness usually means the person heard a character judgment rather than a behavioral observation. If you said something like 'you're not communicating well,' they may be defending their identity — not their behavior. Try: 'Let me be more specific. Tuesday's standup — you said everything was on track, but we found out Friday it wasn't. Walk me through what was happening.' Behavior-level specificity gives the other person something concrete to respond to, rather than a verdict to argue against.

How do you have a difficult performance conversation without it turning into an argument?

The goal of the conversation is ownership — not winning. When it turns into an argument, someone is trying to be right. Lead with curiosity, not certainty: 'I've noticed X pattern. What's your read on it?' Let the answer inform what happens next. If they have context you didn't know about, that changes the picture. If they don't see the pattern the same way, that's important information too — and the starting point for a real conversation rather than a performance verdict.

What is the best way to give constructive criticism at work?

Constructive criticism works when it's specific, early, and focused on behavior rather than character. Name the behavior you observed (not what it means about the person), connect it to impact (what it costs the team or work), and invite their perspective before jumping to the solution. Most 'constructive criticism' fails because it skips the observation and starts with the advice — which feels like a verdict delivered before the trial.

How do you tell someone their performance isn't meeting expectations?

Be direct about the gap between what was agreed and what happened — not about the person's effort or attitude. 'We agreed Q4 forecasts would land by Thursday. Three of the last four didn't — and we're downstream of that gap on two deals that are now at risk. I want to understand what's making the Thursday deadline hard to hit.' You're naming the gap precisely, naming the cost, and opening a door rather than closing one.

For Managers

How to have a difficult conversation at work (a step-by-step guide)

A difficult workplace conversation succeeds when it leads with a specific observation (not a conclusion), names the impact on the work and team, makes space for the other person's perspective, and ends with a clear and agreed-upon change — not a vague commitment to 'do better.'

June 27, 20264 min readDifficult ConversationsAccountability DialManager Behavior

Most difficult conversations fail before they start — not because the person giving them is mean-spirited or the person receiving them is defensive, but because the conversation arrives too late, too loaded, and with the conclusion already baked in.

By the time most managers have the hard conversation, they've been watching the pattern for three to six weeks. They've told the story to a few trusted people. They've decided what it means. And when they sit down to have the conversation, they don't lead with an observation — they lead with a verdict the other person didn't agree to and doesn't yet understand.

That's not a difficult conversation. That's an announcement with questions at the end.

The structure of a conversation that actually changes something

A difficult workplace conversation that works follows a specific structure:

Specific observation — what you saw, in plain language, without interpretation
Ask before telling — what was happening on their end
Impact — what the behavior costs the team, the work, or the relationship
Clear change — what specifically needs to be different, by when

That's it. The problem is that most managers invert the structure — they start with the impact (or worse, the verdict), skip the observation entirely, and never ask.

Why leading with the verdict closes the conversation

When you start with the conclusion — "I'm concerned about your performance," "You're not a team player," "This pattern is starting to affect how I see you" — you're asking the other person to agree with a judgment they weren't party to forming.

The rational response is to defend. Not because they're being difficult, but because they're being asked to accept a characterization of themselves without the evidence.

Start instead with the specific event. "I want to talk about Tuesday's sprint close. The deliverable slipped, and I found out Friday afternoon when I was already on the call with the client." That's a behavior, at a specific time, with a named impact. The other person knows what you're talking about, can respond to it, and hasn't been asked to accept a verdict about who they are.

The ask-before-telling move is not optional

After you name the observation, stop. Ask what was happening on their side. And actually wait for the answer.

This is the step most managers skip because they've already formed their view by the time they sit down to have the conversation. Asking feels like delaying the point.

It's not. It's doing it.

The manager who asks first and listens before concluding is far more likely to get the truth. Sometimes the answer reveals a legitimate blocker you didn't know about. Sometimes it reveals the other person doesn't see the pattern the same way — which is the actual problem worth solving. Either way, you land your concern more accurately because you actually know what you're dealing with.

If the answer resolves the issue — great, acknowledge it and move on. The cost of asking when it turns out to be unnecessary is very low.

What "impact" means — and why judgment isn't the same thing

Once you've heard their side, if the issue is real and still unresolved, name what the behavior costs. Not what you think about it — what it costs.

"When I find out Friday afternoon, I can't adjust the engineering team's priorities and I'm fielding client calls without the right information. That's what this is costing us."

Notice the difference:

"This is costing us" — behavior → impact
"This tells me you're not taking the work seriously" — behavior → character judgment

Impact statements keep the conversation at the level of behavior, where something can change. Character judgments move it to identity, where nothing can change — only be defended or surrendered.

Naming the change specifically

The conversation isn't over until there's a specific, agreed-upon change. Not "I need you to communicate better." Not "Let's see if we can do better next sprint." Something specific:

"If a deliverable is at risk, I hear about it by Wednesday. Not Friday afternoon — Wednesday, when we can still do something about it. Can you commit to that?"

Then follow up in writing. Not a formal write-up — two sentences via Slack or email. "Thanks for the conversation. We agreed: if a deliverable is at risk, you flag it to me by Wednesday. I'll check in after next sprint."

The written record is what keeps the conversation from evaporating and the pattern from recurring.

The Accountability Dial gives this a structure

The Accountability Dial™ names five stages of accountability conversation, from the lightest (Mention — a brief, curious observation within a day) to the heaviest (Limit — the end of coaching on this issue, with a consequence appropriate to the situation).

Most managers skip stages one and two — Mention and Invitation — and reach for a Conversation or Boundary-level response too early. The result is a conversation that feels punitive even when it's meant to help.

Done in sequence — early, light, curious — the hard conversation at stage three is rarely needed. The pattern usually resolves at Mention or Invitation, when the cost of having it is lowest. The difficulty of a conversation is inversely proportional to how early you started it.

For a practical guide to drafting these conversations in your own voice, see Accountability Dial feedback templates. For how this looks inside a product that makes it repeatable, take the 3-min tour.

If this is the standard you want on your team

Send it to them. In your own voice.

One click opens a draft in your email or copies the share text — edit it, send it from your own address. We never email anyone on your behalf.