Running the Five Dysfunctions Assessment Without Wasting Everyone's Time
The assessment is a self-report questionnaire built around Patrick Lencioni's pyramid model. Your team rates themselves on statements tied to each of the five dysfunctions: absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. The official assessment component runs about twenty minutes per person, and the group debrief typically takes another forty-five to sixty minutes depending on how much airtime the facilitator gives each dysfunction. Here is how I have been running it for the past few years after watching too many teams treat it like a box-checking exercise.
The Five Dysfunctions Of A Team Assessment
Start by having each person complete the questionnaire individually and independently. I used to do this live in a meeting room, and it produced garbage data because people saw each other typing. Someone will slow-type if they are filling in "strongly disagree" on the trust items. People will watch and adjust. Just send the link out the day before and ask for completion before the session starts. It saves you twenty minutes and keeps the results honest. Once you have the raw scores, aggregate them by dysfunction level rather than by individual. The point is to see where the team clusters, not to spotlight one person's low score. Lencioni's own scoring guide gives you a banding system: most teams end up with a clear dominant dysfunction that sits at the base of the pyramid. Work from the bottom up. If you try to tackle accountability before you have addressed conflict, you are just putting a bandage on a leaky pipe. I ran this with a cross-functional product team last year and hit an edge case that catches people off guard. The team had identical dysfunction profiles on paper but completely different interpretations of what "fear of conflict" actually looked like in their context. One camp saw it as avoiding disagreement in meetings. Another camp saw it as not pushing back on deadlines. The aggregate score looked fine, but the gap in definitions meant the intervention missed. The workaround was to spend the first fifteen minutes of the debrief session asking people to write down their own definition of each dysfunction on a sticky note before any group discussion happened. Reading those out loud exposed the mismatch immediately and gave us something concrete to discuss instead of arguing about abstract labels.
Here is a counter-intuitive thing most facilitators miss. The assessment is least useful when every dysfunction scores high across the board. That usually means people are either rushing through it or genuinely unsure how to answer, and either way you get a flatline profile that tells you nothing actionable. In those cases, I go back and re-run just the trust and conflict sections with a forced-pair exercise where two people take turns describing a recent disagreement they avoided. The paired conversation surfaces stuff the questionnaire never would, and then the second round of scoring becomes meaningful. Another nuance nobody talks about is that the assessment penalizes team size beyond eight to ten people. I tested this with a twelve-person engineering group and the aggregate scores became unreliable because the variance in the raw data was too wide. Half the team had never worked closely enough together to reliably rate the same dynamics. I split them into sub-teams for the initial assessment, then ran a separate integration session afterward to map where the dysfunction patterns overlapped. Took twice as long but produced actual insights instead of noise. There are also real limitations you need to be honest about. The model assumes dysfunction cascades upward from trust, which is mostly true in co-located teams with stable membership. If your team is fully remote with rotating contractors, the trust dynamic operates differently and the pyramid can mislead you into looking for interpersonal roots when the actual problem is structural—like unclear decision rights or misaligned incentives. In those environments I pair the assessment with a RACI exercise first, because fixing the process layer often resolves what looks like a trust issue on the surface.
The assessment also doesn't account for psychological safety as a standalone construct. Amy Edmondson's work predates Lencioni's model and covers some of the same ground with more empirical backing. If your team is dealing with trauma, restructuring, or a leadership credibility problem, the five dysfunctions framework will feel shallow. I've seen senior leaders use the assessment as a shield to deflect criticism by framing real leadership failures as "team dysfunction." It happens more often than you'd think. If you want the official instrument, it is licensed through The Table Group. A single license for a small team runs roughly in the $200 to $500 range depending on how many seats you need and whether you want the self-facilitation version or the certified facilitator track. Free alternatives exist but they are paraphrased questionnaires that don't carry the validated scoring algorithm, so treat them as warm-ups rather than diagnostic tools. My standard rollout looks like this:
Day one: distribute the assessment link with a brief instruction email. No agenda attached yet. Day two: review aggregated scores in private, identify the dominant dysfunction, prepare a one-page brief for the team. Day three: run the ninety-minute session. Open with the sticky-note definitions exercise if the team is large or diverse. Walk through the pyramid from the bottom up, spending roughly fifteen minutes per level. End with two specific behavior commitments per dysfunction, not vague promises.
Day thirty: check in on the commitments. This is where most programs fail because nobody follows up. The numbers I consistently see after a proper rollout are a twenty to thirty percent shift in the dominant dysfunction score over six weeks, assuming leadership is actually modeling the behavior change. If the manager contradicts the new norms within two weeks, the score reverses and the team loses trust in the process entirely. That is the single biggest failure mode I have observed.
When Not to Use It
Do not administer this during a merger, layoff cycle, or active investigation. The emotional baseline is too distorted for self-report instruments to be meaningful. I learned that the hard way when a team went through a reorg two weeks before our scheduled session. The scores came back uniformly extreme and the debrief turned into a venting session that went nowhere. We rescheduled for six weeks later when things settled, and the follow-up assessment showed genuine movement. Also skip it if your team is under five people and has worked together for less than six months. There is not enough shared history for the patterns to stabilize. You will get noise, not signal.
Bottom Line
The assessment is a starting point, not a solution. It reveals where the team is sitting relative to the model. It does not move them out of that spot. That requires sustained behavioral change, leadership accountability, and usually a follow-up cadence that most organizations drop after the initial session enthusiasm fades. Run it once a year minimum if you want to track progress, and pair it with something that addresses the structural drivers of dysfunction rather than treating everything as an interpersonal problem.
