A manager once told us two of her engineers “just couldn’t get along.” She’d tried mediation, a personality workshop, even reshuffled seating. Nothing held. When we asked what they actually argued about, the answer was always the same: who owned the deployment checklist. That wasn’t a personality clash. It was a process conflict wearing a personality costume, and she’d spent three months treating the wrong illness.
This is the most expensive mistake managers make with conflict. We reach for the easy label, “they’re difficult,” “it’s a clash of styles,” and then apply a fix aimed at a problem that isn’t there. The label feels true. It’s usually wrong.
Sorting out the type first changes everything that comes after. Below are the four recognized kinds of workplace conflict, the ones managers most often confuse, and how to read what’s really being fought over.
What are the 4 types of conflict in the workplace?
Workplace conflict falls into four widely recognized types: task, relationship, process, and value. The core of this model is the task-relationship-process typology validated by organizational psychologist Karen Jehn in her foundational studies of team conflict; most practitioner sources, including Harvard’s Program on Negotiation and AIHR, then add value conflict as a fourth category. Amy Edmondson’s work on psychological safety explains a related point: whether a team can surface these conflicts productively in the first place. The reason the model works is that each type has a different root and needs a different response.
The older habit of inventing categories like “leadership conflict” or “creative conflict” muddies this. Those are settings where conflict happens, not types of conflict. A design debate and a budget fight can both be task conflict, even though one looks “creative” and the other looks “strategic.” Naming the type, not the room it happened in, is what gives you traction.
If you want a quick read on where your own instincts sit before going further, the conflict resolution self-assessment gives you a baseline in a few minutes.
Task conflict: disagreement about the work itself
Task conflict is a clash over what the work should be or how the goal gets reached. It lives in the content of the job, not the people doing it. Two analysts arguing over which metric matters most are in task conflict.
Two team members disagree on how to approach a launch. One wants a methodical, structured rollout with clear milestones. The other wants a faster, more flexible push to learn from real users sooner. They argue over timelines and deliverables.
Handled well, this is the one good kind of conflict. Teams that argue about ideas tend to make better decisions than teams that stay quiet. Task conflict turns toxic only when nobody resolves it, because an unsettled argument about the work slowly curdles into resentment about the person. Your job is to keep it on the work and force a decision before it personalizes.
Relationship conflict: personal friction between people
Relationship conflict is interpersonal tension rooted in dislike, distrust, or hurt, not in the work. It’s the “I just can’t with this person” conflict. Unlike task conflict, this kind rarely produces anything useful.
Two colleagues bristle at each other in every meeting. One reads the other as dismissive and self-promoting. The other reads the first as rigid and territorial. The subject of the meeting barely matters; the friction shows up regardless.
The tell here is that the disagreement follows the people, not the topic. Put them on a different project and the tension travels with them. Real relationship conflict needs direct conversation about the relationship itself, sometimes with a neutral third party. The catch, which we’ll come back to, is that a lot of what gets called relationship conflict isn’t relationship conflict at all.
Process conflict: disagreement about how and who
Process conflict is a fight over the how, not the what. It covers who owns which task, how decisions get made, and how the work flows. It’s the most misread of the four because it so easily looks like a personality problem.
Two team members keep colliding over the same handoff. One assumes she owns the final sign-off. The other assumes it’s shared. Neither is being difficult. The roles were never clearly drawn, so they keep stepping on each other and reading it as the other person overreaching.
That deployment-checklist standoff from the opening was process conflict. So is most of what managers label “they don’t respect each other.” Process conflict usually traces back to unclear ownership, and the fix is structural: define roles, draw the decision rights, name the owner. No amount of relationship coaching fixes a missing org chart.
Value conflict: clashing beliefs about what matters
Value conflict comes from differences in principles, ethics, or what people believe is right. It’s the deepest kind because it touches identity, not just opinion.
One team member believes shipping fast and fixing later serves customers best. Another believes releasing anything unpolished is disrespectful to them. This isn’t a debate about a feature. It’s two different ideas of what “doing good work” means.
You usually can’t resolve value conflict the way you resolve task conflict, because nobody is going to abandon a core belief in a meeting. What you can do is name the value difference openly, decide whose principle governs this specific decision, and agree on that without pretending the disagreement vanished. Forcing a fake consensus on a value gap just buries it.
The misdiagnosis map: what conflict looks like vs what it actually is
Most conflict shows up wearing the wrong label. A manager sees friction, reaches for “personality clash,” and misses the process gap or value difference underneath. This is how the four types tend to disguise themselves, and the tell that reveals the real one.
| Looks like | Usually actually is | The tell |
|---|---|---|
| ”They have a personality clash” | Process conflict | The fight is always about the same handoff, decision, or ownership question |
| ”It’s just a creative difference” | Value conflict | Each person is defending what “good work” means, not just one option |
| ”They’re being difficult” | Task conflict gone stale | There was a real disagreement about the work that nobody ever resolved |
| ”They don’t communicate well” | Process conflict | Roles and decision rights were never clearly defined |
| ”It’s a clash of work styles” | Task or process conflict | Strip the styles away and a concrete disagreement about what or how remains |
The pattern across that table: managers over-diagnose relationship and personality conflict, and under-diagnose process and value conflict. Relationship problems are the rarest of the four and the hardest to fix, yet they’re the first label we reach for. Process and value gaps are common and fixable, yet they hide behind “they just don’t click.”
How to read what’s actually being defended
The fastest way to identify the type is to ignore the words and watch what each person protects. People argue about the surface but defend the real thing.
When someone defends the work and the outcome, you’re in task conflict. The energy goes toward the decision, and they’d accept a different person making the same point. When someone defends how they handled it or who’s responsible, it’s process conflict; listen for “that was my call” or “nobody told me I owned that.”
When someone defends themselves as a person, feeling disrespected, dismissed, or attacked, you’ve moved into relationship conflict. And when someone defends a principle they won’t trade away, it’s value conflict, marked by phrases like “I’m not willing to” or “that’s just not right.” Run that check before you intervene, and you’ll stop solving the wrong problem.
Why do workplace conflicts happen?
Most conflict traces back to a handful of root causes, and each tends to produce a predictable type. Knowing the cause helps you anticipate the type before the argument even starts.
Resistance to change
People resist change when they fear it threatens their standing, their workload, or their way of doing things. This often surfaces as process or value conflict, because the real objection is about how things will work now or whether the change respects what people care about. The move isn’t to overpower the resistance. It’s to understand what feels threatened and address that directly.
Unclear job expectations
When roles and responsibilities aren’t spelled out, people fill the gaps with their own assumptions, and those assumptions collide. This is the number-one source of process conflict, and it almost always gets misread as a personality problem. Clarifying expectations before work starts prevents far more conflict than any amount of after-the-fact mediation.
Poor communication
Communication breakdowns at work create conflict by leaving room for misread intentions and crossed wires. A vague brief, a missed update, or an unclear ask gives two reasonable people two different pictures of the same task. Regular check-ins and explicit confirmations close that gap before it widens. Left alone, this kind of tension can build into broader team friction that’s much harder to unwind.
Differences in personality
Genuine personality differences do create friction, mostly through clashing communication styles and work preferences. The honest caveat is that real personality conflict is rarer than the label suggests. Before you call something a personality clash, run the misdiagnosis check above; more often than not, a process or task issue is hiding underneath.
Diagnose the type, then choose the response
Naming the conflict correctly is half the work. A process gap needs clearer ownership, a task disagreement needs a forced decision, a value clash needs an honest conversation about whose principle governs this call, and a relationship rupture needs direct repair. Match the response to the type, not to the surface.
Once you’ve diagnosed the type, the next step is choosing how to engage, and that depends on your default conflict style. Our guide to the five conflict resolution styles walks through when to compete, collaborate, compromise, accommodate, or avoid, and which style fits which kind of conflict.
Diagnosing conflict in the moment is a skill, and like any skill, it sharpens with practice and feedback. That’s where coaching helps. Merlin, Risely’s AI coach, works through real situations with you and lives natively inside Slack and Teams, so you can pressure-test how to read a conflict right when it’s happening, not a week later in a debrief. The managers who get good at conflict aren’t the ones who avoid it; they’re the ones who learn to name it fast. Practice your next conflict with Merlin before it costs you three months.
For a deeper playbook on resolving what you’ve diagnosed, read our guide on conflict resolution at work for managers.
Frequently asked questions
What are the 4 types of conflict in the workplace?
The four recognized types are task conflict (disagreement about what the work is), relationship conflict (personal friction between people), process conflict (disagreement about how the work gets done and who does it), and value conflict (clashing beliefs about what matters). The task-relationship-process core comes from organizational psychologist Karen Jehn’s research on team conflict, and most practitioner sources add value conflict as a fourth category. It’s the framework most credible sources use.
What’s the difference between task and relationship conflict?
Task conflict is about the work itself, like which strategy to pick or how to read the data. It can be healthy when it surfaces better ideas. Relationship conflict is personal, rooted in dislike, tension, or distrust between people. It almost always hurts a team. The trap is that unresolved task conflict often hardens into relationship conflict over time.
How do you identify the type of conflict at work?
Listen for what people are actually defending. If they defend the work and the goal, it’s task conflict. If they defend their handling and feel disrespected, it’s process conflict. If they defend themselves as a person, it’s relationship conflict. If they defend a principle, it’s value conflict. The words on the surface mislead; the thing being protected tells the truth.
What causes conflict at work?
Common drivers are resistance to change, unclear job expectations, poor communication, and personality differences. These causes usually show up as one of the four conflict types. Unclear expectations, for example, almost always produces process conflict, even though it often looks like a personality clash on the surface.