Estimated Reading Time: 10–12 minutes

What You Will Learn

• What distinguishes an interdependent team from a group of individuals who happen to work near one another.

• How norms, roles, communication patterns, power, and coordination shape collective performance.

• What team coaching is and how it differs from individual coaching, training, and facilitation.

• Why psychological safety matters without being sufficient on its own.

• What current research suggests about the benefits and limits of team coaching.

• Why team design, organizational context, leadership, and timing influence whether coaching works.

• How leaders can build teams that learn, adapt, and take collective responsibility for results.

Introduction: The Work Beneath the Work

Every team has two levels of activity. The first is visible: meetings, deadlines, plans, targets, decisions, and deliverables. The second is less obvious but often just as consequential: who speaks first, whose ideas receive attention, which disagreements are avoided, how mistakes are handled, whether responsibility is shared, and what happens when authority enters the room. Over time, these repeated interactions form patterns that influence how effectively the team can use the expertise of its members.

This less visible layer is sometimes described dramatically as the “secret life” of groups. Historically, thinkers such as Wilfred Bion used psychoanalytic ideas to explain unconscious group processes, including dependency, fight-or-flight, and pairing. Those ideas remain influential in some coaching and organizational traditions, but they should be treated as interpretive frameworks rather than established scientific mechanisms. Contemporary team research gives us more testable concepts: task interdependence, norms, coordination, trust, psychological safety, shared mental models, role clarity, communication, team learning, and organizational support.

Team coaching works within this collective level. Rather than assuming that better individuals automatically create a better team, it asks how people are functioning together and whether their patterns support the work they are trying to accomplish. The team, in other words, becomes the unit of attention.

A Team Is More Than a Collection of Capable People

A group becomes a team when members depend on one another to accomplish shared work. Google’s Project Aristotle made a similar distinction between work groups, whose members may mainly exchange information, and teams, whose members are interdependent in planning, problem solving, decision-making, and execution. That distinction matters because the quality of individual talent tells us surprisingly little about how effectively those individuals will coordinate once their work becomes interdependent.

Classic team research has emphasized several recurring conditions: a clear and compelling purpose, appropriate membership, workable structures, access to needed resources, and processes that support coordination and learning. Katzenbach and Smith popularized the importance of common purpose, complementary skills, and mutual accountability, while Hackman and Wageman argued that coaching cannot compensate indefinitely for poorly designed teams. If membership is unstable, goals are contradictory, roles are structurally confused, or incentives reward competition between people who are supposed to collaborate, coaching alone is unlikely to solve the problem.

This is an important corrective to overly psychological explanations of team performance. Teams do not fail only because members lack trust, emotional intelligence, or communication skills. Sometimes the system around them makes effective teamwork unnecessarily difficult.

What Team Coaching Actually Does

The International Coaching Federation treats team coaching as a distinct coaching modality in which the coach works with the team as a collective entity rather than simply coaching several individuals at once. Current ICF competencies emphasize team cohesion, conflict, participation, autonomy, shared goals, and awareness of patterns that emerge across the whole team. This systemic focus is what separates team coaching from a series of individual development conversations.

In practice, a coach may observe meetings, notice recurring interaction patterns, invite reflection after difficult decisions, help the team clarify expectations, or ask members to examine how they respond when disagreement appears. The coach is not there simply to provide communication techniques or tell people how effective teams behave. Instead, the process helps members become more capable of observing and adjusting their own ways of working.

This reflective component is important. A team may know that it should communicate clearly and still repeatedly interrupt certain members, avoid particular disagreements, or push decisions back toward the leader. Knowledge alone does not automatically change collective habits. Team coaching creates structured opportunities to notice those habits while they are happening and to experiment with different responses.

Team Coaching Is Not the Same as Facilitation or Training

Training typically introduces knowledge or develops a defined skill. Facilitation helps a group move through a particular conversation, meeting, workshop, or decision process. Team coaching may include elements of both, but its central aim is longer-term learning about how the team functions together.

A facilitator may help a leadership team produce a strategy during a two-day retreat. A trainer may teach members how to give feedback. A team coach is more likely to return over time and examine whether those practices are changing everyday interactions, whether old patterns have reappeared, and what prevents the team from applying what it already knows.

These distinctions are not rigid. In real organizational work, practitioners may move among coaching, facilitation, consultation, and teaching. Ethical practice requires clarity about which role is being used and why. The important question is not whether one method is superior, but whether the intervention matches the problem.

Psychological Safety Matters, but It Is Not Comfort

Amy Edmondson defined psychological safety as a shared belief that the team is safe for interpersonal risk taking. In psychologically safer teams, members are more willing to ask questions, admit mistakes, seek help, raise concerns, and disagree without expecting humiliation or punishment. This does not mean that everyone feels comfortable, conflict disappears, standards become lower, or every contribution must be praised.

Psychological safety is particularly relevant because teams need information that individuals may hesitate to reveal. A nurse who notices a possible error, an engineer who doubts a design assumption, or a junior employee who sees a flaw in a senior leader’s plan must decide whether speaking is worth the interpersonal risk. When the expected social cost of speaking is high, important information can remain hidden.

Broader team-learning research supports this connection. A large meta-analysis involving thousands of teams found psychological safety positively related to team learning, while team learning itself was associated with performance and innovation. The useful conclusion is not that psychological safety is the one secret ingredient of successful teams. It is that teams learn more effectively when members can contribute information without excessive interpersonal fear, especially when the surrounding structures also support good work.

What Project Aristotle Really Showed

Google’s Project Aristotle is frequently summarized as proving that psychological safety is the most important factor in team performance. That interpretation goes too far. Within the teams Google studied, researchers identified five particularly relevant dynamics: psychological safety, dependability, structure and clarity, meaning, and impact. The research was valuable because it shifted attention away from trying to assemble teams from particular personality types and toward examining how members actually worked together.

Google itself cautions organizations not to assume that its findings will reproduce identically everywhere. Teams differ by industry, task, culture, technology, expertise, risk, and organizational structure. A surgical team, software team, sales team, and executive committee do not face the same coordination demands.

The broader lesson is therefore more useful than a ranking of five factors. Team effectiveness depends substantially on the conditions and interaction patterns through which people combine their expertise. Team coaching can help teams examine those patterns, but it should not turn Project Aristotle into a universal formula.

The Evidence for Team Coaching Is Promising but Still Developing

Workplace coaching in general has accumulated a growing evidence base, with meta-analyses finding positive effects across several organizational outcomes. Team coaching specifically has a thinner research literature. Much of the field has historically relied on conceptual models, practitioner frameworks, case studies, and small organizational evaluations, which makes confident claims about large percentage improvements difficult to justify.

More rigorous studies are beginning to appear. A 2024 randomized controlled study comparing team coaching with team facilitation found that participants in the coaching condition showed greater improvements in perceived team psychological safety and cohesion. An earlier cluster-randomized study in German rehabilitation teams also evaluated a structured team-coaching intervention in real organizational settings. These studies are useful because they move the field beyond testimonials, but they do not yet establish that team coaching reliably improves every outcome across every organization.

The scientifically responsible conclusion is encouraging but modest: team coaching appears capable of improving some aspects of how teams work together, and the evidence base is growing, but the field is not yet mature enough to support sweeping claims about universal performance gains.

Good Coaching Cannot Rescue Bad Team Design

One of Hackman and Wageman’s most important contributions was their insistence that coaching is contingent. A coach is more likely to help when the basic conditions for teamwork already exist. A real team needs reasonably clear boundaries, a compelling direction, suitable composition, workable task structures, and an organizational environment that provides the resources and information required for performance.

Imagine a cross-functional team whose members are told to collaborate but are rewarded entirely for the success of their individual departments. The resulting tension is not simply a communication problem. Likewise, if leaders repeatedly reverse team decisions, asking members to develop more “shared ownership” may become performative because the team does not actually possess meaningful decision authority.

Team coaching is most powerful when it identifies the boundary between a behavioral problem and a structural one. Some difficulties can be addressed through better reflection and interaction. Others require changes in roles, workload, incentives, authority, staffing, or organizational policy.

Timing Matters

Teams are not equally receptive to coaching at every moment. Hackman and Wageman proposed that different coaching functions are particularly useful at different phases of team work. Early interventions can help teams establish motivation and direction, mid-course coaching can improve how strategies are being executed, and later reflection can help teams learn from what has already happened.

This makes intuitive and practical sense. A detailed review of coordination problems before a new team has done any meaningful work may produce little useful information. After several weeks of experience, however, actual patterns are available to examine. Similarly, a team facing an immediate operational crisis may need decisive coordination before it is ready for an extended reflective conversation.

Effective team coaching therefore requires judgment about when to interrupt, when to observe, and when the team needs to finish the work before analyzing how it worked.

Teams Have Patterns, Not Personalities

Coaching language sometimes describes teams as though they were individual people with personalities, emotions, blind spots, or hidden motives. Metaphors such as “the team is a living organism” can be useful in helping members think collectively, but they should not be taken literally. Teams are systems of interacting people operating within structures and environments.

What can be observed are recurring patterns. Perhaps disagreement consistently disappears when the senior leader enters the discussion. Perhaps one member regularly raises risks while another pushes for speed. Perhaps meetings produce apparent agreement but implementation reveals unresolved disagreement. These patterns can become stable enough that members begin anticipating and reinforcing them.

A coach helps make the pattern discussable without pretending that it belongs to a mysterious collective psyche. Once the pattern is visible, the team can examine whether it serves the work and what might happen if members respond differently.

Emotional Contagion Is Real, but Teams Do Not Share One Emotion

Research by Sigal Barsade and others has shown that emotion can spread through groups and influence cooperation and performance. People respond to one another’s expressions, tone, behavior, and energy, which means an anxious, enthusiastic, irritable, or calm colleague can affect the social climate around them.

Yet this does not mean that a team develops one collective emotion or that a leader’s mood automatically determines everyone else’s state. Members can respond differently to the same event, and teams often contain simultaneous enthusiasm, skepticism, frustration, and uncertainty. Culture, status, relationships, and personal differences all shape how emotion moves through a group.

Team coaching can therefore help members discuss emotional climate without turning feelings into a simplistic group diagnosis. The goal is not to make everyone feel the same. It is to understand when emotional patterns are affecting communication, coordination, judgment, or willingness to contribute.

Conflict Is Not the Opposite of Psychological Safety

Teams sometimes interpret psychological safety as a requirement to reduce disagreement. In reality, a psychologically safer environment should make productive disagreement easier because people are more willing to challenge ideas without expecting interpersonal punishment.

Conflict itself is not automatically useful. Personal attacks, status battles, contempt, and repeated unresolved tension can damage collaboration. But eliminating disagreement can be equally dangerous when teams need to evaluate complex information. What matters is whether members can challenge assumptions, request evidence, and disagree about tasks while maintaining enough relational stability to continue working together.

Team coaching can help teams examine how they disagree rather than encouraging them simply to disagree more. The quality of conflict matters more than its mere presence.

Team Learning Is More Than a Growth Mindset

The language of a “collective growth mindset” is appealing, but it risks stretching Carol Dweck’s individual-level concept beyond its strongest evidence. Team learning has its own substantial research base and does not need to be explained primarily through growth mindset.

Team learning includes behaviors such as asking questions, seeking feedback, discussing errors, experimenting, reflecting on outcomes, and updating routines. Recent meta-analytic work involving more than 15,000 teams found that team learning is associated with motivational, affective, cognitive, structural, and contextual factors, including psychological safety and supportive organizational conditions.

A team becomes more adaptive when learning is built into its work rather than left to occasional workshops. Coaching can support that process by making reflection routine and helping members convert observations into changes in behavior.

What Leaders Can Do Before Hiring a Team Coach

Before introducing coaching, leaders should clarify whether they actually have a team. If members do not depend on one another to deliver shared work, individual coaching, training, or better management may be more appropriate. Leaders should also examine whether goals, authority, roles, resources, and incentives support collaboration rather than undermine it.

The next question is what problem coaching is expected to address. “Improve teamwork” is too vague. A clearer objective might involve improving decision quality, reducing recurring coordination failures, increasing participation in meetings, strengthening cross-functional accountability, or helping a newly formed leadership team establish effective working practices. Outcomes should include both team-process indicators and business-relevant measures where appropriate.

Leaders must also be prepared to receive feedback about their own contribution. Team coaching becomes limited if the leader expects everyone else to change while remaining outside the system being examined.

Measuring Whether Team Coaching Is Working

Team coaching should be evaluated against the purpose established at the beginning rather than against a vague impression that meetings feel better. Useful measures can include psychological safety, team learning, clarity of decision rights, coordination quality, meeting effectiveness, role clarity, turnover intentions, cycle times, stakeholder outcomes, or relevant operational KPIs, depending on why coaching was introduced.

Qualitative evidence matters as well. Are previously avoided issues being discussed? Are members challenging assumptions earlier? Are decisions clearer? Does the team recover more effectively after disagreement? These changes may precede measurable performance outcomes.

Measurement also protects against the tendency to attribute every improvement to coaching. Teams change because of new leaders, new incentives, workload shifts, market conditions, staffing changes, and many other factors. Evaluation should therefore remain cautious about causality.

Final Reflection

The “secret life” of a group is not a hidden collective mind waiting for a coach to uncover it. It is the accumulation of patterns through which people coordinate, interpret one another, respond to authority, manage disagreement, share information, and make decisions. Some of those patterns support the task, while others quietly make collaboration harder than it needs to be.

Team coaching can be valuable because it gives teams a structured opportunity to examine those patterns while they are still capable of changing them. The strongest coaching does not simply make people more open, emotionally expressive, or trusting. It helps them connect reflection to the realities of the work: purpose, roles, authority, coordination, decision-making, learning, and accountability.

The evidence for team coaching is promising, but the field should resist claims that coaching inevitably transforms collaboration or produces predictable percentage gains. Effective teams depend on more than coaching, and some problems cannot be solved through better conversations when the underlying structure remains dysfunctional.

A well-designed coaching process therefore does something more modest and, ultimately, more useful. It helps a team become better at seeing how it works, testing whether those patterns still serve its purpose, and taking greater collective responsibility for changing what it can. When that capacity remains after the coach has left, coaching has contributed not merely to a better conversation, but to a team that is more capable of learning from its own experience.

References

Barsade, S. G. (2002). The ripple effect: Emotional contagion and its influence on group behavior. Administrative Science Quarterly, 47(4), 644–675.

Edmondson, A. C. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.

Google re. (2015). Understand Team Effectiveness: Project Aristotle.

Hackman, J. R., & Wageman, R. (2005). A theory of team coaching. Academy of Management Review, 30(2), 269–287.

Marlow, S. L., et al. (2024). There is no end to learning, but how does it begin? A meta-analysis of the team learning pathway. Journal of Management Studies.

Passmore, J., Tee, D., & Gold, R. (2024). Team coaching using LSP and team facilitation: A randomized control trial study measuring team cohesion and psychological safety. Journal of Work-Applied Management.

Peters, J., & Carr, C. (2013). Team effectiveness and team coaching literature review. Coaching: An International Journal of Theory, Research and Practice, 6(2), 116–136.

Wageman, R., Hackman, J. R., & Lehman, E. (2005). Team diagnostic survey: Development of an instrument. Journal of Applied Behavioral Science, 41(4), 373–398.