Patrick Lencioni’s The Five Dysfunctions of a Team offers one of the most practical and enduring models for understanding why teams fail and how to fix them. Written as a business fable, it tells the story of a struggling technology company whose new CEO must uncover and address the root causes of its poor performance. Through this story, Lencioni reveals a simple but powerful framework describing five common dysfunctions that undermine teamwork. Each dysfunction builds upon the next, forming a pyramid that shows how trust, conflict, commitment, accountability and results are interdependent.
Although the book is told through a corporate narrative, its lessons apply to any team, from start-ups and sports teams to agile product teams. Lencioni’s framework provides a clear roadmap for leaders and team members who want to build strong, cohesive and high-performing groups.
The Foundation: Absence of Trust
At the base of Lencioni’s model lies the most fundamental dysfunction: the absence of trust. Teams without trust cannot perform effectively because members are unwilling to be open or vulnerable with one another. Instead of admitting mistakes, weaknesses or doubts, people hide behind a façade of competence. This prevents honest communication and collaboration, which are essential for solving problems quickly and learning together.
Trust in this context is not about predictability or reliability but about vulnerability-based trust. It means feeling safe enough to say “I don’t know,” “I made a mistake,” or “I need help” without fear of judgment or punishment. When leaders and team members are comfortable showing vulnerability, it sets the tone for openness and honesty.
Lencioni illustrates how the new CEO in the book, Kathryn, rebuilds trust by encouraging honest conversations and modelling vulnerability herself. She admits when she doesn’t have all the answers and invites the team to do the same. Over time, this breaks down barriers and helps team members see one another as human rather than competitors.
In practice, agile teams thrive on this type of trust. Scrum and other agile frameworks rely on transparency and inspection, which only work if team members are comfortable sharing challenges and failures. Without trust, stand-ups become superficial, retrospectives lose value and collaboration stalls. Building trust takes time and consistent behaviour from leaders who reward honesty and openness.
The Second Layer: Fear of Conflict
Once trust is established, teams must be willing to engage in healthy conflict. Lencioni identifies fear of conflict as the second dysfunction. Teams that avoid disagreement often appear harmonious on the surface, but this false harmony hides unresolved issues. When people suppress differing opinions, decisions become weaker and resentment grows.
Healthy conflict is not personal or destructive; it is passionate debate about ideas. It is the kind of constructive disagreement that drives innovation and improvement. Teams that fear conflict fall into artificial harmony, avoiding hard conversations and leaving important problems unaddressed.
Lencioni’s story shows how Kathryn encourages her executive team to embrace debate rather than avoid it. She insists that silence is not agreement and challenges members to speak up even when uncomfortable. By creating a safe environment for open dialogue, she transforms meetings from tedious status updates into productive discussions where real decisions are made.
In agile teams, this principle is crucial. Retrospectives, backlog refinements and sprint planning sessions depend on honest dialogue. When team members fear conflict, they withhold concerns, allowing issues to fester. Leaders should foster a culture where disagreement is seen as a sign of engagement, not disloyalty. Facilitators and Scrum Masters play a key role in ensuring that debates remain respectful and focused on the work, not the person.
The Third Layer: Lack of Commitment
The third dysfunction arises when teams fail to commit. Lack of commitment often stems from a lack of clarity or buy-in. When people do not feel heard during discussions, they are less likely to support the final decision, even if they outwardly agree. This leads to hesitation, second-guessing and slow execution.
Commitment in Lencioni’s model is about clarity and alignment, not consensus. Teams do not need everyone to agree on every decision, but they do need everyone to commit once a decision is made. Lencioni uses the phrase “disagree and commit” to describe how healthy teams move forward.
Kathryn teaches her team to make decisions even when certainty is impossible. She emphasises that clarity and closure are more important than perfection. By setting clear expectations and deadlines, she ensures that decisions are acted upon quickly rather than endlessly debated.
In agile environments, this aligns closely with the idea of empirical process control. Teams make the best possible decision based on what they know now, test it and adapt later. Commitment means everyone moves forward together, even if they would have chosen a different path individually. This shared ownership builds momentum and confidence.
Without commitment, teams drift. Meetings end without clear outcomes, priorities shift constantly, and progress slows. The solution is to create clarity through clear goals, transparent communication and explicit decision-making. Leaders should ensure that everyone understands what has been decided, why and what happens next.
The Fourth Layer: Avoidance of Accountability
The fourth dysfunction, avoidance of accountability, occurs when team members are unwilling to hold one another to high standards. In cohesive teams, accountability is not just the leader’s job; it is shared by everyone. When peers avoid challenging one another’s behaviour or performance, mediocrity becomes acceptable.
Lencioni argues that peer accountability is the strongest form because it demonstrates mutual respect and commitment to shared goals. Teams that depend solely on top-down accountability often struggle with ownership. When leaders are the only ones enforcing standards, improvement becomes slow and compliance-based.
Kathryn tackles this issue by introducing clear expectations and making performance visible. Her team creates measurable goals and reviews progress regularly. When someone fails to meet a commitment, the team discusses it openly and constructively. This creates a culture of mutual responsibility where everyone is invested in collective success.
In agile teams, accountability is built into the framework through daily stand-ups, sprint reviews and retrospectives. These ceremonies create natural points for inspection and adaptation. However, they only work if team members are willing to speak honestly about what is and is not working. A culture of trust and commitment allows accountability to feel supportive rather than punitive.
Leaders can encourage peer accountability by recognising and rewarding constructive feedback. When people see that speaking up helps the team succeed, they become more comfortable addressing issues directly. Transparency through visible metrics, such as burn-down charts or sprint goals, also reinforces accountability by making progress (or lack of it) clear to everyone.
The Top of the Pyramid: Inattention to Results
At the top of Lencioni’s pyramid is the final dysfunction: inattention to results. This occurs when team members prioritise personal goals, departmental success or status over the collective results of the team. When this happens, collaboration breaks down and performance suffers.
Teams that focus on results put collective success above individual recognition. Every member measures success by whether the team achieves its goals, not by their own output or visibility. Lencioni notes that in high-performing teams, egos and titles fade into the background. The only thing that matters is delivering the result that serves the greater mission.
In Kathryn’s story, she reinforces this by defining clear, measurable outcomes and tracking progress publicly. Her team learns to celebrate group achievements and acknowledge when the collective goal is not being met. This shift from individual performance to shared results transforms how people collaborate.
In agile terms, this dysfunction often appears when team members focus on completing their own tasks rather than the sprint goal. Teams overcome it by defining clear, outcome-based objectives and regularly inspecting whether they are delivering value. Shared metrics, such as product increments or customer satisfaction, keep attention focused on what truly matters.
Leaders can counteract inattention to results by ensuring goals are visible, measurable and tied to the team’s purpose. Celebrating team success over individual achievement reinforces the message that everyone wins or loses together.
The Interconnected Nature of the Five Dysfunctions
Lencioni’s model is structured as a pyramid because each dysfunction builds upon the previous one. Without trust, conflict becomes destructive. Without conflict, commitment is weak. Without commitment, accountability disappears. Without accountability, results suffer. This interconnected nature means that fixing one dysfunction often requires addressing the ones below it first.
The process of overcoming these dysfunctions is continuous. Teams must regularly revisit how they are performing across all five areas. Trust can erode, conflict can be avoided, and accountability can slip if not maintained intentionally. The best teams treat these principles as habits rather than one-time fixes.
Kathryn’s story demonstrates that change takes persistence. Her team initially resists the new approach, preferring the comfort of old habits. But through consistent application and honest dialogue, the culture shifts. The team learns to trust one another, debate openly, commit decisively, hold one another accountable and focus on collective outcomes.
Applying the Model in Agile Teams
Lencioni’s framework aligns naturally with agile principles. Agile teams are designed to be collaborative, transparent and self-organising, all of which depend on the same behaviours Lencioni describes.
Trust forms the basis of agile teamwork. Without it, developers, testers and product owners cannot communicate honestly or adapt quickly. Conflict enables better decisions during backlog prioritisation and sprint planning. Commitment ensures that once a sprint goal is agreed upon, everyone works towards it. Accountability keeps progress visible and honest through daily stand-ups and retrospectives. Finally, focus on results ensures that the team delivers value to customers rather than simply completing tasks.
Agile leaders and Scrum Masters can use Lencioni’s model as a diagnostic tool. When a team struggles, identifying which dysfunction is most present can help target improvements. For example, if meetings are quiet and agreement is too quick, the issue might be fear of conflict. If goals keep shifting, the team may lack commitment. Recognising the symptoms allows leaders to intervene thoughtfully.
Practical steps include encouraging vulnerability in retrospectives, setting clear sprint goals, making performance visible and rewarding team success over individual contribution. Over time, these habits build cohesion and resilience.
Building a Culture of Healthy Teamwork
The enduring appeal of The Five Dysfunctions of a Team lies in its simplicity and humanity. It reminds leaders that teamwork is not about procedures or tools but about relationships and behaviour. The best processes in the world cannot compensate for a lack of trust or a fear of honesty.
By focusing on trust, open conflict, commitment, accountability and results, teams create an environment where collaboration thrives. These principles do not require special methodologies or frameworks; they are universal truths about how people work best together.
Patrick Lencioni’s model offers a mirror for every team to examine itself. It challenges leaders to set the tone through vulnerability and consistency. It challenges team members to speak up, take responsibility and focus on the collective good. When teams commit to this approach, they build not only better results but stronger, more fulfilling relationships.
Do You Want To Learn Scrum & Agile?
Learn Scrum & Agile at lost cost and online. Our 5-star rated Ultimate Scrum & Agile eLearning Courses can take you from beginner to advanced at your own pace.
Prepare and practice for the assessments from the major Scrum & Agile providers. Our 5-star rated Ultimate Scrum & Agile Practice Assessments will help you gain certification.
About TheScrumMaster.co.uk
