Task conflict was supposed to be the good kind. The new data says it isn't.

Tuesday's leadership huddle runs long because two of your people are going back and forth over how to sequence a launch. Voices rise a little. Nobody storms out. You let it run because you were taught, probably from the same shelf of management books everyone else read, that this is the good kind of friction — task conflict, not personality conflict — and that a team willing to hash it out in the open is healthier than one that goes quiet. You've been treating the noise as a sign the team is working.

A new meta-analysis in the Journal of Applied Psychology, in its February 2026 issue, updates that assumption. Zhenyu Yuan at the University of Illinois Chicago, with Jingfeng Yin at Hong Kong Polytechnic University and Jiaqing Sun at the London School of Economics and Political Science, revisited the team conflict literature twelve years after the last comprehensive synthesis of it and pooled the research published since. A meta-analysis like this doesn't run a new experiment; it re-weighs the existing evidence across many prior studies, correcting for measurement error and testing whether the average effect holds up. This one also added a fourth conflict type, status conflict, to the three the field had been tracking. I could not get past the paywall on the full paper, so what follows comes from the published abstract and a University of Illinois Chicago release describing the work. The abstract does not say how many studies or how many teams were pooled, and neither does the release, so I can't tell you the scale of the evidence behind these numbers, only that it's a synthesis of "a large body of empirical research that continues to grow to this day."

Our results based on psychometric meta-analysis indicate that all four team conflict dimensions (i.e., task conflict, relationship conflict, process conflict, and status conflict) are negatively related to team performance.Journal of Applied Psychology, published abstract

That's the headline, and it includes task conflict — the disagreement over how to do the work, as opposed to friction between personalities. For years the standard advice was that this kind was worth protecting, even encouraging. The pooled data says the average relationship runs the other way. The paper doesn't stop there, though: it also reports that the task conflict and relationship conflict relationships carry substantial heterogeneity from one study to the next, and that national culture, features of the team, and even how researchers measured conflict all help explain why. In plain terms, the average is negative, but the average isn't the whole story, and the abstract doesn't say which of those contexts flips the relationship or by how much. A University of Illinois Chicago release on the paper put it this way, without attributing the words to any one researcher: "fostering open communication and psychological safety is more effective than relying on conflict to drive results."

Here's why this lands differently for you than for a division head at a company many times larger. At a large company, the two people arguing over the launch sequence are two people in a hundred, and the org has slack built in — other teams, other timelines, a backlog that absorbs the delay. In your shop, the two people in that Tuesday huddle are probably the ones who ship the thing. If the arguing is a drag on their output, it's a drag on your output, this week, with no bench to cover for it. And you're often the one who set the norm that arguing is good, because you read the same books.

The part the research doesn't say, but that I'll say plainly: the mistake isn't having conflict on your team. It's treating the presence of disagreement, by itself, as evidence of health. A meta-analysis correlating conflict with performance can't tell you whether your team's Tuesday argument is converging on a decision or just recycling the same disagreement it had last month. That distinction is mine, not the authors', and it's the one worth checking before you decide the arguing in your building is the productive kind.

This week, pick the one recurring meeting where disagreement is a fixture, and actually track it for a few sessions: does it end in a decision, or does the same issue resurface next time in slightly different clothes? If it's the latter, what you've been calling healthy friction is closer to unresolved conflict wearing a better outfit, and the fix is a decision rule, not more debate.

If you want a clearer read on how you handle disagreement under pressure, and what you bring to the friction on your team, the Leadership Profile at /wiring-map is built for exactly this.