Dysfunction 4: Avoidance of Accountability

Lesson 6: Dysfunction 4 — Avoidance of Accountability

Accountability, in Lencioni's model, is not a manager nagging subordinates. It is peer-to-peer: team members calling each other out — immediately and directly — when behavior or performance falls below the standards the team itself agreed to. Dysfunctional teams won't do it. They'd rather let standards erode than have an uncomfortable conversation.

Root cause: the desire to avoid interpersonal discomfort. Confronting a peer risks awkwardness, tension, and possibly the relationship itself. So teams duck — and in ducking, they quietly communicate that low performance is acceptable.

What it looks like in practice

  • The leader is the only person who ever holds anyone accountable — and usually only in annual reviews.
  • Underperformers go unmentioned; their teammates vent about them to other people instead.
  • Standards drift: if nobody enforces "on time, on spec," then "on time, on spec" stops being the standard.
  • Resentment builds — both toward the underperformers and toward the leader who "does nothing about them."
  • High performers leave. Achievement-oriented people will not stay where mediocrity is protected by silence.
The paradox of "being nice": teams that avoid confrontation to protect relationships end up destroying them. The resentment of unremediated underperformance is far more corrosive to a team than the awkwardness of one honest conversation. Accountability, practiced well, is a form of respect.

How it relates to the other dysfunctions

Avoidance of accountability is downstream of the first three dysfunctions:

  • No trust: criticism feels like a personal attack, so pushback is impossible.
  • No conflict: the team won't puncture its false harmony with a difficult conversation.
  • No commitment: this is the most powerful link — if goals were never clear and never truly bought into, nobody has the right to call anyone out. You can only hold people accountable to standards they agreed to.

And it feeds the apex: without accountability, people miss commitments without consequence, individual egos flourish, and the team's collective results take a back seat to everyone's private agenda (dysfunction 5).

How to combat it

  1. Publication of goals and standards. Write down three things: what the team is trying to accomplish, each person's specific responsibilities, and the code of conduct — how teammates are expected to behave. Public and explicit. This converts "calling someone out" from a personal attack into "holding someone to what we all agreed to."
  2. Simple and regular progress reviews. A rhythm — weekly or monthly — where the team reviews commitments against reality: "We said X; here's where we are; what happened?" The question is asked of the team, by the team, on a fixed cadence. No drama, no surprises, just the score.
  3. Team rewards. Tie incentives to team results, not individual heroics. When everyone's bonus depends on everyone's performance, ignoring a teammate's drop-off becomes expensive — and accountability becomes self-interested instead of self-righteous.
  4. The leader models it. The leader must be the first to call out a missed standard — including their own. When the leader holds people to the agreed standards, consistently and without exception, it legitimizes everyone else doing the same. (And when the leader fails to, the team reads it as permission.)
Fable tie-in: As DecisionTech's standards became explicit and shared, teammates began confronting each other directly — no more hallway venting. JR Rawlins, who refused to live under the new standards, quit. Lencioni's point: accountability isn't just about correcting behavior; it's a filter that keeps the team's culture honest.

Further Reading

🧠 Knowledge Check

1. Who does Lencioni say should hold team members accountable?

2. What is the paradox of avoiding accountability to "protect relationships"?

3. Which of these is a direct tool for enabling peer accountability?