BUSI 427 Week 8 4-MAT Paper Example

A 4-MAT Review of Patrick Lencioni's The Five Dysfunctions of a Team

Summary

The Five Dysfunctions of a Team is a business fable followed by a short explanation of the model the story teaches (Lencioni, 2002). The story follows Kathryn Petersen, a newly hired chief executive of DecisionTech, a Silicon Valley technology company that has talented executives, strong funding and a promising product, yet is falling behind competitors. Kathryn is older than most of her team and comes from a manufacturing background, and the executives doubt her. She spends her first weeks observing and concludes that the company's problem is not strategy or talent but the executive team itself.

Kathryn takes the team to a series of off-site meetings in the Napa Valley. There she introduces a pyramid of five dysfunctions. At the base is absence of trust, which in Lencioni's sense means an unwillingness to be vulnerable with one another. Without trust, teams fear conflict and settle for artificial harmony rather than passionate debate about ideas. Without real conflict, members never fully buy in, so the team suffers from lack of commitment. Without commitment, members avoid holding one another accountable. At the top, inattention to results appears when members put their own status or their department's interests ahead of the team's collective goals.

The story shows each dysfunction in action. The executives hide weaknesses and conduct polite but empty meetings. Mikey, the gifted head of marketing, openly dismisses the exercises and colleagues; Jeff, the former chief executive and cofounder, now heads business development; and the head of engineering, Martin, works on his laptop during meetings. Kathryn uses exercises such as sharing personal histories and discussing personality profiles to build trust, insists on open conflict about real issues, ends meetings by clarifying commitments and holds members accountable publicly. The team struggles, and Mikey ultimately leaves the company when it becomes clear the behavior will not change. By the end of the fable the team is functioning better and DecisionTech's results improve, though the change is hard won.

In the book's final section, the model, Lencioni (2002) restates the five dysfunctions directly, describes how a team that suffers from each behaves and how a team that overcomes it behaves, and suggests practical tools and the leader's role for each level. He stresses that the dysfunctions are interrelated and that overcoming them requires discipline more than brilliance. The model section also offers a short team assessment, a set of statements members rate about their own team, so that a group can see which levels of the pyramid need the most work before choosing exercises.

Concrete Response

Reading the fable brought back my two years on my church's building committee. Seven of us were charged with planning a renovation of the fellowship hall, and we were all committed members who liked one another. Our meetings were warm. Someone always brought coffee, we opened in prayer, and no one ever raised a voice. Yet after eighteen months we had approved almost nothing.

Looking back through Lencioni's pyramid, I can see the dysfunctions plainly. The polite atmosphere was what Lencioni calls artificial harmony. When the architect's first plan came in over budget, several of us privately thought the kitchen expansion should be cut, but no one said so in the meeting because the kitchen was a longtime member's dream. Without that debate we never committed to a decision; each meeting ended with "let's think about it more." And because we never committed, no one held anyone accountable when tasks such as getting a second bid slipped for months. We were not hostile; we were kind in a way that kept us from doing our job.

The turning point came, much as in the fable, through a new leader. A retired contractor joined the committee and, in his second meeting, said, "I think we're all afraid to talk about the kitchen. Can we just put it on the table?" The room was quiet, and then the longtime member admitted she had suspected the kitchen was the problem and had felt we were tiptoeing around her. That moment of honesty, which took perhaps thirty seconds, unlocked the next two meetings, in which we argued openly, reached a decision and assigned clear responsibilities with dates. The renovation was finished the following year.

What struck me in rereading the fable was how familiar the starting point was. I had always assumed that conflict was the enemy of a church committee and that our pleasant meetings were a strength. Lencioni helped me see that our niceness was protecting us from discomfort at the expense of the mission we had been given.

I also had to face my own part in it. I privately favored cutting the kitchen too, and I kept quiet for months rather than be the one who let a friend down. At the time I called that kindness. Reading the fable, I recognized it as the same self-protection that kept DecisionTech's executives quiet: I valued my standing in the group more than the decision the group needed to make. Lencioni would say my silence was a failure of trust, because I did not trust the group to handle disagreement without damaging relationships. The contractor who finally spoke up took a risk I had avoided, and the result was not the damage I feared but relief.

Reflection

The model's greatest strength is that it explains why teams of good people fail. Many leadership books assume dysfunction comes from bad people or bad strategy. Lencioni's fable shows a team of capable executives failing because of patterns in how they interact, which matches my committee's experience exactly. The pyramid also gives teams a shared vocabulary; once our committee could name artificial harmony, we could talk about it.

The model is also broadly consistent with research. Levi (2017) devotes chapters to the processes Lencioni dramatizes, including trust and cohesion, conflict, decision making and team performance. Levi's discussion of conflict distinguishes conflict about tasks from conflict about relationships and describes how cohesive groups can slide into poor decisions when they avoid disagreement, which is the danger Lencioni calls artificial harmony. His treatment of team decision making emphasizes that members accept decisions more fully when they have had a voice, which supports Lencioni's claim that commitment depends on conflict, on members having "weighed in" even if they do not get their way. In these respects the fable is a story told about findings that the research literature reports in more measured terms.

The model has limits, however. First, the pyramid presents the dysfunctions as a strict sequence, but real teams can be strong at one level and weak at another. My committee trusted one another personally, in the sense of believing in each other's good intentions, yet still avoided conflict; trust was necessary but not sufficient. Levi's research-based approach treats team processes as interacting rather than strictly layered, which seems closer to experience.

Second, the fable's format simplifies. Kathryn diagnoses the problem quickly, applies the right tools and is vindicated, while the one executive who resists leaves. Real organizations rarely offer such clean outcomes; the resistant member may be indispensable, the leader may be wrong, or the team may improve only partly. A fable is persuasive partly because it controls the ending.

Third, the book focuses on executive teams that meet face to face. Many teams today are virtual, cross-functional or temporary, and Levi's chapters on virtual teams suggest that building trust and accountability in those settings requires additional structures, such as visible commitments and shared leadership, that the fable does not address. The field guide (Lencioni, 2005) partly fills this gap with practical exercises, but it, too, assumes a team that can gather in a room.

Finally, the model is largely silent on the purpose behind the team's results. Lencioni defines results broadly as the team's collective outcomes, but he does not ask whether those outcomes are worth pursuing. A Christian reader may want to add that a team's results should serve something beyond the team's success. Paul's description of the church as one body in which each member's gifts serve the common good (English Standard Version Bible, 2001/2016, 1 Corinthians 12:4-7) points toward a model of teamwork in which commitment to the shared purpose, not only to collective performance, holds the members together.

A fifth consideration is culture. The fable assumes that open, passionate debate is a sign of health, but norms about disagreement vary. Levi (2017) notes in his discussion of diversity that members from different cultural backgrounds may differ in how directly they express disagreement and how they view challenging a leader. A team leader applying Lencioni's model to a diverse group may need to create several channels for dissent, such as written comments before a meeting or one-on-one conversations, so that members who would never contradict a colleague publicly can still contribute to the conflict the model values. The goal Lencioni describes, honest engagement with ideas, remains valid; the methods for reaching it may need to vary.

Even with these limits, the book's central claim persuades me: avoidance sinks more teams than conflict does, so a leader must first make honesty safe.

Action

I plan to apply the model in two settings, my work team at a regional bank and the ministry team I now lead at church.

First, I will build trust deliberately. At my next team meeting at work, I will use the personal histories exercise from the field guide, asking each member to share where they grew up, how many siblings they have and a challenge they faced as a child (Lencioni, 2005). I will go first and keep my answer honest rather than polished, since the fable shows that the leader's willingness to be vulnerable sets the tone.

Second, I will invite productive conflict. In each ministry team meeting, I will name the hardest topic on the agenda and ask the quietest member for their view before I share mine. I will also set a ground rule from the conflict management chapter (Levi, 2017): we criticize ideas, not people. I will lead these discussions with James's warning in mind, that listening should come quickly and speaking slowly (English Standard Version Bible, 2001/2016, James 1:19).

Third, I will clarify commitments. Every meeting I lead will end with what the field guide calls cascading communication: we will state aloud what we decided, who will do what by when, and what each of us will tell our own teams. I will send the list in writing within a day.

Fourth, I will practice accountability, starting with myself. I will create a shared list of team commitments reviewed at the start of each weekly meeting, and I will ask the team to tell me when I miss mine. When a peer misses a commitment, I will raise it privately and quickly, as Jesus instructed when a brother sins, going to him first alone (English Standard Version Bible, 2001/2016, Matthew 18:15), rather than letting resentment build.

Fifth, I will keep the team focused on results that matter. At the start of each quarter, the ministry team will agree on three outcomes that serve our congregation, and we will review progress monthly. Those results will keep our attention on the purpose we share rather than on individual credit.

I will also tell both teams about these commitments and invite them to hold me to them; letting them watch me try is part of the vulnerability the model expects of a leader. I expect resistance, especially to the first two steps, because they ask people to be uncomfortable. The fable and my committee experience both suggest that the discomfort is temporary and the benefits lasting. I will review my progress on these five commitments with a trusted colleague after three months, and I will ask that colleague to be blunt about where I have slipped. If a practice is not working, such as a team that finds the personal histories exercise awkward, I will adapt it rather than abandon the goal behind it, since the purpose of each step is the level of the pyramid it serves, not the exercise itself.

References

English Standard Version Bible. (2016). Crossway. (Original work published 2001)

Lencioni, P. (2002). The five dysfunctions of a team: A leadership fable. Jossey-Bass.

Lencioni, P. (2005). Overcoming the five dysfunctions of a team: A field guide for leaders, managers, and facilitators. Jossey-Bass.

Levi, D. (2017). Group dynamics for teams (5th ed.). SAGE Publications.