I. Absence of Trust

The Foundation of Invulnerability
Strategic Context & Key Concept
Trust is vulnerability-based trust - being comfortable being "naked" with colleagues: open about mistakes, weaknesses, and fears. The Vulnerability Gap: Inability to admit mistakes leads to a defensive atmosphere where people manage reputations rather than the business.
Symptoms
  • Team members hiding mistakes and weaknesses
  • Hesitation to ask for help or provide feedback
  • Jumping to conclusions about intentions
  • Guarded atmosphere with political word choices
  • Holding grudges, avoiding time together
Healthy Team
  • Members admit weaknesses openly
  • Ask for help and accept questions
  • Give benefit of the doubt
  • Take risks in offering feedback
  • Focus on issues, not politics
  • Offer and accept apologies readily
✓ What Managers Should Do
  1. Lead by example: Be first to acknowledge shortcomings
  2. Personal Histories: Use low-risk disclosure to humanize colleagues
  3. Diagnostic Tools: Use MBTI to understand interpersonal styles
  4. Team Effectiveness: Identify contributions and improvement areas
  5. Protect Vulnerability: Never punish honesty with reprisal
  6. Admit "I don't know": Show you don't have all answers
  7. Shared experiences: Create off-sites for deeper connection
✗ What Managers Should Not Do
  1. Fake vulnerability: Breeds deeper cynicism instantly
  2. Punish honesty: Never use admitted weakness against someone
  3. Allow back-channeling: Force issues "on the table"
  4. Skip "soft" stuff: Human element enables technical work
  5. Offer solutions first: Let team sit with discomfort
  6. Tolerate eye-rolling: Address passive-aggressive behaviors
  7. Avoid the "rebreak": Don't fear interpersonal discomfort
Quick Practices
Personal Histories: Share hometown, siblings, first job • Broken Arm Check: "Where are we 'broken' but pretending fine?" • First to Admit: Manager shares one thing they could have done better • Vulnerability Shield: Thank team members who admit mistakes
Reflection Prompts & Red Flags
Manager: Am I comfortable admitting when I'm wrong? Am I protecting "top performers" from standards? • Team: What do you need to feel safe admitting mistakes? • Red Flags: Guarded atmosphere, scripted meetings, silence during critical decisions

II. Fear of Conflict

The Trap of Artificial Harmony
Strategic Context & Key Concept
Great relationships require productive conflict. Teams need unfiltered, passionate debate over ideas. Many fall into "artificial harmony," avoiding disagreement to stay comfortable. The Harmony Trap: Choosing lack of tension over pursuit of the best answer results in best ideas never being surfaced.
Symptoms
  • Boring meetings lacking energy
  • Back-channeling: complaining in hallways
  • Passive-aggressive behavior: sarcasm, eye-rolling
  • Controversial topics avoided
  • Only speaking up during crisis
  • Post-meeting venting where real opinions shared
Healthy Team
  • Meetings interactive, relevant, exhausting
  • Team "mines" for buried disagreements
  • Issues resolved quickly without damage
  • Voice opinions even when uncomfortable
  • Prioritize "best" answer over "winning"
✓ What Managers Should Do
  1. Mine for conflict: Call out hidden tension - "I sense some don't agree"
  2. Real-Time Permission: Remind team debate is necessary - "This is good"
  3. Ground Rules: Demand engagement - no laptops or phones
  4. Devil's Advocate: Formally task someone to challenge consensus
  5. Interactive Relevance: Remove issues not worth arguing about
  6. Protect "Rebels": Reward those challenging groupthink
  7. Call out sarcasm: Address "Sarcratic" comments masking disagreement
✗ What Managers Should Not Do
  1. Premature intervention: Don't stop heated debate due to discomfort
  2. Protect team members: Let them work through disagreement
  3. Foster consensus: Don't seek 100% agreement - it pleases no one
  4. Allow "Opting Out": Don't let people stay silent
  5. End on "High": Better unresolved mess than false peace
  6. Ignore "The Look": Call out eye-rolls and sighing immediately
  7. Use agenda as shield: Don't let structure prevent "dangerous" topics
Quick Practices
Movie Comparison: Treat meetings like movies - no conflict = audience checks out • Real-time Permission: Say "This is what we need" during debate • Conflict Clock: First 10 min mine for conflict • Laptop Ban: Ensure full engagement • "Elephant" Check: "What didn't we say today?"
Reflection Prompts & Red Flags
Manager: Am I ending debates too early? Have I given permission to disagree? Who's holding back? • Team: What issue are we avoiding? How boring are our meetings (1-10)? • Red Flags: Yawning, quick consensus on complex issues, "boring" meetings

III. Lack of Commitment

The Cost of Ambiguity
Strategic Context & Key Concept
Commitment is the byproduct of clarity and buy-in through "Disagree and Commit." You don't need consensus; you need everyone to feel heard. Reasonable people don't need their way; they just need to be heard. Clarity over Consensus: Consensus attempts to please everyone but usually pleases no one.
Symptoms
  • Ambiguity about direction and priorities
  • Missed opportunities due to excessive analysis
  • Revisiting same discussions repeatedly
  • Lack of confidence and fear of failure
  • Second-guessing decisions after meetings
  • Departments giving different answers about priority
Healthy Team
  • Team aligns behind single "overarching goal"
  • Move forward without perfect data
  • Change direction without hesitation or guilt
  • Everyone leaves with clear, shared understanding
  • Prioritize "First Team" over departments
✓ What Managers Should Do
  1. Force Closure: Make final call on specific goal, number, deadline
  2. Review Commitments: Last 5 min summarizing decisions
  3. Cascading Messaging: Communicate same decisions within 24 hours
  4. Prioritize Ruthlessly: Establish one primary goal for the period
  5. Set Deadlines: Use hard deadlines to prevent analysis paralysis
  6. Demand "Weight In": Ensure everyone inputs before finalizing
  7. Admit "Best Guess": Lower barrier by acknowledging uncertainty
✗ What Managers Should Not Do
  1. Wait for 100% certainty: Don't delay action hoping for all data
  2. Allow "Loopholes": No half-baked or subjective understanding
  3. Value consensus over clarity: Don't let agreement need prevent decision
  4. Individual Autonomy trumps team: No "doing own thing" if conflicts with goal
  5. Ignore post-meeting whining: Call out those who committed but grumble
  6. Be Vague with Goals: Avoid soft goals like "improve revenue"
  7. Skip "No" Decisions: Commit clearly to what you won't do too
Quick Practices
Five-Minute Review: "What exactly did we decide and what are we telling our people?" • Whiteboard Priority: Keep goal at top of meeting board • 24-Hour Cascading: Email decisions to next level within one day • Worst-Case Exercise: Map worst case to show it's survivable • Commitment Audit: Rate commitment (1-10) to last week's decision
Reflection Prompts & Red Flags
Manager: Am I letting team off the hook by not forcing clear decision? Is our goal so clear a janitor could understand it? • Team: How clear are we on top priority (1-10)? If we could only do one thing before year-end, what? • Red Flags: Ambiguity, revisiting same decisions, "I never agreed" as excuse

IV. Avoidance of Accountability

The Burden of Low Standards
Strategic Context & Key Concept
Most effective accountability is peer-to-peer, not top-down. The leader's greatest failure isn't the poor performer's behavior, but the leader's tolerance of that behavior. When you tolerate a toxic "star performer," you aren't being "nice"—you are failing the team. The Peer Pressure Effect: Fear of letting down teammates is more powerful than any professional review.
Symptoms
  • Missing deadlines without peer comment
  • Resentment among members with different standards
  • Leader being only one who "comes down" on anyone
  • Tolerating "star performers" hurting team culture
  • Team looking to manager when deadlines missed
  • Mediocrity becoming the cultural standard
Healthy Team
  • Peers "get in each other's faces" about standards
  • Relationships stay strong; no "walking on eggshells"
  • Problems identified quickly by questioning approaches
  • Feel pressure to perform for the group
  • Manager is "arbiter of last resort"
✓ What Managers Should Do
  1. Publish Scoreboard: Display goals/standards so success/failure is public
  2. Step Back: Allow team to be "first and primary" source of accountability
  3. Team-Based Rewards: Shift from individual bonuses to collective achievement
  4. Confront "Sticky" Issues: Lead in addressing uncomfortable behavioral problems
  5. Regular Progress Reviews: Drill down on key drivers at every meeting
  6. Hold "Stars" Accountable: Be most rigorous with most talented people
  7. Identify "The Freds": Be honest about who's carrying burden for others
✗ What Managers Should Not Do
  1. Be only disciplinarian: If only you hold people accountable, you have individuals, not team
  2. Tolerate toxicity: Never ignore high-performer's bad behavior
  3. Protect from discomfort: Don't let "nice guy" or "genius" excuse low standards
  4. Avoid confrontation: Don't hope behavioral issues "sort themselves out"
  5. Use Subjective Standards: Avoid vague metrics; use "Scoreboard"
  6. Wait for Performance Review: Accountability must be real-time, not yearly
  7. Accept Excuses: Don't accept "I was busy" for missing team commitment
Quick Practices
Scoreboard Reviews: Start every meeting reviewing progress against goal drivers • Real-Time Feedback: Call out broken rules immediately • Accountability Round-Robin: Each member gives status update, peers ask follow-ups • Standard Posting: Post top 3 behavioral standards on conference room wall • "First Team" Check: Did we put department needs ahead of team goals?
Reflection Prompts & Red Flags
Manager: Am I tolerating a behavior frustrating the rest? Do reports feel more pressure from me or peers? Would I fire myself for tolerance of low standards? • Team: Who's carrying a burden because someone else isn't meeting standards? • Red Flags: Manager-centricity, resentment among high performers, "nasty" surprises about project delays

V. Inattention to Results

The Distraction of Status and Ego
Strategic Context & Key Concept
The ultimate goal of teamwork is the collective "score." This dysfunction occurs when team members put Individual Status (careerism) or Departmental Status ahead of team's collective goals. The "First Team" is the executive team, not the departments they lead. The Collective Ego: Shifting focus so that the team's win is the only win that matters.
Symptoms
  • Team members satisfied while company fails
  • Focusing on departmental silos vs. moving resources
  • Focus on personal career development/"resume building"
  • Loss of focus on company's "overarching goal"
  • "Consultant Mentality": isolated from outside own area
  • Stagnation and failure to grow
Healthy Team
  • Individuals make sacrifices in own departments for team goal
  • Team is "bloodhounds for results," obsessed with collective win
  • "First Team" is executive team, not direct reports
  • Success defined by scoreboard, not subjective opinions
  • High performers retained due to winning culture
✓ What Managers Should Do
  1. Reward the Team: Base rewards on collective achievement, not individual numbers
  2. Public Scoreboard: Make results visible so no ambiguity about where team stands
  3. "First Team" Loyalty: Remind primary loyalty belongs to this group, not direct reports
  4. "Bloodhound for Results": Focus meetings on how actions contribute to target
  5. Shift Resources Dynamic: Move people/budget from healthy to struggling departments
  6. Publicly Benchmark: Use "we are behind" speech to maintain urgency
  7. Identify "Individual Hitters": Call out those satisfied with stats while team loses
✗ What Managers Should Not Do
  1. Reward "Individual Hitters": Don't praise people who hit numbers but refuse to help team
  2. Allow Silos: Don't let departmental loyalty excuse not sharing resources
  3. Focus on long-term only: Don't let "profit" be only measure; use near-term goals
  4. Accept "Departmental Excellence": Never let VP say "my department is great" if company fails
  5. Ignore Resume Building: Call out executives worried about "career labels" vs. team output
  6. Let Scoreboard go "Dark": Don't stop measuring results due to discouragement
  7. Be Vague with "Success": No room for "subjective, interpretive, ego-driven success"
Quick Practices
Scoreboard Check-In: Begin every meeting with key metrics: revenue, deals, quality • Resource Shifting: "Do we need to move anyone from engineering to sales this week?" • First Team Huddles: 10 min discussing how to communicate as "First Team" • Result-Only Recognition: Only give awards if team-wide metric also met • Scoreboard Display: Physically display progress on chart in common area
Reflection Prompts & Red Flags
Manager: Have I made "Team 1" concept clear, or am I encouraging "den mothers" for departments? If company fails, will I be proud of personal performance? Who's more loyal to direct reports than peers? • Team: If team loses but your department succeeds, was it a good quarter? • Red Flags: Resume building, departmental turf wars, satisfied failure with no visible pain