Conflict Debt in Teams: The Signs Leaders Ignore

I listened to a great talk at LeadDev NY 2025 recently. It introduced me to the concept of conflict debt in teams: the accumulation of unresolved issues, disagreements, or tough conversations that people avoid addressing. As with financial debt, conflict debt also accumulates interest, but in the form of resentment, lack of trust, and poor collaboration.

Psychologists say conflict is to be expected in any healthy relationship, and it can even be welcomed when we have the necessary skills to deal with it. Handled well, conflict can deepen trust and strengthen connections. Handled poorly, it escalates into low performance at work, poor collaboration, and negative impacts on mental and physical health. Facing conflict head-on is not easy, and that is one of the reasons many of us choose to avoid it, letting conflict debt in teams quietly build.

Is Your Team Accumulating Conflict Debt?

Let us start by identifying whether your team might already be accumulating conflict debt. This is simpler than it sounds. One way to check is by sending an anonymous survey with these statements. If most of your team answers yes, you are likely in good shape: team members address the root causes of conflicts rather than just the symptoms, team members embrace disagreement and address issues directly, team members clearly communicate their expectations of each other, and team members regularly provide feedback on each other's work.

Otherwise, the patterns below are worth a closer look.

What Conflict Debt Looks Like in Practice

I once worked with a team where one developer consistently imposed his technical views. He was confident, decisive, and assertive, but when others expressed concerns, he did not really listen. The rest of the team had a more accommodating style, and instead of pushing back, they chose to avoid the conflict in order to move forward.

Months later, the solution failed to scale. The team had to rework large parts of the system, working long hours to fix issues that could have been addressed much earlier. What was avoided in conversation showed up later as extra effort, frustration, and burnout. That is conflict debt. When the leader and I reflected on what had happened, the lesson was clear: conflict was not the problem. Avoiding it was.

Communication Styles and Conflict

The way a person communicates is closely related to how they deal with conflict. Over time, we each develop a default communication style. Assertive means expressing thoughts and needs clearly and respectfully, while also listening to others. Passive means holding back opinions or needs to avoid tension, even when something matters. Aggressive means pushing a message forcefully, often dismissing or overpowering others. Passive-aggressive means avoiding direct confrontation but expressing disagreement indirectly through sarcasm, silence, or resistance.

None of these styles are inherently right or wrong, but becoming aware of your default pattern is the first step toward communicating more intentionally under pressure.

Conflict Management Styles

This brings us to conflict management styles. We are social beings, and we start learning how to manage conflict very early in life, often within our families. In 1974, Kenneth W. Thomas and Ralph H. Kilmann introduced five conflict styles that continue to be the preferred classification: competing, where I pursue my own position even at the expense of others; avoiding, where I sidestep the conflict altogether; accommodating, where I prioritize the other person's needs over my own; compromising, where we each give up something to reach a middle ground; and collaborating, where we work together to fully address both sides' concerns.

As a team leader, it is important to be familiar with these styles and to observe both yourself and your team in how you communicate and react to conflict. While every style has its place, collaborating is usually the one to aim for in a high-performing team, and leaders can model this for the rest of the team.

A Second Example: When No One Names the Problem

In a different situation, I once coached a team where one member consistently showed low productivity. Everyone noticed it, but no one named it. Most of the team had an accommodating, non-confrontational style, so they absorbed the extra work and hoped things would improve on their own. They did not.

The team fell behind, tension grew, and eventually the client became unhappy. What started as discomfort inside the team turned into a delivery and trust issue on the outside. When they finally had the difficult conversation, expectations were made explicit, goals were clarified, and support was offered. Performance improved, and the team recovered. The insight was simple: even in high-performing teams, expectations drift. Setting and resetting expectations is not a one-time event. It is ongoing leadership work.

5 Signs Leaders Often Miss Before Conflict Debt Accumulates

• Disagreements that resolve too quickly. When a tense discussion ends faster than the topic warrants, it often means someone deferred rather than genuinely agreed.
• Quiet absorption of extra work. When one or two people consistently pick up slack without anyone naming why, accommodation is masking a performance or expectation gap.
• Feedback that only flows upward in formal reviews. If feedback only happens during scheduled reviews rather than in the normal flow of work, the team has likely built informal rules against addressing things directly.
• Recurring rework on the same type of issue. When the same category of problem resurfaces project after project, it usually means the root disagreement was never actually resolved, just postponed.
• A drop in spontaneous disagreement during meetings. Healthy teams disagree out loud. When meetings become unusually smooth and conflict-free, it is worth asking whether people stopped raising concerns rather than stopped having them.

What This Means for Engineering Leaders

Mid-market software companies

For mid-market software companies conflict debt shows up most visibly during incident response and architecture decisions, exactly the moments when a dissenting technical opinion needed to surface earlier. Engineering leaders who build regular, low-stakes opportunities for disagreement into their team rituals catch the small frictions before they compound into the kind of rework this article describes.

In distributed and nearshore engineering teams conflict debt can build even more quietly because the informal hallway conversations that surface tension in co-located teams do not exist in the same way. Building explicit feedback rituals matters more, not less, in these environments.

PE-backed software portfolios

For PE-backed software portfolios conflict debt across PortCo engineering teams often surfaces during post-acquisition integration, when accommodating team members absorb the friction of merging different technical standards rather than naming the disagreement directly. Operating partners who build conflict awareness into engineering leadership development reduce the rework and trust erosion that integration periods otherwise produce.

If this resonates with patterns you are seeing in your own team, our team at Scio would be glad to talk through it.

Frequently Asked Questions

Let Us Slow Down and Listen

Conflict debt does not show up all at once. It builds quietly, conversation by conversation, moment by moment. As a team leader, your role is not to eliminate conflict, but to make it safe, visible, and workable. When you slow down to listen, invite disagreement, and reset expectations, you are not creating friction. You are protecting trust, performance, and people.

The teams that grow strongest are not the ones that avoid hard conversations. They are the ones that learn to have them well. If this is something your team is navigating, I would be glad to talk through it.

References and Further Reading

• Thomas, Kenneth W. and Kilmann, Ralph H., Thomas-Kilmann Conflict Mode Instrument. The original 1974 framework introducing the five conflict management styles referenced throughout this article: competing, avoiding, accommodating, compromising, and collaborating. https://kilmanndiagnostics.com/overview-thomas-kilmann-conflict-mode-instrument-tki/
• Harvard Program on Negotiation, Conflict Management Styles Research. Research on conflict management approaches in professional settings, including the pitfalls and best practices relevant to the communication style patterns described in this article. https://www.pon.harvard.edu/
• American Psychological Association, Conflict and Workplace Relationships Research. Research on how unresolved conflict affects mental health, team trust, and collaboration quality, supporting the conflict debt framework described in this article. https://www.apa.org/
• Google re:Work, Psychological Safety and Team Performance Research. Research identifying psychological safety as the top predictor of team effectiveness, directly relevant to why teams that can surface disagreement safely outperform those that avoid it. https://rework.withgoogle.com/
• Center for Nonviolent Communication, NVC Framework. Framework for direct, respectful communication that supports the assertive communication style this article identifies as most effective for addressing conflict constructively. https://www.cnvc.org/
• Gallup, Employee Engagement and Manager Relationship Research. Research on how manager-employee relationship quality, including how conflict and feedback are handled, affects engagement, retention, and team performance. https://www.gallup.com/
• Scio blog, Tech Lead Anxiety: 5 Real Patterns and How Leaders Recover. How unresolved tension and unspoken expectations contribute to the anxiety patterns this article connects to unaddressed conflict debt. https://sciodev.com/blog/tech-lead-anxiety/
• Scio blog, Emotional Intelligence in Software Engineering: 5 Real Patterns. How emotional intelligence supports the assertive, collaborative communication style this article identifies as the healthiest approach to team conflict. https://sciodev.com/blog/emotional-intelligence-software-engineering/