Five Dysfunctions Of A Team By Patrick Lencioni

The Pyramid Isn't The Point — Most People Miss That Entirely

I picked up Five Dysfunctions Of A Team By Patrick Lencioni around 2014 because a director of mine made it required reading after yet another project imploded from sheer miscommunication. Three years in, it still sits on my desk. Not because it changed my life, but because it gave me a vocabulary for things I was already observing but couldn't articulate. It's an organizational model built as a pyramid with five layers, each one dependent on the one below it. At the base is Absence of Trust. Below that lies Fear of Conflict. Above that is Lack of Commitment. Then Avoidance of Accountability. And at the very top sits Inattention to Results. Here's what most summaries leave out. The model isn't meant to be read top-down like a checklist. You diagnose from the top and build from the bottom. If your team is arguing about priorities but never executing, that's an Absence of Trust problem disguised as a Conflict problem. You don't fix the symptom. You go two layers down and address the root.

I learned this the hard way during a product launch where two senior engineers spent three weeks publicly dismantling each other's architecture decisions. The project manager brought in a conflict resolution workshop. It made the tension slightly more civil for about ten days. Then it erupted again. We stopped trying to manage the conflict and went back to trust. Turns out neither engineer had ever been vulnerable about their actual weaknesses in front of the other. Once that happened — awkward silence, honest conversation, no grand revelation — the conflict became functional instead of personal. The launch shipped on time. Took four months instead of two, but it shipped.

Breaking Down Each Dysfunction And What It Looks Like In Practice

Absence of Trust

This isn't the surface-level version of trust you get from team-building retreats and trust falls. Lencioni means operational trust. The ability to say "I don't know" without being perceived as incompetent. The ability to ask for help without it becoming a performance review. When this is missing, team members hide weaknesses and mistakes. They come to meetings polished and leave them unchanged. In a high-trust team, people admit when they're stuck before the deadline becomes an emergency. In a low-trust team, everyone works late in secret hoping nobody notices until it's too late. The cost difference between these two states is measurable. I've seen projects with chronic trust issues run 40 to 60 percent over budget because nobody would flag risks early. The numbers look fine until they don't.

Fear of Conflict

Artificial harmony is worse than open conflict. A team that never disagrees is a team that hasn't found the right answer yet. The fear of conflict manifests as polite agreement in meetings followed by sabotage in execution. People nod along then go do whatever they actually wanted to do. This is the most common dysfunction I see in mature organizations, not startups. Senior teams are good at being civil. They've spent decades learning not to make waves. The workaround I use is structured disagreement. Before any major decision, I assign one person to argue against whatever direction is trending. Not to be difficult. To surface the actual objections before they surface elsewhere. It takes twelve minutes. Cuts decision review cycles by roughly half.

Lack of Commitment

This is about ambiguity. When a team can't disagree openly, they can't commit fully. They sit on the fence and revisit the decision every time conditions change. "We agreed to Q2" becomes "Actually, I thought we meant Q3" three weeks later. The team appears collaborative because nobody is fighting. They're actually drifting. Commitment in Lencioni's framework doesn't mean blind agreement. It means you can disagree fiercely, then execute as if you agreed. That's called "disagree and commit" and it's the single most underpracticed concept in corporate America. I've worked on teams where people confused commitment with consent. Those teams never moved fast.

Avoidance of Accountability

When commitment is absent, peer accountability disappears. People stop calling each other out because they never really agreed on anything in the first place. The manager becomes the sole enforcer, which means enforcement is inconsistent and resented. Low-performers float because nobody wants to be the bad guy. The signal here is simple. If your manager is the only person holding anyone accountable, you have an accountability problem, not a management problem. The fix isn't stronger leadership. It's clearer commitments from the previous layer. I've seen teams turn this around by publishing three measurable commitments per quarter and reviewing them publicly every Friday. No drama. Just data.

Inattention to Results

The top of the pyramid. A team that cares more about individual success, career trajectory, or departmental goals than collective outcomes. This is where "we did our part" becomes a defense rather than a completion. Individual results matter less than team results. If the product ships late but your module was done on time, you failed the team. In practice, this dysfunction shows up as promotion wars, credit hoarding, and resource hoarding. People protect their territory. They optimize for their metrics while the overall initiative bleeds out. I watched a marketing team hit every KPI for three consecutive quarters while the revenue they generated dropped 18 percent because they were optimizing for clicks, not conversions. The numbers were technically correct and the business was losing money. Classic results dysfunction.

How To Actually Use This Model Without Turning It Into Another Meaningless Corporate Exercise

The biggest mistake I see is treating the pyramid as a diagnostic quiz. People rate themselves on each layer and move on. That's useless. The model only works when you apply it to a specific team problem you're already facing. Pick one active project. Map the dysfunction you're seeing back to the pyramid. Start at the lowest layer that applies and work up. Another common error is assuming this is a one-time assessment. It isn't. Teams regenerate dysfunction when pressure increases, when new members join, or when leadership changes. I re-evaluate my teams against this framework quarterly, not annually. The annual review cycle is too slow. Problems compound faster than that.

The Downloadable Worksheet

There isn't an official PDF from Lencioni's company that I'm aware of. The framework is described in the book, and several consulting firms have created their own adaptation sheets. If you want a working template, I use a modified version that combines all five layers into a single assessment matrix. It tracks symptoms, root layer, intervention, and outcome over a twelve-week cycle. You can find similar free worksheets on sites like Management Consulted and Ken Blanchard's resource library. They're adequate. Nothing is perfect about them. They tend to oversimplify the trust layer and skip over the accountability mechanics entirely. I keep my own sheet because it includes time-boxed exercises for each layer rather than just checkboxes. The exercise for Absence of Trust alone takes forty-five minutes and requires the team leader to go first and be genuinely vulnerable. No amount of paperwork substitutes for that behavior.

Where This Framework Falls Apart

It doesn't work in transactional environments where team members rarely interact beyond handoffs. If your organization is structured as a series of siloed departments with formal interfaces, the pyramid collapses because the dysfunction lives in the gaps between teams, not within them. Remote-first teams also expose a limitation. The model assumes face-to-face interaction as the default condition. You can adapt it, but you need to be intentional about virtual trust-building, which the book barely addresses. The biggest practical limitation is time. Running a proper diagnosis and intervention through all five layers on a single team takes eight to twelve weeks minimum if you're doing it with any fidelity. Most organizations don't have that kind of runway. They want a six-week fix. The framework doesn't give you one. If you're pressed for time, start with just the trust and commitment layers. Two-thirds of the problems resolve there without touching the rest. For very small teams — fewer than five people — the model overcomplicates things. Direct communication usually resolves these issues faster than any structured framework. For very large teams — over twenty — you need to apply it at the sub-team level. A single twenty-person team operating as one unit will never build sufficient trust for the higher layers to function. Break it into smaller groups first.

What To Do Instead If This Doesn't Fit Your Situation

If your team's problems stem from unclear roles rather than interpersonal dynamics, try RACI matrices or a responsibility assignment matrix before touching the pyramid. If the issue is structural — wrong incentives, broken compensation, misaligned KPIs — no amount of trust-building will fix it. Fix the structure first. The model assumes the underlying organization is sound and the problems are behavioral. That's a big assumption. Tuckman's stages of group development — forming, storming, norming, performing — might be more appropriate if your team is newly formed and still in the chaotic early phases. Lencioni's model assumes a team that has existed long enough for dysfunction to become embedded. A brand-new team doesn't have dysfunctions yet. It has confusion. Those are different problems with different solutions. The model is useful because it's simple enough to remember and deep enough to be accurate. It's not complete. It leaves out power dynamics, organizational politics, and the role of external stakeholders. None of those are addressed. I've seen teams master the pyramid internally and still fail externally because a sponsor pulled the funding or a client changed the requirements. Internal cohesion matters. It's not everything.