How to Build a Successful Team: 5 Dysfunctions to Fix

Monday morning meeting. You present next quarter's plan and everyone nods. No objection, no question, not a word about the deadline half the room knows is impossible. An hour later you walk past the kitchen and hear the whole truth, in low voices, between two of your people.

That scene does not mean your team is bad. It means you may have capable people around a table, which is not the same as a team. The difference is what this article is about: what Google found when it studied what makes teams work, the five dysfunctions Patrick Lencioni described, and how to combine the two into a ten-question test you can run on your team this week.

A team is not a group of people in one room

Putting five engineers in one department does not create a team, just as eleven players standing on a pitch do not create a squad. In a group, each person does their own task and is judged on it alone. In a team, each member's success depends on the others', and nobody wins alone.

The researcher Richard Hackman argued in Leading Teams (2002) that a team's performance depends less on the leader's personal style than on how well the leader designs and supports the team so that its members can manage themselves. He named five conditions: a real team, a compelling direction, an enabling structure, a supportive organizational context, and competent coaching.

One observation from the book sounds obvious, and a reviewer called it simple but easy to overlook: members must know who is actually on the team. Ask each person to write down the names of the team members. You may be surprised by how different the lists are. Until that question has a shared answer, talking about trust and accountability is premature.

What Google found when it studied 180 teams

Google wanted to answer one question: what makes a team effective here? In what it called Project Aristotle, it studied 180 teams, 115 engineering project teams and 65 sales groups, and ran hundreds of interviews with leaders, according to the re:Work guide the company publishes. The researchers concluded that what mattered was less who is on the team and more how the team works together.

Several things you might expect to matter did not show a significant link to team effectiveness at Google: having teammates in the same location, consensus-driven decision making, extroversion, individual performance of members, workload, seniority, team size and tenure. The guide itself notes these factors may still matter elsewhere, so do not turn the result into a universal rule.

The five dynamics that did set effective teams apart are listed by Google in order of importance:

1. Psychological safety: members feel able to take a risk in front of colleagues, such as a question, an idea or an admitted mistake, without being seen as ignorant or incompetent.
2. Dependability: teammates reliably complete quality work on time.
3. Structure and clarity: goals that are specific, challenging and attainable.
4. Meaning: a sense of personal purpose in the work or its output.
5. Impact: seeing that one's work contributes to the organization's goals.

Amy Edmondson of Harvard Business School defined team psychological safety in 1999 as a shared belief among team members that the team is safe for interpersonal risk taking. In office terms: can you ask a question that sounds naive, admit a mistake or challenge a decision without paying for it? In her study of 51 work teams at a manufacturing company, safety was associated with learning behavior, and learning behavior was the link between safety and team performance. Google's survey measures it with an item like: "If I make a mistake on our team, it is not held against me."

Psychological safety is not only Google's interest. A 2017 meta-analysis pooled 136 independent samples covering more than 22,000 people and nearly 5,000 groups. According to a research summary of it, psychological safety was strongly linked to information sharing and learning behaviors. But most of the included studies were cross-sectional, snapshots in time, so they cannot support causal conclusions. Treat it as a strong hypothesis worth testing on your own team, not a law.

The five dysfunctions, from absence of trust to inattention to results

Patrick Lencioni, founder of the consulting firm The Table Group, published The Five Dysfunctions of a Team in 2002 as a leadership fable. He draws the five as a pyramid in which each dysfunction rests on the one below: without trust a team avoids conflict, without conflict there is no real commitment, without commitment accountability collapses, and without accountability results suffer.

1. Absence of trust

The sign: nobody admits a mistake or asks for help, because looking weak is costly. Lencioni ties this to the fear of being vulnerable in front of colleagues. My suggested fix is to start with yourself. In your next meeting, say one sentence such as: "I misjudged this task, and here is what I learned." When the team sees that admitting a mistake does not sink the person, others follow. The book The Blind Manager (in Arabic) gives trust a full chapter, titled "The Bank Account of Relationships: The Currency of Trust."

2. Fear of conflict

The sign: polite meetings where everyone seems to agree, then the real disagreements surface in corridors and side chats. According to Lencioni, the desire to preserve artificial harmony stifles productive conflict about ideas.

3. Lack of commitment

The sign: the same decision returns to the agenda two weeks later, and everyone left the room with a different understanding. The cause is a lack of clarity or buy-in; people do not stick to decisions they did not understand or were not heard on. The fix: at the end of every meeting, ask each member for one sentence answering who does what, by when. If the sentences differ, the decision is not finished.

4. Avoidance of accountability

The sign: everyone sees the colleague who is late with their work and nobody says a word, so the manager becomes the only one who speaks. People avoid interpersonal discomfort and put it ahead of the team's performance.

5. Inattention to results

The sign: every member hits their personal target while the team misses its own. Lencioni says that pursuing individual goals and personal status erodes the team's focus on collective success. His firm suggests a shared scoreboard that is specific and public, so no one can quietly succeed while the team fails. Pick three numbers for the team as a whole, not per person, and put them where everyone sees them.

Mind the logic of the pyramid: do not start by fixing accountability when you know trust is missing. The firm's own material says the leader should start at the base of the pyramid and build from there. In my reading this lines up with Google's findings: what Lencioni calls trust is close to what Google called psychological safety, and what he calls commitment and results sit close to structure and clarity and to impact. That overlap is my reading, not a claim made by either side.

In fairness: Lencioni presented his model in a fable, not a study. Organizational psychologists Gordon Curphy and Robert Hogan, in their book The Rocket Model (2012), grant that it is a straightforward and useful model, but argue that the book is explicitly a work of fiction not based on research, with advice that lacks empirical support. One of their examples is the personal-disclosure exercises Lencioni recommends for building trust; they doubt these work and cite Katzenbach and Smith's view that the only effective way for teams to build trust and cohesion is to do real work together. So use the model as a lens that helps you name what you see, not as a scientific verdict, and do not open with a group confession session; start with a small shared task the team can win together.

Healthy conflict: why your team needs to disagree

A team that never disagrees is not necessarily in agreement; it may be afraid. According to Lencioni's material, healthy conflict is about concepts and ideas, not personalities: "This plan has a hole in the budget," not "You don't understand budgets."

That does not mean waiting for everyone to agree. It is striking that consensus-driven decision making was among the factors with no significant link to team effectiveness at Google. Lencioni's material says commitment does not require consensus, only that every member feels genuinely heard before the decision, after which everyone moves forward despite the initial disagreement. In my reading, the condition is that everyone is heard, not that everyone agrees.

Three habits I suggest, from me and not from any particular study, for sparking healthy conflict:

• Before any major decision, ask each member to write their strongest objection before anyone speaks. That way people do not rush to adopt your view before theirs surfaces.
• Ask, "What is the weakest point in this plan?" and receive the answer with welcome, not defense. Your first reaction is the real message about safety.
• Appoint a rotating "devil's advocate" in each meeting whose job is to oppose the prevailing idea; after the debate, everyone commits to the decision.

Accountability between peers, not from the manager alone

When you are the only one who notices lapses and calls them out, you become a cop and your team becomes an audience. Lencioni's firm says colleagues should be ready to confront each other about behavior that harms the group, and that avoiding this loosens standards and makes the leader the only source of discipline. Its conclusion is that teams who hold each other accountable need fewer rules and less oversight, not more.

How do you build that habit? These are my suggestions, not study findings:

• Write agreements in the simplest form: who delivers what and by when. Accountability is hard when the agreement is verbal and vague.
• Give ten minutes of the weekly meeting to each member stating what they committed to last week and what they delivered. Review becomes routine, not accusation.
• Teach the team a polite nudge: "We agreed on delivery Thursday and I haven't received it. What do you need to get it done?" It starts with the agreement, not the person, and ends with a question about support.
• When someone complains to you about a colleague, ask, "Have you told them directly?" Then help them have that conversation instead of becoming a complaints channel.

Remember that accountability is built on top of safety: people who fear admitting their own mistakes will not nudge a colleague for fear of the reaction.

A ten-question test for your team

Where to start this week

Do not try to fix all five at once. At the start of the week, hand the test to your team. Midweek, gather the results and discuss them for twenty minutes, speaking as little as you can. By the end of the week, agree on one habit to begin next week, and write down who follows it up.

Remember, too, that teams change. A new member joining, another leaving or shifting priorities can change the whole picture, so repeat the test every quarter and do not treat it as a final certificate.

If you want to go deeper, the book The Blind Manager (in Arabic) covers understanding people's behavior, building trust and leading with humility. Its third part includes a chapter titled "The Circle of Safety and Politics: The Biochemistry of Trust," and the full version has a section on building cohesive teams alongside OKRs and smart hiring. On the book's page you can listen free to an abridged version, in Egyptian Arabic, that covers the first three parts.