How to Handle Difficult Conversations at Work
A practical 8-step framework to navigate difficult workplace conversations with confidence, empathy, and clarity.
Quick Answer: How to Handle Difficult Conversations at Work
Difficult conversations at work become more productive when you focus on understanding the other person’s perspective before trying to convince them. Prepare for the person as much as the topic, ask thoughtful questions, listen actively, acknowledge their concerns, focus on shared goals, and agree on clear next steps. People are far more likely to support your ideas when they feel respected, heard, and involved in finding a solution.
Why Difficult Conversations Feel So Hard
Over the last 20 years, I have had my fair share of difficult conversations at work.
I have disagreed with managers, had to convince skeptical stakeholders, delivered negative feedback to managers, and, on the other hand, received negative feedback from my managers.
But one project changed the way I think about difficult conversations. It happened while I was consulting for a government agency.
My role was to develop a set of cybersecurity policies. On paper, the project looked straightforward. Review the regulatory requirements, understand the organisation’s technology environment, write the policies, circulate them for feedback, obtain approval, and present them to the board.
The engagement was estimated to take six weeks. It ended up taking four months.
The policies weren’t the problem. The stakeholders could not be convinced.
There were more than sixteen stakeholders involved across Legal, IT, Operations, Risk and several business units. Most of them had worked there for more than twenty years. They knew the organisation inside out and were understandably protective of their teams.
Every meeting seemed to end the same way. Legal would push back on the wording. Then IT would say a control wasn’t practical to implement. Then Operations would bring up the extra workload, and by the time Risk chimed in about the safeguards not going far enough, we’d used the whole hour and gained nothing.
Sometimes we would spend half an hour debating a single paragraph. I walked into those meetings believing my job was to explain why the policy was technically correct. Everyone else walked in, trying to explain why it wouldn’t work for them.
If you’re looking to build stronger workplace communication skills beyond difficult conversations, you may also find my guide on How to Impress Your Manager helpful. Many of the same communication principles apply when building trust with your manager and colleagues.
What I Learned from Richard Gallagher’s How to Tell Anyone Anything
Looking back, neither side was really listening. By the end of the engagement, I was mentally exhausted.
To make matters worse, my manager thought I had screwed up, which was why the six-week project had taken four months. That wasn’t exactly a pleasant conversation either.
After the project finished, I spent a lot of time reflecting on what had happened.
People don’t make decisions based purely on facts. They think about the impact on their team, their workload, their budget, their risks, and whether they feel they’ve actually been heard.
That project taught me something I’ve carried into every role since. Before you can influence someone, you first have to understand what they’re protecting.
Most project don’t fail because of because of poor communication. It is because we weren’t engaging stakeholders early enough. I explain this distinction in Stakeholder Engagement vs Communication: What Most Projects Get Wrong.
A few years later, I came across Richard Gallagher’s book, How to Tell Anyone Anything. It reinforced something I had already learned the hard way: people are far more open to your message when they feel respected, understood, and involved in the conversation.
I’ve stopped thinking of these conversations as something to win. The job is just to make it easier for the other person actually to listen.
8 Steps to Handle Difficult Conversations at Work
I still have difficult conversations every week.
Whether I’m speaking with a customer, a project sponsor, a team member, or an executive, I try to follow the same process.
Step 1: Prepare for the person, not just the topic
Instead of focusing only on the topic of discussion, I focus on the people I’m going to be talking with.
Before every important meeting, I ask myself what they’re responsible for, what pressure they’re under right now, and what they’re hoping to walk away with. I also try to get a read on their social style — worth a separate post on its own, honestly.
Those answers are often more valuable than another PowerPoint slide.
Step 2: Start by acknowledging their perspective
One mistake I made during that government project was jumping straight into solutions.
Today, I acknowledge the other person’s perspective first. For example: “I understand your team has to live with this process every day.” Or, “I can see why this would create concerns for your department.”
People become far less defensive when they know you’re taking their concerns seriously. It shows them you’ve actually listened, and that’s usually the first real step toward them listening to you.
Step 3: Ask questions before giving answers
One lesson I’ve learned is that people don’t enjoy being told they’re wrong. But they’re usually happy to explain their thinking if you let them.
Instead of launching into my recommendation, I’ll ask questions like: What concerns you most about this? What impact would this have on your team? If we implemented this tomorrow, what problems do you think we’d run into?
Those questions often uncover the real issue. Sometimes it’s something I hadn’t even considered but is genuinely important — a lack of resources, a bad past experience, or just a misunderstanding that’s been sitting there unaddressed.
Step 4: Listen until they stop defending themselves
This was probably my biggest mistake years ago. I used to listen just enough to get my turn because I figured the meeting was really about explaining my position, and if I missed that window, I wouldn’t get another one.
Now I listen until the other person has finished saying everything they want to say. Quite often, people don’t need you to solve their problem immediately. They just need to know they’ve been heard, and once that happens, they’re far more willing to hear you out, too.
Step 5: Focus on the shared goal
Almost every difficult conversation has one thing in common: both sides usually want the same outcome. They just disagree on how to get there.
During the policy project, everyone wanted to protect the organisation. The disagreement was never about that. It was about how much friction was worth accepting to get there. Once the discussion shifted to solving the problem together rather than defending positions, things got a lot easier.
The same principle applies when asking for a promotion or salary increase. The conversation becomes much easier when you focus on the value you’ve delivered rather than simply asking for more money. I cover this in How to Ask for a Salary Hike with Confidence.
Step 6: Offer options instead of ultimatums
People naturally resist feeling cornered. So instead of “this is the only way,” I’ll say something closer to: “There are a couple of ways we could approach this. Let’s work out which one meets the security requirement without creating unnecessary overhead.”
It’s a small shift in wording, but it changes the whole tone of the room from confrontational to collaborative.
Step 7: Agree on the next step
Every disagreement can’t be resolved in one meeting. Sometimes, an agreement on the next step is a much better way to move forward.
I now end every difficult conversation with a clear next action, even if it’s a small one. I try to document who owns it, when it’ll happen, and what still needs to be discussed.
Step 8: Follow up afterwards
This sounds simple, but it’s amazing how often it gets skipped. After important conversations, I send a short summary covering what we discussed, what we agreed on, any outstanding issues, and the next actions with owners and due dates attached.
It prevents misunderstandings and saves everyone from re-having the same conversation a week later.
One Lesson I Wish I’d Learned Earlier
Looking back, I don’t think that government project failed because the stakeholders were difficult. It became difficult because I went in focused on the policy and missed the fact that sixteen experienced professionals needed to feel comfortable adopting it — and that part was the actual work, not a side task around it.
I’ve seen the same pattern play out since in cybersecurity projects, digital transformations, software implementations, and even startup fundraising. The idea can be right and still go nowhere if the people on the other side don’t feel respected, understood, and involved in getting there.
If I had to sum up twenty years of this, it’s that.
Frequently Asked Questions (FAQs)
The best approach is to prepare beforehand, understand the other person’s perspective, ask questions, actively listen, focus on shared goals, offer options instead of ultimatums, agree on clear next steps, and follow up afterwards.
Difficult conversations often involve conflicting priorities, emotions, deadlines, or differing opinions. People usually care about how decisions affect their team, workload, or responsibilities, making empathy and active listening essential.
Focus on the person as much as the topic. Understand their priorities, pressures, concerns, and communication style before the meeting. Preparing for the individual often leads to a more productive discussion than preparing arguments alone.
Start by acknowledging the other person’s perspective, discuss specific behaviours instead of personal traits, explain the impact, listen to their viewpoint, and work together on practical solutions.
Take time to prepare, ask more questions than you answer, listen without interrupting, avoid becoming defensive, and focus on solving the problem rather than winning the argument.
Summarise what was discussed, document agreed actions, assign owners and deadlines where appropriate, and follow up to ensure everyone has the same understanding.
Yes. When handled respectfully, difficult conversations build trust, improve collaboration, resolve misunderstandings, and strengthen long-term working relationships.
Examples include giving constructive feedback, disagreeing with a manager, resolving conflicts between colleagues, negotiating project priorities, discussing performance issues, handling stakeholder objections, and managing customer complaints.
Related Articles
If you enjoyed this article, you might also like:
- How to Impress Your Manager: Lessons I Learned Over 20 Years
- Your First 30 Days at a New Job: A Communication Checklist
- Stakeholder Engagement vs Communication: What Most Projects Get Wrong
- How to Ask for a Salary Hike with Confidence
Practise Workplace Conversations Before They Matter
Want to practise difficult workplace conversations before they happen? Recroot.app lets you practise conversations with managers, stakeholders, customers, and colleagues using AI, helping you build confidence in a safe environment before the real discussion.
Download the Recroot App to practice difficult conversations on Google Play or the Apple App Store.