The Five Dysfunctions of a Team: A Leadership Fable

Picture the most talented leadership team you have ever assembled. Marquee CVs, the right logos, a product the market actually wants. Now picture them in a room, nodding politely at a strategy that half of them privately doubt. Nobody says it out loud. The meeting ends on time. The quarter ends in a miss.

If that scene made you even slightly uncomfortable, Patrick Lencioni wrote this book for you.

The Five Dysfunctions of a Team is barely 200 pages, reads like a novel, and has quietly reorganised the way I think about almost every founding team and CXO group I work with across India's growth-stage ecosystem. Here is why I keep returning to it, and the uncomfortable questions it should raise for anyone scaling a company right now.

A fable with a serious model underneath

Lencioni delivers his ideas as a fable. Kathryn, a new CEO, inherits a well-funded, over-credentialed, badly underperforming startup. Sound familiar? The diagnosis is not the market and not the strategy. It is the team itself. He stacks the problem into five layers, each one resting on the one beneath it.

1. Absence of trust

Not the 'I trust you to hit your number' kind. He means vulnerability-based trust: the willingness to say 'I was wrong', 'I don't know', or 'I need help' in front of your peers. In Indian leadership rooms, where hierarchy and deference run deep, this is often the first casualty. The founder is rarely told the unvarnished truth, and the team mistakes politeness for cohesion.

2. Fear of conflict

Without trust, teams manufacture what he calls artificial harmony. Meetings stay calm, decisions stay slow, and the real debate migrates to side conversations and WhatsApp threads. For a growth-stage company that has to make ten near-irreversible bets a quarter, that is quietly lethal.

3. Lack of commitment

People do not commit to decisions they were never allowed to argue about. The CXO who stayed silent in the room has no skin in the outcome. What looks like alignment is often a roomful of unspoken reservations, waiting to resurface the moment things get hard.

4. Avoidance of accountability

When commitment is fuzzy, peers stop holding peers to a standard and wait for the founder to play enforcer. As you cross 100 to 150 people, that single point of accountability becomes the bottleneck that throttles your velocity.

5. Inattention to results

At the top of the pyramid, individual ego and departmental goals quietly outrank the collective scoreboard. Sales protects Sales. Engineering protects Engineering. Everyone is winning except the company.

What makes the model so useful is that it is a ladder, not a checklist. You cannot fix results by ranting about results, because the leak is almost always lower down. Most founders I meet are convinced their problem is dysfunction number five. It is almost always number one.

What the book gets right

• It reads in a single evening. The fable format means your whole leadership team can actually finish it, which is rare for a business book.
• It diagnoses without preaching. The pyramid gives a team a shared language to name what is going wrong, so the conversation stays about the system and not about blame.
• It puts the leader first. Lencioni is unambiguous that trust begins with the person at the top going first, which is exactly where change in a founder-led company has to start.
• It travels well. Written for Silicon Valley in 2002, yet it maps almost too neatly onto the founder-centric, deference-heavy dynamics of Indian startups in 2026.

Where it falls short

• The fable is American and a little dated; you will need to translate its cultural texture into a hierarchy-aware Indian context yourself.
• It is a brilliant diagnosis but a thin manual. Knowing your team lacks trust is not the same as knowing how to rebuild it on a Monday morning, and that gap is precisely where structured coaching does its work.
• The model can be misused. I have watched leaders weaponise 'we need more conflict' as licence to simply be combative. The point was never conflict for its own sake.

The real invitation

Here is the coaching invitation I would leave you with. Do not read it for your team. Read it for yourself, and sit with one question: which of these five am I personally making safer, or harder, for my team to overcome? The most powerful shift I see in the leaders I coach is rarely a new framework. It is the moment they stop diagnosing the room and start examining their own behaviour in it. Trust, conflict, commitment, accountability, results — every one of them begins to move the day the leader goes first.

If that question lands, and especially if it stings a little, that is usually the beginning of the real work. I partner with founders and CXOs navigating exactly these transitions — founder-to-CEO and individual-contributor-to-executive — and the messy, high-stakes job of turning a talented group into an actual team.