Accountability Without Blame: What Cohesive Teams Do Differently (Part 5)

Oct 30

4 min read

Part 5 - The fourth behavior in a strengths-based exploration of Patrick Lencioni’s Five Cohesive Behaviors

When a commitment is missed on your team, who speaks up? If the answer is always the leader, the team may have a bigger opportunity than a missed deadline. Strong teams develop the trust and courage to hold one another accountable through shared ownership of the standards and commitments they have agreed to uphold.

Accountability is often associated with difficult conversations, missed expectations, or correcting poor performance. But on a cohesive team, accountability can mean something more positive: helping one another succeed against the commitments the team has made together.

In Patrick Lencioni’s model, The Five Dysfunctions of a Team, avoidance of accountability is the fourth dysfunction. In the positive framing of The Five Behaviors, the corresponding cohesive behavior is Hold One Another Accountable. Importantly, it follows trust, productive conflict, and commitment. The current Five Behaviors model explicitly states that once people have committed to a clear plan of action, they are more willing to hold one another accountable.

That sequence matters.

Accountability without trust can feel like criticism. Accountability without healthy conflict can remain unspoken. And accountability without clear commitment creates a fundamental problem: What exactly are we holding one another accountable for?

Lencioni’s framework therefore positions accountability as something that grows from the team’s previous work. The Table Group (TableGroup.com) describes the opposite behavior, avoidance of accountability, as a situation in which peers are unwilling to challenge behaviors that undermine the team, allowing standards to slip and leaving the leader as the primary source of discipline.

Reframing Accountability Through a Strengths-Based Lens

A strengths-based approach invites the question: “How can we use what is strongest in this team to help all of us deliver on what we agreed?”

This does not mean ignoring performance gaps or lowering standards. Quite the opposite. Strengths-based accountability combines high expectations with confidence in people’s ability to meet them.

Research gives us useful support for this approach. Van Woerkom, Oerlemans, and Bakker (2016) found that weekly strengths use was positively associated with work engagement and proactive behavior through self-efficacy.

Psychological safety is also relevant. Amy Edmondson’s research identifies psychological safety and learning behavior as important constructs in work teams, while later research has continued to examine psychological safety as an interpersonal construct in organizations.

Seen through this lens, accountability does not have to be“I caught you falling short.” It can become“We agreed this matters, and I want to help us deliver.”

That shift can change the quality of the conversation.

From Leader Accountability to Team Accountability

One of the most important transitions in a team’s development is moving from accountability that flows primarily through the leader toward greater peer-to-peer accountability. This does not remove accountability from the leader. Instead, the leader helps create the conditions in which shared accountability becomes normal team behavior. That means making expectations explicit, clarifying ownership, modeling constructive challenge, and recognizing when colleagues step forward to support one another.

It also means noticing strengths.

Who has the courage to name the issue everyone else is avoiding?
Who brings clarity when responsibilities become ambiguous?
Who naturally follows through and closes loops?
Who asks the question that reconnects the team to its shared purpose?
Accountability becomes stronger when those capabilities are recognized and intentionally used.

When This Becomes Valuable in Team Coaching

This focus can be especially valuable when a team has established reasonable trust and can debate ideas but struggles to translate decisions into consistent execution.

In team coaching, I would listen for patterns such as:

Decisions are made, but ownership remains unclear.
Commitments are repeatedly revisited.
Team members notice missed expectations but expect the leader to address them.
Difficult feedback happens privately rather than directly between colleagues.
Individual priorities begin to compete with collective commitments.

These are useful moments for the coach to help the team explore how it wants accountability to work, rather than simply identifying who has failed to deliver.

Try This With Your Team: The Commitment-to-Action Map

At the end of your next team meeting, choose one important team commitment and spend 10 to 15 minutes answering five questions:

1. What are we committing to? Write the decision or outcome in one clear sentence.

2. What does success look like? Agree on observable evidence that will tell the team the commitment has been delivered.

3. What strengths can we leverage? Ask each person to identify a strength they can bring to achieving the outcome.

4. Who owns what, and by when? Turn the commitment into specific actions, owners, and dates.

5. How will we hold one another accountable? Agree how colleagues can constructively challenge, check in, offer support, or raise concerns when the commitment is at risk.

Close with one coaching question: “What do you need from this team to deliver what you have committed to?”

The goal is not to create another tracker. It is to make accountability clear, mutual, strengths-based, and actionable.

Accountability as an Act of Commitment

The strongest teams are not teams where nobody falls short. They are tea

ms where expectations are clear enough, and relationships strong enough, for people to address gaps together.

Accountability at its best is not blame.

It is a team saying: our commitments matter, our collective results matter, and we care enough about one another to speak up when either is at risk.

And when accountability becomes something team members do with one another rather than something a leader does to them, the team takes another important step toward genuine cohesion.

References

Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.

Edmondson, A. C., & Lei, Z. (2014). Psychological safety: The history, renaissance, and future of an interpersonal construct. Annual Review of Organizational Psychology and Organizational Behavior, 1, 23–43.

Lencioni, P. (2002). The Five Dysfunctions of a Team: A Leadership Fable. Jossey-Bass. The Table Group identifies the book as published in 2002 and describes its five-part model.

Lencioni, P. (2012). The Advantage: Why Organizational Health Trumps Everything Else in Business. Jossey-Bass.

van Woerkom, M., Oerlemans, W. G. M., & Bakker, A. B. (2016). Strengths use and work engagement: A weekly diary study. European Journal of Work and Organizational Psychology, 25(3), 384–397. DOI: 10.1080/1359432X.2015.1089862.