The Most Expensive Conflicts Are the Ones No One Leads

Ask most product organizations whether they have a conflict problem, and the answer is usually no. People are professional. Meetings stay civil. Roadmaps get agreed, priorities get nodded through, and everyone leaves the room on good terms. That answer is often sincere. It is also where the real cost hides.

Because the expensive conflicts are rarely the loud ones. The disagreements that quietly drain a product organization don’t look like conflict at all. They look like alignment.

The conflict you can’t see on the board

A prioritization call that three people privately doubt, but no one challenges. A recurring tension between product and engineering that everyone has simply learned to route around. A stakeholder whose actual objection never makes it into the room — only into the hallway conversation afterward. Nothing escalates, nobody raises their voice and the work moves on, carrying the unresolved question with it.

This is the uncomfortable pattern we see in so many organizations: what leaders read as harmony is often just a conflict that no one was willing to have out loud. And an unspoken disagreement doesn’t disappear when you look away from it. It goes underground, attaches itself to the work, and resurfaces later (usually at a moment when no one connects it back to its origin).

Where the cost actually shows up

The bill for a silent conflict is rarely presented where the conflict lives. It appears downstream, disguised as something else.

It shows up as decisions that get reopened three times, because the disagreement they papered over was never actually resolved. As alignment meetings that are really proxy debates for a tension nobody will name directly. As cycle time that creeps up, not because the team is slow, but because unclear, contested work keeps entering delivery as if it were ready to build. Or as a strong engineer or product manager who leaves, and says something in the exit conversation that leadership could have heard a year earlier.

This is the same mechanism behind so much delivery friction: the organization paying interest on ambiguity it declined to resolve upstream. Very often, a silent conflict is a form of upstream debt. And for product leaders, managing this kind of social complexity — the competing incentives, the unspoken objections, the stakeholder tensions that never quite get named — is not a soft skill on the side. It is a large part of the actual work (and yes, writing better tickets is the easy part).

What the research puts a number on

The qualitative picture is backed by a surprisingly consistent body of data. Employees spend an estimated 10–15% of their working time dealing with conflict, and for managers KPMG puts it as high as 30–50%. That load is rising: the average time employees spend on conflict roughly doubled — from 2.1 hours per week in 2008 to 4.34 hours in 2022 (CPP / The Myers-Briggs Company).

At the organizational level the bill is substantial. Acas estimates workplace conflict costs UK employers £28.5 billion a year — around £1,000 per employee — while the earlier CPP study valued it at $359 billion in paid hours in the US alone. And culture is not a soft variable in this equation: an MIT analysis of millions of employee reviews found a toxic culture to be roughly ten times stronger a predictor of attrition than compensation. Zoom out further and Gallup attributes close to 9% of global GDP to low engagement.

Made concrete, the numbers add up quickly. Run a conservative model for a single 200-person technology organization — front-line staff losing 10% of their time, managers 30%, a handful of conflict-driven departures — and the annual cost of unaddressed conflict lands at roughly €2.75 million. None of that comes from dramatic blow-ups. It accumulates quietly, one avoided conversation at a time — which is exactly the point.

Why silence feels cheap

The reason silent conflict is so persistent is that it feels almost free in the moment. Skipping the awkward conversation costs nothing today. The meeting stays pleasant, the relationship stays intact, the day moves on.

But the price doesn’t vanish. It is simply deferred, and it compounds. A year too late, the conflict is expensive to repair — trust has eroded, positions have hardened, good people have already made quiet decisions. Addressed early, while it was still small and still cheap, it would have taken one honest conversation. The organization almost always pays the more expensive version.

Leading a conflict is not escalating it

Part of what keeps leaders from acting is a quiet assumption: that to lead a conflict is to escalate it. The opposite is true. to lead a conflict is to take it in hand deliberately, before it escalates on its own — in passive resistance, in the slow disengagement of a capable team, in the resignation that seems to arrive out of nowhere. Looking prevents the loud version. Looking away only postpones it, with interest.

Conflict-capable leadership, then, is not a matter of temperament. It is a decision that gets made (or avoided) many times a week: to look at the tension and address it, or to let it pass and keep the surface calm.

And this reframes what a healthy product organization actually is: it is not one without conflict. Optimizing for the absence of disagreement usually just drives it underground, where it gets more expensive. A healthy product organization is one where the right conflicts get led — early, in the open, in the room where they belong.

The next time a team feels stuck and the instinct is to make it faster, it is worth asking a different question first: how many quiet conflicts are running through this organization right now — and who is actually leading them?

---

Some conflicts have run quietly for too long to be led from the inside. The positions have hardened, and everyone involved has become part of the pattern. That’s exatly the point where a neutral third party makes the difference. In our conflict resolution work, we help product and leadership teams bring these unspoken tensions into the open and resolve them before they keep compounding downstream.

---

If this resonates, it’s the shorter version of a longer piece (German only) we’ve been developing on the cost of silence in product organizations and was originally published by Brigitte Pfeifer-Schmöller

---

Sources

• KPMG (2009). Konfliktkostenstudie – Die Kosten von Reibungsverlusten in Industrieunternehmen; and KPMG (2012). Best Practice Konflikt(kosten)-Management – Der wahre Wert der Mediation.
• CPP Inc. / OPP Ltd. (2008). Workplace Conflict and How Businesses Can Harness It to Thrive (CPP Global Human Capital Report).
• The Myers-Briggs Company (2022). Conflict at Work. Saundry, R. & Urwin, P. (2021). Estimating the Costs of Workplace Conflict (Acas).
• Sull, D., Sull, C. & Zweig, B. (2022). Toxic Culture Is Driving the Great Resignation (MIT Sloan Management Review). Gallup. State of the Global Workplace.