Difficult conversations are hard in any language. In English, as a non-native speaker, there's an additional layer: you may be uncertain whether the difficulty is the conversation itself, or whether something in the language is making it harder than it needs to be.
Often both are true. But the language dimension is solvable. The conversation dimension is also addressable — most of what makes difficult conversations difficult is not language at all, but the human discomfort of saying things that will be unwelcome, to people whose opinion matters to you.
Here's a framework for the conversations that most people avoid, and the language that makes having them possible.
What Makes a Conversation "Difficult"
A conversation is difficult when some combination of the following is true:
- What you need to say will be unwelcome to the person hearing it
- The relationship matters and you're afraid of damaging it
- You're uncertain about your right or standing to say the thing
- The stakes of getting it wrong — the relationship, the outcome, your reputation — are real
Difficult conversations are not optional for people in leadership roles. Avoiding them produces the outcomes you were hoping to prevent: the underperformer doesn't improve, the bad deal goes ahead, the relationship is damaged by what went unsaid rather than by what was said.
The goal isn't to make difficult conversations comfortable. It's to have them in a way that is clear, fair, and preserves the relationship where possible.
Delivering Bad News
The most common error: delaying the bad news by surrounding it with context, positive framing, or explanation. This makes the conversation harder, not easier. The person is waiting for the news — their anxiety is highest during the preamble, and the news itself, when it arrives, can actually reduce tension by making the situation concrete.
Bad news should arrive early:
"I need to tell you something difficult. [Name the situation clearly]. I want to explain how we got here and what it means going forward."
The structure: name the situation first, then the context. Not context then situation.
What to say after the news is named:
- Explain the reasons briefly and factually — not as justification, but as context that helps the person understand
- Name what comes next: "Here's what this means for [them/the project/the relationship]"
- Where relevant: "Here's what I want to do about it" or "Here's what I'd like us to do together"
The tone should be calm and serious, not apologetic. Over-apologising before bad news signals that you feel guilty, which makes the conversation emotionally harder for both parties.
Pushing Back on a Decision or Direction
In English professional contexts, pushing back on a decision is legitimate and often expected from senior people. The convention is to acknowledge the decision before challenging it.
"I understand the rationale here, and I want to raise something before we commit to this direction. My concern is [X]. Here's why I think it matters."
Acknowledge first, challenge second. The acknowledgement is not capitulation — it demonstrates that you've understood the position before disputing it. Challenges that skip the acknowledgement are read as not having listened.
After stating your concern, invite the other person's view: "That's my read on it. What am I missing?"
This framing — challenge plus genuine openness — is the combination that makes pushback productive rather than adversarial. The person being pushed back against is more likely to engage seriously with a challenge that allows them to be right than with one that requires them to be wrong.
Addressing Underperformance
The most common error here: addressing the pattern rather than the behaviour. "You need to be more organised" or "your communication needs to improve" are non-actionable. The person cannot change a pattern — they can change specific behaviours.
"I want to talk about something I've noticed. In the last month, we missed the deadline on [X] and the report for [Y] came in with errors that needed significant rework. I want to understand if there's something getting in the way, and figure out what needs to change."
Specific. Behavioural. Forward-facing. Not a verdict — an opening to a conversation.
After naming the specific instances: ask before telling. "What's your read on what happened?" This does two things: it gives the person the opportunity to provide context you may not have, and it gives them agency in the conversation, which makes the subsequent discussion more productive.
Expressing Disagreement to Someone Senior
Disagreeing upward is high-stakes and frequently avoided. The cost of avoiding it is that decisions get made with incomplete information, and the senior person doesn't know that your view differs.
The framing that makes disagreement upward receivable:
"I want to be honest with you about something, because I think it matters. I have a different view on [X], and I'd like to share it — not to change the decision, but because I think the perspective is worth having on the table."
Then: the position, stated clearly, with one or two specific reasons. Then an invitation for response: "That's how I see it. I'm genuinely open to being wrong here — what's your view?"
The last line is the move that makes the challenge receivable. A senior person who is challenged and then invited to refute is far more likely to engage seriously than one who is simply contradicted.
The Language Principles
Across all difficult conversations, the language that works shares these qualities:
Directness over euphemism.
"We are not renewing the contract" rather than "We're going to have to let the arrangement come to a close." "I disagree with this decision" rather than "I'm not entirely sure I see it quite the same way."
Euphemism is uncomfortable to receive because the person has to do additional work to understand what you actually mean — and they sense that you're managing them rather than being straight with them.
Ownership over attribution.
"I've decided" rather than "a decision has been reached." "I need to tell you this" rather than "feedback has been received that..." The passive voice in difficult conversations often reads as evasion of responsibility.
Questions after statements, not instead of them.
Asking questions can be a way to avoid making the statement. Ask "what do you think about how things are going?" when you mean "I think things are not going well" is evasion, not dialogue. Name the thing first. Then invite response: "That's my view. What's yours?"
The right emotional register.
The tone you bring to the conversation sets the tone for the other person. A calm, serious delivery signals that this is a significant matter being addressed — not a crisis, not a casual observation. Anxiety produces anxiety. Composure produces composure.
Frequently Asked Questions
How do I start a difficult conversation I've been avoiding?
Name the avoidance: "I've been meaning to raise this for a while and I haven't — I want to address it now." This removes the weight of the delay from the conversation itself and acknowledges that you're aware of the timing.
What if the other person becomes emotional or defensive?
Acknowledge it without trying to manage it away: "I can see this is difficult to hear. I want to give you a moment." Waiting out an emotional response with calm presence is usually more effective than trying to redirect immediately.
How do I know if I've been too blunt or not direct enough?
The test is whether the person could repeat back to you what you said. If the message would be clear if repeated, the directness was right. If there's ambiguity about what you meant or what needs to change, you weren't direct enough. If the relationship was damaged by delivery rather than by content, you may have been too blunt in framing.
Should I prepare scripts for difficult conversations?
Not scripts — the opening lines and the core message. Knowing exactly how you'll open and what the one or two key points are gives you the stability to stay composed when the conversation gets harder. Over-scripting produces rigidity when the conversation goes differently than planned.
If any of this resonates, I run weekly sessions with founders and senior professionals on exactly this kind of thing. Free 10 minute fit call to see if it's a fit. Book here.