The Five Dysfunctions Pyramid
Teams fail from the bottom up: fix trust before anything else
Patrick Lencioni's Five Dysfunctions model is a pyramid-shaped framework that identifies the five interrelated failures that prevent teams from performing at their best. The dysfunctions build on each other in a specific order: absence of trust at the base, followed by fear of conflict, lack of commitment, avoidance of accountability, and inattention to results at the top. The model reveals that most team failures are not about strategy or talent but about the interpersonal dynamics that either enable or destroy collaboration.
What makes this framework particularly powerful is its counter-intuitive insight that conflict is not the enemy of teamwork — artificial harmony is. Teams that avoid productive disagreement end up with ambiguity, which prevents genuine commitment, which makes accountability impossible, which ultimately means nobody is focused on collective results. The pyramid structure means you cannot fix a higher-level dysfunction without first addressing the ones below it.
- Trust is the foundation of every functioning team — without it, nothing else works.
- Productive conflict is not a sign of dysfunction; artificial harmony is.
- Commitment requires clarity and buy-in, not unanimous agreement.
- Accountability must be peer-to-peer, not just top-down from the leader.
- The ultimate measure of a team is whether members prioritize collective results over individual status.
- Build Vulnerability-Based TrustCreate an environment where team members feel safe admitting mistakes, weaknesses, and asking for help. This is not predictive trust but vulnerability-based trust. Use personal history exercises where team members share formative experiences, and model vulnerability as the leader by going first in disclosing weaknesses.Pro tipStart meetings with a simple personal check-in question to gradually build comfort with openness.WarningDo not force vulnerability — it must be genuine or it creates cynicism.
- Master Productive ConflictOnce trust exists, teach the team to engage in unfiltered debate around ideas — not personal attacks, but passionate disagreement about strategy, direction, and decisions. Mine for conflict by asking quiet team members directly for their views. Distinguish between ideological conflict and interpersonal politics.Pro tipWhen conflict gets uncomfortable, remind the team that what they are doing is necessary and productive.
- Achieve Genuine CommitmentAfter thorough debate, make clear decisions and ensure everyone commits even if they initially disagreed. The two biggest enemies of commitment are the desire for consensus and the need for certainty. Teams must learn that disagreeing and committing is better than false agreement. At the end of every meeting, review key decisions.Pro tipUse a disagree-and-commit protocol — explicitly ask dissenters whether they can commit fully.
- Embrace Peer-to-Peer AccountabilityBuild a culture where team members hold each other accountable directly, rather than relying on the leader to be the sole enforcer. This requires the trust and conflict foundations to already be in place. Publish goals and standards clearly so everyone knows what they are being held accountable for.Pro tipThe leader should step back slightly to encourage peers to speak up first.WarningWithout trust and healthy conflict, peer accountability feels like personal attacks.
- Focus on Collective ResultsEstablish clear, measurable team goals that override individual ego, departmental priorities, or career advancement. When team members prioritize their own status over the team's collective objectives, the team fails. Create public scorecards that track team-level outcomes and reward collective achievement.Pro tipTie compensation and recognition to team results rather than individual metrics.
In Lencioni's fable drawn from real consulting experiences, the fictional CEO Kathryn Petersen takes over DecisionTech, a company with a talented executive team losing to competitors with less talent. She diagnoses the five dysfunctions layer by layer, starting with an off-site where executives share personal histories.
Pat Flynn describes how his own growing team at Smart Passive Income experienced these dysfunctions as they scaled. Team members were polite rather than honest, decisions were ambiguous, and nobody was clear on priorities. After reading Lencioni's book, Flynn implemented vulnerability exercises and encouraged direct feedback.
Patrick Lencioni developed this framework over decades of consulting with executive teams at organizations ranging from Fortune 500 companies to startups and nonprofits. He published The Five Dysfunctions of a Team in 2002 as a leadership fable, telling the story of a fictional CEO named Kathryn Petersen who takes over a dysfunctional Silicon Valley company called DecisionTech. Lencioni drew on patterns he observed repeatedly across hundreds of teams, noticing that the same five problems appeared regardless of industry, size, or culture.