What Are the Reasons That Teams Succeed or Fail?

After forty years of coaching executives and the teams they lead, I can give you the answer directly, and it begins with a distinction that almost no advice on this subject makes. The standard reasons teams succeed or fail are real. The research on them is solid. Trust, communication, role clarity, shared direction, psychological safety. These are the factors every team effectiveness study identifies, and they are correct as far as they go. What the research does not tell you, and what the standard advice cannot, is what actually produces those factors in a team. Trust is not produced by a trust-building exercise. Communication is not produced by a communication protocol. Psychological safety is not produced by a leader who has been told to create psychological safety. These factors are what is left when a specific layer of thought has thinned in the people on the team, and that layer is the one telling them they need to protect themselves, prove themselves, or control outcomes. The effort to produce the factors is what is preventing the factors. This is the paradox at the center of team effectiveness, and understanding it is the difference between a team that performs and a team that performs the behaviors of performing.

Let me explain what I mean, because the distinction is the entire answer. The most thorough research on team effectiveness, published by McKinsey in late 2024, investigated fourteen annual literature reviews and more than one hundred forty published studies, and tested a diagnostic called the Team Effectiveness Index across one hundred ten teams and nine hundred five team members in forty-two countries. The research identified the drivers that matter most: direction, structure, people, and relationships, with trust and communication running through all of them. The research also debunked two myths that most leaders still believe. The first myth is that teams just click or they do not, that team chemistry is something you either have or lack. The second myth is that finding a capable leader is sufficient, that the heroic leader makes the team thrive. Both myths are false. The research found that three in four cross-functional teams underperform on their key metrics, a statistic first reported by Behnam Tabrizi in the Harvard Business Review in 2015 and confirmed in the years since. The research is descriptively accurate. Teams that have high trust, clear direction, and strong communication do outperform teams that lack them. The problem is that the research describes what effective teams look like. It does not describe what produces the looking. And the standard advice, which tells you to build trust, improve communication, and create psychological safety, treats the factors as behaviors you can install, when the factors are actually what is left when a thought layer that has been obstructing them is no longer running.

The research from the American Psychological Association points at the same thing from a different angle. Studies on team composition found that teams with higher average conscientiousness self-regulate their teamwork more effectively, and that the collective coordination of a team matters more than the individual ability of its members. The McKinsey research confirmed this with a concrete example. The United States men's Olympic four-by-one-hundred-meter relay team has included some of the fastest individual sprinters on the planet across multiple Olympics, and the team has underperformed or been disqualified repeatedly since 2008, because the team prioritized individual talent over collective practice. The runners were fast. The baton passes were not. All of this is accurate. But notice what every one of these findings has in common. They are all descriptions of a quality that is present when something is absent. Trust is present when self-protection is absent. Communication is present when the thought layer producing guardedness is absent. Coordination is present when the thought layer producing individual self-demonstration is absent. The factors are not additions. They are what is left when the subtractions happen. And the subtractions happen not by effort but by seeing the thought layer that has been producing the additions' opposite.

Why the Standard Advice Fails

The standard advice for building effective teams goes like this. Build trust. Improve communication. Clarify roles. Create psychological safety. Align on goals. Hold people accountable. Encourage collaboration. Manage conflict constructively.

Some of this advice is behaviorally accurate, in the sense that effective teams do these things. But the advice fails for a specific reason. It treats the factors as behaviors you can perform, and it ignores the thought layer that is preventing the factors from being present naturally. A leader who is told to build trust holds a trust-building exercise, and the exercise produces a temporary feeling of trust, and the temporariness is the problem. The team can tell the trust is manufactured, because manufactured trust has a quality that organic trust does not. The manufactured version is effortful. The organic version is effortless. And the team members reading the signal are reading the effortlessness, not the behavior. The standard advice gives the leader the behavior without addressing the thought layer producing the effort, and the effort is what makes the behavior read as inauthentic.

Here is what I have seen across forty years. A leader who is told to create psychological safety creates psychological safety, and the safety feels conditional, because the thought layer producing the conditionality is still running. A leader who is told to improve communication improves communication, and the communication reads as managed, because the thought layer producing the management is still running. A leader who is told to align on goals aligns on goals, and the alignment reads as compliance rather than commitment, because the thought layer producing the compliance is still running. The advice produces a performance of the factors, and the performance is detectable, and the detection is what prevents the team from developing the organic capacity the advice was trying to produce. The factors are not produced by performing them. They are produced by the absence of the thought layer that has been covering them.

There is a second reason the advice fails, and it is the one that matters most. The advice keeps the leader in what one assessment framework usefully calls the control register. The control register is the mode of operating where you are managing outcomes, directing behavior, resolving conflicts, and ensuring coordination through your own effort. The control register is what produces the team dysfunction that the research describes, because a team led by a person in the control register learns to wait for the leader rather than think for itself, and the waiting produces the passivity that the leader then tries to fix with more control. The standard advice does not address the thought layer producing the control register. It gives the leader behaviors to perform on top of it, and the thought layer continues running underneath the behaviors, and the behaviors read as performed because the thought layer is still producing the effort. The leader who builds an effective team is the leader who has shifted out of the control register, and the shift happens not by performing different behaviors but by seeing the thought layer that has been keeping them in the register.

The Real Mechanism

Let me explain what is actually happening, because understanding the mechanism is what makes the shift possible. The factors every team effectiveness study identifies are the default capacities of a group of minds that are not being obstructed by a layer of self-referential thought. The mind, when the obstructing layer is thin, naturally settles into a state of trust, openness, and coordination. This is not something the mind has to do. This is what the mind does when it is not being interfered with. The interference is the thought layer, and the thought layer is not a perception of the situation. It is an interpretation of the situation that runs fast and below awareness and feels like a perception.

Consider what happens when you watch a team that has the quality you are trying to build. People speak honestly, and the honesty does not produce conflict, it produces clarity. Decisions get made, and the decisions read as collective rather than imposed. Disagreements surface, and the disagreements do not produce defensiveness, they produce better thinking. The standard analysis says the team has trust and psychological safety. But watch more carefully. What you are actually seeing is the absence of something. You are seeing the absence of the self-referential thought layer that produces the self-protection, the proving, and the control. The team members are not adding trust. They are not performing psychological safety. They are simply present, without the thought layer running that would otherwise be telling them they need to protect their position, demonstrate their competence, or manage the impression they are making. The presence, without that layer, is what reads as trust and safety. The factors are not additions. They are what is left when the subtraction has happened.

The Thought Patterns That Produce Team Failure

After forty years of coaching executives and their teams, I can tell you that team failure is produced by a small number of thought patterns that run in the minds of the people on the team, and the patterns are more visible in the leader because the leader's patterns set the context for everyone else. Here are the ones I see most often.

The first is the control thought. The thought says: if I do not control this, it will go wrong. The thought produces a leadership style that manages outcomes rather than cultivating conditions, and the style produces a team that waits for the leader rather than thinking for itself. The control thought is activated by anything. A project running behind. A team member who made a mistake. A decision with real consequences. A stakeholder who is unhappy. The content varies. The mechanism does not. The mechanism is the mind interpreting a manageable situation as one requiring personal control, and the interpretation produces a behavior that undermines the team's capacity to function without the control. When the control thought is seen as a thought, the grip loosens, the team is given room to operate, and the coordination that emerges is organic rather than directed. The coordination was not produced by the leader letting go. It was produced by the absence of the thought that had been preventing it.

The second is the threat thought. The thought says: this person is a challenge to my position, or this team member's competence is a reflection on mine, or this disagreement is a danger. The thought produces reactivity, defensiveness, and the guarded communication that every team dysfunction study identifies as a symptom. The threat thought can be activated by anything. A peer who disagrees in a meeting. A direct report who has a better idea. A cross-functional partner who pushes back. The content varies. The mechanism does not. The mechanism is the mind interpreting a neutral or manageable stimulus as a threat, and the interpretation produces a physiological activation that is incompatible with the openness people read as trust. When the threat thought is seen as a thought, the activation drops, the defensiveness goes, and the communication that follows reads as honest rather than guarded.

The third is the proving thought. The thought says: I need to demonstrate my value, or I need to be the one with the answer, or my contribution needs to be visible. The thought produces the behavior that the McKinsey research identified in the relay team example. The individual performs at their personal best, and the personal best undermines the collective coordination that the team requires. The proving thought is what produces the team of individuals rather than the individual team. When the proving thought is seen as a thought, the self-demonstration drops, and the person begins to operate in service of the team rather than in service of their position in it.

The fourth is the separation thought. The thought says: this is us and that is them, or this is my function and that is theirs, or this is my responsibility and that is yours. The thought produces the siloed behavior that the research on cross-functional teams identifies as the most common cause of underperformance. The separation thought is activated by organizational structure, by competing priorities, by resource constraints, by personality differences. The content varies. The mechanism does not. The mechanism is the mind interpreting a structural distinction as a personal one, and the interpretation produces a behavior that prevents the collaboration the structure was designed to enable. When the separation thought is seen as a thought, the boundary becomes a functional distinction rather than a personal one, and the collaboration that follows is natural rather than forced.

What Actually Works

The standard advice tells you to build trust, improve communication, and create psychological safety. The direct answer is that you do not build these factors. You stop obscuring them. The factors are the default capacities of a team in which the obstructing thought layer has thinned, and the thinning happens by seeing the thought layer as a thought rather than as a perception. This is the work, and it is the work whether you are the leader or a team member, because the thought layer runs in everyone and the team's capacity is the aggregate of what is running in each person.

Here is what I tell the executives I coach. Start by noticing the thought layer in yourself, because your thought layer is the one you can see most directly, and it is the one setting the context for everyone else. When you feel the urge to control an outcome, notice the thought that says you need to control it. When you feel the urge to defend your position, notice the thought that says your position is under threat. When you feel the urge to demonstrate your competence, notice the thought that says you need to demonstrate it. When you feel the urge to protect your function, notice the thought that says the function is yours to protect. The thought is not a perception. It is an interpretation. And an interpretation that is seen as an interpretation stops producing the behavior that was covering the factor the team needs.

Then notice the same patterns in your team. The team member who is guarded is running the threat thought. The team member who is performing rather than contributing is running the proving thought. The team member who is siloed is running the separation thought. You do not fix these patterns by telling the person to trust, communicate, or collaborate. You help the person see the thought that is producing the guardedness, the performing, or the siloing. A thought that is seen is a thought that stops running the behavior from below awareness. This is the mechanism, and it works the same way in every person on the team, including you.

The research confirms this without naming it. The McKinsey study found that team effectiveness is less art and more science, and that the science is not about installing behaviors but about addressing the conditions that produce the behaviors. The condition that produces trust is the absence of the threat thought. The condition that produces communication is the absence of the guardedness thought. The condition that produces coordination is the absence of the proving thought. The conditions are produced by seeing the thoughts, and seeing the thoughts is what coaching does.

What This Means for Executives

If you are an executive leading a team that is underperforming, the standard analysis says you have a team problem. The direct answer is that you have a thought problem, and the thought problem is running in you and in the people on your team, and the team's performance is the visible output of the invisible patterns. The three-in-four failure rate for cross-functional teams is not a failure of team design. It is a failure of the thought layers in the people on those teams, and the thought layers are the one variable that the standard advice does not address.

The executives I coach across Ventura County and the rest of the country are dealing with this every day. In the technology and professional-services corridors around Thousand Oaks and Agoura Hills, the proving thought is dominant. Teams of high performers arrive at a senior level and find that the performing that earned them their roles is now the thing preventing the team from operating as a collective, because the proving register is still running in each person and the proving reads as individual effort rather than team coordination. In the healthcare and established-profession communities around Ventura and Oxnard, the control thought is common. Leaders who are holding substantial responsibility carry a continuous low-grade activation that they mistake for vigilance, and the activation produces a management style that undermines the autonomy the team needs to function. In the entrepreneurial and founder communities of Ojai and Santa Barbara, the separation thought runs. Founders who have built something real find that the team has grown beyond the point where personal relationships can carry the coordination, and the structural distinctions start to feel like personal ones, and the siloing begins.

If you want to explore this, learn more about executive coaching or book a free discovery call. You pay nothing upfront. At the successful conclusion of coaching, you pay what you think it was worth. That model exists because I am confident the work works, and I would rather you find out for yourself than take my word for it.

Ready to See What Is Actually Covering Your Team's Capacity?

If you have been trying to build team effectiveness by installing behaviors, and the effectiveness has not become reliable, the reason is not that you have not found the right behaviors. The reason is that the effectiveness is not produced by behaviors. It is produced by subtraction, and the subtraction is done by seeing the thought layer that has been covering it, not by adding more behaviors on top of it. That thought layer can be seen. And a thought that is seen is a thought that stops covering the capacity from below awareness.

If you are ready to stop performing your way into team effectiveness and start seeing what is actually covering it, book a free discovery call. We will look at the thought together. You will see, probably for the first time, that the effectiveness you have been chasing was never going to be reached by performing the factors. It was going to be uncovered by seeing the thought that was telling you to control, to defend, to prove, and to separate. Seeing it is the work. The work is what changes everything.