# Difficult Conversations at Work: Examples and What to Say Canonical URL: https://headwayskills.com/knowledge/communication/difficult-conversations-at-work-examples/ Markdown URL: https://headwayskills.com/knowledge/communication/difficult-conversations-at-work-examples.md Entity type: Article Last updated: 2026-07-07 Language: en Primary audience: professionals improving communication at work Owner: Headway Skills Contact: https://headwayskills.com/contact/ ## Short answer Real examples of difficult conversations at work - with a colleague, your manager, or about your own mistake - plus what to say to open each one. ## Key facts - Title: Difficult Conversations at Work: Examples and What to Say - Category: Communication - Primary skill: Communication - Related skills: Building Confidence, Teamwork - Primary keyword: difficult conversations at work examples - Source page: https://headwayskills.com/knowledge/communication/difficult-conversations-at-work-examples/ ## What this page covers - Real examples of difficult conversations at work - with a colleague, your manager, or about your own mistake - plus what to say to open each one. - Practical guidance for difficult conversations at work examples - How this topic connects to Communication ## Detailed explanation There is usually one specific conversation behind a search like this, and it has usually been put off at least once already — the teammate whose part keeps arriving late, or the manager whose decision you think is wrong. The most common difficult conversations at work are telling a colleague their work isn't landing, disagreeing with your manager, owning a mistake before someone else finds it, asking for a raise, and pushing back on a deadline you know you'll miss. Almost all of them follow the same shape: what you observed, the effect it had, what you're asking for, and then their side of it. Below are the examples people actually face, the words that open each one, and one reason the scripts you find elsewhere so often don't fit. ## What counts as a difficult conversation at work? The definition that keeps recurring across workplace guidance comes from the Crucial Conversations tradition: a conversation where three things are true at the same time — the stakes are high, opinions differ, and emotions are running strong. That is worth holding onto, because it moves "difficult" out of your character and into the situation: you are not finding this hard because you are bad at talking to people, but because all three conditions happen to be present at once. It works in the other direction too. If only one of the three applies — you disagree with a colleague, but nothing much rides on the outcome — you are probably preparing for a hard conversation that isn't one. ## What are the most common difficult conversations at work? Search results on this are dominated by a single vantage point. Workology frames its list around the ten hardest conversations for managers, Elevate Leadership and ManageBetter both title theirs as conversations "with employees," and the Australian Fair Work Ombudsman publishes an entire manager's course on the subject. The scenarios are consistent: performance drops, missed deadlines, performance improvement plans, denied promotions, disappointing pay news, dress code, terminations. If you manage nobody, almost none of that is your list. The conversations most people actually face run sideways and upward: - a colleague who isn't delivering their part of shared work - someone taking credit for something that was yours - disagreeing with a decision your manager has already made - pushing back on a deadline you can see you'll miss - admitting a mistake before somebody else finds it - asking for a raise - telling a colleague who keeps handing you work that you can't keep absorbing it Most people find one or two of these far harder than the rest, and which ones stays fairly consistent. That pattern is worth knowing: it points at a specific, learnable gap rather than a general failing, and the free Job Skills Test will show you [which pattern is yours](https://assessment.headwayskills.com/). ## How do I start one without making it worse? Preparation comes first, and the Fair Work Ombudsman is specific about its shape: write down your key points and gather the concrete detail — dates, documents, the particular interactions you mean — but prepare talking points rather than a full script, and run them past someone you trust first. The reason to stop short of a script is practical: a memorized one collapses the moment the other person says something you didn't plan for, and they will. Then open by asking rather than announcing. A pattern that appears across several guides is to name the topic and get agreement before you begin — something in the register of "I wanted to talk about how we're splitting the reporting work. Are you open to doing that now?" It removes the ambush. The other person arrives oriented instead of cornered, and a "not right now" hands you a scheduled time rather than a refusal. From there, four moves in order: what you observed, the effect it had, what you're asking for, and then their view of it. Elevate Leadership's worked example runs: "During Monday's team meeting, you interrupted two colleagues while they were speaking. It made it difficult for them to finish their thoughts and disrupted the discussion. Going forward, I need you to allow people to finish before responding." The construction to drop is the generalization. "You always miss the deadline" is arguable — one counterexample and you have lost the conversation. "The last three drafts arrived after the deadline" isn't. Vagueness is what makes these conversations feel like an attack; specifics are what stop them from becoming one. ## What do I say to a coworker who isn't pulling their weight? Start with the threshold, because it decides whether this is yours to raise at all. Alison Green of Ask a Manager draws the line at impact: don't become the behavior police unless the person's work is materially affecting yours. If a colleague is coasting and nothing lands on your desk as a result, it belongs to their manager. If you are redoing their work, it belongs to you. That threshold also supplies the phrasing. Green's script anchors everything in the speaker's own workload rather than the colleague's character: "Jane, I've been having to redo your account entries because so many of them are incomplete. It's taking me a lot of time to redo them, so going forward can you be careful to fill out every field?" Nothing in that sentence is a claim about who Jane is. Notice what it does differently from the manager example above. "Going forward, I need you to" carries authority a peer doesn't have; "Can you" asks for the same change without borrowing a rank you don't hold. That swap is the most useful edit you can make to almost any script written for managers. ## How do I tell my manager I disagree with them? This direction is thinly served online — the University of Texas at Austin's HR pages are one of the few dedicated resources for taking a difficult conversation upward, against dozens of guides pointed the other way. The four moves still hold, but two things change. First, lead with the shared goal rather than the disagreement, because your manager is weighing constraints you may not see. Second, bring the alternative with you: raising a problem invites a defense of the decision, while raising it alongside a workable option invites a comparison. And say it once, properly. If the decision stands after you have made your case, implement it anyway rather than relitigating it in the corridor — disagreeing openly and then committing is a normal sequence, not a climbdown. ## Should I have this conversation in person or send an email? Almost always in person, or at least on a call. The pull toward writing it down is strongest exactly where writing performs worst: sensitive subjects, emotional weight, anything that needs back-and-forth. Written words can't be adjusted when you see someone's face change, and they get reread later in whatever mood the recipient is in. Writing has one clear job here, and it comes afterward: once you have agreed something, a short message confirming what you both landed on removes the risk of two different memories of the same conversation a month later. ## What if they get angry, defensive, or upset? Expect some version of it, and plan to stay level. Guidance from Pollack Peacebuilding is blunt about the mechanism: if you look irritated, the other person starts reacting to your irritation rather than to what you actually said, and the conversation becomes about the exchange instead of the problem. The move when the temperature rises is to stop advancing and start listening — let them finish the whole objection, then answer what they actually said. Defensiveness is usually a first reaction rather than a settled position, and it often deflates when it isn't met with more pressure. ## What if nothing changes afterward? Close the conversation properly, first of all, because this is the step most people skip. Before it ends, summarize out loud what you agreed, what you still disagree on, and who is doing what. Ten seconds of that separates a conversation that changed something from one that merely happened. If the behavior continues after a clear, specific request, you have done the part that was yours. That is the point to bring your manager in — and you can now show you raised it directly first, which is what most managers want to know before they get involved. Waiting, meanwhile, has a cost that keeps accruing. The Crucial Conversations column in Psychology Today puts it sharply: when a colleague coasts and nobody says anything, the silence is part of what keeps it going. ## Why some people find these easier than others Read those answers back and the same three things keep doing the work. Saying it plainly instead of circling it. Being willing to start at all. Staying on the problem rather than drifting to the person. **Communication** covers most of the visible part — choosing a conversation over an email when the subject is sensitive, leading with your actual point instead of building up to it, keeping it brief, and genuinely wanting to hear the other person's account rather than waiting out your turn. There is no universal script, which is why the same wording lands well with one colleague and badly with the next; adapting to the person in front of you is part of the skill. **Building Confidence** is the part nobody searches for, and usually the real bottleneck. The wording is rarely what stops you — the postponing is. This one is handled concretely: decide in advance exactly when and where you'll do it, get past the first step only, and accept feeling uncomfortable rather than waiting to feel ready. The steadiness arrives from having done it, not from before. **Teamwork** is what keeps the conversation from costing you the relationship. Raising a missed commitment early and specifically, engaging a disagreement instead of swallowing it, staying on topic so it never turns personal, and noticing when trust has slipped so you can reset — these are what make it possible to say something hard to someone you'll still be sitting next to on Monday. None of the three is a personality setting; each is a behavior, and most people are much further along in one than in the others. The free Job Skills Test scores where you stand across the twelve work skills this framework treats as learnable — these three among them — so you can see [which one to build first](https://assessment.headwayskills.com/) instead of trying to fix all three at once. Some of this may already be how you operate. Noticing when something needs saying, weighing how it will land, choosing the moment — that instinct is the harder half to acquire, and the wording is the part that gets learned — without turning you into someone blunter than you are. These conversations don't get rarer from here. They get bigger — more money attached, more people affected — and the habits you build on the small ones are the ones you'll be running when the stakes are higher. All of it stays learnable, which is the useful part. And you went looking for the words before the conversation rather than after it went badly. That is most of what separates people who get better at this from people who keep putting it off. What's left is an honest read on where you stand. ## Where your skills actually stand You don't have to guess which part of this is your weak spot. The Job Skills Test is a **free** self-assessment of your work skills — twelve of them, including the three this article has been circling — and it gives you a plain read on which one would change the most if you worked on it. It takes seven minutes, there is nothing to prepare, and your results appear as soon as you finish. No pressure to do anything with them straight away. **[Take the test](https://assessment.headwayskills.com/)** *Free, seven minutes, and your results appear straight away.* ## Who this is for - Professionals building practical workplace skills - Readers looking for specific, usable work advice - Managers, educators, and coaches supporting career readiness ## Common questions ### What is this guide about? Real examples of difficult conversations at work - with a colleague, your manager, or about your own mistake - plus what to say to open each one. ### Which Headway skill does this connect to? This guide connects primarily to Communication. It also relates to Building Confidence, Teamwork. ### What is the recommended next step? Use the free Work Skills Test to reflect on which work skill to improve next. ## Related pages - https://headwayskills.com/knowledge.md - https://headwayskills.com/knowledge/communication.md - https://headwayskills.com/knowledge/confidence.md - https://headwayskills.com/knowledge/teamwork.md - https://headwayskills.com/work-skills-test.md ## Citation guidance Use the canonical page when citing this content: https://headwayskills.com/knowledge/communication/difficult-conversations-at-work-examples/ Preferred summary: "Real examples of difficult conversations at work - with a colleague, your manager, or about your own mistake - plus what to say to open each one." ## Change log - 2026-07-07: Content collection version published.