How to Have Difficult Conversations at Work

Why difficult conversations go sideways

Use the three-conversation model before you speak

Nonviolent Communication in real workplace language

Give critical feedback without triggering a fight

The conversation you have been avoiding

note

A decision tree for the conversation you have avoided

Ask yourself:

• Is this a facts problem, a feelings problem, or both?
• Do I need to persuade, repair, or set a boundary?
• What outcome would be good enough?
• What will I do if the first answer is no?

For a raise, good enough might mean a raise now, a written review date, or a promotion plan with criteria.

For conflict, good enough might mean a behavior change, a new process, or a mediated follow-up.

diagram

illustration

note

Your final checklist

Before the conversation:

• Write the facts in one sentence.
• Name your feeling in one word.
• Identify the need or standard.
• Decide on a specific request.
• Plan your follow-up.

If you can do those five things, you are ready to begin.

Transcript

Welcome to Slate. Today we're looking at How to Have Difficult Conversations at Work. We'll cover The Harvard Negotiation Project's three-conversation model, Nonviolent communication in practice, Delivering critical feedback without triggering defensiveness, and Having the conversation you have been avoiding. Let's get into it.

Most hard talks fail before the first sentence lands. The real problem is not the topic. It is the hidden mix of facts, feelings, and identity. A performance review can sound like a spreadsheet. To the other person, it can feel like a verdict. That mismatch is where defensiveness starts. The Harvard Negotiation Project, especially Douglas Stone, Bruce Patton, and Sheila Heen in Difficult Conversations, published in 1999, gives a useful map: every tough talk has three conversations inside it. What happened. The emotions. And the identity threat. If you only argue about facts, the feelings leak out sideways. If you ignore identity, people protect themselves instead of solving the issue. Here is the key pattern to notice in the diagram: the topic is usually not the whole problem. The threat underneath is. A manager saying, “Your report was late,” may really be asking, “Can I rely on you?” A teammate hearing that may hear, “I am incompetent.” Once you see that split, the conversation becomes more precise. You stop trying to win a debate and start trying to reduce danger. That is the first skill in any hard conversation: separate the issue from the story each person is telling about it.

Before a difficult conversation, do a fast diagnosis. Ask three questions. What happened, from my view? What am I feeling? What identity story am I telling myself? Then ask the same three about the other person. This is not mind reading. It is hypothesis building. You are trying to predict where the conversation may snag. If the issue is a missed deadline, the facts matter. But so does whether the person may be embarrassed, overloaded, or afraid of looking careless. The model is powerful because it keeps you from overcorrecting. Some people come in with a pile of evidence and no empathy. Others bring empathy and no clarity. You need both. A good opening sounds like a bridge, not a verdict. Instead of “You keep missing deadlines,” try “I want to talk about the last two project dates and what got in the way, because I need to understand the pattern and figure out how we prevent it next time.” That sentence does three things. It names the issue. It signals curiosity. And it points toward a shared goal. The visual here should feel like a checklist in your head, not a script to memorize. The point is to prepare your mind so your tone stays steady when the other person reacts.

Nonviolent Communication, or N-V-C, was developed by Marshall Rosenberg and popularized in the 1960s and 1970s. The core idea is simple: separate observation from evaluation, then connect feeling to need, then make a clear request. That sounds soft until you use it well. It is actually very precise. If you say, “You are careless,” you have mixed observation with judgment. If you say, “The spreadsheet had three broken formulas in the revenue tab,” you have something the other person can verify. Then comes the feeling. Not “I feel like you do not care,” because that is a hidden accusation. Try “I felt anxious when I saw the errors.” Next is the need. Maybe you need reliability, time, or shared standards. Finally, ask for a specific action. “Can you review the formulas with me before the next send?” The analogy is a camera before a courtroom. A camera records what happened. A courtroom argues what it means. N-V-C starts with the camera so the conversation does not begin as a trial. It also helps with raises and conflict. You can say, “When my scope grew by two projects without a title change, I felt frustrated because I need role alignment. Can we discuss what a promotion path would look like?” That is much harder to dismiss than vague dissatisfaction.

Critical feedback lands best when it is narrow, timely, and behavior-based. The goal is not to unload your frustration. The goal is to change future behavior. Research on feedback shows that vague praise or vague criticism helps less than specific information about the task. One practical rule is to discuss the impact, not the person. Say what the behavior did to the work. Not who they are. For example, “When the client was told the deck was ready and it still had missing numbers, I lost trust in the handoff,” is cleaner than “You are unreliable.” Another useful move is to invite their view early. That lowers the feeling of being ambushed. Ask, “How did you see it?” or “What got in the way?” Then listen for constraints, not just excuses. Sometimes the problem is skill. Sometimes it is workload. Sometimes it is a misunderstanding of standards. If you need a concrete model, use this sequence: describe, impact, ask. Describe the behavior. State the impact. Ask for a change. The visual should make the sequence feel almost mechanical, because that is the point. In a stressful moment, a simple structure keeps your words from turning sharp. Think of it like a seat belt. It does not prevent the crash. It reduces the damage.

The hardest conversations are usually the ones you postpone because the outcome matters and the answer is uncertain. Asking for a raise. Naming a pattern of disrespect. Saying you cannot keep absorbing extra work. Avoidance feels safer in the short term, but it quietly teaches the other side that the status quo is acceptable. So the last skill is commitment. Set the meeting. State the topic. Bring one or two concrete examples. And decide in advance what you will do if the answer is no or if the other person gets defensive. That is not pessimism. It is preparation. A raise request, for instance, should include your evidence, your market context, and your ask. A conflict conversation should include the behavior you need to stop, the standard you want, and the consequence if it continues. Here is the pattern to remember: prepare, open, listen, clarify, and close with next steps. The closing matters because many talks feel good in the room and disappear afterward. Write down who will do what by when. If you want one sentence to carry into the real world, use this: be kind, be specific, and stay with the issue. That is how difficult conversations become workable ones.