Resolve Conflict at Work — Professional Development #014
Resolving a conflict at work means naming the real issue, talking to the person directly, and leaving with one written agreement. It starts before the conversation — with your own motives, your own emotions, and the facts — and it ends with a date to check back. Most conflicts are not as big as they feel on the worst day. They feel big because nobody has said the plain thing out loud yet, and every day of silence adds a layer of story on top of the facts.

Disclosure: some links on this page are affiliate links. As an Amazon Associate, Changenaire earns from qualifying purchases made through links on this page, at no extra cost to you.
Key takeaways
- A work conflict gets smaller when you name the real issue in one sentence — the fact, not the person.
- Prepare before you talk: check your motives, challenge the story you tell yourself, and gather the facts.
- Talk to the person directly and privately — call them in, don't call them out.
- Listen first, then say back what you heard before you answer with your own view.
- Leave with one written agreement and a date to check back on it.
Who this is for: owners and operators working with one other person — a partner, a client, a contractor, a teammate — where something has gone wrong between you and the work is suffering for it. No training is needed; the practice is the training. Who should adjust: if the conflict involves safety, threats, or a legal matter, follow the steps below for the ordinary working disagreement, but get advice from someone outside it before you act — this guide is not a substitute for counsel.
Here is the honest version. A conflict left alone does not stay the same size; it grows, because each person keeps adding to the story in their own head while the facts stay the same. The researchers behind Crucial Conversations spent thirty years studying moments like these, and their finding is blunt: when it matters most, we do our worst — we cower or coerce, hide the facts or exaggerate them, argue or defend. This guide is part of the Professional Development hub, and it travels with Have the Hard Conversation — the opening shape there, the fact, the effect on the work, and the question, is the same shape you open with here.
Go deeper (affiliate link — we may earn a commission): the five steps below are the whole method, and you need nothing to buy to run them. If you want the longer study — why teams that avoid conflict end up with artificial harmony and worse decisions, and the five breakdowns that follow when trust is missing — The Five Dysfunctions of a Team by Patrick Lencioni is the book this guide leans on. Skip it if you only want this week's practice — the steps below are enough to start.
Name the real issue in one sentence
Write down the conflict as one sentence about the work, not about the person: what happened, what it cost the work, and what you need instead. "The delivery was three days late, the client called twice, and I need a date I can give them" is a sentence you can work with. "He never respects my time" is not — it names a character, not a fact, and a person who hears it will defend their character instead of fixing the delivery.
The preparation matters more than the words you use in the room. Harvard Business Review records the rule from the Crucial Conversations authors: do not start by sharing your conclusion — share the facts and premises that led you to it, lay out your data, explain the logic, and let the other person challenge your case (checked November 2026). If the sentence you wrote names a flaw in the person, rewrite it until it names a fact about the work. A sentence you cannot say out loud without blaming someone is not ready yet.
Do it like this: one sentence, three parts: "What happened: ___. What it cost the work: ___. What I need instead: ___." Write it on paper before you book the meeting. If any part names who the other person is instead of what happened, cross it out and write the fact.
Get your own head right before you talk
Before the conversation, answer four questions in writing: what do I really want — for me, for the other person, for the relationship, and for everyone else the work touches? Under stress, motives shrink to the short term: being liked, being right, winning, avoiding the fight. Writing the four answers out pulls them back to the long term, and that changes how you walk into the room. A person who knows what they really want sounds different from a person who only knows what they are angry about.
Then challenge the story you are telling yourself. Harvard Business Review records the two questions the authors use: "What am I pretending not to know about my role in this?" and "Why would a reasonable, rational, and decent person do what they did?" (checked November 2026). Most of us tell ourselves a victim story about our own part and a villain story about the other person's — and both stories make the conversation worse before it starts. The same authors put a number on it: in a hard conversation, 60% is getting your head, heart, and gut right, and 40% is saying it right (checked November 2026). Do the 60% first.
Do it like this: four lines, in writing, before you book anything: "What I really want — for me: ___. For them: ___. For the relationship: ___. For the work: ___." Then one more line: "The story I am telling myself about them is ___, and the fact underneath it is ___." If you cannot write the fact, you are not ready to talk yet.
Talk to the person directly, in private, soon
Book 30 minutes with the person, in person or on video, within a few days — not next month, and not by email. Email turns a conflict into a paper trail both sides can re-read in the worst possible light, and a group chat turns it into a performance. A private conversation is the only place where someone can change their mind without losing face. Open with the sentence you wrote in step one: the fact, the effect on the work, and the question. Then stop talking and let them answer.
Treat the other person as a potential ally in fixing the problem, not as an adversary to beat. Harvard Business Review records the advice from four experts: call people in to a dialogue instead of calling them out — start with the aim of understanding their view, not with a verdict on it (checked November 2026). When you invite someone to discuss an issue rather than trying to win a battle, they are more likely to listen and move forward from the conversation positively. And if the conversation you need is the hard kind you have been putting off, Have the Hard Conversation covers the opening in full: rehearse the sentence out loud twice, alone, before the meeting.
Do it like this: one message, today: "Can we sit down for 30 minutes this week? I want to sort out [the fact] before it costs us more work." Pick a private place, bring your one sentence, and open with it. No audience, no email chain, no ambush.
Listen first, then say back what you heard
Ask the other person to tell you their view of what happened, and listen without interrupting or arguing. Then say back what you heard, in your own words, before you answer with your own view: "I understand what you said is this. Did I get that right?" The question matters — it tells them you heard them, and it gives them a chance to correct you before you argue with a version of their view they never held. Listening is not agreeing. It is finding out what the other person actually thinks, instead of arguing with the version you invented in your head.
There is a reason this works. Harvard Business Review records the research finding that we often exaggerate how extreme our opponents are — one sentence from them, and we build a whole story about who they are and what they intend, then proceed as if it were true (checked November 2026). Listening breaks that habit: when people feel heard, they are much more likely to hear you back. The same skill carries the rest of this engine — Listen So People Feel Heard is the full practice, and this step is where you use it under pressure.
Do it like this: two questions, in this order: "Tell me more about your view of what happened." Then, after they finish: "I understand what you said is ___. Did I get that right?" Do not add your own view until they say yes — or correct you.
Leave with one written agreement and a date
End the conversation by writing down what each person agreed to do, and send it the same day. Not a summary of feelings — a list: who does what, by when. Then put one date on the calendar to check back on the agreement — a week out is usually enough. The written record is what keeps the conversation from dissolving into two different memories of what was decided. If the same problem comes back, the record is what you bring to the next conversation, or to a manager.
This is where the team model from the book comes in. Patrick Lencioni's five dysfunctions run in a chain: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results — each one caused in part by the one below it (checked November 2026). A team that never holds a real conflict cannot commit to a decision, a team that never commits cannot hold anyone accountable, and a team that holds no one accountable ends up caring about individual scoreboards instead of the shared result. Your written agreement is the commitment and the accountability, at the scale of two people. One page, two names, one date.
Do it like this: four lines, sent the same day: "What we agreed: ___. Who does what: ___. By when: ___. We check back on: ___." If the other person disagrees with your version, that disagreement is itself the next conversation — have it now, while the words are still fresh.
At a glance
| Step | The short version |
|---|---|
| Name the real issue | One sentence about the work — the fact, not the person |
| Get your head right | Four wants in writing, then challenge the story you tell yourself |
| Talk directly, privately | Thirty minutes, in person or on video, within a few days |
| Listen, then say it back | Their view first, paraphrased, confirmed — before your answer |
| One written agreement | Who does what, by when, and a date to check back |
Common mistakes
Leading with your conclusion instead of your facts. "You don't care about this project" is a verdict, and a verdict gets a defense, not a discussion. Fix: share the facts and the logic that led you there, and let the other person challenge the case — that is the whole point of the conversation.
Talking about the person instead of the work. Labelling someone — lazy, difficult, toxic — turns a fixable problem into a fight about character, and nobody changes their character in a meeting. Fix: keep every sentence on what happened and what it cost the work; if a sentence names who they are, rewrite it until it names a fact.
Skipping the preparation because the conversation feels urgent. Walking in angry, with no clear wants and no facts written down, is how a thirty-minute talk becomes a month-long standoff. Fix: do the sixty percent first — four wants, the story you tell yourself, the facts — before you book the room.
Leaving without anything written down. A conversation with no record becomes two different memories within a week, and the same conflict comes back wearing a new date. Fix: send the four lines the same day — what was agreed, who does what, by when, and the date you check back.
Can't do it this week?
Do the 20-minute version: write the one sentence about the real issue, and write your four wants — for you, for them, for the relationship, for the work. That is the preparation, and it is the part most people skip. The missed-week rule is simple: let the week go, and run the five steps on the next real week that comes. What counts as enough: one sentence written down, four wants written down, and one conversation booked before the week is out.
Questions people ask
What is the first thing to do when a conflict starts at work?
Name the real issue in one sentence about the work, not about the person: what happened, what it cost the work, and what you need instead. Harvard Business Review's advice on tough conversations is to gather the facts first and share the facts and premises that led to your conclusion, not the conclusion itself — start with what happened, then explain the logic that got you there. If your one sentence names a character flaw, rewrite it until it names a fact.
Should I talk to the person directly, or go to a manager first?
Talk to the person directly and privately first, when it is safe to do so — most work conflicts are between two people who have never actually said the plain thing to each other. Go to a manager first when the conflict involves safety, a legal matter, or repeated behavior after you have already talked directly once. Bring the written record of what you agreed last time; it keeps the conversation about the work, not about who is right.
What do I say when the other person gets angry?
Stay with the facts and slow down: repeat back what you heard them say, in your own words, and ask whether you got it right. Harvard Business Review's experts warn against labelling people in the heat of the moment — calling someone a narcissist or a gaslighter dehumanizes them and drives the conversation into a corner. If the room gets too hot, say so plainly and suggest a short break and a time to resume; a paused conversation is better than a finished relationship.
What if we talk and nothing changes?
Check back on the date you agreed, and name plainly what has and has not changed — that is the point of writing the agreement down. If the same problem repeats, bring the written record to a manager or to human resources and ask for help with the next step. Patrick Lencioni's model of team breakdowns puts avoidance of accountability near the top of the chain: a team that never calls a missed commitment what it is ends up caring about individual scoreboards instead of the shared result.
What comes next
Keep the one-page record. One sentence, four wants, one agreement, one date — that is the practice, and it fits in the margins of work you are already doing. And give the working relationship somewhere to go: Ask for Feedback That Helps shows how to keep the conversation going after the conflict is settled, because the same person you disagreed with this week is the person whose honest view you will need next week. Name the issue. Prepare. Talk directly. Listen. Write it down.
Sources
Every fact in this post was checked against the sources below in November 2026.
- Harvard Business Review — 4 Things to Do Before a Tough Conversation (January 2019, checked November 2026) — the four preparation steps: get your motives right ("What do I really want?" for me, for the other person, for the relationship, for other stakeholders), get your emotions right (victim and villain stories; "What am I pretending not to know about my role in this?" and "Why would a reasonable, rational, and decent person do what he did?"), gather the facts (share facts and premises, not conclusions), and get curious ("The best way to persuade others is with your ears, by listening," as Dean Rusk put it); "crucial conversations are 60% getting your head, heart, and gut right, and 40% saying it right."
- Harvard Business Review — How to Have Difficult Conversations Without Burning Bridges (May 19, 2023, checked November 2026) — see the other person as a potential ally, not an adversary; "call people in" to dialogue instead of "calling them out"; listen actively and paraphrase ("I understand what you said is XYZ. Did I get that right?"); research shows we often exaggerate how extreme our opponents are; labelling people as narcissists, gaslighters, or toxic dehumanizes them; humor only with care and only where it helps the conversation move forward; find allies for larger organizational issues.
- The Five Dysfunctions of a Team: A Leadership Fable by Patrick Lencioni (Jossey-Bass, 2002), ASIN 0787960756 — the book recommended in this post; the five dysfunctions in order: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results, each caused in part by the one below it.
Subscribe for more free step-by-step how-to guides to help you get more things done to grow your business or project everyday.
Email required. Unsubscribe anytime.
Read our Privacy Policy.
