As an Engineering Manager, there's one thing you want to avoid at all costs: unresolved conflicts.
I learned that the hard way.
Early in my career, I believed that conflicts should be resolved independently by the individuals involved. This approach led to losing great team members and putting entire projects at risk.
Those experiences taught me the importance of conflict resolution, prompting me to develop these essential skills actively.
So, in today’s newsletter, this is what we are going to cover:
❓ What is conflict — and why does it arise in engineering teams.
🔍 How to recognize — the conflict in its early stages, to help timely resolution.
🔬 How to identify — involved parties and root causes.
🤝 How to solve — the conflict by choosing the appropriate resolution style.
🔭 How to monitor — the situation to avoid relapses.
💡 Final tips — a final list of simple ideas coming from my experience.
Let’s dive in!
❓What is conflict?
Conflicts in professional settings are about situations where team members have differing opinions, goals, or approaches regarding work or communication.
This is just normal. Like in any group setting, these conflicts arise from the interplay of different personalities, skills, and roles.
Now, from my observation, conflicts in engineering teams usually arise from the big five reasons:
🛠️ Technical disagreements — probably the most frequent. This is when team members have different views on solutions, practices, or implementation of technologies.
📊 Resource allocation — disagreements over allocating limited resources like time, budget, or people.
🔗 Interdependence — engineering projects require collaboration among various specialists. The nature of collaboration means that decisions and actions by one individual or group can significantly affect the outcomes of others, sometimes leading to conflicts.
🗣️ Communication — poor communication can lead to misunderstanding and conflicts, especially in large or geo-distributed teams.
🤝 Personal style and values — differences in work style, personal values, or professional ethics can lead to conflicts. For example, a conflict might arise between team members who value rapid innovation vs those who prioritize thorough, risk-averse approaches to problem-solving.
🩺 How to deal with conflicts
Over the years, I have met many conflicts. Initially, I approached them with a bit of improvisation, but eventually, I developed a structured framework that has successfully helped me manage them.
This framework is made up of four steps:
🔍 Recognize — the conflict.
🔬 Identify — involved parties, root cause, and conflict resolution styles.
🧯 Solve — the conflict.
🔭 Monitor — and follow-up.
Let's go through each of these steps.
1) Recognize the conflict 🔍
The main challenge of recognizing a conflict is to do so in its early stages, so that it’s easier to put out the fire.
These are some common signs that a conflict could be around the corner: