A team that never fights is a broken team.

At Rodati I read Patrick Lencioni’s The Five Dysfunctions of a Team. It’s the book that did the most to change how I build teams — and the lesson it carries is deeply counterintuitive when you’re young and running your first team.

I was young at Rodati. I had no idea what I was doing assembling people. Like most first-time managers, my instinct was to minimize friction. Keep the room calm. Don’t push too hard. Let smart people do their thing.

That instinct is the dysfunction.

the pyramid

Lencioni’s argument is that team dysfunction isn’t a single problem — it’s a stack. Each layer rests on the one below it. Pull out the base and the whole thing collapses upward.

                       /\
                      /  \
                     / 5  \             ← inattention to results
                    /______\
                   /        \
                  /    4     \          ← avoidance of accountability
                 /____________\
                /              \
               /       3        \       ← lack of commitment
              /__________________\
             /                    \
            /          2           \    ← fear of conflict   ★
           /________________________\
          /                          \
         /             1              \ ← absence of trust
        /______________________________\

Read it bottom-up:

1. Absence of trust. People don’t open up about weaknesses, mistakes, or what they actually think.
2. Fear of conflict. With no trust, no one risks disagreeing. Meetings go quiet, decisions go to the loudest voice or the most senior title.
3. Lack of commitment. When debate doesn’t really happen, people leave the room without buying in. They nod, then they hedge.
4. Avoidance of accountability. Without commitment, no one feels licensed to call out a peer who’s slipping. Everyone protects everyone.
5. Inattention to results. With no accountability, individual goals (status, ego, departmental wins) quietly outrank the team’s outcome.

The bottom two are where almost every team dies. Trust is hard but slow. Conflict is the one most managers get wrong on purpose.

the counterintuitive part

If a team has no conflict, the team is dysfunctional. That’s the whole insight.

It feels backwards because we grow up associating conflict with broken relationships, broken families, broken companies. So we instinctively dampen it. We rephrase the disagreement, change the subject, “let’s talk offline.” Comfortable rooms feel like good rooms.

Comfortable rooms are dead rooms.

The book’s plot is literally a CEO inheriting a polite, quiet, deeply broken executive team — and her first move is to make them argue. Out loud. About things that matter. Because she knows the comfort is the symptom, not the success.

what this means in practice

Working with me — at Rodati, at Sirena, at Darwin — has meant inheriting some specific behaviors I picked up from this book:

• Disagreements get said in the room, not after it. If you only push back in the hallway or in DMs, you’re contributing to the dysfunction.
• Senior people speak last when possible. Otherwise the conflict you wanted never appears.
• Bad decisions made with debate beat good decisions made without it. A team that committed to a wrong call together will course-correct fast. A team that nodded along to a right call will repeat the silence next time.
• Calling out a peer is part of the job, not a special escalation. If accountability only flows down from the manager, you’ve offloaded the team’s immune system to one person.

Especially in flat or horizontal teams, everyone has to be able to say what they think — comfortably, and to anyone in the room. If the org chart is flat but the conversation isn’t, the flatness is fake.

the rule

Build the team for productive conflict, not for harmony. Read the book if you haven’t. Then check your last three meetings: did anyone disagree out loud? If not, the team isn’t aligned. The team is dead and you haven’t noticed yet.

▮