9.3 Lencioni: Assessing and Growing Team Effectiveness

Patrick Lencioni (2002) identifies five dysfunctions that characterise an ineffective team. These dysfunctions point to five positive characteristics that should be developed when seeking to build an effective change team, and CM3 stresses that the five positive characteristics build on one another.

The five characteristics and their dysfunctions

The exam most often gives you a behaviour and asks which characteristic or dysfunction it describes. The mapping to hold onto: commitment and follow-through corresponds to lack of commitment to decisions.

Why the sequence matters

The characteristics build on one another, which means you cannot fix a later one while an earlier one is missing. This is what makes the model diagnostic rather than merely descriptive.

1. Trust and psychological safety

The foundation. Trust here means being able to be vulnerable with each other — to admit a mistake, a gap in knowledge, or a wrong call. This is Edmondson's psychological safety, and Lencioni's placing it first is the same argument.

2. Constructive conflict about ideas

Without trust, people will not argue honestly, because disagreement feels risky. With trust, teams can have vigorous debate about ideas — the qualifier matters. Constructive conflict is about the substance, not about people.

A team that appears harmonious is often not healthy but conflict-avoidant. Real disagreement exists and is being routed into corridors, private messages and passive non-cooperation instead of the meeting.

3. Commitment and follow-through

This is the characteristic that reveals whether stage 2 actually happened. People commit to decisions they have had the chance to argue about. A decision reached without genuine debate produces nodding in the room and nothing afterwards — the false consensus that change managers experience as an agreed plan nobody delivers.

So when a change team repeatedly agrees actions that do not happen, the intervention is usually not tighter action tracking. It is going back to whether the disagreement was ever surfaced.

4. Mutual accountability

Team members holding each other to account, not waiting for the leader to do it. This requires commitment, because you cannot hold someone to a standard they never agreed to. Where accountability runs only through the leader, the team is dependent rather than effective.

5. Focus on team results

The apex. Members prioritise the collective outcome over individual status, departmental interests or personal recognition. It requires all four beneath it — without mutual accountability, individual agendas are never challenged.

Applying Lencioni to change work

The model is most useful applied to the change team, the change agent network and the sponsoring leadership group — the three groups whose effectiveness determines whether a change is deliverable.

A practical diagnostic sequence, working from the bottom:

1. Can people admit mistakes and gaps in this group? If not, everything above is compromised and trust is the only useful intervention.
2. Does real disagreement surface in the meeting, or only outside it? Silent meetings followed by corridor dissent indicate fear of conflict.
3. Do agreed decisions actually get delivered? Repeated non-delivery usually traces back to conflict that never happened.
4. Do members challenge each other, or only the leader challenge them? Leader-only accountability indicates a dependent team.
5. When individual and collective interests conflict, which wins? Consistent individual precedence indicates inattention to results.

Working upward from the lowest failing level is the whole point of the sequence. Adding an accountability process to a team that does not trust each other produces a process that is complied with and ignored — which is, in miniature, the same lesson Kelman teaches about compliance.

The link to psychological safety and diversity

Lencioni's first characteristic explicitly names psychological safety, which ties this model to Edmondson and to CM3's guidance on team diversity — where diverse teams need time to develop their full effectiveness and the psychological safety that frees them to perform. In Tuckman's terms, a diverse team may spend longer in storming, and Lencioni explains why that is productive rather than problematic: the storming is where constructive conflict about ideas is learned.

Building trust deliberately

Since everything in the model rests on the first characteristic, it is worth being concrete about what builds it. Lencioni's sense of trust is specifically vulnerability-based — confidence that being wrong, not knowing, or asking for help will not be used against you. That is a narrower and more demanding thing than reliability.

Three behaviours build it faster than any team-building exercise:

• The leader goes first. A change manager who opens a review by naming their own misjudgement has demonstrated the cost of admission and shown it is survivable. Nobody more junior will do it before someone more senior has.
• Mistakes are handled consistently. One instance of a mistake being used against someone erases months of stated openness, and the team will treat the exception as the true policy.
• Not knowing is normalised. "I don't know, I'll find out" from a leader is a more useful signal than a confident wrong answer, and it licenses the same response from everyone else.

This is also where the model connects to change specifically: change teams are usually new, cross-functional and temporary, which means they have the least accumulated trust at exactly the moment they most need to disagree productively.