Why Great Teams Often Clash – And How You Can Fix It

Why Everyone Wants the Same Thing – And Still Fails

“Actually, we all want the same thing here.” I hear this sentence in nearly every team coaching session. And most of the time, it’s true. Few conflicts arise from a lack of motivation or effort. They stem from different ideas about how good collaboration should look.

Some people make decisions quickly and clearly—others need time to think things through thoroughly. Some address issues directly, while others wait to avoid straining relationships. These differences aren’t the problem. The issue arises when they go unspoken. That’s when assumptions like these start to form:

• “He doesn’t listen.”
• “She’s holding everything up.”
• “He overcomplicates things.”

What’s often overlooked? The very strengths of a person can sometimes feel like obstacles in certain situations. Without a shared understanding of how decisions are made, responsibilities are distributed, or work styles are allowed to play out, differences quickly become personal.

When Strengths Suddenly Become Obstacles

A fictional example: Imagine you’re working on a project team. Your colleague is an analytical thinker—she questions assumptions, checks data, and develops well-founded solutions. For you, this is often valuable because she spots risks early. But in a situation where quick decisions are needed, her thoroughness suddenly feels like a roadblock. “Why does she take so long?” you think. Maybe you even accuse her of slowing the team down.

Yet her strength is exactly what the team needs in other moments. The conflict doesn’t arise because she’s “too slow,” but because her work style doesn’t fit the situation—and because the team lacks a common language to discuss it.

What Positive Psychology Says About This

Research by Martin Seligman, one of the founders of Positive Psychology, shows that people are happiest and most productive when they can use their strengths. At the same time, Gallup’s studies warn that unspoken expectations and differing work styles are among the most common causes of team conflict. The solution? A framework that sees differences not as problems, but as resources.

How a Strengths Journey Creates Clarity

A strengths journey—a structured process where teams reflect on their individual strengths and work styles—provides exactly this language. It helps teams contextualize differences instead of trying to eliminate them. The goal isn’t for everyone to think the same way, but for everyone to understand:

• How do we make decisions—and why?
• How do we distribute responsibility?
• How do our different work styles affect each other?

Once teams start seeing differences as functional rather than personal, the way they interact changes noticeably. The tone becomes calmer, friction more constructive, and collaboration clearer.

A fictional example: From Conflict to Appreciation

Some time ago, I worked with a leadership team at a mid-sized tech company facing a similar situation. The sales and development departments regularly clashed over priorities. The sales team accused the developers of working “too slowly.” The developers, in turn, felt pressured and unappreciated.

During a strengths journey, we discovered that both sides were right—but from different perspectives. Sales needed quick solutions to win customers. Development needed time to build sustainable products. Instead of blaming each other, they began to see their differences as complementary. They agreed on clear communication rules and defined together when speed and when thoroughness should take priority. Conflicts decreased, and collaboration became more productive.

Key Takeaway: Differences Aren’t Flaws—They’re Opportunities

Teams rarely fail because of a lack of motivation, but because of unspoken expectations and differing work styles. A strengths journey helps make these differences visible and use them as resources. It creates clarity about how decisions are made, responsibilities are distributed, and work styles are lived—without anyone having to hide their strengths.

The key isn’t to avoid conflicts, but to see them as part of the process. Because only when differences are named can they be appreciated. And that’s what makes the difference between a good team and a great one.

Originally published on LinkedIn.