Five Dysfunctions: Spot Team Patterns

The model organizes team problems into five layers, from trust to shared results.

  • Look beyond the symptoms
  • Check trust first
  • Find the next leverage point

Five layers of teamwork

The model organizes team problems into five connected layers. Start with trust and test each idea against concrete observations. It is a conversation model, not a validated diagnosis.

  1. Absence of trust

    Mistakes, uncertainty, and requests for help stay hidden.

  2. Fear of conflict

    The team avoids open disagreement and preserves artificial harmony.

  3. Lack of commitment

    Decisions remain unclear or lack shared support.

  4. Avoidance of accountability

    Missed commitments and standards go unchallenged.

  5. Inattention to results

    Personal or departmental goals displace the shared result.

How the pattern appears

A product team plans a release:

  1. Absence of trust

    Nobody says that the new interface is still unclear.

  2. Fear of conflict

    No one challenges the tight timeline in planning. Concerns appear later in direct messages.

  3. Lack of commitment

    Friday remains the official release date. Two contributors already plan for the following week.

  4. Avoidance of accountability

    The integration test is missed. Nobody addresses the unmet commitment.

  5. Inattention to results

    Everyone reports their tasks as complete even though the release must be postponed.

One possible reading, not a diagnosis. Test assumptions together against concrete observations.

When this method helps

Use the model when a capable team feels distant, overly polite, or persistently unproductive.

Limits and when to pause

This model supports reflection; it is not a validated diagnosis. Do not label people or treat one response as proof of a team-wide pattern.

Where Reflacto uses this method

Choose the situation you want to reflect on:

Key benefits

  • Organizes symptoms into five connected layers
  • Gives the team shared language for difficult patterns
  • Shows where the team can start

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. Each layer builds on the one below.

Why do you have to start at the bottom?

Higher-level problems often grow from deeper ones. Demanding accountability without trust can create self-protection rather than candor.

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

Watch what happens after meetings. Healthy teams disagree openly; conflict-averse teams agree in the room and continue the debate in private.

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

Go first: admit a mistake, name what you do not know, or disagree respectfully. You do not need to be the manager to build trust.

Is this an assessment tool?

No. The model helps teams discuss observed patterns. It is not a validated measurement tool and does not provide comparable team scores.

Origin and Reflacto's adaptation

Patrick Lencioni published the model in 2002 as a business fable (Jossey-Bass). 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 asks rating-and-evidence pairs about trust, conflict and commitment. One final planning question combines accountability and results instead of assessing all five layers separately.

Primary sources and further reading

Editorially reviewed by Daniel Schmeiß

Last substantive review: August 30, 2026

Compare all methods