Artificial harmony
- No raised voices in meetings
- Decisions made without dissent
- Mistakes hidden, then surface late
- 'We're aligned' said often, untested
- Conflict avoided to preserve speed
People
The Five Dysfunctions of a Team
by Patrick Lencioni
Source book · ~4h read
“Politics is when people choose their words and actions based on how they want others to react rather than based on what they really think.”
Pairing
Why this book, in this stage
The Five Dysfunctions of a Team is paired with the People stage — who builds it with you determines whether it gets built at all.
The argument
Central thesis
Patrick Lencioni argues that team dysfunction follows a predictable hierarchy. At the bottom is absence of trust — when teammates won't be vulnerable with each other. That breeds fear of conflict (artificial harmony, no honest disagreement). Without conflict, you get lack of commitment (no real buy-in to decisions). Without commitment, avoidance of accountability (no peer pressure to deliver). And without accountability, inattention to results (people optimize for individual goals over team outcomes). The five build on each other; you can't fix the top without fixing the bottom.
At a glance
Two ways a team can be 'doing fine'
Productive conflict
- Passionate debate about ideas
- Decisions made after real disagreement
- Mistakes surfaced early, openly
- 'We're aligned' = we just argued
- Conflict embraced to find truth
The hook
The founder problem this book solves
Most co-founder splits aren't about strategy. They're about a team that never learned to fight.
Founders rarely have a People problem in isolation. They have a trust problem masquerading as a strategy disagreement, a roadmap dispute, or a 'culture fit' issue. Lencioni's gift is naming the layers — once you can see them, you stop arguing about the wrong floor.
For first-time founders specifically, the early team is small enough that one absence of trust cascades through the whole company. A co-founder relationship with no real vulnerability calcifies into 'efficiency': you avoid hard conversations, you ship fast, you scale fast — and then one day something cracks and nobody knows how to repair it because you've never practiced repair.
5 takeaways
What to remember
01 / 05 — Trust = vulnerability
Trust isn't 'I think you're competent.' It's 'I'll show you my mistake before you find it.' Vulnerability-based trust is the foundation; nothing above it works without it.
Use ← → keys, or swipe on mobile
Practice CardOne-screen exercise
The Trust Audit
Pick your two highest-stakes peer relationships — usually a co-founder, sometimes a key early hire. For each, answer privately:
When was the last time you admitted to them you'd made a mistake before they noticed?
When did you last raise something that risked the relationship?
If the answer is 'I can't remember' or 'never,' you don't have vulnerability-based trust. You have artificial harmony. The fix isn't a team-building exercise — it's one honest conversation, this week, where you put something on the table you've been keeping private. The vulnerability has to come from you first; don't wait for them. The other four dysfunctions can't be addressed until trust is real.
Read
Get the book
Share