Principle · Chief HR Officer

Five Dysfunctions of a Team.

Source: Patrick Lencioni, The Five Dysfunctions of a Team: A Leadership Fable (2002), Jossey-Bass.

The Principle

Lencioni's model names five layered dysfunctions that prevent teams from producing collective results. They are stacked because each builds on the one below it. Fix them in order, from the bottom up, and the team converges on results. Skip a layer and the higher layers cannot hold.

The pyramid, from bottom to top: (1) Absence of Trust. Team members do not feel safe being vulnerable with each other, so they posture instead of producing. (2) Fear of Conflict. Without trust, the team avoids productive disagreement, so decisions are made on partial information. (3) Lack of Commitment. Without real conflict, decisions are not genuinely owned, so commitment is performative. (4) Avoidance of Accountability. Without commitment, team members do not hold each other to standards, so performance drifts. (5) Inattention to Results. Without accountability, individual or departmental wins replace collective outcomes, so the team optimizes for the wrong things.

The model is powerful because it explains why most "team improvement" interventions fail. A team with no trust cannot be fixed with a results-focused offsite. The diagnosis is wrong. The lower dysfunction is what is preventing the higher one from improving. Always look down the stack first.

Why It Matters Here

The CHRO is the executive most likely to be brought in to fix a team that is "not working well together." Without this principle, the CHRO ends up running surface-level interventions (more meetings, clearer roles, better communication tools) that fail to land because the actual dysfunction is two layers deeper. With it, the CHRO diagnoses up the stack and intervenes at the layer that is actually broken, which is usually trust or conflict.

Signals (When to Apply)

A leadership team meeting feels polite but produces no real decisions
The same issues come back up repeatedly because no one ever truly committed to the resolution
Team members complain about each other privately but never to each other
Departmental wins are celebrated more loudly than company outcomes
An executive team is high-performing on paper but the company is missing its goals

How to Apply

Diagnose down the pyramid, not at the symptom level. If the team is not committing to decisions, do not run a commitment workshop. Look at the conflict layer. Are real disagreements being surfaced? Look at the trust layer. Are people willing to be wrong in front of each other?
Build trust through structured vulnerability. Personal histories, working-style assessments (DiSC, Enneagram, Myers-Briggs as a starting point, not a destination), peer-to-peer acknowledgments. The exercises feel uncomfortable. That is the point.
Make conflict productive by naming it as expected. The team has different perspectives by design. Disagreement is the input to a good decision, not a sign of dysfunction. Refer to the company's productive-conflict cultural norm and reinforce it.
Force commitment by asking explicitly. End every decision meeting with "we are agreeing to X, by Y, owned by Z. Anyone not on board?" Silence after that question is consent. Rumblings later are violations of the commitment, not new disagreements.
Build accountability peer-to-peer, not just manager-to-direct. The strongest teams hold each other to the standards they committed to, without waiting for the boss to enforce them. The CHRO designs rituals (peer reviews, retrospectives, mutual scorecards) that make this normal.
Tie performance and reward to collective results, not just individual or departmental ones. If bonuses are paid on hitting departmental KPIs while the company misses its top-line, the system is incentivizing exactly the dysfunction the model warns about.
Run team health diagnostics quarterly. Lencioni's published assessment or a custom version. The data identifies which layer to invest in next.

Examples

Applied well A 10-person leadership team is missing quarterly targets, and the founder asks the CHRO to run a "team alignment offsite." The CHRO interviews each leader individually first and finds the diagnosis is at the trust layer: three of the leaders openly distrust two others, and the entire team avoids real conflict in meetings. The CHRO designs the offsite around trust building (personal histories, behavioral profile sharing, structured vulnerability) before any goal-setting work. Real conflict surfaces on day two. By the end of the offsite, the team has not "aligned" yet, but they are willing to disagree out loud. Two weeks later, the team makes a hard call (cutting a struggling product line) that they had been avoiding for months. The miss in quarterly targets gets addressed because the team can finally make the decisions it had been postponing.

Misapplied The same CHRO skips the diagnosis and runs an offsite focused on "results and accountability." The team builds beautiful scorecards and commitments. Within a quarter, the scorecards are out of date, the commitments are silently broken, and the team is back to the same pattern of polite meetings and missed targets. The work was real. The diagnosis was wrong. Without trust and conflict in place, the accountability layer cannot hold. The CHRO solved a level-4 problem that was actually a level-1 problem.

When to Break It

In acute crisis where the team must produce a result this week and there is no time to rebuild trust first. Make the call from the top, deliver the result, then go back and fix the underlying layer once the fire is out.
In a brand new team that has not yet had time to develop trust naturally. Skipping ahead to results is unavoidable in the first 30-60 days. Use the early work as the trust-building substrate, not as a bypass.
When the dysfunction is not actually a team problem but a single-individual problem. One wrong-person executive can simulate all five dysfunctions for the team they are on. The intervention is not team work. It is a personnel decision.