Teams That Work Summary and key ideas

Teams That Work, by Scott Tannenbaum and Eduardo Salas.

A team is two or more people who interact and depend on one another at least some of the time, pursue a common or overlapping purpose, and are seen by themselves or others as a unit. Merely sharing a workplace or doing similar tasks does not make people a team. Membership can shift, roles can be unclear, and members need not share one perfectly defined goal. What matters is some real interdependence and a recognizable collective purpose.

Effectiveness takes a longer view than a single result. The authors describe a highly effective team as one that sustains strong performance, works through adversity and recovers from setbacks, and retains the energy and resources to meet future demands. A short-term win can hide depleted people or capabilities, while a team that does well in easy conditions may struggle under stress. The framework draws on a substantial, developing body of behavioral-science research. Its evidence is useful, though any synthesis is limited by the quality of the studies it combines.

The authors organize the explanation around seven connected drivers. Capability means having the knowledge, skills, and other attributes needed for the work. Cooperation includes members’ trust, confidence in the team, commitment, and willingness to help one another. Coordination is the action of noticing what is happening, backing up teammates, and adapting. Communication is the exchange of useful information within the team and with people outside it. Cognition is what members understand, individually and together, about priorities, roles, expectations, and the situation. Conditions include resources, time, autonomy, policies, rewards, and the surrounding work climate. Coaching covers leadership functions that provide support, guidance, and continued learning.

These drivers reinforce one another, and their relative importance can vary by situation. Information sharing can build a shared understanding of what teammates are doing; that understanding can make timely backup easier. Cooperative attitudes can also make people more willing to offer or accept help. Coaching matters partly because leaders need to ensure the team has enough of the other drivers. The framework is therefore more useful as a way to see connected causes than as a demand that every team emphasize each factor equally.

The first myth is that teamwork is separate from real work. When a task depends on collaboration, teamwork is how the work gets done. The authors cite a synthesis of 130 studies associating better teamwork processes with a greater likelihood of success, and research linking team training with improved job performance. The practical point is not to add meetings or talk for its own sake. Teams need the interactions their work requires, and the quality of those interactions matters more than their volume.

The second myth is that harmony guarantees effectiveness. Teammates do not have to like one another to work well together if they have a clear understanding of and an agreement about how they will perform together. Research cited by the authors did not support the idea that the best teams simply spend more time socializing. Dinners or retreats may be enjoyable, but they cannot fix unclear roles, competing priorities, or insufficient expertise. Avoiding every disagreement can also conceal problems the team needs to address. The third myth—that team players must sacrifice individual excellence—sets up a false choice. Organizations can need individually capable people who also help others succeed; the authors cite evidence that strong collaborators can also be top performers.

The fourth myth is that teamwork can make up for severe incompetence. Cooperation can help a team use its abilities, but it cannot create missing expertise or make members able to perform work they do not know how to do. A team needs sufficient competence for its assignments. Nor does adding highly capable people automatically improve results: individual skill still has to fit the work and connect with what others are doing.

The fifth myth is that teams are always the right structure. Some work is better handled by one person or by people whose tasks are only loosely connected. Requiring a team when members have little reason to rely on one another can add delays and coordination costs, encourage social loafing, or suppress innovation. A poor experience with a badly matched team structure does not prove that teamwork never works; it shows why the task and the structure need to fit.

Mookie Betts’s catch for the Red Sox makes the seven drivers visible in a play that first looks individual. Betts had the speed, athletic ability, and hand–eye coordination to reach the ball. As he ran, Rusney Castillo came from left field to back him up, so Betts could pursue the catch without worrying as much about a ricochet. Jackie Bradley Jr. ran toward center and called how close Betts was to the wall. That warning mattered because Betts had previously been injured on a similar play, but it let him keep his attention on the ball.

The outfielders also shared expectations: a ball hit into right-center triggered known roles and a synchronized response. Their instructor, Arnie Beyeler, had prepared them to back one another up, take angles, cut balls off, and hold balls to singles, limiting extra bases. The Red Sox culture treated teamwork as expected, rather than leaving each player to protect only his own interests. Capability made the catch possible, while cooperation, coordination, communication, shared understanding, coaching, and conditions supported it. The visible achievement belonged to Betts, but connected team contributions helped make it possible. Effective teams sustain results and remain ready for what comes next by building those drivers around the work they actually do.