A Walkthrough of the Five Dysfunctions Skill: Diagnosing and Fixing Team Breakdowns
Six commands that assess your team across Lencioni's five dysfunctions and build the trust, conflict norms, commitment, accountability, and results focus that high-performing teams require.
Patrick Lencioni's The Five Dysfunctions of a Team describes the cascading failures that prevent teams from performing: absence of trust leads to fear of conflict, which leads to lack of commitment, which leads to avoidance of accountability, which leads to inattention to results. The model is presented as a pyramid because each dysfunction is foundational to the ones above it.
The Five Dysfunctions BookSkill has six commands for team leaders. Here's what each does.
The Six Commands
/team-assessment — Score All Five Dysfunctions
What it does: Provides a comprehensive assessment of your team across all five dysfunctions. For each dysfunction, you evaluate your team with specific behavioral evidence — not "how do you feel about team trust?" but "give me an example of a time someone on your team admitted a mistake openly." The evidence-based assessment produces a more accurate picture than intuition.
What you get: A team dysfunction scorecard — your team's current score on each of the five dysfunctions, with the specific evidence behind each score and identification of the most critical dysfunction to address first.
When to use it: First. The assessment establishes where your team is and directs the other commands toward the highest-priority issues.
/trust-builder — Build Vulnerability-Based Trust
What it does: Lencioni distinguishes between predictive trust (I trust you because I know your behavior) and vulnerability-based trust (I trust you enough to be honest about my mistakes and weaknesses). The latter is harder to build but is the foundation of genuine team function. This command designs exercises and practices that build vulnerability-based trust.
What you get: A trust-building action plan — specific exercises and team practices (like personal history exercises, behavioral profiles, and structured feedback) that build the kind of trust that enables productive conflict.
When to use it: When the team assessment reveals low trust. Trust-building is the foundational work — the other commands are much less effective without it.
/conflict-norms — Establish Healthy Disagreement Rules
What it does: Lencioni's observation: teams that avoid conflict don't have less conflict — they have more, but it goes underground. Hidden conflict produces passive-aggressive behavior, political maneuvering, and poor decisions. This command helps you establish norms for healthy, productive disagreement: how conflicts are surfaced, how they're conducted, and how they're resolved.
What you get: A conflict engagement rules document — the specific norms your team agrees to for how disagreements are handled, including what kinds of conflict are expected and constructive.
When to use it: After building trust. Conflict norms only work on a foundation of trust — without trust, the norms feel like permission to attack rather than permission to disagree productively.
/commitment-clarity — Ensure Everyone Leaves Aligned
What it does: Lencioni's commitment insight: teams don't need consensus to commit — they need clarity. Everyone doesn't have to agree with the decision, but everyone needs to know what the decision was and be willing to commit to it. This command helps you establish practices for ensuring meetings and discussions produce clear commitments that everyone understands.
What you get: A commitment clarity checklist — specific practices for closing meetings and discussions with clear commitments: who is doing what by when, and what "done" looks like.
When to use it: When the team assessment reveals lack of commitment, or when decisions seem to get relitigated after they've been made.
/accountability-structure — Build Peer Accountability
What it does: Lencioni's accountability finding: in high-performing teams, peer accountability — team members holding each other to commitments — is more powerful than hierarchical accountability. This command designs peer accountability mechanisms: how the team tracks commitments, how members call each other out when standards slip, and how accountability conversations are conducted.
What you get: An accountability framework — specific mechanisms for tracking and reinforcing team commitments, including how to have accountability conversations that feel collaborative rather than punitive.
When to use it: After commitment clarity is established. Accountability only works when commitments are clear.
/results-scoreboard — Create Shared Focus
What it does: The fifth dysfunction is inattention to results — when team members prioritize their individual status, their department's metrics, or their personal preferences over the team's collective results. This command helps you create a visible, shared scoreboard that focuses team attention on collective outcomes.
What you get: A team scoreboard design — the two or three collective metrics that define team success, presented in a way that makes the team's progress visible and creates shared ownership of the outcomes.
When to use it: As an ongoing practice. The scoreboard isn't a one-time exercise — it's a persistent visual reminder of what the team is collectively accountable for.
Recommended Sequence
Work up the pyramid in order:
/team-assessment— diagnose all five dysfunctions/trust-builder— foundational; everything else depends on this/conflict-norms— establish rules for productive disagreement/commitment-clarity— ensure clear commitments come from decisions/accountability-structure— build peer accountability/results-scoreboard— maintain collective focus on outcomes
What Lencioni's Framework Delivers
Lencioni's most important observation is that team dysfunction is systemic, not individual. It's not that you have bad people on your team — it's that you have a system that makes trust, productive conflict, and accountability difficult. The Five Dysfunctions Skill addresses the system, not the people.
The assessment often reveals that the visible problems (poor results, unclear accountability) are downstream symptoms of less visible problems (fear of conflict, lack of trust). The skill directs the work to the right level.
Ready to assess your team? Get the Five Dysfunctions BookSkill and start with /team-assessment.