“How do you handle conflict between two team members?”
What the interview question doesn’t tell you, and what psychology, philosophy, and organisational science do
Most organisations treat conflict like a burst pipe. Something has gone wrong, someone needs to fix it fast, and the goal is to get back to normal as quickly as possible. Bring in HR. Have the difficult conversation. Move people to different teams if you have to. Patch the leak.
This instinct is understandable, but it misses something fundamental. Conflict doesn’t appear out of nowhere. It surfaces because something underneath is unresolved: competing values, unclear expectations, unmet needs, a power dynamic nobody has named, or simply two people with genuinely different views on what good looks like. Treat the symptom without understanding the cause, and the conflict will come back. Usually louder.
The first shift worth making is conceptual. Conflict is not the opposite of a healthy team. Avoidance is. A team where nobody ever disagrees is not a harmonious team. It’s a team where people have learned that expressing disagreement is unsafe or pointless. That is a much more serious problem, because it’s invisible.
Patrick Lencioni, in his work on team dysfunction, placed absence of trust at the very base of what makes teams fall apart. But trust here doesn’t mean “we all get on well.” It means psychological safety: the shared belief that you can speak honestly without being punished for it. Prof. Amy Edmondson at Harvard has spent decades studying this, and the research is consistent. Teams with high psychological safety don’t avoid conflict. They have more of it. What they’re better at is making it productive.
So the question isn’t how to remove conflict from a team. The question is how to raise the quality of it.
The three patterns underneath most team conflicts
Underneath most team conflicts, if you look closely enough, you’ll find one of a small number of recurring patterns.
The first is competing legitimate goods. Two people are both right, but they’re optimising for different things. The engineer wants to do it properly; the product manager wants to ship it now. The team lead wants consistency; the senior developer wants autonomy. Neither of them is wrong. They’re just prioritising different values that are genuinely in tension. Aristotle would have called this a problem of phronesis, practical wisdom: knowing not just what is good, but how to navigate situations where several good things pull in different directions. Resolving this kind of conflict requires surfacing both sets of values explicitly and deciding together which one takes precedence in this context. That’s not a compromise. It’s a choice made consciously.
The second pattern is attribution asymmetry. We judge ourselves by our intentions, but we judge others by their behaviour. I was blunt because I was under pressure. You were blunt because you don’t respect me. This cognitive bias, well documented in social psychology, turns interpersonal friction into moral judgement faster than almost anything else. Once someone has been labelled as difficult, dismissive, or political, the label tends to stick, and the actual content of the disagreement gets buried under a layer of personal narrative. The antidote is perspective-taking: a genuine attempt to understand what the other person is trying to accomplish, and what pressures they’re navigating. This sounds obvious. It’s surprisingly rare in practice.
The third pattern is structural conflict. This is the one teams most often misdiagnose as personal. Two people seem unable to get along, but actually their roles are set up in a way that makes them adversarial. They’re rewarded for different things, they answer to different people, and the organisation has never clearly decided who owns what. Chris Argyris called this “organisational defensive routines”: the ways in which the system itself generates stress and then buries the evidence. You can coach both individuals to within an inch of their lives and it won’t help, because the conflict is in the structure, not in the people.
Behind every accusation, there is an unmet need
Marshall Rosenberg’s Nonviolent Communication framework offers one of the most practically useful lenses for working through interpersonal conflict. Its core insight is that behind every accusation, there is an unmet need. When someone says “you never listen to me,” they’re not really talking about listening. They’re expressing something about recognition, respect, or belonging. When someone says “this team has no standards,” they’re usually expressing a need for quality, predictability, or professional pride.
NVC asks you to separate observations from interpretations, and to connect behaviour to feelings and needs rather than to character judgements. It sounds clinical when described, but in practice it does something powerful: it shifts conversations from blame to need, which is the only terrain on which genuine resolution becomes possible. You can argue forever about who did what. It’s much harder to dismiss someone’s need once it’s been clearly named.
The philosopher Jürgen Habermas wrote about what he called the ideal speech situation: a conversation in which all parties have equal standing, speak honestly, and are open to being persuaded by the better argument rather than by power or status. It’s utopian, obviously. But it’s useful as a direction to aim in. The question it generates is practical: what would need to be true for this conversation to be one where the best idea wins, rather than the loudest voice or the highest rank?
The drama triangle and why nobody moves forward
The drama triangle, originally described by Stephen Karpman in the 1960s, is worth knowing because it describes a pattern that plays out in teams with almost mechanical regularity. It involves three roles: the persecutor, the victim, and the rescuer. They seem like fixed identities, but they’re not. People shift between them constantly, often within a single conversation. The manager who’s trying to protect their team member (rescuer) becomes the person creating dependency (persecutor). The colleague who feels unfairly treated (victim) becomes the one sabotaging decisions (persecutor). The rescuer feels righteous; the victim feels justified; the persecutor feels either powerful or vindicated. Nobody is moving forward.
The way out of the drama triangle, according to David Emerald’s reframing of it, is to shift from reactive to creative: from “what’s wrong and who’s to blame” to “what do we want and what can we do.” This isn’t about being positive. It’s about redirecting agency. Conflict locks people into a past-oriented, causal story. Resolution requires a future-oriented, intentional one.
The leader’s real job is not to resolve conflict but to contain it
The leader’s role in all of this is often misunderstood. Many leaders believe their job is to resolve conflicts: to step in, assess the situation, and hand down a decision. This sometimes works in the short term. What it teaches the team is that conflict is the leader’s problem to solve, not their own capacity to develop. Over time, it creates a team that escalates rather than resolves, and a leader who is permanently stuck in the middle.
A more useful frame, drawn from systemic coaching and family systems theory, is the leader as container. The job is not to eliminate tension but to create conditions in which the team can sit with tension long enough to understand it. This requires a specific kind of confidence: the ability to resist the pull towards premature resolution. Ronald Heifetz at Harvard Kennedy School distinguishes between technical problems, which have known solutions that someone with expertise can apply, and adaptive challenges, which require the people involved to change how they think. Most team conflicts are adaptive. They can’t be solved by the leader implementing the right answer. They require the team to work through something together.
This is why the most important thing a leader can do in a moment of conflict is often not to solve it, but to slow it down. Ask questions rather than provide answers. Name what’s happening without taking sides. Make the implicit explicit. Create enough safety for people to say what they actually think.
Conflict prevention happens in ordinary moments, not just critical ones
There’s a strand of sociology, particularly in the work of Randall Collins on interaction ritual chains, that points to something teams rarely discuss: the emotional energy in a room. When people feel seen, included, and engaged, they generate positive emotional energy that makes collaboration easier. When they feel marginalised, ignored, or dismissed, they generate negative emotional energy that makes everything harder. This isn’t soft. It’s how groups actually work. Social identity theory, developed by Henri Tajfel and John Turner, shows how quickly people sort themselves into in-groups and out-groups, and how much of team conflict is actually about belonging rather than the ostensible subject of the disagreement.
What this means practically is that a lot of conflict prevention happens not in the difficult moments but in the ordinary ones. Whether you notice someone’s contribution in a meeting. Whether you ask about someone’s view before the decision is made. Whether you check in with the quieter members of the team, not just the loudest. These small acts of inclusion or exclusion accumulate over time and determine whether people feel invested in the team’s success or quietly estranged from it.
When conflict genuinely cannot be resolved
None of this is to say that all conflicts can be resolved by better communication and more empathy. Sometimes values are genuinely incompatible. Sometimes people are acting in bad faith. Sometimes the problem really is that two people cannot work together, and the most honest thing to do is acknowledge that rather than keep pretending otherwise.
The Stoics were clear about what lies within our control and what doesn’t. You can change how you communicate, what you invite, what you model, what structures you put in place. You cannot change another person’s willingness to engage. At some point, continued investment in a conflict that the other party is not interested in resolving becomes a form of self-deception.
But that point comes much later than most people think. The vast majority of team conflicts that get written off as irresolvable have actually never been properly named, never had the structural conditions examined, never had someone ask sincerely what each person actually needs. They’ve had plenty of difficult conversations in which two people talked past each other while the real issue stayed underground.
What to actually do
If I had to distil this into something actionable, it would be this.
Start by assuming the conflict is information. Ask what it’s telling you about values, needs, structures, or dynamics that haven’t been made visible yet. Resist the pull towards fast resolution. Create conditions where people can speak honestly without penalty. Separate the people from the positions and try to understand the interests underneath. Name what’s happening, including the things that feel uncomfortable to name. Ask whose voices are missing from the conversation.
And remember that a team capable of navigating conflict well is not a team that has achieved some kind of permanent peace. It’s a team that has developed the muscle to disagree, recover, and keep going together. That muscle is one of the most valuable things a team can have. It doesn’t come from avoiding conflict. It comes from doing it better, over and over, until it stops feeling like a threat and starts feeling like work.
References
Patrick Lencioni — The Five Dysfunctions of a Team (2002)
Amy Edmondson — The Fearless Organization (2018); “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly (1999)
Aristotle — Nicomachean Ethics, on phronesis (practical wisdom)
Chris Argyris — Overcoming Organizational Defenses (1990)
Marshall Rosenberg — Nonviolent Communication: A Language of Life (2003)
Jürgen Habermas — The Theory of Communicative Action (1981)
Stephen Karpman — “Fairy Tales and Script Drama Analysis,” Transactional Analysis Bulletin (1968)
David Emerald — The Power of TED (2009)
Ronald Heifetz — Leadership Without Easy Answers (1994); The Practice of Adaptive Leadership (2009, with Linsky and Grashow)
Randall Collins — Interaction Ritual Chains (2004)
Henri Tajfel and John Turner — “An Integrative Theory of Intergroup Conflict,” in The Social Psychology of Intergroup Relations (1979)
Epictetus — Enchiridion, on the dichotomy of control