One of the easiest ways to misdiagnose a team is to start where the problem becomes visible.
A project got delayed.
A product decision took too long.
A customer issue remained unresolved.
People did not escalate in time.
Someone obvious underperformed and nobody dealt with it.
The postmortem then sounds familiar. Planning issue. Ownership issue. Follow-through issue. Process issue. Review issue. Prioritization issue.
Sometimes those diagnoses are correct. Often they are not wrong so much as shallow.
They describe where the problem surfaced, not where it began.
Leadership teams rarely say the thing they most need to say.
Not: the launch slipped because we did not update the tracker.
But: the launch slipped because we did not trust one another enough to say what we really thought early enough.
That second diagnosis is harder because it is no longer procedural.
Now the conversation is about trust. Fear. Avoidance. Artificial harmony. Reluctance to confront. Preference for being liked over being clear.
Those are much more uncomfortable things to name than a weak review cadence.
This is why Five Dysfunctions still endures
One reason Patrick Lencioni's five dysfunctions model remains useful is that it gives simple language to a pattern most leadership teams have lived through but often fail to diagnose cleanly.
The model is straightforward:
- absence of trust
- fear of conflict
- lack of commitment
- avoidance of accountability
- inattention to results
What makes it durable is not that it is academically complicated. It is that it follows the causal chain better than most management discussion does.
A leadership team rarely begins with "we are inattentive to results."
It usually begins much earlier.
People do not trust one another enough to be vulnerable.
Because they do not trust one another, they avoid real conflict.
Because they avoid real conflict, decisions get fake agreement rather than real buy-in.
Because there is no real buy-in, accountability becomes performative.
Because accountability is weak, personal priorities quietly outrun team results.
By the time the problem appears in a dashboard, a deadline, or a customer issue, the team has usually been going wrong for a while.
Leaders prefer process language because it feels safer
This is the part that matters most to me.
Leaders are often more comfortable discussing process than trust.
It feels more objective. More managerial. Less exposing.
If we say the launch slipped because the weekly review was weak, we can fix the weekly review.
If we say the launch slipped because two executives did not trust each other enough to say what they really thought three weeks earlier, the problem gets personal.
Now we are talking about emotional risk, not only process design.
Now we are talking about whether people are hiding disagreement until it is expensive.
Now we are talking about whether meetings are genuine forums for decision or staged rituals of politeness.
Now we are talking about whether a team prefers false peace over useful friction.
That is a much more uncomfortable diagnosis.
It is also why many organizations stay stuck. They keep repairing the visible machinery while leaving the human structure underneath untouched.
Artificial harmony is one of the costliest lies in a company
Many teams are not low-conflict. They are conflict-avoidant.
From the outside this can look mature. Meetings are polite. Nobody interrupts. People sound aligned. There are few visible flare-ups. Decisions appear to move forward calmly.
Then the real movie starts after the meeting.
Side conversations multiply.
Reservations surface privately.
People comply without committing.
Execution slows because unresolved disagreement has simply moved underground.
This is one of the most common patterns in teams that believe they have an execution problem.
What they actually have is an honesty problem.
People are not fighting about the right things in the right room at the right time.
So the organization pays later in delay, drift, hedging, ambiguity, and weak follow-through.
Healthy conflict is expensive in the moment and cheap in the aggregate.
Avoided conflict feels cheap in the moment and becomes extremely expensive later.
Commitment is not consensus
Another reason teams misdiagnose themselves is that they confuse commitment with comfort.
Real commitment does not require everyone to get their preferred outcome.
It requires clarity. It requires people to feel heard. It requires the decision to be explicit enough that they can genuinely align behind it after the debate is over.
Many teams never get there.
They leave a meeting with language like "roughly aligned," "let's take this forward," or "we can refine as we go."
That sounds collaborative. Often it is evasive.
Ambiguity then travels downstream disguised as flexibility.
The result is familiar. Teams revisit decisions, interpret them differently, or quietly wait for more certainty before acting. What looks like slow execution is often unresolved commitment.
This is one reason I dislike over-romanticized consensus cultures. They often create less commitment, not more.
People leave without enough clarity to act and without enough ownership to defend the call when it gets hard.
Accountability is hardest among peers
This is another place teams stay superficial.
They talk as if accountability is mainly a manager's responsibility.
It is not.
The strongest form of accountability in a serious team is peer accountability.
Can colleagues call one another out directly when behavior is slipping, promises are drifting, standards are being lowered, or the team is rationalizing bad work?
That is where many teams fail.
Not because they lack standards in theory, but because holding a peer accountable is emotionally uncomfortable. It risks tension. It risks retaliation. It risks awkwardness. So people escalate upward, stay silent, or soften the feedback until it no longer changes anything.
Then the manager becomes the only source of correction, and the team remains politically polite but operationally weak.
If the only person who can say the hard thing is the boss, you do not yet have a strong team.
You have a reporting structure.
Results deteriorate long before the dashboard shows it
The final dysfunction in Lencioni's model is inattention to results, but by the time a team gets there, the decay has usually been underway for a while.
Personal status starts competing with team success.
Departments optimize locally.
Leaders protect turf.
People care more about being right than getting to the right answer.
The meeting becomes a place to preserve image rather than solve reality.
At that point, the result problem is obvious.
But it is not primary.
It is the visible consequence of a team that has stopped functioning as a team lower down.
This is why some organizations keep missing goals despite looking full of intelligent, hardworking people. Intelligence and effort are not enough when the human operating system underneath the team is mistrusted, conflict-avoidant, ambiguous, and low on peer accountability.
Every company eventually reveals what it is willing to confront
I think this is one of the deepest cultural tests of an organization.
What is it willing to name?
Is it willing to say that the missed deadline was not mainly about planning, but about a team avoiding an honest disagreement?
Is it willing to say that the customer issue persisted not because nobody cared, but because functions protected themselves instead of confronting one another clearly?
Is it willing to say that a leader is smart but erodes trust?
Is it willing to say that the room is polite and ineffective?
Is it willing to say that false harmony is now costing the company speed?
Many companies are not.
So they become sophisticated at describing symptoms and amateurish at confronting causes.
The problem beneath the problem is usually human
This does not mean process is irrelevant.
Good operating systems matter. Clear roles matter. Decision rights matter. Review rhythms matter. Planning discipline matters.
But process usually amplifies the quality of the team underneath it. It rarely saves a team from fundamental dysfunction for long.
A low-trust team can turn any process into bureaucracy.
A conflict-avoidant team can turn any meeting cadence into theater.
A team without commitment can turn planning into drift.
A team that avoids accountability can turn scorecards into decoration.
This is why many company problems are misread as operational failures when they are actually human-system failures.
The process may be where you first notice the break.
The team is often where it was born.
Better diagnosis is a competitive advantage
One of the biggest advantages a leadership team can develop is the ability to diagnose at the right depth.
Not just what failed.
Not just which process broke.
But what kind of team dynamic made that failure more likely in the first place.
That requires courage because deeper diagnosis is always less flattering.
It demands that leaders look beneath missed deadlines and ask whether the team trusts one another enough, argues honestly enough, commits clearly enough, and holds peers accountable directly enough.
Many execution problems do not begin as execution problems.
They begin as trust problems that have not yet become legible.
And once you see that clearly, the work changes.
You stop treating symptoms as causes.
You stop trying to process-design your way out of human avoidance.
You stop congratulating polite teams for being healthy.
And you start looking for the problem beneath the problem.
That is where most real execution work begins.