Introduction

I think conflicts are one of the most misunderstood aspects of teamwork.

Especially in the IT industry.

Many people unconsciously assume that healthy teams should avoid conflicts completely.

But honestly — I don’t think this is realistic.

Or even healthy.

Because wherever:

•  different personalities,

•  different perspectives,

•  pressure,

•  ambitions,

•  deadlines,

•  emotions,

•  and communication styles

meet together, friction naturally appears.

And friction itself is not necessarily bad.

In fact, complete absence of conflict may sometimes signal:

•  emotional disengagement,

•  lack of honesty,

•  fear,

•  avoidance,

•  or psychological unsafety.

What matters most is not whether conflict exists.

What matters is how people approach it.

Conflict is often about unmet needs

One fascinating thing about conflicts is that surface-level disagreement is often not the real issue.

For example:

•  argument about deadlines may actually be about stress,

•  disagreement about architecture may be about control,

•  frustration during code review may be about feeling undervalued,

•  tension between departments may be about communication gaps.

Interesting, right?

People usually communicate through layers.

And conflicts often reveal hidden needs underneath:

•  respect,

•  clarity,

•  safety,

•  autonomy,

•  recognition,

•  understanding,

•  or trust.

This is why slowing down and observing context becomes extremely important.

Small tensions grow silently

I think many workplace conflicts become destructive not because initial problem was huge.

But because small tensions were ignored for too long.

At first:

•  someone feels slightly frustrated,

•  misunderstood,

•  overloaded,

•  or emotionally uncomfortable.

But instead of addressing situation openly, tension stays hidden.

Then:

•  communication becomes colder,

•  sarcasm appears,

•  assumptions increase,

•  patience decreases,

•  emotional distance grows.

And eventually simple issue transforms into emotionally charged conflict affecting entire team atmosphere.

This is why early communication matters so much.

Sometimes ten-minute honest conversation may prevent months of unhealthy dynamics.

Conflict between roles

Another interesting thing in the IT industry is that conflicts often appear between roles rather than individuals themselves.

For example:

•  developers and QA engineers,

•  product and engineering,

•  designers and stakeholders,

•  management and contributors.

Why?

Because each role usually optimizes for different priorities.

Developer may prioritize maintainability.

Business stakeholder may prioritize speed.

Designer may prioritize customer experience.

QA engineer may prioritize stability.

And honestly — none of them are automatically wrong.

The problem usually begins when people stop seeing each other as collaborators and start seeing each other as obstacles.

This changes entire emotional dynamic inside team.

Ego and identity

I think ego influences conflicts much more than many people realize.

Especially in industries strongly connected with expertise and intelligence.

People often identify themselves with:

•  their ideas,

•  technical skills,

•  solutions,

•  seniority,

•  knowledge,

•  or status.

So when disagreement appears, nervous system may interpret it as personal threat instead of simple difference in perspective.

This is why emotionally mature communication requires distance between:

"“my idea”"

and

"“my identity.”"

Without this separation, discussions easily become emotional battles.

Conflict avoidance creates other conflicts

One paradox I’ve noticed is that avoiding conflict often creates even more conflict later.

Why?

Because reality does not disappear when we ignore it.

For example:

•  unclear expectations stay unclear,

•  unhealthy behavior continues,

•  frustration accumulates,

•  communication quality decreases,

•  resentment grows silently.

At some point emotional pressure becomes too large and situation explodes unexpectedly.

Sometimes people say:

"“This came out of nowhere.”"

But usually it did not.

Signals existed much earlier.

They were simply ignored or avoided.

Healthy disagreements

I think healthy teams understand something very important:

disagreement is not automatically disrespect.

People can:

•  disagree strongly,

•  challenge ideas,

•  question decisions,

•  or express frustration

while still respecting each other as human beings.

And honestly — this is one of the biggest signs of maturity.

Because mature collaboration is not based on pretending everything is perfect.

It is based on ability to navigate imperfection honestly.

Emotional regulation again

Conflicts often activate emotions very quickly.

Especially under:

•  stress,

•  exhaustion,

•  pressure,

•  uncertainty,

•  or lack of psychological safety.

This is why emotional regulation becomes one of most valuable soft skills.

Sometimes best thing we can do during conflict is simply slowing down.

Not replying immediately.

Not escalating.

Not assuming intentions too quickly.

Not treating temporary emotions as objective truth.

Because emotionally reactive decisions often create long-term consequences.

Listening during conflict

I think listening becomes hardest exactly when it becomes most important.

During conflicts many people stop listening to understand.

They start listening to defend themselves.

And this changes communication completely.

Interesting thing is that many conflicts begin decreasing the moment people genuinely feel heard.

Not because everyone suddenly agrees.

But because emotional tension decreases enough for rational discussion to appear.

Understanding does not always require agreement.

And this distinction is extremely important.

Conflict can improve systems

Another thing worth remembering is that conflicts sometimes reveal valuable information.

Healthy conflicts may expose:

•  unclear processes,

•  communication gaps,

•  unrealistic expectations,

•  poor leadership,

•  unhealthy workloads,

•  or hidden emotional tension inside teams.

So perhaps conflict itself is not enemy.

Maybe unresolved and poorly managed conflict is.

If team can observe problems honestly without ego dominating entire process, conflicts may actually improve collaboration quality long term.

Final thoughts

I think conflicts are unavoidable part of human collaboration.

Especially in complex industries like software development where people constantly operate under pressure, uncertainty, and changing priorities.

The goal probably should not be eliminating conflicts completely.

That would be unrealistic.

Perhaps healthier goal is learning:

•  emotional regulation,

•  communication,

•  listening,

•  observation,

•  empathy,

•  and psychological flexibility.

Because conflicts are often less about “winning” and more about understanding what is happening underneath surface.

And maybe strongest teams are not the ones without tension.

Maybe they are the ones where people can move through tension without destroying trust, dignity, and mutual respect.

Because after all — behind every role, ticket, sprint, architecture, and pull request there is still another human being.

Soft Skills series

Part 9 of 32. Read more on the Empatalk blog or take the Communication DNA survey at empatalk.app/survey.

Sources and further reading

•  Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly. https://doi.org/10.2307/2666999

•  Brown, P., & Levinson, S.C. (1987). Politeness: Some Universals in Language Usage. Cambridge University Press. https://doi.org/10.1017/CBO9780511813085

•  Ross, L. (1977). The intuitive psychologist and his shortcomings. In L. Berkowitz (Ed.), Advances in Experimental Social Psychology (Vol. 10). https://doi.org/10.1016/S0065-2601(08)60357-3