Concept
Peer accountability
Peer accountability is Lencioni's fourth layer: on a healthy team, members hold each other to their commitments, and it is not primarily the manager's job. The manager makes it safe and expected with public standards, group progress reviews, and visible approval the first time one member challenges another.
It is the layer most new managers resist, because it feels like their job to say you said Thursday. But if the only person who ever says it is the manager, every missed commitment becomes a discipline problem between one person and the boss, and the team learns to manage the manager rather than each other. Peer accountability depends on the layers below: commitments that were stated aloud and agreed, after an argument people were part of, on a team that trusts itself enough to be uncomfortable. The manager builds it by stating standards in public, reviewing progress in the group rather than one-on-one, and, crucially, approving out loud the first time a peer holds another to a date instead of smoothing it over. Grove's version is that the team's meetings, not the manager's memory, are where the work is tracked.
A real-life example
In the sprint after Nihan introduces the closing ritual, a designer reminds an engineer of a date before Nihan does. Nihan says, in front of the team, that this is exactly right. It is the last time she is the only person who tracks a commitment.
How to use it
- 1State standards in public and review progress in the group, not only in one-on-ones.
- 2The first time a peer holds another to a commitment, approve it out loud.
- 3Stop being the only person who says you said Thursday.