Skip to content
Psy testsUnderstand yourself betterScanMyLoveDecode your relationship

When Team Conflict Is Organizational: Six Patterns to Investigate


Here is my take on “When Team Conflict Is Organizational: Six Patterns to Investigate”. To extend this reflection in a more personal way, I designed the mental rumination test. Unrelated to this theme, I also offer ScanMyLove, a tool that analyses couple conversations from an export. I return to it at greater length in Your Thoughts Don’t Have to Run Your Life.

When tension persists after staff changes, organizational conditions deserve investigation. That does not exclude individual responsibility. Reviewing priorities, resources and decision-making can help identify changes that are within the team’s influence. Understanding Your Attachment Style can complement this reading.

Three signs to investigate an organizational contribution

These observations can support a hypothesis; they still require context.

The tension moves. Somebody leaves, the situation eases for two months, then the same tension reappears — at the same point in the process, on the same subject, with a different person. This is the most decisive sign, and it is only visible with hindsight. It reproduces across different pairs. If three different pairs of people clash over the same object — sign-off, prioritisation, access to a resource — shared constraints may be contributing. It follows a calendar. Tension rises at quarter-end, during reporting week, before each committee. A rhythm may point to a constraint, alongside interpersonal factors.

These signs can be recorded, and they record far better in the exchanges than in memories. The density of messages by period, the channels used, the concentration of exchanges on certain members, the timings: that is what ScanMyJob puts into series, and the team conflict case shown as a reconstructed demonstration — seven participants, thirteen weeks — shows exactly this kind of reading: what share of the exchanges concentrates on two contributors, what share goes through the group channel, at what moments messages fall outside working hours.

The six configurations

1. Contradictory objectives between functions

What it is: two people are assessed on indicators that cannot be met together. Sales on signed volume, delivery on margin; production on lead time, quality on the rework rate; operations on availability, safety on shutdowns. The indicators: the disagreement is always the same, it comes back on every file, and both positions are defensible. Both positions may reflect legitimate but conflicting priorities. What acts on it: clarify objectives or add a shared indicator, alongside attention to how people treat each other; and that is decided above the two people concerned. Bringing them together to "work on their relationship" asks them to resolve between themselves a contradiction the organisation created.

2. The single contested resource

What it is: a skill, a tool, a person, a slot that several people depend on and that cannot serve everyone. A sole expert, a cross-functional developer, a room, a machine, a budget. The indicators: the tension bears on access, not on substance. Requests come earlier and earlier, then more and more insistently, then by roundabout routes. The person who is the resource is often the first to be exhausted, and the last to be seen as concerned. What acts on it: an explicit allocation mechanism — a queue, announced prioritisation, arbitration by a third party — or an increase in the resource. Other support may also be needed. In the absence of a rule, access is settled by relative force, and it produces exactly the behaviours that will afterwards be held against the people.

3. Overlapping remits

What it is: two functions whose boundaries have never been settled. Who answers the client, who signs off, who is informed, who decides in the event of disagreement. The indicators: they are formal before they are verbal. Sign-offs requested twice, documents in parallel versions, meetings called on the same subject by two people, and one recurring sentence: "I wasn't aware of that." What acts on it: a written clarification, with the overlapping areas named and an arbitrator designated for them. Clearer roles can help, though established tensions may also need follow-up.

4. The absence of decision-making

What it is: decisions are not taken, or are taken and then reopened. The team then has to renegotiate permanently what ought to be settled. The indicators: the same subjects come back to meetings without conclusion; decisions circulate orally and contradict one another; people build up proof of what was said. That last point is very characteristic: when a team archives systematically, it is because it cannot rely on what is decided. What acts on it: a record of decisions, written, dated, with a name attached. It is the simplest remedy on the list and one of the most effective. It may require discussion about authority and accountability.

5. Workload

What it is: the volume of work is lastingly greater than what the team can absorb. Every request then becomes an aggression, not out of malice but by arithmetic. The indicators: tension rises with the load and falls with it; requests are refused before they have even been read; messages go out beyond working hours; mutual help, which is the first indicator of a team doing well, is the first thing to disappear. What acts on it: review demands, staffing and priorities, while addressing harmful behavior. If sleep, health or recovery are affected, seek healthcare support. Occupational health access and confidentiality arrangements vary by country and employer; check local options rather than assuming French procedures apply in the United States.

6. Instability of composition

What it is: arrivals and departures follow one another, and the team never gets past the stage at which implicit rules stabilise. The frame that can help: Tuckman’s stages are a descriptive model, not a fixed sequence every team follows. A change in membership may prompt renegotiation of roles, but does not predict an automatic return to a stage or resolution within months. The indicators: consider when tension began, what changed, and whether clearer responsibilities help. Do not dismiss persistent harmful conduct as a normal stage. What acts on it: making the rules explicit instead of waiting for them to be passed on. A team that changes often cannot run on the implicit.

What team research adds

Two contributions are worth knowing, because they shift the way you look.

Psychological safety. Edmondson’s 1999 study of 51 work teams in one manufacturing company found an association between psychological safety and learning behavior. This supports attention to whether people can raise questions and mistakes; it does not establish that safety universally predicts performance better than competence.

The marker is simple and can be checked: the last time somebody got something wrong, did they say so themselves, or was it discovered?

The cascade of dysfunctions. Patrick Lencioni offers a practitioner model, not a demonstrated universal causal law. He describes a chain that repays reading backwards: inattention to collective results comes from avoidance of accountability, which comes from lack of commitment, which comes from fear of conflict, which comes from absence of trust. A team in which nobody ever contradicts anyone in a meeting is not a team at peace — very often it is a team in which disagreements are handled elsewhere.

Who can do what

A team member can do three things, and they are not negligible. Describe the configuration instead of designating a person — "requests from department X reach both of us with no priority set" rather than "he takes everything". Document the regularity, which can help a manager understand the pattern. And take the question forward as an organisational request, while also reporting any specific harmful conduct. A manager can act on five of the six configurations: remits, decision-making, resource allocation, explicit rules, and — partly — workload. The approach has to be prepared, and the first step is always the same: check whether the tension moves, reproduces, or follows a calendar. The level above may have authority to change the first configuration — contradictory objectives between functions — and it is the one that wears people down longest, precisely because the team may lack authority to change those targets directly.

To take stock of what the situation is costing you and of your way of approaching collective tensions, the tests on the platform are available, and the assistant can help you word a description of a configuration before taking it forward.

Three things this article does not do

It does not say that nobody is involved. Individual behaviours exist and they count. What it argues is that the three signs should be checked before concluding — because getting the cause wrong costs a departure for nothing. It does not describe anyone. The six configurations describe properties of an organisation, not characteristics of team members. That is what makes them treatable. It characterises nothing. Some situations belong to other circuits — employee representatives, occupational health doctor, HR, a lawyer. Assessing them belongs to a court, not to an article.

Sources and scope

In brief: Team tension can reflect organizational conditions as well as individual behavior. Six configurations below offer starting points for investigation, not a diagnosis. Look for recurring patterns, document their context, and consider responsibilities at several levels without overlooking bullying or discrimination.
Gildas Garrec, CBT practitioner

About the author

Gildas Garrec · CBT practitioner

Author of books and articles on applied psychology and relationships.

Was this article helpful?

Join our exchange community on WhatsApp

Join the Community (waiting list)