The Five Dysfunctions Of A Team Facilitators Guide

Facilitating the Pyramid: What Actually Works When You Open This Book

I've run this workshop probably two dozen times across different orgs. Most people treat Patrick Lencioni's model like a checklist. That's why it fails half the time. The facilitator's guide sits there with its exercises and timing breakdowns, looking useful, but if you just march through it without reading the room, you'll produce exactly what you were trying to prevent. Here is how I approach it, and where the guide quietly under-sells what you need to handle.

The Five Dysfunctions Of A Team Facilitators Guide and Why It Needs a Different Read

The core pyramid moves from Absence of Trust through Fear of Conflict, Lack of Commitment, Avoidance of Accountability, and Inattention to Results. The guide structures the session around each layer. You spend time on trust-building exercises, then conflict, then commitment, and so on. The logical flow makes sense on paper. In practice, the layers are not independent. When you address Commitment without Trust, the exercise collapses. People nod. They agree to things they won't follow through on because the foundation isn't there. The guide warns about this sequence, but it doesn't emphasize strongly enough that you can sometimes diagnose the wrong layer. I had a team once that couldn't hold each other accountable. Everyone assumed it was an Accountability problem. We were about two-thirds through the Accountability exercise when I noticed the real signal: people were avoiding direct disagreement during the conflict segment before it, masking their positions with polite agreement. The Accountability exercise was surface-level posturing. We went back up to Conflict and spent another hour there before the Accountability work actually landed. This is the most common mistake. You diagnose the visible symptom instead of the structural cause. One specific workaround I use: during the opening Trust exercise, I don't just run the standard personal history sharing. I watch who stays vague, who deflects, and who over-shares as a performance move. Those three behaviors tell me immediately which layer is fragile. If someone is over-sharing, they're building false intimacy. That team won't have genuine vulnerability later. If someone stays vague, they're protecting something. The team will avoid Conflict. I adjust the session based on that initial read rather than following the guide page-by-page.

Running the Exercises Without Looking Like a Corporate Consultant

The guide provides detailed instructions for each activity. The personal history exercise, the conflict debate, the commitment vote. The instructions are thorough. Thorough enough that you could lose the thread. What the guide doesn't spell out is that your delivery tone determines whether these exercises feel like therapy or like a compliance activity. Most facilitators tip into compliance mode without realizing it. They read the instructions, they check the time, they move to the next slide. The team senses this and mirrors it back. I keep the guide open but I rarely read from it verbatim. I paraphrase. I set the context, I state the objective, I give people 90 seconds to understand what's happening, and then I step back. The more you narrate an exercise, the more it becomes a performance. The less you narrate, the more people actually engage. This usually cuts the per-exercise runtime by about a third because you stop adding transitional commentary that nobody needs. The conflict exercise is the one that breaks most facilitators. The guide tells you to assign opposing positions and have people debate. The assumption is that teams will engage in productive disagreement. They won't. They will perform disagreement. You will hear "I see your point but..." repeated until the timer runs out. This is not conflict. This is polite disagreement dressed up as work.

The workaround I use: I pre-wire two or three people privately before the session. I give them permission and encouragement to actually press each other during the exercise. Not aggressively. Directly. When the rest of the room sees two people having a real, slightly uncomfortable conversation about substance, the social permission spreads. The exercise suddenly becomes useful. Without that pre-wiring, the conflict segment is almost always theater.

When the Guide Does Not Apply

The Five Dysfunctions Of A Team Facilitators Guide assumes a co-located or consistently synchronous team that meets regularly. It does not account well for distributed teams operating across time zones with async communication as the default. I ran this with a team spread across four time zones and three continents. The trust exercise worked adequately. The conflict exercise produced nothing useful because people who never interact synchronously don't have the relational currency to engage in real disagreement. The accountability segment devolved into email-thread blame because the social feedback loop was absent. In those situations, I substitute portions of the guide with structured peer feedback rounds using a written format first. People write their concerns anonymously, they get read aloud, they discuss. It is slower. It is less energetic. But it produces actual data instead of the polite fiction you'd get from a live conflict exercise across Zoom with ten people on mute. Another scenario where the guide falls apart: teams with a severe power imbalance where the leader is actively undermining psychological safety. No amount of trust-building exercises will fix this. The leader sets the tone. If the leader rewards loyalty over honesty, the team will learn that lesson faster than anything you can facilitate in a two-hour session. I've seen this repeatedly. The dysfunction isn't absense of trust. It's leadership behavior disguised as team culture. You can facilitate the exercises, but the results won't stick. In these cases, the honest recommendation is usually to address the leadership issue directly rather than running a team workshop. It wastes everyone's time otherwise.

The Accountability Section and What Nobody Says Out Loud

This is the part most facilitators fumble. The guide presents accountability as peer-to-peer commitment to standards. In organizations where performance management is centralized and controlled by managers, peer accountability is structurally impossible. People will agree to hold each other accountable in the session. They will not do it afterward because the actual consequences flow upward, not laterally. The guide doesn't address this organizational design problem. I always clarify this during the accountability segment. I ask the group directly: who actually has the authority to enforce the standards you're about to commit to? If the answer is "our manager" and not "us," then you're not building peer accountability. You're building a wish. I redirect the exercise toward commitment to a small set of team-level norms that peers can actually enforce, separate from the formal performance system. It's a narrower scope. It's more realistic. And it actually changes behavior.

Practical Notes on Session Flow

A full facilitated session using the guide typically runs three to four hours. If you are rushing, cut the trust exercise short and accept the consequence: the later segments will feel hollow. I've done it. I regret it every time. A half-hour truncated trust exercise leaves the team operating at about sixty percent capacity for the remaining segments. Better to do one layer thoroughly than three layers superficially. The guide recommends breaking into small groups for several exercises. This works well for teams of eight to twelve. Beyond twelve, the small group conversations lose depth because people rotate through too many strangers. I cap the session at twelve participants. If you have more, you run two parallel sessions or you split the group. Combining fourteen people into breakout rooms produces muffled conversations that resolve nothing. Post-session follow-up is where most implementations die. The guide mentions it briefly. I treat it as the most important part. Within two weeks of the session, I schedule a thirty-minute check-in focused on one thing: which commitment from the session did you actually act on? Not which exercise was valuable. Which specific action did you take. This follow-up takes about twenty minutes of my time and it roughly doubles the retention rate of the session content. Teams that skip it revert to old patterns within a month. It is that predictable.

If you are looking for the actual facilitator's guide document, it is published by Jossey-Bass alongside the main book. You can find it through standard business book retailers. It accompanies the five-part assessment tool that Lencioni's organization provides. The assessment gives you baseline data on where the team sits on each dysfunktion. Use it before the session, not after. It saves time by showing you which layer to prioritize rather than assuming you need to cover all five equally. The model itself is simple. Simpler than most team dynamics frameworks. That simplicity is both its strength and its weakness. It is easy to teach, easy to remember, easy to reduce to a poster on a conference room wall. Doing that is where it becomes useless. The work happens in the facilitated session and the follow-up behavior change. Not in the concept. If you treat it as a concept, you'll spend an hour explaining the pyramid and nothing will change. If you treat it as a process with real friction and real human resistance, it will do what it claims to do, assuming the team actually needs this and isn't dealing with a structural leadership problem that no workshop can fix.