Use regular team health checks to surface dysfunction early

Teams that check in on how they’re working together catch dysfunction before it compounds.

Why it works

Lencioni’s pyramid is a compounding model: each dysfunction builds on the one below and enables the one above. Early detection of a crack at the trust or conflict level prevents it from propagating up to accountability and results. Most dysfunctions are invisible to the team while they are forming and only become obvious after significant damage has accumulated. Deliberate, regular process checks create an early-warning system.

How to do it

1. Quarterly, ask the team to rate on a 1–5 scale: trust (can we be honest about weakness?), conflict (do we debate ideas freely?), commitment (are we aligned after decisions?), accountability (do we call each other out?), results (do we put team first?).
2. Share the results openly with the team rather than only with leadership.
3. Treat low scores as information and a starting point for a conversation, not as blame.
4. Make the check-in a standing ritual — a team that only checks its health in crisis will check it too late.

Evidence

Team process check-ins and retrospectives are associated with higher team learning and adaptation in team effectiveness research. Making implicit team dynamics explicit is a well-supported intervention for improving team performance. (mechanistic)

Team retrospectives and learning behavior research support regular process review; Lencioni’s five-dimension diagnostic is his specific assessment instrument, not a validated psychometric tool.

Common mistake

Sharing health-check results with leadership only — when the team doesn’t see and own the scores themselves, the exercise produces data for management rather than accountability and shared ownership for the team.