Leap Forward - People Infrastructure Architect
← Back to insights
Team operations6 min

Conflict management in tech teams: stop mediating, start designing

Key Takeaways

  • Most team conflict is structural, not interpersonal.
  • Recurring fights signal decision, ownership, or metric gaps.
  • Redesign the system before mediating the people.

Most conflicts in engineering and product orgs aren't interpersonal. They're structural. Here's how to tell the difference – and what to do about each.

When a CTO calls us about 'a personality clash' between two senior engineers, our first question is rarely about the engineers. It's about the org chart, the roadmap, and the incentive system.

Structural conflict has a fingerprint. The same disagreement keeps surfacing in different rooms. The fight always touches one of three things: who decides, who's measured, or who owns the work.

When we see that fingerprint, mediation makes the problem worse. The fix is design, not therapy.

True interpersonal conflict – the other 20% – travels with one of the people across contexts and often pre-dates the current company.

The most expensive mistake is treating structural conflict as interpersonal and interpersonal conflict as structural.

More insights