The Five Dysfunctions of a Team — Review for Academic Medicine
Your Team Is Not Broken — It Is Stuck
Think about the last time your faculty meeting produced a genuine disagreement that ended with a real decision everyone actually followed through on. If you cannot remember one, you are not alone. That silence is not harmony. It is dysfunction with a polite face.
Patrick Lencioni's The Five Dysfunctions of a Team is the most useful book I have encountered for naming what goes wrong inside leadership teams. Published in 2002 and still landing hard, the book lays out a model of five dysfunctions team review readers will immediately recognize in their own departments. If you lead physicians, this book will make you uncomfortable in the best possible way.
The Model: A Pyramid of Connected Failures
Lencioni structures his five dysfunctions as a pyramid, with each layer building on the one below. That structure matters. You cannot fix the top without addressing the bottom.
- Absence of Trust. Team members are unwilling to be vulnerable with each other. They do not admit mistakes, ask for help, or say "I do not know."
- Fear of Conflict. Without trust, people avoid productive disagreement. Meetings are polite, surface-level, and useless.
- Lack of Commitment. Without honest debate, decisions feel imposed rather than shared. People leave the room without real buy-in.
- Avoidance of Accountability. Without commitment, no one holds colleagues to standards because they never genuinely agreed to those standards in the first place.
- Inattention to Results. Without accountability, individuals prioritize their own status and ego over collective outcomes.
The genius of the model is its causality. Most physician leaders I coach want to start with accountability. "My faculty do not follow through." But Lencioni would ask: follow through on what? Decisions they never committed to? Commitments after debates that never happened? You have to start at the bottom.
Absence of Trust in Academic Medicine
Lencioni's definition of trust is narrower and more useful than the everyday version. He does not mean predictability or reliability. He means vulnerability-based trust — the willingness to say "I was wrong," "I need help," or "Your idea is better than mine."
Academic medicine actively trains this out of people. From the first day of medical school through fellowship, the signal is consistent: competence means certainty. Showing doubt is showing weakness. By the time a physician becomes a department chair or division chief, they have spent decades building armor. Asking them to take it off in a leadership meeting is not a small request.
But without it, nothing else in the pyramid works. In my coaching practice, I see this constantly. A leadership team that cannot have an honest conversation about resource allocation because no one wants to admit their program is struggling. A division that avoids discussing a faculty member's chronic underperformance because raising it feels like a personal attack rather than a professional obligation.
Lencioni recommends exercises like the Personal Histories Exercise, where team members share formative life experiences. It sounds trivial. In practice, it is one of the most powerful interventions I have used with physician teams. When you learn that your colleague grew up in a family where asking for help meant failure, you understand their resistance differently. That is the beginning of trust.
Fear of Conflict: The Silent Faculty Meeting
Here is a pattern I see so frequently that I consider it a diagnostic sign. The chair presents a significant proposal — a new compensation model, a restructured call schedule, a curriculum overhaul. The room is quiet. Someone asks a clarifying question. The chair says, "Great, sounds like we are aligned." Two weeks later, nothing has changed, and three faculty members are complaining in the hallway about the decision they silently endorsed.
That is fear of conflict in action. Lencioni distinguishes between productive ideological conflict and destructive interpersonal conflict. Teams that avoid the first inevitably get more of the second, because unresolved disagreements do not disappear. They go underground.
The fix is not to encourage people to argue. It is to make conflict safe and expected. One technique Lencioni describes is "mining for conflict" — a leader actively looking for unspoken disagreement and pulling it into the open. "I can see some of you are hesitant. What am I missing?" That question, asked genuinely, can transform a faculty meeting from theater into governance.
Lencioni Team Dysfunction and the Physician Ego Problem
I want to name something Lencioni does not address directly but that every physician leader knows. The fifth dysfunction — inattention to results — takes a specific form in academic medicine. The "results" that individuals prioritize over team outcomes are not usually financial. They are reputational. Publications, grants, speaking invitations, named professorships. These are the currencies of academic identity, and they are almost entirely individual.
This creates a structural tension. The department needs collective performance. The incentive system rewards individual achievement. A physician leader trying to build a real team is working against the grain of how academic careers are built.
Lencioni's answer is to define team results clearly and make them visible. In academic medicine, this means the chair who tracks and celebrates collective metrics — trainee match outcomes, patient experience scores, collaborative grant submissions — with the same energy the institution gives to individual awards. It means asking, "What did our division accomplish this quarter?" rather than "What did each of you accomplish?"
Where the Fable Works and Where It Does Not
The book is written as a leadership fable — a fictional story about a CEO who inherits a dysfunctional executive team. The fable makes the model memorable. You will recognize characters in your own leadership meetings. The technically brilliant team member who will not engage. The people-pleaser who agrees with everyone and commits to nothing.
Where the book is thinner is on implementation in complex organizations. Lencioni wrote for corporate executive teams — small groups with a single leader and clear authority. Academic medicine is messier. Faculty have tenure protections, dual reporting lines, and a relationship to their discipline that often trumps their relationship to their department. The model still applies, but the application requires more creativity than the book provides.
The One Sports Analogy I Will Allow Myself
Think about a basketball team where every player is trying to score rather than trying to win. The stats look fine individually, but the team loses. That is a department full of productive faculty members who never coordinate, never sacrifice individual advantage for collective gain, and never hold each other accountable for anything beyond personal output. Trust is the foundation. Everything else follows from it.
Who Should Read This
If you lead a team in academic medicine — any team, from a two-person research group to a fifty-member department — The Five Dysfunctions of a Team is essential reading. It is short, accessible, and will give you language for dynamics you have been sensing but could not name.
Read it and then do one thing. At your next leadership meeting, ask your team a genuine question and do not fill the silence. See what surfaces. If nothing does, you know where to start.
Learn about coaching for departments.
