What This Workbook Actually Is
The Five Dysfunctions Of A Team Workbook is the companion to Patrick Lencioni's original book. It's not just exercises slapped onto blank pages. It's structured around the pyramid model — trust at the base, then commitment, accountability, results, and engagement at the top. Each section has reflection questions, group activities, and scoring sheets designed to surface real problems rather than performative team-building. I've run this with teams in healthcare, fintech, and a few nonprofit orgs. The model itself isn't revolutionary. What separates it from generic workshops is the workbook structure. You don't just discuss the five dysfunctions abstractly. You're forced to put actual numbers and observations on paper. That pressure is where the value lives. The typical session starts with the personal risk assessment. Each participant scores themselves anonymously across the five areas. Then the facilitator pulls out the aggregate. What you'll see on that first page is usually embarrassing. People rate their own trust significantly higher than the rest of the group does. That gap is the whole point.
How To Run It Without Looking Like An Amateur
Most people screw this up by treating it like a morale exercise. It's not. The workbook expects participants to be uncomfortable. If everyone walks out saying "we're great," you didn't do it right. Here's what I actually do when I run it. First, I skip the full pyramid in the opening. I don't walk through the theory for twenty minutes. People zone out. Instead, I start with the Team Risk Assessment right away. Get them scoring. Let them see the data before they hear the lecture. The numbers create genuine curiosity. Then I do the Trust assessment. Specifically the personal risk assessment. This is the one where people answer things like "Would you share your true feelings with teammates?" on a scale. Forty-five minutes. No discussion. Just individual reflection. After that, I have people share their answers in pairs, not in the full group. Small groups lower the threat level. By the time we talk about it collectively, people have already had a chance to say their piece without performing.
Commitment comes next. This is where the real work happens. I ask each person to identify one decision their team recently made and rank how clearly it was communicated. It's a blunt question. It cuts through the noise. When someone says "I'm not sure we were actually committed to that product launch timeline," the room usually goes quiet for real. Accountability is the section where most programs stall. People avoid peer-to-peer feedback like it's contagious. I handle it differently. Instead of open floor criticism, I use the structured peer feedback exercise in the workbook. Each person receives a printed card with three things going well and one area to improve. It's anonymous but specific. It gives permission for the conversation without making anyone feel targeted.
Get the Full Details
A Specific Problem I Faced
Last year I was running this with a remote engineering team of twelve. Two senior engineers refused to fill out the accountability section honestly. They wrote vague answers like "good communication overall" and "everyone is aligned." The rest of the team had already been brutal in earlier sections. Those two answers stood out like a sore thumb. My workaround: I pulled them aside individually after the session. Not publicly. One at a time. I showed them the aggregate from their section and asked them directly what was happening. They admitted the rest of the team didn't actually hold each other accountable and they didn't want to be the first to call it out. I adjusted the next session to include a structured accountability exercise where they practice giving feedback using a template from the workbook. Two weeks later, the same two engineers had shifted their self-ratings significantly. The workbook had a dedicated exercise for that exact scenario.
What Most People Miss About This Workbook
The model assumes you can diagnose dysfunction the way you'd diagnose an illness. That's partially true and partially dangerous. Not every team problem maps cleanly onto the five-dysfunction pyramid. A team might score perfectly on trust and engagement but still be failing because of broken compensation structures, unclear promotion paths, or leadership that rewards the wrong behaviors. Lencioni himself notes this occasionally but the workbook doesn't fully address it. My approach is to run the assessment and then separately map the results against organizational structures. If the dysfunction scores don't match the symptoms people describe, the problem is likely structural rather than cultural. That distinction matters. Another thing nobody warns you about: the workbook generates data that can be misused. I've seen managers take the trust scores and use them to justify firing low-scoring individuals. That's not what the tool is for. It's designed to reveal patterns, not punish outliers. Low scores often reflect systemic issues, not personal defects. The aggregate tells the real story.
When This Doesn't Work
Here's the blunt truth. This workbook fails in environments where psychological safety is already absent and leadership isn't willing to model vulnerability first. If the CEO or direct manager never admits mistakes in front of the team, running this exercise becomes theater. People will either game their answers to please authority or they'll stay silent and learn nothing. It also doesn't help much with brand new teams under six months old. The trust assessment requires enough shared history for people to have formed opinions. A team that just came together last month will give uniform high scores simply because there's no negative history yet. That looks like success but it's actually noise. For those situations, I usually recommend starting with simpler interventions. A basic retrospectives format or a structured one-on-one check-in system. Build the baseline trust first. Then bring in the workbook when the team has enough shared experience to produce meaningful data.
What I Actually Use From It
Over multiple runs, I've converged on a shorter version. The full workbook takes about six to eight hours. I rarely have that kind of time. I cut it down to roughly two hours by focusing on the Trust and Accountability sections. Those two drive the rest. If trust is present, accountability happens naturally. If they're both solid, commitment and results follow. The scoring sheets are genuinely useful though. I keep a running log of the aggregate scores across quarters. That longitudinal data is worth more than any single session. You can track whether a team is actually improving or just temporarily comfortable after a workshop. If you're looking to get started, you can find The Five Dysfunctions Of A Team Workbook as a standalone PDF or print version through standard business book retailers. It's fairly inexpensive compared to hiring a facilitator. The catch is that without a skilled facilitator, you'll probably waste half the content on polite conversation instead of real diagnosis. Even a basic video walkthrough helps a lot.
