Monday morning, the stand-up has already been running fifteen minutes longer than it should. Marta, a senior in the team, publicly questions Kamil’s architectural decision, citing a previous project that ended with delays. Kamil responds defensively — he raises his voice, accuses Marta of not trusting his competence. The rest of the team sits silently, staring at their screens. The Scrum Master tries to diffuse the tension by changing the subject, but after the meeting the atmosphere is so thick you could cut it with a knife. Two people don’t speak to each other for the rest of the day. Three team members discuss the situation on a private channel. No one addresses the problem directly.
This scene — or its variants — plays out daily in thousands of teams. Workplace conflicts are not an anomaly. They are a natural consequence of different people, with different experiences, perspectives, and priorities, trying to achieve goals together. The problem never lies in the fact that conflict appeared. The problem lies in how — or whether at all — it gets resolved.
Research by CPP Global (publisher of the Thomas-Kilmann tool) shows that employees spend an average of 2.8 hours per week dealing with conflicts. That’s the equivalent of one working day per month lost not to creating value, but to managing tension that could have been resolved faster and more effectively. In this article, you will find concrete tools, models, and techniques that will allow you to turn destructive conflicts into opportunities for team development.
Quick Navigation
What you will learn from this article:
- What are the main types of team conflicts and why distinguishing them is crucial for choosing a resolution strategy
- How to identify the true causes of conflicts — from value differences to unclear roles and communication gaps
- Five conflict resolution styles according to the Thomas-Kilmann model — when to use each one and what consequences they carry
- How to conduct mediation step by step — from preparation, through conversation, to implementing agreements and follow-up
- Communication techniques that de-escalate tension — Nonviolent Communication (NVC), active listening, paraphrasing, and “I” statements
- How to build a team culture where conflicts are resolved constructively before they escalate into crises
What Exactly Is Team Conflict
Before we move on to resolution tools, it’s worth organizing the concept itself. Team conflict is a situation in which at least two people (or groups of people) perceive their goals, values, needs, or interests as mutually contradictory. The key word is “perceive” — we’re not always dealing with real contradiction. Often conflict stems from misinformation, misinterpretation of intentions, or lack of space to clarify the other party’s perspective.
Not every conflict is bad. Research by Karin Jehn from the Wharton School of Business showed that task conflicts — concerning how work is executed, priorities, or strategy — can positively affect the quality of team decisions, provided they are managed in an atmosphere of respect. The problem begins when task conflict turns into relationship conflict — personal, emotional, attacking the identity or competence of the other person. This type of conflict almost always reduces team effectiveness and spoils the atmosphere.
There’s also a third type — process conflict — concerning who is responsible for what, what the workflow looks like, and who makes decisions. In organizations with unclear role structures, this type appears most often and can be the most frustrating, because people feel lost in responsibility.
Distinguishing these three types is not an academic exercise. It’s the foundation of effective intervention. Task conflict requires a different strategy than relationship conflict, and process conflict — yet another. A leader who treats every dispute identically wastes time and deepens the problem.
Causes of Conflicts — Beneath the Surface
The most common mistake in conflict resolution is addressing symptoms instead of causes. Marta and Kamil are arguing about architecture? Maybe. But maybe the real problem is that Marta feels excluded from the decision-making process because Kamil consulted the solution exclusively with the Tech Lead. Or Kamil is worried that his position in the team is threatened because Marta has more experience and is listened to more often.
Here are the most common deep causes of team conflicts:
Unclear roles and responsibilities. When two people believe a given area belongs to them, or — conversely — no one feels responsible, friction is inevitable. In IT teams, this problem often appears at the intersection of roles: who decides about architecture? Who approves technology choices? Where does the developer’s responsibility end and the DevOps’s begin?
Differences in values and priorities. One person values speed of delivery, another — code quality. One prioritizes innovation, another stability. Both are right in their context, but without agreeing on common priorities, collision is a matter of time.
Communication deficits. People don’t say directly what they need. They assume intentions are obvious. They interpret silence as agreement and questions as attack. In distributed teams where most communication happens through text, the risk of misunderstandings multiplies. It’s worth reaching for proven techniques in such situations — you can find more about this in the article on team communication.
Uneven workload distribution. When one person regularly takes on more than others — and it’s not appreciated or compensated — frustration builds up, which eventually explodes. Often not about workload, but at a completely different occasion.
Lack of psychological safety. In teams where people are afraid to speak openly about problems, conflicts don’t disappear — they go underground. They escalate in the form of passive aggression, gossip, avoiding cooperation. Amy Edmondson from Harvard has repeatedly shown that teams with high psychological safety don’t avoid conflicts — they learn to resolve them openly and quickly.
Stress and external pressure. Deadlines, business pressure, job insecurity — these factors lower tolerance for frustration and cause minor friction to turn into serious conflicts. People react disproportionately to the situation because their emotional “buffer” is depleted.
Five Conflict Resolution Styles — The Thomas-Kilmann Model
In the 1970s, Kenneth Thomas and Ralph Kilmann developed a model of five conflict management styles. The model is based on two axes: assertiveness (how much I strive to realize my own needs) and cooperativeness (how much I consider the other party’s needs). Each style has its application — none is universally good or bad. The key is conscious choice of a style appropriate to the situation.
| Style | Assertiveness | Cooperativeness | When to Use | Risk |
|---|---|---|---|---|
| Competing | High | Low | Crisis situations, decisions requiring quick action, defending core values | Deterioration of relationships, resistance from the other party, conflict escalation |
| Avoiding | Low | Low | Matter is trivial, emotions are too intense for rational conversation, you need time | Problem doesn’t go away, frustration builds, loss of trust |
| Accommodating | Low | High | Matter is more important to the other party, you want to build goodwill, you realize you’re wrong | Feeling used, loss of influence, growing resentment |
| Compromising | Medium | Medium | Both parties have equal power, quick solution needed, goals are moderately important | No one is fully satisfied, solution may be suboptimal |
| Collaborating | High | High | Both relationship and outcome are important, there’s time to thoroughly examine the problem, matter is complex | Time-consuming, requires high communication competencies from both parties |
Competing — striving to realize one’s own goals at the expense of the other party. In everyday team work, this style is rarely constructive. However, it works in crisis situations when a decision must be made immediately and there’s no time for discussion. A leader who says “we’re doing it this way, no discussion” during a production outage — is using competing and doing so correctly.
Avoiding — withdrawal from conflict. This isn’t always weakness. Sometimes emotions are too intense to conduct a constructive conversation. Saying “let’s come back to this in an hour when we’ve cooled down” is strategic avoidance, not cowardice. However, chronic avoidance — systematically skirting difficult topics — is one of the most common reasons conflicts in teams escalate to crisis level.
Accommodating — sacrificing one’s own needs for the other party. Useful when the matter really is more important to the other person, or when maintaining the relationship is a priority. The risk? A person who always accommodates will sooner or later explode or withdraw emotionally.
Compromising — both parties give up part of their expectations. Quick, pragmatic, but rarely optimal. Compromise is “fifty-fifty” — and sometimes means both parties are equally dissatisfied.
Collaborating — jointly seeking a solution that considers both parties’ needs. Most often leads to the best results, but requires time, goodwill, and communication competencies. In teams that regularly practice collaboration, conflicts become a driver of innovation instead of a source of destruction.
It’s worth emphasizing: most people have a dominant style they use habitually. Recognizing one’s own pattern is the first step toward more conscious conflict management. A leader should know their people’s dominant styles — this allows predicting the dynamics of a dispute and better selecting intervention.
Mediation Step by Step — How to Conduct a Difficult Conversation
When conflict requires intervention from a third party — a leader, Scrum Master, HR Business Partner — structured mediation is needed. Here’s a proven six-step process.
Step 1: Preparation. Before the meeting, speak separately with each party. The goal is not to judge who’s right, but to understand each person’s perspective. Ask: “How do you see this situation?”, “What do you need to resolve this?”, “What would be an acceptable outcome for you?”. Gather facts — not opinions about the other party’s intentions.
Step 2: Establishing rules. At the beginning of the joint meeting, clearly define the rules: everyone speaks without interruption, we talk about behaviors — not character traits, the goal is resolution — not winning. Clearly state that your role is moderating, not arbitration.
Step 3: Hearing both parties. Each person presents their perspective without interruption. After each statement — paraphrase to make sure you understand correctly: “Do I understand correctly that you feel excluded from the decision-making process and that’s the main source of your frustration?”.
Step 4: Identifying common ground. Look for points where both parties agree. There’s almost always a higher-order common goal: “You both want the project to succeed”, “You both care about code quality”. Articulating common ground changes the dynamic from “me versus you” to “us versus the problem”.
Step 5: Jointly developing a solution. Don’t impose ready-made solutions. Ask both parties: “What could we do differently so this situation doesn’t repeat?”. Encourage generating many options. Let the parties choose a solution both agree on. Write down the arrangements.
Step 6: Follow-up. Schedule a control meeting in a week or two. Check if arrangements are being implemented. Ask if the situation has improved. If not — return to step three. Mediation is a process, not a one-time event.
Communication Techniques That De-escalate Conflicts
The most effective conflict resolution tools are not procedures — it’s the way people talk to each other. Here are four techniques worth teaching teams.
Nonviolent Communication (NVC). Marshall Rosenberg’s model is based on four elements: observation (facts without judgment), feeling (what I feel), need (what I need), request (what specifically I’m asking for). Instead of “You never consult me on technical decisions” — “At the last meeting, the framework choice decision was made without inviting me to the discussion (observation). I feel excluded (feeling), because I care about having influence on key technical decisions in the project (need). Can we agree that with such decisions we will consult with the whole team? (request)”. NVC sounds artificial on paper, but in practice it radically changes the tone of conversation. If you want to delve deeper into this topic, I recommend the article on conflict management with NVC.
Active listening. Most people don’t listen — they wait for their turn to speak. Active listening means: full focus on the speaker (put down the phone, close the laptop), paraphrasing (“Do I understand correctly that…”), asking deepening questions (“Tell me more about…”), reflecting emotions (“I see this situation frustrates you”). When someone feels truly heard, the tension level drops by half before you even get to a solution.
“I” statement instead of “you”. “You always…” and “You never…” are the fastest path to escalation because they trigger defense mechanisms. The “I” statement shifts focus to one’s own experience: “I feel frustrated when decisions are made without my input” instead of “You ignore me”. It’s a subtle but fundamental shift in perspective. You can find more about this technique, in the context of setting boundaries, in the article on assertiveness in practice.
The LATTE technique (Listen, Acknowledge, Take action, Thank, Explain). Simple but effective structure for responding to a complaint or grievance: listen, acknowledge the other person’s feelings, propose action, thank for raising the topic, explain next steps. Starbucks uses this technique in barista training — it works equally well in project teams.
The Leader’s Role in Conflict Management
The team leader doesn’t have to be a mediator — but must create conditions in which conflicts are resolved, not swept under the rug. This requires several key competencies and attitudes.
Normalize conflict. Teams where the leader openly says “difference of opinion is natural and valuable” move faster from friction to resolution. A leader who avoids confrontation at all costs teaches the team that problems must be hidden.
React early. Most serious conflicts start from minor tensions that are ignored. A leader who notices a change in dynamics — someone stops speaking up in meetings, two people avoid cooperating, someone systematically undermines someone’s ideas — should react before the situation escalates. A simple conversation “I noticed it hasn’t been easy between you lately. Do you want to talk?” can prevent weeks of building tension.
Don’t take sides. This is the hardest part. Even when internally you agree with one party, your role is moderating the process, not passing judgment. If you must make a decision — explain its logic and give the other party space to express disagreement.
Model behaviors. If you yourself react defensively to criticism, don’t expect openness from the team. If you avoid difficult conversations, don’t be surprised that your people do the same. A leader who can say “I was right about X, but wrong about Y, I apologize” — builds a culture where admitting mistakes is not weakness.
Build team competencies. Conflict resolution is a skill that can be trained. Investment in training the team in communication, mediation, and emotion management pays off many times over. Teams that have undergone such training resolve conflicts faster, with lower emotional cost, and with better outcomes.
Prevention — How to Prevent Escalation
The best conflict is one that doesn’t escalate. Here are strategies that minimize the risk of destructive disputes.
Clear roles and responsibilities. Use a RACI matrix (Responsible, Accountable, Consulted, Informed) for key processes and decisions. When everyone knows who’s responsible for what — and who has the right to decide — you eliminate the biggest source of process friction.
Regular retrospectives. Meetings where the team openly discusses what works and what doesn’t — are a safety valve. Problems expressed at retro don’t accumulate to the point of explosion. Condition: retro must be a safe space where no one is punished for honesty.
Team contract. At the beginning of a project or team formation, establish common rules: how do you make decisions? How do you communicate disagreement? What do you do when someone feels excluded? A contract written and accepted by everyone is a reference point in difficult moments.
One-on-ones. Regular conversations between the leader and each team member — not about project status, but about well-being, challenges, and relationships — allow catching tensions at an early stage.
Diversity of work styles. Help the team understand that differences in work style (e.g., introversion vs extroversion, planning vs improvisation, detail vs big picture) are not flaws — they’re resources. Tools like MBTI, DISC, or Insights allow naming differences in a neutral way and finding value in them.
Feedback culture. Teams that regularly give each other feedback — positive and constructive — build communication muscles that come in handy during conflict moments. Feedback shouldn’t be reserved for annual reviews. It should be part of daily culture.
How EITT Supports Competency Development in Conflict Management
Conflict resolution is a competency that requires both theoretical knowledge and intensive practice in a safe environment. Training in conflict management, NVC communication, mediation, or assertiveness is among the most sought-after topics in development programs for leaders and teams.
EITT — with over 500 experts in the training network, experience from over 2500 conducted trainings, and an average participant rating of 4.8/5 — offers training that combines solid theoretical foundations with intensive workshop practice. EITT’s communication and conflict management programs are based on simulations, case studies, and exercises with real feedback — participants not only learn the Thomas-Kilmann model or NVC technique but practice them in controlled scenarios similar to everyday situations in their organizations.
EITT trainings in this area include, among others: team conflict management, managerial communication, Nonviolent Communication for leaders, organizational mediation, and building psychological safety. Programs are adapted to industry specifics and participant levels — leaders in a software house face different challenges than those in a financial corporation, and yet different ones in a public organization.
If your team struggles with escalating tensions, chronic avoidance of difficult conversations, or dispute escalation — conflict management training may be one of the best investments in your development budget.
Summary
Conflicts in teams are not a sign of dysfunction. They are a sign that different people are engaged in their work and have expectations about it. Dysfunction is ignoring them, suppressing them, or resolving them solely through authority.
Effective conflict management requires three things: awareness (understanding types of conflicts, their causes, and one’s own reaction patterns), tools (Thomas-Kilmann model, NVC techniques, mediation structure, “I” statements), and culture (psychological safety, regular feedback, clear rules, and a leader who models openness).
None of these things appear on their own. Each requires conscious work — individual and team-based. But the results are worth the effort. Teams that have learned to constructively resolve conflicts make better decisions, build stronger relationships, and — paradoxically — experience fewer destructive disputes because problems are addressed promptly before they grow to crisis proportions.
Instead of fearing conflict, teach your team to resolve it. It’s one of the most valuable skills you can give them.
Read also
- Meeting Moderation and Mediation: Effective Collaboration and Conflict Resolution
- Team Conflict Management
- Building Effective Communication in a Team
Develop your skills
Want to deepen your knowledge in this area? Check out our training led by experienced EITT instructors.
➡️ Conflict management - resolution and mediation techniques — EITT training
Frequently Asked Questions
Are all team conflicts harmful to productivity?
No. Research by Karin Jehn from the Wharton School shows that task conflicts — disagreements about how work should be executed, priorities, or strategy — can actually improve the quality of team decisions when managed in an atmosphere of respect. The harmful type is relationship conflict, which becomes personal and attacks the identity or competence of individuals, almost always reducing team effectiveness.
What is the Thomas-Kilmann conflict resolution model?
The Thomas-Kilmann model identifies five conflict management styles based on two axes: assertiveness and cooperativeness. The five styles are competing, avoiding, accommodating, compromising, and collaborating. No single style is universally best — effective conflict management requires consciously choosing the appropriate style based on the situation, the importance of the outcome, and the value of the relationship.
How much time do employees typically lose to workplace conflicts?
According to research by CPP Global, employees spend an average of 2.8 hours per week dealing with conflicts, which is equivalent to approximately one full working day per month. This time is spent not on creating value but on managing tension that could often be resolved faster and more effectively with proper tools and techniques.
What is the single most important thing a team leader can do to prevent destructive conflicts?
The most impactful action is to normalize conflict by openly stating that differences of opinion are natural and valuable, while simultaneously reacting early to minor tensions before they escalate. Leaders who model openness, respond to subtle changes in team dynamics, and create psychological safety enable their teams to address issues constructively rather than letting them fester underground.