The Conflict Every High-Performing Team Learns to Have

Part 2 of a 3-part series on building high-performance teams

In Part 1, I made the case that teams stall because of hidden patterns in the system they form together, and that the most common of those patterns is disagreement nobody says out loud. This post is about that silence, and about something I've come to believe that a lot of leaders find hard to hear:

A team that never has conflict usually isn't healthy. It's just quiet. Those are not the same thing.

I spent years as a litigator before I became a coach — a whole profession built on structured disagreement — and it left me convinced that conflict isn't the opposite of collaboration. Avoiding conflict is. The best teams I've worked with haven't been the ones that keep the peace. They've been the ones that can disagree without it going sideways.

But I want to be careful here, because there's a piece most leadership advice skips. For a lot of people, hanging back from an argument isn't a confidence problem or a personality flaw you can coach away in a session. It's something they were raised to value. If you don't understand that, every "we need more candor around here" speech you give is going to miss them completely.

Harmony isn't weakness

In a lot of Western companies, we treat open debate as obviously good. Say the hard thing. Push on the idea. Play devil's advocate. And we assume the people who stay quiet just need a nudge.

Sometimes they don't. For a great many people, holding your tongue when you disagree isn't timidity. It's good manners. It's maturity. It's respect. It's how they learned to behave well around other people, and they're not going to abandon that because you asked them to in a Tuesday meeting.

This isn't a soft impression I picked up here and there — it's one of the most consistent findings in cross-cultural research. Geert Hofstede, whose study of IBM employees across more than fifty countries became one of the most cited pieces of work in the field, drew a line between what he called collectivist and individualist cultures. In collectivist cultures, people are woven tightly into their groups, and keeping the group in one piece often matters more than pushing a task forward. Open disagreement gets avoided, not because people have nothing to say, but because preserving the relationship comes first.

Stella Ting-Toomey built on this with what she called face-negotiation theory — "face" being the image of yourself you're trying to protect in front of other people. Her point was that different cultures handle conflict in genuinely different ways. People from individualistic cultures tend to get more assertive to protect their own standing; people from many East Asian cultures lean on indirectness, silence, deference, to protect the other person's standing and keep the peace. And this isn't armchair theorizing. When she and John Oetzel tested it across China, Germany, Japan, and the United States, the pattern held: the more someone's sense of self was bound up with the group, the more they leaned toward smoothing things over or working around the conflict rather than taking it head-on.

Here's the finding that should stop a team leader cold, because it cuts against something we all assume — that a team will naturally beat a lone individual. Researchers at the Harvard Program on Negotiation looked at exactly this and found that negotiating teams outperformed solo negotiators in the United States, but lost to them on the same exercise in Taiwan. The reason was cultural. In Taiwan, the teams put their energy into protecting the relationships in the room, so they challenged each other far less. The result was a more harmonious team that generated fewer good ideas.

Sit with that for a second: more harmony, fewer ideas. The same instinct that makes a team pleasant to sit in can be the thing quietly holding it at average. Not because the people aren't sharp, but because the culture they're working inside treats saying the hard thing as a kind of rudeness.

This isn't only about "international" teams

It would be easy to file all of that under "helpful if I manage a global team" and move on. I'd push back on that. Every team is cross-cultural, just in a less obvious way.

People carry the rules of the households they grew up in, the places they're from, the first boss who ever shaped them, the profession they trained in. Someone taught that cutting in on an elder is disrespectful doesn't unlearn it because they joined your product team.

Someone whose first company quietly punished whoever delivered bad news has learned, in their gut, that honesty is dangerous. So when you stand up and tell a room like that to "just be more open," you're asking some of them to break a rule they experience as basic decency — and then you're puzzled when only the same three loud people ever speak.

So the quiet on your team isn't one thing. Some of it is fear. Some of it is politics. And some of it is a sincere, decent belief that keeping things harmonious is the respectful way to behave. If you can't tell those apart, you'll keep reaching for the wrong fix.

Conflict isn't a toxin. It's a nutrient.

This is the thing I most want you to take away, and it works for the harmony-minded person as much as anyone.

Most people who duck conflict do it because, somewhere along the line, they came to see conflict as poison — something that wrecks relationships and makes a group feel unsafe. And if that's what conflict is, then avoiding it isn't cowardice. It's sense. Nobody should swallow poison.

The trouble is that the word "conflict" is hiding two completely different things. There's conflict aimed at people — the kind that humiliates, steamrolls, and breaks trust. That really is poison, and the instinct to get away from it is correct. And then there's conflict aimed at the work — pressure-testing a plan, naming a risk, sharpening a decision before it's made. That isn't poison at all.

That kind is a nutrient.

A good team digests disagreement the way a body digests food: it breaks it down, takes what's useful, and comes out stronger. A team that goes without it doesn't stay safe. It slowly goes soft, making decision after untested decision in a comfortable quiet, right up until that quiet costs it something real.

I lean on this distinction so much because it speaks straight to what the harmony-minded person is actually trying to protect. You're not asking them to stop respecting the group.

You're showing them that the thing they're afraid of — damage to the relationship — comes from the personal kind of conflict, not the kind about the work that you're inviting. You're not telling them to care less about harmony. You're changing where they think harmony comes from. Done right, arguing about the work isn't a threat to a team's closeness. It's one of the truest signs of it. Telling a team the hard truth is an act of care, not an attack.

What disagreeing well actually looks like

Once you see conflict as a nutrient rather than a toxin, the practices mostly take care of themselves. And every one of them is really about keeping the nutrient and cutting out the poison.

Keep it about the work, not the person. That's the whole distinction, made practical. "I think that plan underestimates the risk" and "you always rush these things" are not two versions of the same comment. One builds the team up and the other quietly tears it down — and that line is exactly what makes it safe for someone who was raised to protect relationships to weigh in at all.

Invite the disagreement; don't just allow it. For someone who thinks harmony is the polite default, your permission isn't enough — staying quiet is still the courteous move. Things only shift when you actually go looking for the pushback. "What's the case against this?" "Who's seeing it differently?" — and you have to mean it. When the person in charge openly asks for candor, speaking up stops feeling like a breach of the peace and starts feeling like doing your job.

End every disagreement with a decision. An argument that never resolves just curdles into a grudge — and for the harmony-minded person, that unresolved tension is the exact thing they were dreading. So close it out. Say what was decided, who owns it, and what everyone's now signed up for, including the people who argued the other way. That last part — disagree, then commit — is what makes the whole thing safe. People will tell you hard truths far more readily once they trust that losing the argument won't mean being resented, and that once the call is made, everyone rows in the same direction. The harmony comes back. It just comes back on the other side of the hard conversation instead of in place of it.

The leader's actual job

Here's where I'll leave it. Most leaders, when a team gets tense, instinctively try to bring the temperature down — smooth it over, settle everyone, get back to the agenda. On a team shaped by harmony-first values, that pull is even stronger, because the discomfort is real and you feel responsible for it.

The more useful thing to do is almost the reverse: raise what the team can tolerate, and do it in a way that respects what people walked in with. Name the dynamic out loud. Say plainly that for some people here, speaking up runs against everything they were taught about respect — and then build the safety, the invitation, and the clean ending that lets them do it anyway. And model it yourself, because a team never gets more candid than its leader is visibly comfortable being.

A team that can disagree well can handle almost anything else you throw at it. It'll make the hard calls, adjust when things change, and tell you the truth while a problem is still small and cheap to fix. A team that can't will hold its peace right up to the day that peace finally costs you something.

The point was never to turn quiet people loud. It's to get everyone on the team — whatever they grew up believing about harmony — to stop treating disagreement as something to survive and start treating it as the thing that makes the whole group stronger.

What comes next

So far we've looked at why teams stall, and at the single most important pattern to change: moving from avoided conflict to the productive kind, across the cultural grain that shapes how people feel it. In the last post, I'll get into the question every leader asks eventually — how do you make a change like this actually stick? Why does most leadership development light everyone up for a week and then fade by the next quarter, and what does it take to build the kind that genuinely changes how people lead?

Sources

• Geert Hofstede, Cultures and Organizations: Software of the Mind — individualism and collectivism, and the finding that in collectivist cultures group harmony often takes precedence over the task at hand.

• Stella Ting-Toomey, face-negotiation theory; Oetzel & Ting-Toomey's four-nation study (China, Germany, Japan, United States) linking a person's sense of self to the way they handle conflict.

• Harvard Program on Negotiation, "Teams Across Cultures" (research by Brett, Huang, Imai & Tsai) — teams beat solo negotiators in the U.S. but underperformed them in Taiwan, where harmony-focused teams challenged each other less.