Why Teams Fail Even When Everyone Is Smart

When projects fail, we usually blame the usual suspects.

  • timelines
  • budgets
  • technology
  • requirements

It feels comforting. Those things are tangible. They show up in PowerPoint. They can be escalated.

What we hesitate to confront is the team.

Not because the team did not work hard, but because the team dynamics quietly undermined everything else.

The real battlefield is often the team itself.

The illusion of a “good team”

Teams can look fine from the outside.

People are polite.
Meetings are calm.
Status is green.
Nobody openly disagrees.

From a distance, this feels healthy.

But in reality, it often means something very different:

  • people are careful
  • problems are hidden
  • conflict is avoided
  • decisions are accepted, but not owned
  • results become secondary to personal positioning

I have seen teams with brilliant individuals fail repeatedly, and average teams outperform expectations.

The difference was never intelligence or skill.

It was trust, conflict, commitment, accountability, and focus on results.

Trust is not about liking each other

Trust is one of the most abused words in management.

People think trust means:

  • liking each other
  • getting along
  • being friendly

That is not what matters.

The trust that makes teams work is much more uncomfortable.

Imagine the following situation:

It is your first day in a new project. Tasks are distributed. You receive one you have never done before. Even worse, you have no clue how to get it done.

What do you do?
Most people stay silent.
Not because they understand the task, but because they do not want to look stupid.

They think:

  • “I’ll figure it out.”
  • “I’ll Google it.”
  • “I’ll try not to bother anyone.”

And weeks later, when the deadline is close, the problem suddenly appears.

That is not laziness. That is fear.

Trust in teams is not about being friendly or predictable.
Humans become predictable automatically.
After some time, you already know from someone’s tone of voice whether they are stressed or relaxed.

That is not trust. That is pattern recognition.

Real trust is vulnerability.

It is saying:

  • “I don’t know.”
  • “I need help.”
  • “I won’t make Friday.”
  • “This is more complex than expected.”

And here is the leadership problem:

You cannot order trust.

You can’t say “trust each other” the same way you say “finish this by Friday”.

It does not work.
Nowhere.
Never.
Not because you do not find the right tone, but because trust is emotional.

It takes time to build.
It is not something to decide on the spot.

Trust grows indirectly:
through behavior,
through environment,
through leaders who show that problems are allowed before they become disasters.

This is exactly why The Emperor’s New Clothes is such a powerful metaphor.

In the tale, the emperor is sold invisible clothes that only the worthy and competent are supposed to see, while in reality he is naked.

And everyone sees the same thing.

The emperor is naked.
The truth is obvious.
But nobody speaks up.

Not the advisors. Not the ministers. Not the crowd.

Why?
Because every single person thinks:

  • “If I say it, I might be the only one.”
  • “If I say it, I might look stupid.”
  • “If I say it, I might get punished.”

So everyone stays silent, even though everyone knows.

Until one child, unaware of the unspoken rule, says what everyone sees, the emperor is naked.

In teams with low trust, this story plays out constantly.

Everyone sees that the milestone is unrealistic.
Everyone knows the dependency is broken.
Everyone senses the risk.

And yet, nobody says it openly.
The status stays green.
The report looks clean.
The illusion holds.

Until reality breaks through.

Why nice teams are often the most dangerous ones

After trust comes conflict.
And conflict has a terrible reputation.

Nobody likes it.
Nobody enjoys tension.
So teams try to avoid it.

I have seen teams that were incredibly polite.
Meetings were calm, friendly, almost cosy.
Everyone agreed. Nobody pushed back.

And nothing moved.

The real discussions happened later, in side conversations, in private chats, in coffee breaks.

That is not harmony. That is politics.

Healthy teams fight. Not personally, but intellectually.

They challenge ideas. They disagree openly. They argue about the best solution.

During my lectures, I use an example that usually makes people pause.

Think of the last time you had a really strong argument, an openly burning verbal fight, perhaps even screaming at each other.

Remember that moment in detail.

Now imagine you say something and your counterpart answers:
“Oh well, yes, true, I think you’re right” and the fight stops on the spot.

No. It does not work like that.

When emotions are hot, words rarely cool them down.

It is not the arguments.
We respond to emotions.
We feel hurt. We feel misunderstood.
We feel treated unfairly. And your counterpart in that fight feels the same.

To be totally clear, lessons learned for the future:
it will never work by adding another argument.

If a situation is emotionally escalated, both sides have usually already evaluated the other side’s arguments and dismissed them, otherwise there would not be a fight.

So do not use words when a situation has escalated. Take time to calm down.
Both sides should do that. Come back to a level of emotion where reflection and communication can restart.

The goal is not to win the argument. It is to solve the conflict.

At the emotional peak of a conflict, words do not convince.
In that moment, it does not matter how good the arguments are.
Logic does not land when emotions are high.

Now reflect on this: people escalate emotionally in very different ways.

Some people escalate fast and loud. They get emotional quickly, say everything at once, and calm down just as fast.

Others escalate slowly. They absorb tension, stay quiet, and only react once a threshold is crossed.

When these two types clash, something dangerous happens.

The fast escalator thinks: “We talked it out, it’s done.”
The slow escalator thinks: “This just started.”
Both walk out of the same meeting with completely different emotional states.

This is why one simple rule matters so much:
Good leaders sense this early.

They interrupt discussions.
They slow things down.
They take people aside.
They resume later, when emotions have cooled.

And they are especially careful with teams that are “too friendly”.

Because teams that like each other a lot often stop challenging bad ideas. They do not want to offend. They do not want tension. They prefer harmony.

The frustration does not disappear. It just moves underground.

Commitment does not mean consensus

One of the hardest moments for any leader is this:

The team discusses a topic.
Everyone agrees on a solution.
And you, as the leader, think it is wrong.

Now what?

If you override the team, you create frustration. If you follow the team, you risk a bad decision. If you avoid deciding, you destroy everything.

Avoiding the decision is always the worst option.

Commitment does not come from consensus. It comes from clarity.

People want to be heard.
They want to understand why a decision was made.
They do not need to win.

“Discussion is allowed. Disagreement is allowed. But once a decision is made, execution starts.”

Disagree and commit.
No reopening. No “I told you so”. No passive resistance.

Projects don’t fail because decisions are wrong. They fail because decisions dissolve.

Accountability is not your job alone

In weak teams, accountability flows upward.
People deliver because the boss expects it.

In strong teams, accountability flows sideways.
People deliver because they do not want to let their teammates down.

This is the ideal state: all for one and one for all. This is real team.

The problem is that this ideal only works if all members buy in.
As soon as you have one single person outside this spirit, true accountability will not emerge.

This is where leadership becomes uncomfortable.
Many leaders shy away from it, and it is really hard to manage.

The hard problem to solve is the toxic high performer.
Brilliant technically. Delivers results. Socially destructive.

And every leader hears the same internal excuses:

  • “We can’t lose them.”
  • “They’re difficult, but effective.”
  • “That’s just their style.”

I have seen what happens when leaders avoid this.

One person poisons the atmosphere.
Others withdraw.
Energy is wasted.
Performance drops.

Let’s reflect on why this is so hard to fix, and why many leaders fail.

No leader has a problem confronting a sales employee about missed sales targets.
That is easy.

The numbers are there. The KPI is clear. The expectation is measurable.
Those conversations are comfortable.

The hard conversation is about behaviour.
Real mastery of leadership starts where things are not measurable.

Tone.
Social friction.
Trust.
Fear.
Intimidation.
Politics.

These are not on dashboards.
They don’t show up in PowerPoint.
And they are always subject to interpretation.

A story from growth, restructuring, and the famous five-minute excuse

There is a story I often tell, because it looks harmless at first and then slowly becomes uncomfortable.

The situation is this:

A company is doing reasonably well and keeps growing stadily.
As the day to day business has become quite big, the CEO wants to apply some changes.
He want to restructure the organisation allowing him to focus more on strategy.

Less day-to-day firefighting. More long-term direction.

So an idea comes up: we should appoint a COO.
Someone who takes over operations, so the CEO can step back a bit.

So far, completely reasonable.
Now, inside the organisation, there is one special senior manager.

Very good technically.
Very capable.
Knows the business.
Gets things done.

But socially, super super difficult.
Not openly aggressive, but intimidating.
The kind of person others avoid talking to.

And this senior manager all of a sudden starts telling people:

  • “When I’m COO, we’ll finally change this.”
  • “Once I take over operations, things will be different.”
  • “Just wait until I’m in that role.”

Not officially. Not announced.
Just casually. In meetings.
In corridor conversations.
In front of others.

Often enough that people start to notice, and to worry.

People don’t know if it is true.
People don’t know if the CEO is behind it.
People start behaving differently.

Some stop challenging him.
Some try to align early.
Some pull back completely.

The organisation becomes very very nervous.

Then, after a couple of weeks, during one of the regular follow-up meetings, the topic is raised with the CEO.

One of the consultants hired to define the future organization asks the CEO:
“Do you actually know that one of your managers is telling people openly he will become the new COO?”

The CEO looks surprised and answers honestly: “No. I didn’t know that.”

Then the consultant asks the second question:
“Well, to share our opinion, we got to know this particular manager and from our point of view he is one of the most complex persons we have met in the whole organization. Please tell us, is he actually a real option for the COO role?”

The CEO answers immediately: “No. Absolutely not.”

And then he adds:
“You’ve met him. He’s very good at what he’s doing, but socially he’s very weak. He is not good with people at all. The COO role would never work for him.”

Very clear. No ambiguity.

Then comes the third question, and this is the key one:
“Will you talk to him?”

And now comes the answer that quietly damages the organisation.
The CEO says:

“No. I don’t have time for this.
Look, there are more urgent and important things on my agenda.
One of our best clients is threatening to leave for a competitor.
There is a patent rights issue that could turn into a legal claim.
And on top, there is the investor call next week that needs my full attention.

All of this is might be true.
All of this is actually important.
All of this sounds somehow reasonable.

And this is exactly why this story is so dangerous.
Because this is where leadership fails quietly.

That conversation with the complex senior manager would take five minutes. Just FIVE.

Not a strategy workshop.
Not a board meeting.
Not a restructuring program.

Five minutes.

And by not having it, the CEO allows the organisation to stay scared.
He allows rumours to grow.
He allows informal power to shift.
He allows one socially difficult person to shape behavior without mandate.

This is the moment where I stop and tell my students:

This has nothing to do with time.
“I don’t have time” is just an excuse, and a weak one.

If I ever find out that one of you tells an employee, “I don’t have time for such a conversation”, I will personally hunt you down.

They laugh. And they remember it.

Five minutes at the right time are worth more than months of damage control later.
Avoiding these five minutes helps nobody.

Not the CEO.
Not the team.
Not the organisation.

What it does do is send a clear signal:

  • This behaviour is tolerated.
  • This tension is acceptable.
  • This problem is not important enough.

And organisations always read signals faster than formal rules.

When ego beats results, teams fall apart

At the top of the dysfunction pyramid sits the most destructive one: ego.

Team members start optimizing for themselves.
Recognition matters more than outcome.
Visibility beats results.

In this context, I like to tell the story of the Chicago Bulls.
From the year after Michael Jordan retired, after winning 3 consecutive years the NBA finals.

In that year after Jordan left, Scottie Pippen became captain.
Expectations were enormous. The team was still strong. The system still worked.

Then came a decisive playoff game.

Final seconds.
One possession.
Down by one.
Timeout.

The coach drew a play.
Not for Pippen.
For another player.

Tactically, it made sense.
Everyone expected Pippen to take the shot.
The defense would collapse on him.

Pippen disagreed.
Loudly.
Emotionally.
He started arguing with his coach at the sideline.
He insisted on getting the last shot.

When the coach refused, Pippen made his decision.
He refused to return to the court.

The team played the final minutes without its captain.
They executed the play.
They scored.
They won the game.

And in that very moment, the team broke.

Because everyone understood what had happened.
The captain had chosen ego over team success.

Trust broke.
Unity collapsed.
The season ended shortly after.

Short-term success did not compensate for long-term damage.

The CTO story that made everything click

Two CTOs. Same company.

The first was a technical genius.
A brilliant architect.
Always the smartest person in the room.

And almost impossible to work with.

Low trust.
High friction.
People worked around her, not with her.

Her successor was different.
Not trying to show individual technical brilliance.
Not trying to intimidate others through superiority.
More focused on enabling collaboration across the organization.

He was a team player.

And suddenly, people talked. Problems surfaced early. Solutions were found together.

Overall performance improved.

That was the moment the pattern became undeniable.
Results are produced by teams, not individuals.

Leadership quality is measured by team output, not IQ.

The uncomfortable lesson

Strong teams don’t happen by accident.

They trust each other.
They fight constructively.
They commit after discussion.
They hold each other accountable.
They focus on collective results.

Leadership is not heroism.
It is not brilliance.
It is not control.

Leadership is creating the conditions under which teams can perform.

And if you ever wonder why a project struggles despite smart people and solid plans, don’t look at the Gantt chart first.

Look at the team.

That’s usually where the real problem starts.

And where real leadership begins.

Leave a Comment