The Five Dysfunctions of a Team
The Five Dysfunctions of a Team: A Leadership Fable

The Five Dysfunctions of a Team

Introduction:

In today's competitive landscape, success is not solely determined by financial performance, strategic planning, or technological innovation. Rather, the strength of teamwork stands as the ultimate competitive advantage. Rooted in Agile , teamwork emerges as one of the paramount principles, recognising that the best outcomes arise from self-organising teams. In software development, the collaborative effort of individuals across roles — from engineering and quality assurance to project and product management — is essential for delivering value to customers.

Conflicting Goals: "The main thing is to keep the main thing the main thing." Stephen R. Covey
If you can get all the people in an organisation rowing in the same direction at the same time you can dominate any market at any time.

However, despite the immense potential for success when all team members align their efforts, achieving this ideal is often challenging. Teams consist of individuals with diverse perspectives, personalities, and inherent contradictions, which can lead to dysfunction. Patrick Lencioni's work emphasises this reality, pointing out that genuine teamwork is elusive for many organisations due to these inherent human complexities.

Patrick highlights two key truths: genuine teamwork remains as elusive as ever for most organisations, and many fail to achieve it because they unknowingly fall prey to five natural but dangerous pitfalls.

The Five Dysfunctions Of A Team are illustrated in the diagram below and will be explored in depth in the following subsections.

Understanding the 5 Dysfunctions of a Team: Trust, Conflict, Commitment, Accountability, and Results

  1. Absence of Trust ??
  2. Fear of Conflict ??
  3. Lack of Commitment ??
  4. Avoidance of Accountability ??
  5. Inattention to Results ??

The book begins with a fictional story that illustrates the concepts and principles of building and maintaining effective teams. It follows the executive team at DecisionTech as they navigate and attempt to overcome the dysfunctions hindering their success. This storytelling approach is similar to that of "The Phoenix Project" making it highly relatable to many of our own experiences. After setting the scene and providing context, the author delves into the five dysfunctions, explaining their interconnections and why they must be addressed collectively.

Just like a chain, with one link broken teamwork deteriorates even if a single dysfunction is allowed to flourish

This blog will follow a structured approach: summarising each challenge, reflecting on techniques to overcome them based on my own experiences, and concluding with a practical team assessment tool.

Absence of Trust ??

"Without trust, we don't truly collaborate; we merely coordinate or, at best, cooperate. It is trust that transforms a group of people into a team." – Stephen R. Covey

The word "trust" is often used and misused, diminishing its impact. In a team context, trust means having confidence in the good intentions of your peers and allowing team members to be open and unguarded with one another. Trust is the glue of life, the most essential ingredient in effective communication, and the foundational principle that holds all relationships.

Absence of Trust is demonstrated by:

  • An unwillingness to be vulnerable within the group.
  • Team members not being open about mistakes and weaknesses, making it impossible to build a foundation for trust.

To overcome the absence of trust, team members need to become comfortable being vulnerable with one another. This includes openly sharing weaknesses, acknowledging skill deficiencies, discussing opportunities for growth, admitting mistakes, and making simple requests for help. In a culture lacking trust, teams fear that their vulnerabilities will be weaponised and used against them. See the examples below contrasting teams with and without trust.

With Absence of Trust vs Without Absence of Trust
Trust takes years to build, seconds to break, and forever to repair." - Dhar Mann

When trust is established within a team, energy is directed towards the task at hand rather than being consumed by politics or insincerity aimed at shielding individual vulnerabilities. Overcoming this challenge can be difficult because we are often trained to prioritise competitiveness and individual achievement over teamwork throughout our careers and education.

To effectively hold each other accountable for their behaviours and actions, team members must have a clear understanding of expectations. Clarity in roles, responsibilities, and team goals makes it easier to establish and maintain accountability

Building Trust within a team facilitates constructive Conflict, allowing members to engage in passionate and emotionally charged debates.

Fear of Conflict ??

Teams lacking trust often avoid engaging in open, passionate debates about ideas, instead resorting to veiled discussions and guarded comments. However, productive conflict is crucial for the growth of great relationships.

Ideological conflict focuses on concepts and ideas, avoiding personal attacks or mean-spiritedness, but it still involves passion, emotion, and frustration. Patrick introduces this concept with the Conflict Continuum Scale, as illustrated below.

The Conflict Continuum - "Peace is not the absence of conflict, it is the ability to handle conflict by peaceful means." - Ronald Reagan

Teams engaging in productive conflict aim to efficiently reach the best solution. They recognise conflict as a valuable tool and avoid deferring important discussions or "taking issues offline," ensuring that crucial topics are promptly addressed rather than repeatedly surfacing in future meetings. See further comparisons between Teams Fearing Conflict and those Engaging in Conflict in the table below.

Allow conflict to happen naturally without restraint, and the resolution comes naturally.
Teams Fearing Conflict vs Engaging in Conflict

Engaging in Productive Conflict allows teams to tap into the perspectives and opinions of their members, enabling them to confidently Commit to and buy into decisions.

Lack of Commitment ??

"Commitment is what transforms a promise into reality." - Abraham Lincoln

When team members refrain from expressing their opinions in passionate debates, it's rare for them to fully buy into and commit to decisions. Commitment within teams is influenced by two key factors: clarity and buy-in. Exceptional teams prioritise making clear and timely decisions, and they move forward even when some members have dissented.

The two primary causes of the lack of commitment are the pursuit of Consensus and the craving for Certainty.

Consensus: reasonable human beings do not need to get their way to support a decision. They need to know their opinions have been heard and considered.
Certainty: unite behind decisions, "a decision is better than no decision." Better to make a decision and be boldly wrong and boldly change direction than not make a decision.
Teams Failing to Commit vs. Committing

For team members to hold each other accountable for their behaviours and actions, they must have a clear understanding of expectations. Clear expectations make it easier to hold people Accountable.

Avoidance of Accountability ??

"Accountability breeds response-ability." Stephen R. Covey

Lack of genuine buy-in and commitment often results in team members avoiding accountability. When there's no commitment to a clear plan of action, even the most focused and driven individuals may hesitate to address counterproductive actions and behaviours among their peers. At the core of this dysfunction lies the reluctance of team members to endure the discomfort of addressing their peers' behaviour, leading to avoiding difficult conversations.

Peer pressure serves as one of the most effective mechanisms for fostering accountability within a team, as individuals fear letting down their peers. It acts as a powerful motivator for improving performance.

Teams that Avoid vs. Teams that Hold Each Other Accountable

If they are not held accountable for their contributions they will likely turn their attention to their own needs rather than Collective Results.

Inattention to Results ??

"Success is not about individual accolades or personal gain; it's about achieving collective goals and driving meaningful results as a team"

When team members fail to hold each other accountable, it often leads to inattention to results. Individuals prioritise their personal needs, such as ego, career advancement, and recognition, over the collective goals of the team. This dysfunction manifests in two main areas:

  1. Team Status: Members may prioritise being associated with prestigious organisations like Apple or Tesla over achieving collective success.
  2. Individual Results: Instead of prioritising the collective outcomes of the group, individuals focus on self-preservation and personal achievements.

Individual vs Team Results

To foster a healthy team dynamic, it's crucial for members to prioritise the team's overall success over individual goals and status.

Recap:

?? Absence of Trust:

  • Trust is vital for effective communication and teamwork.
  • Vulnerability and openness build trust within teams.

?? Fear of Conflict:

  • Productive conflict is essential for growth.
  • Ideological conflict is necessary for reaching optimal solutions.

?? Lack of Commitment:

  • Clarity and buy-in are crucial for commitment.
  • Consensus and certainty hinder commitment.

?? Avoidance of Accountability:

  • Lack of commitment leads to avoiding accountability.
  • Peer pressure fosters accountability within teams.

?? Inattention to Results:

  • Focusing on individual needs over collective goals leads to inattention to results.
  • Team assessment tools provide insights into team performance.

Team Assessment

The book and this blog conclude with a Team Assessment tool, which provides insights into a team's specific strengths and areas for improvement. This tool can generate useful retro ideas or quarterly insights on how teams are performing.

Several tools are available to run assessments at the squad or team level. One such tool is available for free and is simple to use. You can access it through this GitHub link: Team Dysfunctions Assessment.


Next up will either be Extreme Programming Explained: Embracing Change or the latest Scrum book by Jeff Sutherland looking at First Principles.

Thanks,



Sakina Shabbir

Portfolio Manager @ Burgan Bank | Cards & Switch | Banking | IT | SAFe | Prince2? Practitioner

9 个月

Love this book! Patrick’s book “The ideal team player”is also a great read!

赞
回复

要查看或添加评论,请登录

Matthew Binder MBA的更多文章

  • Fixing Your Scrum: Practical Solutions to Common Scrum Problems

    Fixing Your Scrum: Practical Solutions to Common Scrum Problems

    This blog uncovers Ryan Ripley and Todd Millers' insights from "Fixing Your Scrum: Practical Solutions to Common Scrum…

    3 条评论
  • User Stories Applied: For Agile Software Development

    User Stories Applied: For Agile Software Development

    Introduction: "User Stories Applied: For Agile Software Development" is written by two of the heavy hitters from the…

    3 条评论
  • Agile Estimation and Planning

    Agile Estimation and Planning

    "Planning is everything. Plans are nothing" Introduction: Agile Estimating and Planning by Robert C.

    5 条评论
  • The Culture Game

    The Culture Game

    Introduction: The Culture Game by Daniel Mezicz explores the idea that culture is a key factor in the success of agile…

  • Inspired: How to create tech products customers love

    Inspired: How to create tech products customers love

    In a world obsessed with output, discover why product teams should focus on outcomes. This agile blog is based on ??…

    3 条评论
  • The Coaching Habit: Say Less, Ask More, & Change the Way you Lead Forever

    The Coaching Habit: Say Less, Ask More, & Change the Way you Lead Forever

    Introduction: Are you ready to discover the secrets of coaching that can empower your team and transform your…

    12 条评论
  • Kanban Successful Evolutionary Change for Your Tech Business

    Kanban Successful Evolutionary Change for Your Tech Business

    Introduction: I've successfully used Kanban as a tool to visualise and manage technical teams' workflows during project…

    2 条评论
  • The Surprising Power of Liberating Structures

    The Surprising Power of Liberating Structures

    Introduction: People, resources and structures are conventionally the ingredients that drive the performance of…

    9 条评论
  • Succeeding With Agile Software Development Using Scrum

    Succeeding With Agile Software Development Using Scrum

    Introduction: Scrum or the "rugby approach" was first used metaphorically by scholars Hirotaka Takeuchi and Ikujiro…

    4 条评论
  • Agile Retrospection Making Good Teams Great

    Agile Retrospection Making Good Teams Great

    Introduction After reading Agile Retrospectives making good teams great it has triggered some intended and un-indented…

    2 条评论

社区洞察

其他会员也浏览了