Reflacto

ENDE
All reflection methods

5 Dysfunctions of a Team

Team problems usually have a root cause: people don't trust each other enough to have real conflicts, so they fake agreement, avoid accountability, and focus on individual success over team results.

  • Team feels "off"
  • Polite but unproductive
  • Trust foundation

What is the Five Dysfunctions model?

Patrick Lencioni’s practitioner model describes five interrelated barriers to teamwork. It is a framework for reflection and conversation, not a validated diagnostic instrument.

  1. Absence of trust

    Team members conceal mistakes, uncertainty, or weaknesses instead of openly asking for support.

  2. Fear of conflict

    Different perspectives are not discussed openly; artificial harmony replaces constructive disagreement.

  3. Lack of commitment

    Decisions remain unclear or lack shared support because viewpoints were not sufficiently explored beforehand.

  4. Avoidance of accountability

    Team members do not challenge one another when commitments, standards, or agreed behaviours are not upheld.

  5. Inattention to results

    Personal or departmental interests receive more attention than the team’s shared outcome.

The five dysfunctions in a concrete example

An illustrative view of a product team ahead of a planned release:

  1. Absence of trust

    Nobody openly admits that they do not yet fully understand the new interface.

  2. Fear of conflict

    No one challenges the tight timeline during planning; concerns appear only later in direct messages.

  3. Lack of commitment

    Friday remains the stated release date, while two contributors privately plan for the following week.

  4. Avoidance of accountability

    When the agreed integration test is missed, nobody directly addresses the unmet commitment.

  5. Inattention to results

    On Friday, everyone reports their individual tasks as complete even though the shared release must be postponed.

The example offers one possible reading of the five layers; it does not establish a team diagnosis. The assumptions should be compared with concrete observations in a team conversation.

When this method helps

Use when your team feels "off" but you can't pinpoint why, when meetings are polite but unproductive, or when people seem disengaged despite being capable.

Limits and when to pause

This practitioner model is a reflection lens, not a validated diagnostic instrument. Avoid using it to label individuals or treating one response as proof of a team-wide pattern.

Where Reflacto uses this method

Choose the situation you want to reflect on:

Key benefits

  • Offers a lens for exploring whether an underlying team pattern is driving visible symptoms
  • Suggests an order for discussing the five interconnected dysfunctions
  • Translates Lencioni's practitioner model into concrete topics for team discussion
  • Provides possible actions for each level of the model

Questions Reflacto asks

Reflacto turns the method into these concrete reflection questions:

  1. 1How would you rate the level of trust within your team?
  2. 2What specific examples support your trust rating?
  3. 3How well does your team handle productive conflict?
  4. 4Describe how conflicts are typically handled in your team
  5. 5How strong is commitment to team goals and decisions?
  6. 6Based on your assessment, what specific actions will improve team health?

Common questions about the five dysfunctions

What are the five dysfunctions of a team?

Absence of trust, fear of conflict, lack of commitment, avoidance of accountability, and inattention to results. Patrick Lencioni set them out as a pyramid because each one grows from the one below it. The order isn't a list — it's a diagnostic sequence, and it's what makes the model useful rather than just descriptive.

Why do you have to start at the bottom?

Because the visible symptoms sit at the top and can't be fixed directly. Demanding accountability in a team without trust doesn't produce candour, it produces cover — people start documenting instead of talking to each other. Trust is the only layer you can work on immediately; several of the others partly resolve once it moves.

How do I tell artificial harmony from a genuinely healthy team?

Look at what happens after the meeting. A healthy team disagrees in the room and goes to lunch together afterwards. A conflict-averse team agrees in the room and has the real conversation in the hallway or in DMs. If you routinely find out later what people actually thought, that's your signal.

What can I do if I'm not the manager?

Trust is built by going first, and anyone on the team can go first. Name your own mistakes before someone asks. Say when you don't know something. Disagree respectfully once, in a meeting where everyone else is nodding. It works more slowly than an intervention from above, and it's the only move nobody has to authorise.

Is this an assessment tool?

No. The five dysfunctions are a conversation model, not a measurement instrument — they give a team language for something it already senses but struggles to name. Turning it into a score and comparing teams stretches the model past what it supports. The value is that an observation becomes discussable.

Origin and Reflacto's adaptation

The Five Dysfunctions of a Team was published by Patrick Lencioni in 2002 (Jossey-Bass) as a business fable; it is a practitioner framework, not a peer-reviewed or empirically validated instrument.

Also known as: Lencioni’s Five Dysfunctions model

What Reflacto changed

Reflacto turns three of the five layers — trust, conflict and commitment — into paired rating-and-evidence questions, then closes with a single improvement-planning question that covers accountability and results together rather than asking about all five layers separately.

Primary sources and further reading

Editorially reviewed by Daniel Schmeiß

Last substantive review: August 23, 2026

Related reflection methods

Compare another method that approaches a similar situation from a different angle.

Compare all methods