Managing team conflicts in practice

When a meeting ends in silence, sarcastic comments, or decisions that no one seems to really support, the problem isn't always the disagreement. It's often the way the team handles it. Managing team conflict isn't about eliminating all tension. It's about separating useful disagreement from relationship-damaging disagreement and bringing the conversation back to shared decisions. In this article, you'll see why conflicts arise, what signs need early intervention, and how a manager or executive can operate with clarity, composure, and practical boundaries.

Why conflicts aren't always a problem

A team that never disagrees may not be harmonious. It may simply avoid difficult issues. Disagreement over priorities, timelines, resource allocation, or professional judgments can improve the quality of a decision because it brings to the surface facts and alternatives that would otherwise be left out of the discussion.

The critical distinction is between conflict over the task and conflict over the person. The former may be about “which solution best serves the goal?” The latter quickly shifts to “I can’t work with you” or “you always undermine my work.” Research shows that relationship conflict is consistently associated with lower performance and less satisfaction in the team, while the impact of disagreement over the task depends on the context and the way the discussion is conducted (De Dreu & Weingart, 2003).

For an executive, then, the goal is not to become the peacemaker in every difficult moment. It is to create the conditions so that the disagreement remains specific, controllable, and solution-oriented. Research shows that conflict within a team isn't automatically negative — it depends on whether it concerns the task itself or the relationships between members (Jehn, 1995).

The first signs that are not worth ignoring

Most teams don't suddenly reach a serious rift. There are small patterns that, if left unaddressed, become the new way of working together. In meetings, this is evident when two people systematically interrupt each other, when decisions are constantly being reworked, or when the real disagreement is transferred to private messages after the meeting.

Another signal is vague language. Phrases like “there’s no communication,” “the other department isn’t helping,” or “some people aren’t taking responsibility” sound serious, but they don’t describe behaviors that can be changed. The more general the conversation, the more assumptions about intent increase.

Also watch out for withdrawal. It is not expressed only in tension. It can appear as passive acquiescence, delays, minimal participation, or the “whatever you say” of a capable collaborator who has stopped believing that his or her point of view will be heard. A sense of psychological safety—that one can speak up, ask a question, or point out a mistake without humiliation—is associated with learning and group effectiveness (Edmondson, 1999).

Managing team conflicts: start with the facts

When tension has already arisen, the first trap is hasty attribution of blame. “Whose fault is it?” may seem like a natural question, but it rarely leads to useful cooperation. It is more effective to start with a shared description of what happened.

Instead of “Mary is not cooperating,” try: “On the last two deliveries, the specifications changed after the work started and the sales team was not informed.” The second wording doesn’t deny the problem. It does, however, make it debatable. From there you can ask: What decision was delayed? What information didn’t arrive? Who had the final say?

This shift from interpretation to observable fact reduces defensiveness. It doesn't mean there aren't personal repercussions or difficult behaviors. It means you first build common ground before you demand accountability.

Make room for different perspectives, not personal attacks

A good conflict discussion needs clear context. Ask each person involved to talk about three things: what they noticed, how it affected the work, and what needs to be done differently going forward. This structure helps avoid absolute judgments like “always” and “never.”

As a facilitator, you can intervene with calm, specific phrases: “Let’s stick to the specific incident,” “What would better communication mean in practice?” or “I’m hearing two different risk assessments. What data will help us decide?” You are not taking sides in favor of the strongest or most persuasive speaker. You are protecting the quality of the process.

There are, of course, cases where a joint discussion is not the right first step. If there is intense disparagement, repeated interruption, or a very charged history, brief individual discussions can reduce tension and prepare for a more productive meeting. Transparency remains essential: individual conversations should not become a field of alliances or backroom.

From discussion to employment agreement

A conflict is not resolved because everyone has spoken. It has moved forward when the team agrees on specific behaviors, responsibilities, and recheck points. The intention to “communicate better” is positive, but it is not enough. It needs to be translated into operational decisions.

For example, a team might agree that priority changes are confirmed in writing by a specific person, that scope disagreements are discussed before work is assigned, and that each weekly meeting ends with an owner, deadline, and completion criteria. These small agreements reduce the need for constant interpretations.

It is useful to also set a review date. Not as a threat, but as a reality check: “In two weeks we will see if the new process has reduced delays and what needs to be adjusted.” Accountability without control becomes wishful thinking. Control without a willingness to adapt becomes bureaucracy.

The executive's personal management amidst tension

Your own reaction disproportionately affects the group. If you respond defensively, ironically, or with hasty decisions, you signal that tension is dangerous. If, on the other hand, you try to accommodate everything and do not set boundaries, you may be allowing aggressive behavior to dominate.

Before you intervene, take a short pause and separate the event from your thoughts about it. The thought “I’m being questioned” may be understandable, but it’s not necessarily the only given. Ask yourself: “What is the goal of this conversation? What needs to be said clearly? What boundary needs to be set?” This small process is linked to basic emotion regulation skills, which help us choose a response rather than acting impulsively (Gross, 2015).

Assertiveness here does not mean harshness. It might sound like this: “I accept that there is disagreement about the decision. But we will not continue with characterizations. Let’s return to the criteria we will use.” The message is both clear and respectful.

When is external support needed?

If the same conflict recurs despite agreements, if trust has eroded, or if a manager feels trapped between opposing sides, external support can provide useful space for reflection. Through mentoring or coaching with CBT tools, an executive can examine their automatic interpretations, prepare for difficult conversations, and practice more effective interventions.

The value doesn’t lie in a “perfect” speech. It lies in being able to recognize recurring patterns, regulate tension, and guide the team toward clear agreements. Every conflict is an opportunity to make the way you work together more visible—and to change it before the costs become greater.

Bibliographic references

De Dreu, CKW, & Weingart, LR (2003). Task versus relationship conflict, team performance, and team member satisfaction: A meta-analysis. Journal of Applied Psychology, 88 (4), 741-749.

Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44 (2), 350-383.

Gross, JJ (2015). Emotion regulation: Current status and future prospects. Psychological Inquiry, 26 (1), 1-26.

Jehn, KA (1995). A multimethod examination of the benefits and detriments of intragroup conflict. Administrative Science Quarterly, 40 (2), 256-282.