What Is Conflict?

Introduction

Conflict is one of those words that carries weight before it is even defined. For most people, the word brings up images of arguments, raised voices, frosty silences, escalating emails, meetings that end badly, working relationships that never quite recover. It carries an emotional charge that comes from accumulated personal experience, including memories of conflicts that hurt, conflicts that lingered, conflicts that changed how someone felt about their workplace or about themselves. And because the word carries that weight, most people approach the topic of conflict the way they approach any uncomfortable subject. They flinch. They avoid. They prefer not to think about it until they have to. And when conflict arises in their teams, they treat it as a problem to be suppressed rather than a phenomenon to be understood. That avoidance, which feels protective in the moment, turns out to be one of the most expensive habits in leadership.

The reason avoidance is expensive is that conflict, in some form, is not optional in any team that is doing meaningful work. Wherever people with different perspectives, priorities, personalities, and stakes work together over time, friction emerges. That friction is not a sign that something is broken. It is a sign that real work is happening, that people care about outcomes, that ideas are being tested, that boundaries are being negotiated, that the team is alive in the ways that teams have to be alive in order to do anything meaningful. A team with no conflict at all is almost always either a team that has not been together long enough for it to emerge, a team that is suppressing it through fear or politeness, or a team that has stopped caring about its work. None of those are healthy states. Conflict, properly understood, is one of the signs of a team that is functioning, not one of the signs that a team is failing.

But this understanding requires you to look beneath the word. The word "conflict" is doing a lot of work. It covers everything from a brief disagreement in a planning meeting to a long-running feud that has poisoned a team for years. It includes substantive disputes about the right approach to a problem. It includes personality clashes that have nothing to do with the work. It includes resource competition between people who would otherwise be friends. It includes the silent conflict of someone who has stopped trying because they feel unheard. It includes the conflict that erupts in a moment and the conflict that simmers for months. All of these are conflict, but they are not the same kind of conflict. And the first step in dealing with conflict in teams is to recognize that the word itself describes a family of phenomena, not a single thing. Different kinds of conflict need different responses. Lumping them together produces the wrong response to whatever specific conflict is in front of you.

This article begins the chapter on understanding team conflicts by exploring the most fundamental question: what is conflict, actually? What is the phenomenon we are describing when we use the word? What are its essential features? What distinguishes conflict from disagreement, from competition, from tension, from interpersonal dislike, from any of the other states that can produce friction between people? What are the dimensions along which conflicts vary? And how does a clear understanding of what conflict is shape how leaders should respond to it when it appears in their teams? These questions are not just theoretical. The way you understand conflict shapes the way you experience it, the way you talk about it, the way you intervene in it, and the way you support the team members who are caught in it. A leader who understands conflict clearly handles it differently from a leader who treats every disagreement as a crisis or every tension as a personal failure. And that difference, across years and across many conflicts, produces dramatically different teams.

By the end of this article, you should be able to define conflict in terms that are clear and practical, recognize the different forms it takes, distinguish conflict from related but different phenomena, and begin to develop the disposition that allows leaders to engage with conflict as a normal part of team life rather than as an emergency that must be suppressed. That disposition is the foundation on which everything else in this chapter rests. Without it, the specific techniques and frameworks for addressing different kinds of conflict have no ground to stand on. With it, those techniques become tools you can use intentionally, in service of teams that work better because their conflicts have been understood rather than feared.

Simple Meaning: What Is Conflict?

Conflict is the state that arises when two or more people, or two or more parts of a system, perceive that their interests, perspectives, needs, values, or goals are incompatible with each other, and that incompatibility produces friction, tension, or active opposition between them. It is not just disagreement. Disagreement is a difference of opinion that may or may not produce friction. Conflict is the situation in which the difference has consequences, in which one or both sides experience the difference as something that affects them, in which there is a felt sense of opposition between what one party wants and what another party wants. It can be substantive or interpersonal. It can be open or hidden. It can be brief or sustained. It can be productive or destructive. But at its core, conflict is the phenomenon of perceived incompatibility producing felt friction between people.

Conflict is the natural state that arises when people who are connected by work, relationships, or shared systems perceive that what they want, need, value, or believe is in tension with what someone else wants, needs, values, or believes. It is not a sign that something has gone wrong. It is a sign that real differences exist between real people who are interacting with each other in a context that gives those differences consequences. Wherever there are people, conflict is possible. Wherever there are people working together over time, conflict is inevitable. The question is not whether conflict will appear in your team. It will. The question is what kind of conflict will appear, how it will be understood, and what will be done with it. Conflict can be substantive, focused on the work itself, the right approach, the right priority, the right decision. It can be interpersonal, focused on how people are working together, including patterns of communication, respect, and relationship. It can be about resources, about values, about goals, about identity, about power, about history, about almost anything that matters to the people involved. It can be open and visible, expressed in clear terms that everyone can see. Or it can be hidden, expressed only in cold silences, indirect communication, withdrawn engagement, or the slow erosion of trust. It can be brief and self-resolving. Or it can be sustained over months and years, growing more entrenched the longer it goes unaddressed. It can be productive, producing better decisions, sharper thinking, stronger relationships, and more honest engagement. Or it can be destructive, damaging relationships, producing avoidance, depleting energy, and corroding the conditions in which the team can do its work. Understanding what conflict is, in all its forms, is the foundation of being able to engage with it skillfully when it appears in your team. Without that understanding, conflict becomes a single overwhelming category that triggers avoidance or overreaction. With it, conflict becomes a phenomenon you can recognize, name, understand, and respond to in ways that fit the specific situation in front of you.

Conflict can be understood through four essential dimensions:

What Conflict Is Not

One of the most useful steps in understanding conflict is being clear about what it is not. Many situations get called "conflict" when they are something else, and that misnaming leads to the wrong response.

Each of these distinctions matters because the response to conflict should be different from the response to disagreement, debate, competition, discomfort, personality difference, negative feedback, or difficult conversation. Conflating them causes leaders to either over-respond to ordinary friction or under-respond to actual conflict. Both errors damage teams.

The Different Dimensions Along Which Conflicts Vary

Once you understand what conflict is in general, the next step is to recognize the dimensions along which conflicts vary. Not all conflict is the same. A leader who can distinguish the different dimensions is far better equipped to respond to whatever specific conflict is in front of them.

Dimension 1: Substantive vs Relational

Substantive conflict is about the work itself. What approach should we take? What should the priority be? Which decision is right? Relational conflict is about how people are working together. Patterns of communication, respect, trust, behavior. These two dimensions often intertwine, but they are not the same. Substantive conflict, well handled, often improves the work. Relational conflict, well handled, often deepens relationships. Conflating them, or addressing one when the actual conflict is the other, produces ineffective interventions.

Dimension 2: Open vs Hidden

Open conflict is expressed in clear terms. People name the disagreement. They engage with each other about it. It is visible to participants and often to observers. Hidden conflict is not openly expressed. It shows up in withdrawn engagement, cold silences, indirect communication, side conversations, decreased collaboration. Hidden conflict is often more destructive than open conflict because it cannot be addressed directly without first being surfaced. A team where conflict is openly named is not a team in worse shape than a team where it is hidden. It is often a team in better shape.

Dimension 3: Brief vs Sustained

Some conflicts arise, get worked through, and resolve in a single conversation or a short period. Others persist for weeks, months, or years. Sustained conflict is different from brief conflict not just in duration but in character. It tends to accumulate emotional weight. It tends to develop history. It tends to involve patterns that have been reinforced over time. Responding to a sustained conflict the way you would respond to a brief one rarely works.

Dimension 4: Productive vs Destructive

Productive conflict produces something valuable. Better decisions. Sharper thinking. Stronger relationships. More honest engagement. Clarification of differences that needed to be clarified. Destructive conflict produces damage. Eroded relationships. Wasted energy. Decreased trust. Avoidance. Departure. The same underlying disagreement can become productive or destructive depending on how it is engaged with. One of the most important distinctions a leader can make is recognizing which kind of conflict is in front of them and what would shift it from destructive toward productive.

Dimension 5: Two-Party vs Multi-Party

Some conflicts involve just two people. Others involve groups, subgroups, or the whole team. Two-party conflicts are usually easier to address because the participants are clearly identifiable and the dynamics are simpler. Multi-party conflicts involve more complexity because multiple perspectives are in play, alliances may form, and the dynamics shift as different combinations of people interact.

Dimension 6: Equal vs Unequal Power

Some conflicts are between people of roughly equal power within the team or organization. Others involve significant power differences, including manager-team member, senior-junior, or majority-minority dynamics. Conflicts involving power differences require more careful handling because the less powerful party is often less safe to engage openly, and the more powerful party often does not see the dynamic clearly.

Dimension 7: Cognitive vs Affective

Cognitive conflict is about ideas, approaches, and decisions. Affective conflict involves emotional reactions, personal feelings, and interpersonal dynamics. Cognitive conflict tends to be more workable through reasoning and structured discussion. Affective conflict requires attention to emotion and relationship. Most real conflicts include both, but recognizing which dimension is dominant in a specific situation shapes the response.

The Anatomy of a Conflict

Every conflict, whatever its specific form, has a recognizable anatomy. Understanding the components helps you see what is happening when a conflict appears.

A leader who can identify each of these components in a specific conflict is far better positioned to respond to it skillfully. Without this kind of analysis, conflicts look like undifferentiated emergencies. With it, they become situations that can be understood, named, and engaged with intentionally.

Why Conflict Is Not Inherently Bad

One of the most important shifts in how leaders think about conflict is recognizing that conflict is not inherently bad. It can be bad. It can be destructive, damaging, and depleting. But it can also be good. It can produce growth, insight, and depth. The difference is not in the conflict itself but in how it is engaged with.

What Productive Conflict Can Produce

• Better decisions. When different perspectives are honestly engaged with, the resulting decision is usually better than what any single perspective would have produced.
• Sharper thinking. Having to defend, refine, and reconsider your position in the face of opposition produces clearer reasoning.
• Stronger relationships. Working through conflict honestly often deepens trust between the parties involved.
• Surfaced assumptions. Conflict often reveals unspoken assumptions that needed to be examined.
• Clarified values. The values that matter most to people and teams often become clearest when they come into conflict with other values.
• Renewed engagement. Conflict that gets worked through can produce a renewed sense of investment in the work and the team.
• Cultural development. How a team handles conflict shapes the culture of the team. Teams that work through conflict well develop the capacity for honest engagement.
• Innovation. Some of the most creative outcomes emerge from the friction between competing ideas.

What Destructive Conflict Can Produce

• Damaged relationships that take years to repair.
• Decreased trust across the team.
• Avoidance patterns that limit collaboration.
• Reduced engagement and investment in the work.
• Departures of valuable team members.
• Cultures of suppression where honest engagement becomes risky.
• Stalled decisions and projects.
• Wasted energy that could have gone into the work.
• Cynicism and burnout.

The Difference Is Not the Conflict

Notice what produces these different outcomes. The difference between productive and destructive conflict is not the nature of the underlying disagreement. Two teams can have the same substantive disagreement and produce wildly different outcomes depending on how they engage with it. What makes the difference is the engagement: how the parties communicate, how they listen, how they manage their emotions, how they treat each other, how they understand each other's interests, how they look for common ground, how they let the conflict shape them. The conflict itself is neutral. The engagement is what makes it productive or destructive. That is one of the most empowering things a leader can recognize, because it means that conflict in your team is not a problem to be eliminated. It is a phenomenon to be engaged with skillfully. And the skill of that engagement is something that can be developed.

The Different Faces Conflict Can Wear

Conflict does not always look like an argument. One of the most important things a leader can learn is to recognize the many different faces conflict can wear.

The Obvious Face: Open Disagreement

Two people are clearly at odds. They name the disagreement. They engage with each other about it. Tension is visible. This is the kind of conflict most people picture when they hear the word.

The Quiet Face: Withdrawal

One or both parties go silent. They stop engaging. They withdraw from meetings, conversations, or collaboration. They do the minimum required and no more. This kind of conflict is often invisible to leaders who are only watching for open disagreement, but it is one of the most common forms.

The Polite Face: Surface Civility With Hidden Friction

Both parties remain professionally civil. They do not openly argue. But there is unmistakable tension beneath the surface, visible in tone, body language, and the way they avoid certain topics or each other. This is one of the hardest forms of conflict to address because the surface civility makes it seem like nothing is wrong.

The Indirect Face: Triangulation

Instead of addressing the conflict directly with the other party, one or both parties talk about it with others. They build alliances. They complain to peers. They escalate to leaders without first attempting to engage directly. This pattern can spread conflict across a team without any direct confrontation between the original parties.

The Suppressed Face: Internalized Conflict

One party is in conflict but says nothing. They internalize the friction. They may become resentful, anxious, or disengaged. The other party may not even know there is a conflict. This is one of the most difficult forms because there is no visible signal until the suppressed conflict eventually surfaces, often in unexpected ways.

The Performative Face: Conflict as Display

The conflict is being expressed openly, but the expression is partly performance for an audience. Each party is positioning themselves in front of others. The substance of the conflict matters less than how each party is being seen handling it. This kind of conflict can be hard to resolve because the audience dynamics distort the engagement.

The Eruptive Face: Sudden Escalation

A conflict that has been building beneath the surface suddenly erupts, often over what seems like a small trigger. The intensity of the eruption surprises observers who were not aware of the underlying tension. This pattern often indicates suppressed conflict that has been accumulating.

The Systemic Face: Conflict Built Into the System

Sometimes what looks like interpersonal conflict is actually conflict built into the structure of the team or organization. Misaligned incentives. Unclear boundaries of responsibility. Resource scarcity. Competing goals between teams. When the conflict is structural, addressing it interpersonally produces little because the structure keeps producing the same friction.

The Disposition of a Leader Who Understands Conflict

Understanding conflict is not just intellectual. It produces a particular disposition in the leader. Leaders who understand conflict have a different stance toward it than leaders who do not.

They Are Not Surprised by It

They know that conflict will appear in their teams. They do not treat its appearance as a sign of failure. They expect it as a normal feature of team life and engage with it without panic.

They Do Not Try to Eliminate It

They recognize that conflict cannot be eliminated from a team that is doing real work with real people. Their goal is not zero conflict. Their goal is conflict that is productive, well-engaged, and resolved in ways that strengthen rather than damage the team.

They Distinguish the Different Forms

They recognize that conflicts vary along many dimensions and that different conflicts require different responses. They take the time to understand the specific situation in front of them rather than treating every conflict as the same.

They Engage Rather Than Avoid

They do not pretend the conflict is not there. They do not hope it will resolve itself. They engage with it, sometimes by addressing it directly, sometimes by supporting the parties to address it, sometimes by surfacing the systemic factors that are producing it.

They Are Not Triggered by It

They do not become emotionally activated by the appearance of conflict in ways that compromise their judgment. They can hold their own steadiness while engaging with conflict. That steadiness is one of the most important things they bring to the situation.

They Take the Long View

They recognize that how the team handles this conflict shapes how it will handle the next one. They are building the team's capacity for healthy conflict engagement, not just resolving the immediate situation.

They Care About Both Parties

In most conflicts, both parties have something legitimate they are bringing. Leaders who understand conflict do not take sides reflexively. They engage with the full situation, including what each party is bringing and what the team needs.

They Are Willing to Be Wrong

They recognize that their initial read of a conflict may be incomplete. They are willing to update their understanding as they learn more. They do not lock in early interpretations and defend them against new information.

The Costs of Not Understanding Conflict

To appreciate why understanding conflict matters, it helps to look at the costs of not understanding it.

Practical Workplace Scenario

Scenario

A team lead named Aditi noticed that two of her senior engineers, Rohit and Priya, were no longer working together as well as they had been. Six months earlier, they had collaborated effectively on a major project. Now, when they were in meetings together, they were polite but distant. They rarely spoke directly to each other. When their work touched, they communicated through Aditi rather than directly. Other team members had started to notice. Aditi was not sure what was going on, but she could feel that something was off.

Approach 1: Treating It as a Single Undifferentiated Problem (What Could Have Happened)

Aditi could have approached the situation with a generic "conflict" frame. She could have called Rohit and Priya into a meeting and said, "I think you two are in conflict. We need to resolve it." She could have asked them to discuss what was wrong. She could have pushed for a quick resolution. But without a clear understanding of what kind of conflict was in front of her, her intervention would have been likely to fail. If the conflict was substantive, treating it as relational would have missed the point. If it was hidden, forcing it into the open without preparation might have escalated it. If it was rooted in something systemic, addressing it interpersonally would have produced no lasting change. Aditi would have walked away feeling she had done something, while the underlying situation continued.

Approach 2: Understanding First, Then Acting (What Actually Happened)

Aditi took a different approach. Rather than rushing to intervene, she spent two weeks observing more carefully and having separate one-on-ones with both Rohit and Priya. She asked open questions. She listened for what each of them was actually experiencing. She tried to understand the situation along multiple dimensions before deciding what to do.

What she learned was complex. The substantive layer of the conflict was that Rohit and Priya had disagreed three months earlier about an architectural decision. Rohit had felt that Priya, who had more institutional seniority, had overridden his proposal without genuinely considering it. Priya had felt that Rohit had been pushing too hard for an approach she thought was wrong, and she had felt she had no choice but to make the call. The relational layer was that Rohit had felt unheard. Priya had felt cornered into making a decision under pressure. Both had carried hurt feelings into subsequent interactions without naming them. The systemic layer was that the team's decision-making process was unclear, which had set them up for the conflict by not providing a structure that respected both voices.

Aditi recognized that this was not one conflict. It was three overlapping conflicts. Substantive (the architectural decision), relational (the pattern of communication after the decision), and systemic (the unclear decision-making process). And each layer needed to be addressed differently. She started with the relational layer because the broken communication pattern was preventing any other progress. She facilitated a conversation between Rohit and Priya, helping each of them name what they had experienced and hear what the other had experienced. That conversation took an hour and was uncomfortable, but it produced the beginning of repair. Then she addressed the systemic layer, working with the team to clarify how architectural decisions would be made going forward, with explicit roles for input, debate, and decision. The substantive layer, the original disagreement, became less important once the relational and systemic layers had been addressed.

Result

Three months later, Rohit and Priya were working together again, not just civilly but well. They had developed a stronger working relationship through the work of repairing the broken one. The team's decision-making process had improved. And the experience had taught Aditi something she carried into her future leadership: conflicts often have multiple layers, and skilled engagement requires understanding which layer to address first. She also realized that if she had treated the situation as a single undifferentiated conflict, she would have missed most of what was actually happening.

Learning

The difference between the two approaches was not Aditi's intention. In both cases, she would have been trying to help. The difference was her understanding of what conflict actually is. With a clear understanding, she could distinguish the layers, recognize the different forms, and engage with each one appropriately. Without that understanding, she would have approached the situation as a single problem and likely made it worse. That is what understanding conflict makes possible.

What Is Conflict Checklist

Self-Reflection Questions

Use these questions to think about your own understanding of and relationship with conflict.

1. What is my immediate emotional reaction when conflict appears in my team? Do I tense up, lean in, want to escape?
2. Have I been treating conflict as a sign of failure or as a normal feature of team life?
3. How well do I distinguish conflict from related phenomena like disagreement or discomfort? Have I been over-applying the conflict label?
4. When I look at conflicts in my team, can I identify the substantive, relational, and systemic layers, or have I been seeing them as single undifferentiated problems?
5. What forms of conflict do I tend to miss? Open conflict, hidden conflict, suppressed conflict, systemic conflict?
6. How well do I maintain my own steadiness when conflict appears? What tends to throw me off balance?
7. Have I been suppressing productive disagreement in my team in the name of avoiding conflict? What would change if I welcomed more honest engagement?
8. What conflicts in my current team am I aware of? Which of them am I avoiding rather than engaging with?
9. What conflicts in my current team am I unaware of? What would I need to do to surface what I am not seeing?
10. If I imagined a team that handled conflict skillfully, what would be different about how we engage with each other?

Key Takeaways

• Conflict is the state that arises when two or more people perceive that their interests, perspectives, needs, values, or goals are incompatible and that incompatibility produces friction, tension, or active opposition between them.
• Conflict has four essential dimensions: perceived incompatibility, felt friction, consequences that matter, and some form of opposition. Together they define what makes a situation a conflict rather than something else.
• Conflict is not the same as disagreement, debate, competition, discomfort, personality difference, negative feedback, difficult conversation, or failure. Distinguishing these matters because each requires a different response.
• Conflicts vary along multiple dimensions: substantive vs relational, open vs hidden, brief vs sustained, productive vs destructive, two-party vs multi-party, equal vs unequal power, and cognitive vs affective. Recognizing these dimensions allows leaders to respond to specific conflicts appropriately.
• Every conflict has a recognizable anatomy: parties, issue, underlying interests, positions, emotions, history, context, behavioral pattern, impact, and possible outcomes. Identifying each component helps leaders understand what is actually happening.
• Conflict is not inherently bad. Productive conflict produces better decisions, sharper thinking, stronger relationships, surfaced assumptions, clarified values, renewed engagement, cultural development, and innovation. Destructive conflict produces damaged relationships, decreased trust, avoidance, departures, and waste. The difference is not the conflict but how it is engaged with.
• Conflict wears many faces, including open disagreement, withdrawal, surface civility with hidden friction, triangulation, suppressed conflict, performative conflict, eruptive conflict, and systemic conflict built into the structure of the team or organization. Leaders who only recognize the obvious face miss most of what is happening.
• Leaders who understand conflict develop a particular disposition: not surprised by it, not trying to eliminate it, distinguishing the different forms, engaging rather than avoiding, not triggered by it, taking the long view, caring about both parties, and willing to be wrong.
• The costs of not understanding conflict are significant: avoidance until it is worse, suppression of productive disagreement, mistaken interventions, addressed symptoms instead of causes, leaders getting pulled into the dynamics themselves, lost trust on both sides, cultures of suppression, and burnout.
• Conflicts often have multiple layers: substantive, relational, and systemic. Skilled engagement requires understanding which layers are involved and addressing each appropriately, often starting with the layer that is blocking progress on the others.
• Understanding what conflict is, in all its forms, is the foundation of being able to engage with it skillfully. Without that understanding, conflict becomes a single overwhelming category. With it, conflict becomes a phenomenon that can be recognized, named, understood, and responded to in ways that fit the specific situation in front of you.

Conclusion

Conflict is one of the most consequential phenomena in team life, and one of the most misunderstood. For most leaders, the word carries weight that distorts how they perceive and respond to actual conflicts in their teams. They flinch from it. They avoid it. They treat it as a sign of failure or a problem to be eliminated. And in doing so, they miss the opportunity to engage with conflict as the normal feature of team life that it actually is. The shift that this article has tried to support is the shift from treating conflict as an emergency to treating it as a phenomenon. Something that can be understood. Something that can be recognized in its different forms. Something that can be engaged with skillfully rather than feared.

A leader who understands conflict carries a different orientation into their team. They expect it. They do not panic when it appears. They can distinguish the different forms it takes and respond to each appropriately. They do not suppress productive disagreement in the name of avoiding conflict. They do not overreact to ordinary friction. They engage with hidden conflict rather than ignoring it. They take the long view, recognizing that how the team handles this conflict shapes how it will handle the next. They build the team's capacity for healthy engagement, not just resolution of immediate situations. And they do all of this while maintaining their own steadiness, which is one of the most important things they bring to any conflict in their team.

The most important lesson of this article is this: Conflict in your team is not a sign that something is broken. It is a sign that real people with real differences are working together on something that matters. The question is not whether you can eliminate conflict from your team. You cannot. The question is what kind of conflict will appear, how it will be understood, and what will be done with it. That question is in your hands as a leader. The way you understand conflict, the way you engage with it, the way you support the parties involved, the way you build the team's capacity for healthy engagement, all of these shape what conflict in your team becomes. Done with care, your relationship with conflict can become one of your most important leadership capacities. Done with avoidance or suppression, it can become one of the patterns that quietly undermines your team across years. The choice is not whether to have conflict. The choice is how to be in relationship with it. The rest of this chapter will explore why conflicts happen in teams, what specific kinds of conflict commonly arise, and how to distinguish healthy conflict from unhealthy conflict. But the foundation of all of it is what this article has tried to establish: a clear understanding of what conflict actually is, and a disposition that allows you to engage with it as the normal phenomenon of team life that it is. Carry that understanding into the rest of the chapter. Carry it into your work with your team. And let your relationship with conflict become one of the steady, skillful capacities you offer the people you have the privilege of leading. That is what understanding conflict makes possible. And that is what this article has been preparing you for.