qa-aman/team-health-check

Overview

Based on "The Five Dysfunctions of a Team" by Patrick Lencioni. The five dysfunctions build on each other as a pyramid: absence of trust is the root, and each layer makes the next worse. You cannot fix accountability without first fixing conflict norms, and you cannot fix conflict without first building trust. Diagnose from the bottom up, fix from the bottom up.

The Five Dysfunctions Pyramid

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

| Layer | Dysfunction | Healthy State | |-------|-------------|---------------| | 1 | Absence of trust | Vulnerability-based trust | | 2 | Fear of conflict | Productive ideological conflict | | 3 | Lack of commitment | Clear decisions with buy-in | | 4 | Avoidance of accountability | Peer-to-peer accountability | | 5 | Inattention to results | Collective focus on team outcomes |

Workflow

Step 1: Run the Diagnostic

Score each dysfunction 1-5 (1 = severe problem, 5 = healthy). Be honest - this is a diagnostic tool, not a performance review.

Trust - Score ___/5

• Do team members admit mistakes without fear of judgment?
• Do people ask for help when stuck, or silently struggle?
• Is there a gap between what people say in 1:1s vs. group meetings?

Conflict - Score ___/5

• Are difficult topics discussed openly in team meetings, or in side conversations afterward?
• Does the team reach real resolution, or does it "table" uncomfortable discussions?
• Do people disagree in the room, or wait until the decision is made and then undermine it?

Commitment - Score ___/5

• After decisions are made, do people execute with full effort even if they disagreed?
• Are meeting outputs clear decisions, or ambiguous "next steps"?
• Do people leave meetings with different understandings of what was decided?

Accountability - Score ___/5

• Do peers call each other out when a colleague drops the ball?
• Does accountability only flow downward (manager to report), or sideways too?
• Are standards applied consistently, or only when the manager is watching?

Results - Score ___/5

• Do team members prioritize team goals or their individual/department metrics when they conflict?
• Do people share information that would help teammates, or hoard it?
• Is collective success celebrated, or only individual wins?

Step 2: Identify the Root Layer

Find the lowest-scored dysfunction. That is where to start. It is almost always trust. If two layers score equally low, start with the lower one on the pyramid.

Example: Conflict scores 2/5 and trust scores 3/5. The conflict problem is real but traces back to trust. Recheck trust using more specific questions before prescribing conflict interventions.

Step 3: Prescribe Interventions by Layer

Trust (score < 3)

• Personal histories exercise: each person shares 3 facts others don't know (run in a team meeting or offsite)
• Leader goes first - share your own mistakes, failures, and areas of growth before asking others
• Working styles discussion: each person names their communication preferences and blind spots
• Timeline: 4-8 weeks of consistent behavior before trust measurably shifts

Conflict (score < 3)

• Name the pattern explicitly in the next team meeting: "I've noticed we align quickly. I want us to slow down and surface real disagreements."
• Assign a devil's advocate role in major decisions - rotate it so no one person becomes "the skeptic"
• Run pre-mortems: "Assume this plan fails in 6 months. What went wrong?" This gives permission to raise doubts
• After significant meetings, ask: "Is there anything said in the hallway that wasn't said in the room?"

Commitment (score < 3)

• Close every meeting with a 2-minute "decisions made" summary - read aloud, confirm agreement
• Use "disagree and commit" explicitly: team members can vote against but commit to execute
• Reduce decision latency - slow decisions kill commitment because context and energy decay

Accountability (score < 3)

• Create a team working agreement (written, visible, referenced in retrospectives)
• Shift accountability conversations from manager-only to peer-enabled: "I want you to tell each other when standards slip, not wait for me"
• Monthly retro focused only on: "what did we commit to, and what actually happened?"

Results (score < 3)

• Post team-level metrics somewhere everyone sees them (Slack, wiki, standup)
• Celebrate team wins explicitly - not just individual contributions
• When conflicts arise between team and individual goals, resolve them in favor of team - visibly, with explanation

Step 4: Write the Team Health Report

Team Health Check - [your team] - [date]

Overall Health Score: [x/25]

Scores:
  Trust:          [x/5]
  Conflict:       [x/5]
  Commitment:     [x/5]
  Accountability: [x/5]
  Results:        [x/5]

Root issue: [lowest layer]
Primary intervention: [specific action and owner]
Timeline: [when you will reassess - 6-8 weeks]

Key observations:
  [2-3 specific behaviors observed that support the diagnosis]

Next check-in: [date]

Anti-Patterns

1. Starting at the top layer Bad: "Our results are bad, let's focus everyone on metrics." Good: Poor results almost always trace back to trust or conflict issues. Fixing metrics without fixing trust produces short-term compliance and long-term cynicism.

2. Treating symptoms as the root cause Bad: "We have an accountability problem, so I'm adding more check-ins and status updates." Good: Accountability without commitment is theater. Commitment without healthy conflict produces fake buy-in. Check whether the "accountability problem" is actually a commitment or conflict problem first.

3. Leader skipping vulnerability Bad: Running trust exercises with the team but not sharing your own mistakes, fears, or development areas. Good: The leader always goes first. If you won't model vulnerability, the team won't either - they read your behavior, not your words.

4. One-time exercise Bad: "We did a team offsite and covered all five dysfunctions. We're done." Good: Health degrades under pressure. Teams revert. Reassess every 6-8 weeks during high-stress periods, every quarter otherwise.

5. Using the framework as a performance review Bad: Scoring individuals on the five dysfunctions and sharing those scores. Good: The framework is a team diagnostic, not a 360 review. Keep scores at the team level.

Quality Checklist

• [ ] Scored all five layers, not just the most visible problem
• [ ] Identified the lowest-scoring layer as the starting point
• [ ] Prescribed at least one concrete behavioral intervention per problematic layer
• [ ] Leader's own behavior included in the assessment
• [ ] Report documents specific observed behaviors, not just impressions
• [ ] Reassessment date is set (6-8 weeks out)