How to Have a Difficult Conversation at Work (Without Wrecking It)

Why do we avoid difficult conversations, and when should you speak up?

Most people do not avoid hard talks because they are weak. They avoid them because silence looks sensible in the moment. The cost of speaking feels immediate: an awkward meeting, a defensive colleague, maybe tears. The cost of staying quiet is slow and hard to see, so it gets underweighted.

Conflict is common. In November 2025 Acas, the UK's workplace conciliation service, reported that 44% of people in Great Britain had experienced conflict at work in the previous twelve months, the highest level it had recorded. The same survey found that stress, anxiety or depression and a drop in motivation were frequent effects. Conflict is not unusual; what varies is whether it is handled early and well.

Avoidance also charges interest. The behaviour continues, you start reading everything the other person does through a negative lens, and when you finally speak you bring months of frustration with you. That is often why people conclude that 'raising things makes it worse'. The issue was not the raising. It was the timing.

A quick test stops the agonising. Answer four questions in writing; it takes about three minutes.

• Is it recurring or significant? One late reply is noise; five is a pattern; one error that affects a client decision is significant.
• What happens if nothing changes for three months? If the honest answer is resentment or a visible business impact, speak up.
• Can I name what I want to be different? If not, you may need to vent to a friend, not talk to the colleague.
• Am I the right person, and is this the right channel? Some issues need a manager or a formal process (see the escalation section below).

How should you prepare for a difficult conversation?

The most useful preparation habit is separating facts from stories. A fact is what a video camera would have recorded: words said, actions taken, numbers and dates. A story is the meaning you have attached: motives, labels and predictions. 'He called my document unusable in front of eight people' is a fact. 'He wanted to humiliate me' is a story. It might be true, but opening with it starts an argument about intentions you cannot win.

Write your facts, then your story, then at least two other explanations for the same facts, including one that is generous to the other person. Next, decide what you want for yourself, for them and for the working relationship. Finally, write a single specific request. If you cannot write the request, you are not ready.

What should you say to open a difficult conversation?

The first thirty seconds tell the other person what kind of conversation this is. If they conclude they are under attack, they stop listening. A good opener does four things: names the topic, states a shared purpose, shows your intent and invites their view.

Here is a template: 'I'd like to talk about [topic]. My aim is [shared purpose]. I'm not looking to [blame / criticise]; I want to [solve / understand]. Can I share what I've noticed, and then hear how it looks from your side?' For example: 'Can we talk about how deal paperwork reaches my team? I want your deals approved faster. I don't think anyone's being careless; I suspect the form is a pain. Can I show you what I'm seeing?'

Avoid openers that guarantee defensiveness: 'We need to talk', 'Don't take this the wrong way', 'Everyone's noticed', and the compliment sandwich, which teaches people that praise is a warning.

How do you listen when the other person gets defensive?

People cannot hear you until they feel heard. When someone is defensive or upset, resist the urge to correct them. Instead, run a simple loop: listen without interrupting, offer back what you heard in your own words, name the feeling you are picking up, and ask a genuine question. Then check: 'Have I got that right?'

Acknowledging is not agreeing. 'I can see why that felt unfair from where you were' does not concede the point. It shows you understand, which is usually what lowers the temperature enough for a real discussion. Swap 'why' questions, which can sound accusatory, for 'what' and 'how': 'What was going on for you at that point?'

How do you give feedback to a peer or your manager?

The Situation-Behaviour-Impact model, developed by the Center for Creative Leadership, keeps feedback specific and factual. Describe the situation (when and where), the behaviour (what the person said or did, camera-style) and the impact (the effect on you, the work or others). CCL also recommends exploring intent, so follow the impact with a question such as 'What was happening on your side?'

For a peer: ask permission, deliver one SBI, ask about intent, make a specific request and agree next steps. For your manager: tie the feedback to their goals ('Can I share something that would help me hit your deadlines more reliably?'), raise it in a one-to-one, and ask for a process change rather than an apology.

Feedback upward and sideways matters because people rarely get it. Amy Edmondson's 1999 study of 51 work teams, published in Administrative Science Quarterly, found that team psychological safety was associated with learning behaviour, which in turn related to performance. Respectful candour between colleagues is part of what makes that safety real.

How do you say no or push back without burning bridges?

A reluctant yes often does more damage than a clear no, because it leads to late work or quiet resentment. A simple structure helps: yes to the person and their goal, no to the specific request, yes to an alternative. 'I can see the night shift needs this. I can't add two sessions within this budget. I can add them at the agreed rate, or swap two day sessions for night sessions at no extra cost. Which works better?'

If they push back, do not pile on new justifications; each one sounds negotiable. Acknowledge the frustration, restate the limit and return to the options. For anything involving pricing or contract terms, check your contract and involve your manager before you commit.

How do you apologise and repair a work relationship?

Research led by Roy Lewicki at Ohio State University, published in 2016, tested apologies built from six elements. Acknowledging responsibility was the most important, followed by an offer of repair; requesting forgiveness mattered least. In practice: name exactly what you did, show you understand the impact, and say what you will do to put it right and differently next time. Drop 'if', 'but' and excuses.

One apology rarely fixes a strained relationship. Plan a series of small positive moves: keep a visible promise, credit their work publicly, ask their view on something in their area. Tracking these with dates stops follow-ups from quietly slipping, which is easy to do when a relationship feels uncomfortable.

What does a good difficult conversation sound like? A worked example

Here is a composite example from the kind of situation we see in workshops. Ahmed, a finance analyst in Dubai, receives a reconciliation file from his peer Layla at 5:45 pm every month-end, often with formula errors, for a report due at 9 the next morning. He has complained about it to other people for months, but never to her.

Prepared, the conversation goes like this. Ahmed asks for fifteen minutes the next day 'to talk about the month-end handover'. He opens: 'Can I give you some feedback on month-end? Last Thursday the file reached me at 5:45 with errors in three columns, and I was fixing it until 8, so the report went out without a proper check. What's happening on your side?'

Layla explains that a regional office always sends its data late, and she has been waiting until she has everything. Ahmed loops: 'So you're stuck waiting on Riyadh, and sending it late feels better than sending it incomplete. That sounds frustrating.' She agrees. He makes a request: 'Could you send whatever you have at 3 pm and flag the gaps? I can work around missing data far more easily than late data.' They agree, and Ahmed offers to email the regional office about their timing.

Notice what is missing: no labels like 'disorganised', no list of every past failure, no audience. One situation, one behaviour, one impact, a genuine question, a reasonable request. The whole thing takes about ten minutes, which is less time than Ahmed had spent complaining about it in a single week.

When should you escalate, and how do you handle conflict in chat?

Text strips out tone, so readers fill the gaps, and under stress they fill them negatively. Use a two-reply rule: if a written exchange has gone back and forth twice with rising tension, stop typing and suggest a call. Never escalate by adding someone's manager to a tense email; tell the person first. After any call, confirm agreements in a short, neutral written summary.

Escalate when there is a risk to safety, legality or ethics, when you have tried directly and the behaviour has continued, when the decision is beyond your authority, or when a power imbalance makes a direct conversation unsafe. Bring facts, what you have tried and the impact, and ask for a decision or support rather than punishment. For harassment, discrimination or fraud, follow your company's formal process and seek qualified advice; this article is educational, not legal or HR advice.

If you want to measure where you are starting from, AssessAll's Conflict Navigation & Resolution assessment gives you a baseline, and Jobulary can turn the results into an individual development plan with goals and review dates. For the full method with planners, 50 scripts, email templates and a relationship tracker, see the Hard Talks, Good Outcomes kit from Bodhih Training.