TEAM DYNAMICS · 5 min read

When leaders come to me with a team friction problem, there is usually an implicit goal underneath the stated one. The stated goal is: 'We want to improve communication and reduce conflict.' The implicit goal is: 'We want everyone to get along and stop disagreeing so much.'

Those are very different goals, and conflating them is one of the most expensive mistakes a leadership team can make.

Friction is not a sign that something is wrong with your team. In most cases, friction is a sign that something is right — that you have people with genuinely different perspectives, skills, and orientations, and that those differences are creating some productive tension.

The goal is not to eliminate friction. The goal is to develop a team that knows how to use it.

What the research actually says

There is a long tradition in organizational psychology of studying team composition and performance. One of the most robust findings is that cognitively diverse teams (teams whose members think and approach problems differently and challenge each other's assumptions) consistently outperform homogeneous teams on complex tasks.

The catch is that cognitively diverse teams are also more uncomfortable to be on. They have more conflict. They reach consensus more slowly. They require more effort to coordinate. In the short run, they look less efficient.

In the long run, they produce better outcomes on any problem involving uncertainty, novelty, or real-world complexity. The friction is not incidental to the performance. In significant part, the mechanism is friction.

The friction is not incidental to the performance. In significant part, the mechanism is friction.

What unproductive friction actually looks like

There is an important distinction to make here. Not all friction is productive. Productive friction occurs when people disagree about ideas, approaches, or interpretations of data. It generates heat, but it also generates light.

Unproductive friction is the kind that occurs when people talk past each other because they do not understand each other's communication styles. A Dominant style that reads a Cautious style's detailed questioning as obstruction, and responds with visible impatience, is not creating productive friction. They are creating a communication breakdown. The C-style starts with withholding concerns. The D-style starts making decisions without full information. Both lose.

This is where DISC is genuinely useful. It is not a tool for eliminating disagreement, but for making it productive. When a Dominant style understands that their Cautious colleague's need for information is a feature, not a bug, and adjusts accordingly, the conversation changes. The friction remains. The dysfunction goes away.

The specific mistake: building for harmony over rigor

I see this pattern most often in leadership teams that have been together for a long time, or that were built by a leader who values cohesion above all else. The team gets very good at not fighting. They reach consensus quickly. Meetings run smoothly.

They also make poor decisions at a higher rate than they should, because the mechanisms that exist specifically to catch errors (e.g., the person who asks the uncomfortable question, the voice that says 'wait, have we considered,' the analysis that everyone secretly hopes no one will commission, etc.) have been slowly socialized out of the team's culture.

The technical term for this in the organizational psychology literature is groupthink. The lay term is 'everyone in the meeting agrees, and then the project fails.'

What to do instead

The reframe I use with leadership teams is simple: stop managing for harmony and start managing for quality of disagreement.

Good disagreement is specific. It is about the idea, not the person. It is bounded by a shared goal. It produces a decision that is better than what either party would have reached alone.

Building a team capable of that kind of disagreement requires a few things. It requires psychological safety…people need to be able to surface dissent without risking their careers. It requires shared behavioral language. DISC gives teams a framework for understanding why their colleagues think differently without making it personal. And it requires leadership modeling. The leader has to visibly invite pushback, take it seriously, and occasionally change their position in response.

That last one is harder than it sounds. But it is what makes everything else work.

Want to help your team develop a shared language for navigating disagreement? Ask about team DISC workshops.