Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
Teams That Work

Teams That Work

The Seven Drivers of Team Effectiveness
Make your team work better by fixing the conditions behind its coordination, candor, and results.
by Scott Tannenbaum 2020 269 pages
4.09
185 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Measure a team's staying power, not its latest win

Success has three parts. A team is more than people sharing a room or doing similar jobs. Members must rely on one another at least sometimes and share some sense of purpose. Effectiveness means sustained results, resilience under pressure, and enough energy and resources to keep working well. A team that hits one deadline by exhausting everyone may have succeeded once, but it has damaged its capacity to succeed again.

Individual feats have a team behind them. When Mookie Betts made a spectacular catch for the Red Sox, a teammate ran behind him in case he missed, another called out how close he was to the wall, and their coach had practiced the response with them. The visible achievement belonged to Betts. The conditions that made it possible were collective.

Analysis

This definition resists a common managerial error: treating short-term output as the whole scorecard. It brings performance together with resilience and human capacity, much as safety-critical fields distinguish a successful operation from a system that can repeat it without accumulating hidden damage. The Red Sox play makes an abstract point memorable: individual excellence is often the last visible link in a chain of preparation and support. The challenge is measurement. Vitality and resilience can be harder to quantify than revenue or deadlines, which makes it especially important to assess them deliberately.

Put people in teams only when their work genuinely depends on one another

Teamwork has a price. The authors describe reliance as a continuum: salespeople may work mostly alone, while a surgical team or soccer squad must coordinate continually. As dependence increases, coordination, communication, and shared understanding become more consequential. Not every task deserves a committee. Unnecessary teams can add delay, social loafing, and friction without improving the work.

Teams also differ in other ways. Membership may be stable or frequently changing; tasks may be predictable or volatile; people may work together in one place or at a distance; and their expertise may overlap or be distinct. These differences shape what a team needs. A rotating, remote project group with specialized roles, for instance, cannot rely on the same informal routines as a stable crew working side by side.

Analysis

This is a useful corrective to the assumption that collaboration is inherently virtuous. The relevant question is not whether people can meet, but whether one person's work changes what another person can do. That resembles a systems-design decision: add coordination only when the gains from integration exceed its costs. The sliding-scale view is stronger than rigid team categories because work can shift over time. A team that once needed little coordination may need much more after a new dependency, deadline, or membership change.

Close skill gaps before asking teamwork to perform miracles

Competence is the floor. Teams need sufficient technical ability for the work. A group of friendly, cooperative graduate students cannot make up for a major athletic disadvantage against a team that is faster, taller, and more skilled. When a gap matters, the options are to develop people, bring in expertise, or redesign the work. Team spirit cannot replace missing capability.

Portable teamwork skills matter too. Communication, feedback, conflict management, interpersonal judgment, and leadership skills help people contribute across different teams. Teamwork savvy means knowing how teams function and what effective teammates do. Collective orientation, a tendency to put the team's interests into consideration, also helps, especially when members rely on one another. But do not burn out the people who always volunteer to help.

Analysis

The distinction between task skill and teamwork skill is valuable because organizations often invest heavily in the former and treat the latter as personality or goodwill. The book instead frames many collaboration skills as learnable capacities. That is compatible with deliberate practice: people improve when behaviors are made explicit, exercised, and followed by feedback. The caution about overusing helpful colleagues is also important. A team can quietly transfer coordination costs onto its most cooperative members, then mistake their exhaustion for an individual problem rather than a design flaw.

Add stars carefully when teammates must coordinate constantly

More talent is not always better. In research on soccer and basketball teams, adding elite players improved results only up to a point. Performance flattened and could decline when roughly 60 percent of a team, give or take 10 percent, were classified as elite. The proposed explanation was competition for status and disruption of coordination. Baseball teams, with more independent episodes of play, did not show the same pattern.

Talent travels with its support system. A study of more than 1,000 investment analysts found that star analysts who changed firms often suffered a performance decline lasting five years on average. The drop was smaller when new employers offered comparable support, and disappeared for analysts who moved with teammates. Teamwork can help stars thrive, but it cannot rescue a team with a severe skill deficit.

Analysis

The important insight is not that stars are harmful, but that talent produces value through a social and organizational setting. This parallels the idea of complementarity in economics: a high-performing component can be less useful when the system around it cannot integrate its output. The sports comparison adds needed nuance because interdependence changes the effect of adding talent. The approximate threshold should not be treated as a hiring formula, however. The studies show a pattern in particular settings, not a universal percentage for every workplace.

Build trust and candor through repeated actions, not slogans

Silence can be dangerous. During the 1996 Everest expedition, the leaders' strict rule against dissent made it harder for climbers to challenge a decision to continue past the planned turnaround time. Five people died. The book presents poor psychological safety, the belief that one can raise concerns without being harshly judged, as a major part of the failure. Trust and psychological safety are related but distinct: trust concerns whether others will act well; safety concerns whether speaking up feels acceptable.

Four beliefs matter. The authors identify trust, psychological safety, collective efficacy, and cohesion as important team attitudes. Collective efficacy is a shared belief that this team can handle a particular task. Cohesion includes commitment to the work as well as interpersonal connection. These beliefs grow from what people experience, so leaders should keep commitments, invite dissent, recognize progress, and address harmful conduct.

Analysis

Psychological safety is most useful when understood as permission to take interpersonal risks, not permission to avoid standards. The distinction matters: a team can maintain high expectations while making it safer to report errors or challenge a plan. In this sense, candor is an information-quality mechanism, not merely a comfort benefit. The Everest account shows how hierarchy can suppress corrective information. Yet no single team climate explains every disaster; capabilities, fatigue, resources, and judgment also matter. Safety improves the odds that concerns become visible, not the guarantee that every decision will be sound.

Make disagreement useful by arguing over the work, not each other

Conflict has different forms. Disagreement about the substance of a task can expose faulty assumptions and improve a decision. Personal conflict and disputes about how work is assigned tend to harm performance. Across 116 studies involving more than 8,800 teams, interpersonal and process conflict were negatively related to results, while task conflict had a more complicated effect.

The climate and method decide the outcome. Task disagreement is more likely to help when people feel safe enough to speak and the group seeks the best answer rather than trying to make one person's idea win. Avoidance is not a solution either: unresolved concerns remain, often out of sight. Leaders can encourage constructive debate by inviting different views, not speaking first when they want independent input, and separating criticism of an idea from criticism of its author.

Analysis

This section avoids the simplistic choice between harmony and confrontation. Disagreement can function like error detection in engineering, but only if the signal can be raised without being converted into a status contest. The recommendation to focus on the work is especially practical because people often experience critique as personal even when that is not the speaker's intent. One limitation is that a call for debate can become performative if leaders have already decided. Genuine openness requires clarity about which decisions can still change.

Train teams to notice, help, adapt, and review their own work

Coordination is visible behavior. Effective teams monitor their teammates, their own results, and changing conditions. That awareness lets them offer advice, lend a hand, or temporarily fill a gap. Help is not automatically helpful: people need the skill and time to assist, and repeated rescue can encourage a teammate to withdraw effort. Teams should clarify when backup is expected and who can provide it.

Improvement needs a routine. Teams adapt in real time when an unexpected event demands a quick response, and they adapt through reflection when they learn from experience. A team debrief is a structured review of what happened, what worked, and what to change. A meta-analysis cited by the authors found that teams conducting debriefs outperformed others by an average of 20 percent. Leaders trained to debrief teams saw gains of up to 40 percent in one study.

Analysis

The sequence from noticing to acting to reviewing offers a compact model of team learning. It resembles feedback control: a system must detect a deviation, respond, and compare the result with its aim. The debrief is powerful because it turns experience into an explicit adjustment rather than assuming repetition creates learning by itself. But reflection needs boundaries. Endless review can consume time and turn into blame or process theater. A useful debrief ends with a small number of concrete actions, an owner, and a follow-up.

Improve the information exchanged, not the volume of messages

Useful communication is selective. A team needs information that is clear, accurate, timely, and delivered to the people who need it. Especially valuable is unique information, knowledge that others do not yet have. A nurse's unshared note about a patient's travel history, for example, can matter more than a flood of routine updates. More talking can create noise without helping decisions.

Close the loop. In closed-loop communication, one person sends a message, the recipient repeats their understanding, and the sender confirms or corrects it. In a study of pediatric trauma cases, tasks were completed 3.6 times faster when teams used this method. Teams also need boundary spanning, the work of sharing information and maintaining relationships with people outside the group. They should decide who communicates with each stakeholder and what information must cross the boundary.

Analysis

The emphasis on unique information is a subtle but strong improvement over the generic instruction to communicate more. It directs attention to what the team does not yet know, which is often where decision quality is lost. Closed-loop confirmation also counters the false confidence that a message sent is a message understood. These techniques are especially useful at handoffs, where responsibility and context change hands. They should not be applied mechanically to every casual exchange; the point is to use extra precision when misunderstanding has a meaningful cost.

Align the team's understanding before expecting seamless improvisation

Shared cognitions make coordination possible. These are accurate, overlapping or complementary understandings of goals, priorities, roles, methods, expertise, and likely contingencies. They do not require everyone to know everything. They do require members to know enough about the situation and who knows what. The Los Angeles Rams' offense demonstrated this when players adjusted together to an unexpected defensive formation, even though the changed play was not scripted.

Check the team's common picture. Ask whether members can answer similar versions of these questions: Where are we headed? What matters most? Who handles what? How do we work? Why? Who knows? What if conditions change? What is happening now? Build alignment through role clarification, cross-training, scenario practice, onboarding, huddles, and debriefs. Familiarity helps, especially professional familiarity, but long-standing teams can become complacent and rely too heavily on old routines.

Analysis

Shared understanding is not conformity. A team can know that priorities are unsettled, or that two experts disagree, and still share an accurate picture of its uncertainty. That distinction is crucial in complex work, where forcing premature agreement can conceal risk. The Rams example illustrates how preparation can make improvisation look effortless. In less dynamic teams, the equivalent may be a simple agreement about decision rights or handoffs. Familiarity helps create fluency, but it can also harden habits, so teams need both common expectations and periodic chances to question them.

Fix incentives and constraints that reward the wrong behavior

The environment teaches priorities. At a luxury retailer, one salesperson pretended to answer a phone rather than handle a customer's return. Individual sales drove compensation and promotion, so the behavior was understandable within the system, even though it harmed the customer and team. The company changed its certification and reward practices to recognize collaborative contributions, then made clear that high sales did not excuse refusing teamwork.

Look beyond team attitudes. Hiring, onboarding, performance reviews, promotions, and senior leaders' conduct all send signals about what is valued. Local constraints matter too: a team without enough time, resources, information, or decision authority may be unable to collaborate well. The authors call a situation strong when its cues and incentives make expected behavior clear. A strong situation can support cooperation or reinforce selfishness, depending on what it rewards.

Analysis

This is the book's sharpest organizational claim: culture is partly enacted through ordinary systems, not just stated values. The fake phone call is memorable because it reframes a so-called attitude problem as a predictable response to incentives. That perspective connects team behavior to institutional design. It also guards against blaming individuals for constraints they cannot control. Still, incentives are not destiny. People sometimes cooperate against their immediate rewards, and poorly designed group rewards can hide unequal effort. Effective systems align incentives while preserving accountability for individual contribution.

Make leadership a team function, bounded by clear accountability

Leadership is work to be done. A team needs someone to clarify direction, roles, and priorities; hold members accountable; remove obstacles; manage morale; create safety; encourage participation; and support learning. A formal leader cannot see everything, so members may need to step up. Shared leadership means members informally perform useful leadership actions, not that authority disappears or every decision becomes a vote.

Style matters, but behavior matters more. The authors draw lessons from transformational leadership, which inspires commitment; servant leadership, which prioritizes team members' needs; and civil leadership, which rejects incivility. Empowerment needs boundaries so initiative does not become unauthorized commitment. Leaders should also guard against self-anchoring, the tendency to assume others think and feel as they do. Asking team members directly is better than guessing.

Analysis

This approach treats leadership as a set of functions rather than a personality costume. That makes it easier to distribute work without romanticizing leaderlessness: authority can remain clear while expertise and initiative circulate. The warning about self-anchoring adds a useful cognitive check, since power can make a leader's own perspective feel like the team's consensus. The tradeoff is that shared leadership can create confusion if decision rights remain implicit. Teams benefit when members know where initiative is welcome, where approval is required, and who remains accountable for the final call.

Analysis

The book's central contribution is to replace personality-centered explanations of teamwork with a system diagnosis. When teams struggle, the easy stories are that people dislike one another, a leader is not forceful enough, or communication is insufficient. The authors offer a more discriminating set of questions: Does the team have enough expertise? Do incentives make collaboration rational? Can people speak up? Are roles and priorities understood? Does anyone notice when conditions change, and does the team learn from its response?

The framework's strength is its integration. Skills, beliefs, behavior, information, shared understanding, leadership, and context influence one another rather than operating as isolated variables. This explains why a morale event cannot repair unclear roles, why confidence cannot replace competence, and why the same communication practice may help one team but burden another. The emphasis on interdependence provides a practical way to tailor advice instead of prescribing maximum collaboration everywhere.

Its main limitation is also a feature of any broad framework: seven categories can become a checklist that appears more precise than diagnosis actually is. The evidence described includes meta-analyses, field studies, and examples from high-stakes settings, but associations do not automatically identify the best intervention for a particular team. Managers should use the categories to generate hypotheses, then check them against observable work, member perspectives, and constraints. The framework is most powerful when it leads to a small experiment, such as clarifying a handoff or protecting time for a debrief, followed by evidence that the change helped.

The practical message is not that every team should become close-knit or endlessly collaborative. It is that teams should be designed for the work they do, supported by conditions that reward the needed behaviors, and given routines to adjust. Sustained effectiveness emerges when competence, candor, coordination, and context reinforce one another, rather than when a team relies on a heroic individual to compensate for everything else.

Summary in 30 Seconds
Effective teams need the right mix of expertise, interdependence, trust, clear roles, useful information, and incentives that support collaboration. Debate about the work can improve decisions when people feel safe to speak, while personal and process disputes tend to hurt results. Structured team debriefs improve performance by an average of 20 percent, and closed-loop communication helped pediatric trauma teams finish tasks 3.6 times faster. Match teamwork practices to the task, then test whether changes help.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.09 out of 5
Average of 185 ratings from Goodreads and Amazon.

Teams That Work receives mostly positive reviews, with an average rating of 4.17/5. Readers appreciate its evidence-based approach, practical tips, and comprehensive coverage of teamwork principles. The book is praised for its research-backed recommendations and actionable advice. Some find it academic and occasionally dry, while others consider it outdated. Many readers value its insights on team dynamics, leadership, and performance improvement. Overall, it's viewed as a valuable resource for leaders and team members seeking to enhance collaboration and effectiveness.

Your rating:
4.58
162 ratings
Want to read the full book?

Glossary

The Seven Drivers of Team Effectiveness

Team performance diagnostic

The authors' framework for examining seven connected influences on team outcomes: individual and collective capability, cooperative attitudes, coordination behaviors, communication, shared understanding, leadership, and the surrounding conditions. It is intended as a diagnostic, not a universal recipe. A team should identify which drivers matter most for its work and where a weakness is limiting sustained performance.

Reliance continuum

Degree of work dependence

A way to describe how much team members must depend on and coordinate with one another to complete their work. At one end, people perform mostly independent tasks and combine results. At the other, members coordinate continually. The level of reliance affects how important teamwork behaviors, shared understanding, and collective confidence are.

Collective orientation

Preference for team interests

A relatively stable tendency to value team goals and support teammates, alongside one's own work. People high in collective orientation are more inclined to share information and provide help. It does not mean abandoning personal excellence or always putting others first, and its effects depend on whether the team's context makes cooperation possible.

Psychological safety

Safety for interpersonal risks

A shared belief that team members can ask questions, admit mistakes, offer dissent, seek help, and share concerns without being harshly judged or punished. It is not the absence of pressure, friendship, or accountability. It makes it more likely that relevant information and disagreement will surface, particularly in hierarchical teams.

Collective efficacy

Shared task-specific team confidence

A shared belief among team members that their team can succeed at a particular task, mission, or situation. It differs from general confidence in the team because it concerns a specific challenge. Collective efficacy can support effort and persistence, but belief alone cannot compensate for a serious shortage of skill or resources.

Shared cognitions

Common, complementary team understanding

The accurate, overlapping or complementary understanding team members hold about matters such as goals, priorities, roles, tasks, contingencies, current conditions, and where expertise resides. Members need not know identical things. They need a sufficiently common picture to coordinate, adapt, and locate knowledge when it is needed.

Transactive memory systems

Shared map of who knows

A team's distributed knowledge structure, including members' understanding of who possesses particular expertise and how that knowledge can be accessed. A functioning system does not require every member to learn every subject. It helps the team direct questions and requests to the right person, supporting coordination and adaptation.

Situational awareness

Understanding changing conditions

Awareness of relevant events and conditions that may affect team performance. The authors describe it as noticing what is happening, interpreting what it means, and anticipating what may happen next. Team members can each see different parts of a situation, so sharing observations helps create collective awareness and guide action.

Closed-loop communication

Confirming message understanding

A communication method with three steps: one person sends a message, the recipient repeats their understanding, and the sender confirms or corrects it. The check helps reveal misunderstanding before it affects action. It is especially useful for consequential instructions, handoffs, and situations where accuracy matters more than conversational speed.

Boundary spanning

Communication beyond the team

The work of maintaining relationships and exchanging information with people outside a team, such as other departments, customers, suppliers, or senior leaders. It can involve obtaining resources, coordinating interdependent work, or seeking outside expertise. Teams benefit from clarifying who handles these contacts and what information needs to move across the boundary.

Situational strength

Power of contextual cues

The degree to which a situation clearly signals how people are expected to behave and creates incentives for those behaviors. Strong situations encourage similar responses across people, while weak situations leave more room for personal preferences. Strength is not inherently positive: policies and norms can strongly encourage either teamwork or competition.

Team debrief

Structured team learning review

A guided discussion after an event, work period, or project in which members examine what happened, identify what worked and what did not, and agree on adjustments. Effective debriefs include task work and teamwork, invite members to speak before the leader dominates, and conclude with specific actions and follow-up.

FAQ

What’s Teams That Work: The Seven Drivers of Team Effectiveness by Scott Tannenbaum about?

  • Science of Team Effectiveness: The book explores the science behind what makes teams effective, focusing on sustained performance, resilience, and vitality.
  • Seven Key Drivers: It introduces seven drivers—capability, cooperation, coordination, communication, cognition, coaching, and conditions—that consistently influence team success.
  • Practical and Evidence-Based: Drawing on 30 years of research and consulting, Tannenbaum provides actionable, research-backed advice for leaders, members, and consultants.
  • Broad Applicability: The book is designed for anyone involved in teams, from business to healthcare to sports, offering tools to improve teamwork in diverse settings.

Why should I read Teams That Work by Scott Tannenbaum?

  • Teamwork is Essential: Over 90% of employees see teams as critical, but less than 25% rate their teams as very effective, highlighting a widespread need for improvement.
  • Debunks Teamwork Myths: The book dispels common misconceptions, such as the idea that teamwork is a distraction or that liking teammates guarantees success.
  • Actionable Insights: Readers gain practical, evidence-based strategies for building and sustaining effective teams, with real-world examples from organizations like NASA and healthcare.
  • Tailored for Multiple Roles: Advice is relevant for team leaders, members, consultants, and senior leaders, making it broadly useful.

What are the seven drivers of team effectiveness in Teams That Work by Scott Tannenbaum?

  • Capability: The right mix of knowledge, skills, and attributes, including both task and teamwork abilities.
  • Cooperation: Attitudes and beliefs like trust, psychological safety, and cohesion that enable collaboration.
  • Coordination: Teamwork behaviors such as monitoring, backing up, adapting, and managing emotions.
  • Communication: Sharing clear, timely, and unique information, with an emphasis on quality and closed-loop communication.
  • Cognition: Shared mental models and understanding of goals, roles, expertise, and contingencies.
  • Coaching: Leadership behaviors, both formal and shared, that guide and support the team.
  • Conditions: Organizational and environmental factors, such as resources, culture, and policies, that support or hinder teamwork.

What are the key takeaways from Teams That Work by Scott Tannenbaum?

  • Team Effectiveness is Multifaceted: Success depends on a combination of individual capabilities, team dynamics, leadership, and organizational context.
  • Shared Understanding is Crucial: Teams with strong shared cognitions perform better, adapt faster, and coordinate more smoothly.
  • Leadership is Distributed: Effective teams benefit from both formal and shared leadership, with members stepping up as needed.
  • Organizational Support Matters: Policies, resources, and culture at both the organizational and team level significantly impact team effectiveness.

What are the most important myths about teamwork debunked in Teams That Work by Scott Tannenbaum?

  • Teamwork is Not a Distraction: Research shows teamwork boosts performance by 20-25%, contrary to the belief that it wastes time.
  • Liking Teammates Isn’t Essential: Success depends more on clear roles and agreements than on personal harmony.
  • Teamwork Can’t Replace Talent: Competence is necessary; teamwork cannot compensate for significant skill gaps.
  • Teams Aren’t Always the Answer: Not all work requires teams; inappropriate use can lead to inefficiency and frustration.
  • Individual Excellence and Teamwork Coexist: Being a strong individual contributor and a great team player are both valuable.

How does Teams That Work by Scott Tannenbaum define a highly effective team?

  • Sustained Performance: Consistently delivers positive results over time, not just in the short term.
  • Resilience and Vitality: Can overcome challenges and maintain energy and resources, avoiding burnout.
  • Unit Identity: Recognized as a cohesive unit with shared goals and interdependence among members.
  • Adaptability: Able to bounce back from adversity and adjust to changing conditions.

What does Teams That Work by Scott Tannenbaum say about team capabilities and talent?

  • Task and Teamwork Skills: Both technical expertise and teamwork skills like communication and conflict resolution are essential.
  • Balance of Talent: Too many “stars” can harm performance in highly interdependent teams; balance is key.
  • Personal Attributes Matter: Traits like collective orientation, adaptability, and agreeableness enhance teamwork, while toxic traits disrupt it.
  • Team Composition: Leaders should consider the collective mix of skills and gaps before adding or replacing members.

How does Teams That Work by Scott Tannenbaum describe cooperation and its importance?

  • Emergent Attitudes: Cooperation includes trust, psychological safety, collective efficacy, and cohesion, all of which develop over time.
  • Trust and Safety: Trust is built on ability, benevolence, and integrity, while psychological safety allows for open communication and risk-taking.
  • Collective Efficacy: Shared belief in the team’s ability boosts motivation and resilience.
  • Cohesion and Fault Lines: Cohesion unites teams, but leaders must watch for subgroups that can divide the team.

What are the key coordination behaviors in Teams That Work by Scott Tannenbaum?

  • Monitoring and Awareness: Teams must stay aware of each other’s status, performance, and the environment.
  • Providing Backup: Members proactively offer help and support, enabled by shared skills and expectations.
  • Adapting to Change: Teams adjust in real time and reflectively to improve performance and respond to new challenges.
  • Managing Emotions and Conflict: Constructive handling of disagreements fosters innovation and morale, while minimizing harmful conflict.

What communication principles does Teams That Work by Scott Tannenbaum emphasize for effective teamwork?

  • Quality Over Quantity: Effective teams prioritize clear, timely, and unique information sharing.
  • Closed-Loop Communication: Ensures messages are understood and confirmed, reducing errors.
  • Boundary Spanning: Teams must communicate effectively with external stakeholders, not just internally.
  • Overcoming Barriers: Teams should address biases, hierarchy, and challenges from dynamic or dispersed membership.

How do shared cognitions improve team performance according to Teams That Work by Scott Tannenbaum?

  • Shared Mental Models: Teams with common understanding of goals, roles, and contingencies coordinate more smoothly.
  • Motivation and Adaptation: Shared cognitions boost motivation, enable implicit coordination, and allow for rapid adaptation.
  • Eight Types of Shared Understanding: Includes vision, priorities, roles, tasks, rationale, expertise, contingencies, and situational cues.
  • Assessment and Alignment: Leaders should regularly check for alignment in these areas to ensure team readiness.

What leadership approaches and practical advice does Teams That Work by Scott Tannenbaum recommend for team leaders and members?

  • Transformational and Shared Leadership: Leaders should inspire, challenge, and empower, while encouraging members to share leadership roles.
  • Servant and Civil Leadership: Focus on serving team needs, removing obstacles, and maintaining civility to foster psychological safety.
  • Build Capabilities and Safety: Ensure the right talent, promote psychological safety, and maintain shared understanding and quality communication.
  • Debriefs and Advocacy: Use team debriefs for learning and advocate for resources and supportive organizational conditions. Members should proactively support teammates, communicate effectively, and avoid toxic behaviors.

About the Author

Scott Tannenbaum is an organizational psychologist and expert in team effectiveness and leadership development. He is the president of The Group for Organizational Effectiveness (gOE), a consulting firm specializing in team and leadership solutions. Tannenbaum has extensive experience working with diverse organizations, including Fortune 500 companies and government agencies. He has authored numerous scientific articles and book chapters on teamwork, leadership, and organizational behavior. Tannenbaum's research-driven approach and practical insights have made him a respected figure in the field of organizational psychology and team dynamics.

Download PDF

To save this Teams That Work summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.48 MB     Pages: 23

Download EPUB

To read this Teams That Work summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.49 MB     Pages: 30
Want to read the full book?
Follow
Listen
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 24,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...