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
Teaming

Teaming

How Organizations Learn, Innovate, and Compete in the Knowledge Economy
When teams form on the fly, how can leaders make expertise work before coordination breaks down?
by Amy C. Edmondson 2005 352 pages
3.93
500+ ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat teamwork as a practice, not a permanent organizational chart.

Work changes faster than teams. Traditional teams are stable groups whose members learn one another’s roles over time. Edmondson’s term teaming describes the active work of coordinating with people as needs arise, even when membership shifts and there is no time to build familiarity. It depends on noticing interdependence, communicating quickly, and adjusting actions together.

A hospital handoff shows the cost. One patient’s CT scan required several specialists, each completing a task competently. Yet poor coordination stretched less than two hours of direct work across nearly 100 hours. No single worker owned the full process, and departmental boundaries hid how each step affected the next. Teaming means taking responsibility for those connections, not just completing one’s own task.

Analysis

What's striking is that the hospital delay was not primarily a skills problem. It was a design problem: work was divided by specialty, while the patient experienced one continuous process. This is a central lesson of sociotechnical thinking, which studies how people and systems jointly shape outcomes. A useful test for any organization is to trace a customer or patient journey across handoffs. The limitation is that coordination itself consumes time, so it should be concentrated where tasks truly depend on one another, not added as ritual meetings.

Match your management style to how much is known about the work.

One organization can need several modes. The Process Knowledge Spectrum sorts work by how well people understand the steps that produce a desired result. Routine work calls for reliable repetition and incremental improvement. Complex operations mix known procedures with shifting needs and surprises, so they require active problem solving. Innovation work has no dependable recipe yet, making experimentation essential. Large organizations often contain all three at once.

Misdiagnosis is expensive. Telco knew how to deliver conventional phone service, but treated a new DSL launch as if its procedures were already settled. The rollout missed 75 percent of commitments, accumulated 12,000 late orders, and sent customer satisfaction plunging. The problem was not a lack of discipline. Managers applied a routine-production approach to work whose process knowledge was still immature.

Analysis

This framework resembles contingency theory: effective management depends on the task and environment, rather than on a single universally superior style. Its practical value lies in forcing a diagnosis before choosing metrics, controls, or incentives. A caveat is that work can shift categories within one project. A new product may contain routine manufacturing alongside uncertain customer adoption. Managers therefore need to classify the specific work, not label an entire company as either efficient or innovative.

Make it safer to raise a concern than to stay quiet.

Silence has operational consequences. Psychological safety is the shared belief that asking questions, admitting mistakes, or offering concerns will not bring humiliation or punishment. It is not the same as comfort or agreement. During the Columbia shuttle mission, engineer Rodney Rocha worried that launch debris might have damaged a wing, but hierarchy and earlier discouragement made escalation difficult. The concern was not fully pursued, and the shuttle was lost on reentry with all seven astronauts aboard.

Safety needs standards beside it. Edmondson distinguishes a climate that welcomes speaking up from one that lowers expectations. When people can report problems and are still held to clear standards, teams can detect risks without treating every mistake as misconduct. In one cited study, more than 85 percent of interviewed employees and managers described occasions when they had withheld a concern.

Analysis

Psychological safety can be understood as infrastructure for error detection. In aviation and medicine, weak signals matter because a small anomaly may be the only early clue to a larger hazard. Leaders shape whether such signals travel by asking for dissent, acknowledging uncertainty, and responding constructively when someone speaks. Still, encouraging voice alone cannot guarantee sound decisions. Reports need clear channels, timely investigation, and the authority to act, or openness becomes another slogan layered over unchanged systems.

Frame uncertain projects as shared learning, not expert performance.

People take their cues from leaders. A learning frame presents a project as an uncertain challenge that requires everyone’s knowledge. An execution frame implies that the task is familiar and success means following the expert’s lead. In a study of 16 hospitals adopting minimally invasive cardiac surgery, two succeeded and two abandoned the effort among the four cases examined in detail. Resources, seniority, and prior innovation did not explain the difference as well as how leaders framed the work.

Status could either narrow or widen input. Successful surgeons acknowledged their dependence on nurses and other specialists, treated them as contributors, and connected the work to patient benefit. In less successful cases, staff were treated as support workers and the change as a competitive necessity. The learning process included selecting participants, preparing together, trying the procedure, and discussing what the attempts revealed.

Analysis

Framing is not merely motivational language. It distributes permission: who may notice, question, and influence the work. The cardiac surgery cases make that concrete because a surgeon’s expertise remained vital, but could not substitute for the observations of colleagues managing equipment and information. In organizational change, a compelling purpose can help people endure uncertainty. Yet purpose must remain honest. If leaders oversell benefits or conceal risks, an aspirational frame can become pressure to comply rather than an invitation to learn.

Diagnose failure before deciding whether to prevent it or learn from it.

Failure is not one thing. In predictable operations, preventable failures usually signal a process, skill, or support problem and should be reduced. In complex operations, failures can emerge from interacting conditions that no one could fully anticipate, so early detection and containment matter. In innovation, an unsuccessful but carefully designed test may be an intelligent failure because it produces useful information.

The response must fit the cause. Toyota’s assembly workers can pull an Andon Cord when they spot a production problem, prompting a rapid investigation and sometimes stopping the line. By contrast, drug development may involve failure rates above 90 percent because most candidates do not survive testing. Treating both settings as if every failure were a preventable error confuses learning with blame and discourages useful experiments.

Analysis

This taxonomy adds an important distinction to the familiar advice to learn from mistakes: the same response is not appropriate for every mistake. Safety engineering makes a similar distinction between individual violations and system conditions that shape behavior. Leaders can ask whether the process was known, whether the event arose from interacting factors, or whether the trial was designed to test uncertainty. The difficult part is resisting convenient labels. Calling an avoidable lapse an experiment excuses it, while calling a thoughtful test incompetence wastes its learning.

Make boundaries visible before they become coordination failures.

Expertise creates walls as well as value. Boundaries divide people by location, status, profession, or organization. They are often reinforced by unspoken assumptions: two groups may use the same words but mean different things, or overlook information known only to one member. Useful ways to cross them include setting a shared goal, asking curious questions, and agreeing on how work will connect across groups.

Chile’s mine rescue required all three. Thirty-three miners were trapped underground for 70 days. Miners organized survival below ground, technical teams tested different drilling approaches above ground, and government leaders secured outside expertise and resources. Short test-and-review cycles helped teams abandon bad options and use new information. The rescue depended not on one all-knowing team, but on distinct groups coordinating their work across physical, professional, and national boundaries.

Analysis

The rescue illustrates a network form of problem solving: specialized groups can work in parallel, provided their findings and needs connect at the right moments. This is different from simply assembling diverse people in one room. Boundary-spanning tools, such as shared diagrams, prototypes, or agreed handoff procedures, give groups something concrete to coordinate around. Diversity is not automatically an advantage, however. Without time to surface assumptions and resolve status differences, it can increase misunderstanding as readily as insight.

Build learning into delivery through small tests and frequent reflection.

Learning belongs inside the work. Execution-as-learning means delivering a product or service while also improving how it is delivered. Instead of separating action from a distant postmortem, teams repeatedly assess the situation, choose a next step, try it, and examine what happened. The cycle should match the work: a factory may analyze recurring measures, while an innovation team may learn from a prototype or a single trial.

The Motorola RAZR shows experimentation in practice. Its team explored competing design and engineering needs, built and tested options, and discovered that placing the battery beside the circuit board could make the phone thinner. The product went on to sell 50 million units in its first two years and 110 million over four years. The route included a missed initial deadline, but the team kept learning while producing.

Analysis

This approach turns feedback into a working resource rather than a verdict delivered after the fact. It also fits the logic of iterative design: cheap, early tests can expose constraints before they become expensive commitments. Reflection need not mean a long meeting; brief, timely observations may be more useful when conditions change quickly. The risk is endless iteration without a stopping rule. Teams need measures of progress and a clear sense of when the evidence is sufficient to standardize a process or move on.

Give routine workers ownership of measurable improvements.

Simmons paired trust with a concrete target. When Charlie Eitel became CEO of the struggling mattress manufacturer, he invested in team development instead of relying only on restructuring or cost cuts. The company focused employees on reducing waste, a goal that workers across different jobs could understand and measure. A pilot at a poorly performing plant improved quickly, helping build support for wider adoption.

The results followed the operating context. In the first year, the company recorded $21 million in measurable cost reductions while sales and revenue grew. A new incentive program tied 25 percent of weekly compensation to plant-wide quality and productivity, making employees’ outcomes more interdependent. The company used training, visible goals, and skill development to help teams improve a process that was already understood, rather than asking them to invent a new one.

Analysis

Simmons demonstrates that empowerment is not the opposite of performance management. Employees received a clear target, practical support, and a reason to help one another, while retaining room to decide how to improve the work. This combination is especially suited to routine operations, where stable measures can show whether changes help. The case also raises an implementation question: incentives tied to group results can encourage cooperation, but they need safeguards against unfairness when workers have unequal control over the outcome.

Treat patient-safety mistakes as system evidence, not a hunt for culprits.

A near miss can reveal a chain of weaknesses. At Children’s Hospital, a young patient nearly died after receiving too much morphine. Several factors contributed: the medication label hid important information, staff lacked experience with the pump, and unit capacity pressures shaped where the patient received care. Focusing on one person would have missed how the conditions combined.

Julie Morath made reporting part of the work. As COO, she brought clinicians and managers together, invited them to examine their own experiences, and introduced confidential or anonymous reporting. Cross-functional reviews examined how events unfolded and what might prevent recurrence. Front-line staff created Safety Action Teams and a Good Catch Log to surface hazards and track whether reports led to changes. The aim was not immunity from accountability, but better understanding of how the care system operated.

Analysis

This case is a practical example of systems thinking: outcomes can arise from interactions among people, tools, labels, staffing, and policy. A blame-first review narrows attention to the last visible action, while a learning review searches the entire pathway. That broader view is valuable, but it should not erase individual responsibility for reckless conduct. A just process distinguishes human error, risky shortcuts, and deliberate violations, then responds proportionately so that both candor and patient protection remain credible.

Innovation stalls when designers ignore the client's ability to implement.

A clever idea is not yet an adopted idea. IDEO’s early Phase Zero work helped clients discover new product opportunities. In a Simmons project, the team identified mobile young adults who needed bedding suited to frequent moves and small homes. The research and concepts were promising, but Simmons did not act on them. IDEO had studied end users without sufficiently learning how the client organization made decisions and turned proposals into products.

The firm changed its own teaming. Later Phase Zero projects involved clients more directly and added expertise in business systems and organizational constraints. This expanded the work beyond generating designs to helping ideas travel through the client’s organization. Phase Zero eventually contributed 30 percent or more of IDEO’s revenue. The lesson is specific: innovation requires understanding both the people who will use a product and the organization that must make it real.

Analysis

This is a useful corrective to the myth that creativity ends when a strong concept appears. Implementation is a social and organizational process, shaped by budgets, incentives, authority, and operational capacity. Including clients earlier can expose these constraints while ideas are still flexible. At the same time, client involvement can domesticate ambitious concepts if decision-makers reject unfamiliar possibilities too quickly. Effective collaboration therefore needs both contextual understanding and enough protected space to challenge current assumptions.

Analysis

The book’s central argument is that organizations cannot rely on stable teams and prewritten procedures when work is uncertain, interdependent, and changing. Its alternative is not an anti-management celebration of improvisation. It is a more demanding form of management: leaders set direction, make speaking up safer, distinguish useful experiments from preventable breakdowns, and build routines for learning while work continues.

The Process Knowledge Spectrum is the book’s organizing instrument. It prevents a common category error: applying factory controls to exploratory work, or treating predictable processes as though every mistake were a novel discovery. The strongest examples expose the costs of this mismatch. Telco’s new service was managed with the precision of a mature operation before the service process was understood. Conversely, Simmons used measurable targets and standardized skill development because mattress production already had a workable process to improve.

The argument also makes collaboration concrete. The CT scan delay, Columbia concerns, and children’s hospital medication incident show that outcomes emerge across handoffs and status differences. Psychological safety matters because information is distributed, while fear makes people withhold it. Yet safety is not a substitute for accountability. The book is most persuasive when it presents both as complementary conditions: candor is necessary to detect problems, and clear standards are necessary to respond fairly.

The evidence is unusually grounded in organizational settings, with case studies that reveal mechanisms leaders can recognize and act upon. These cases are persuasive illustrations, though they do not establish that the same intervention will work identically everywhere. The broader contribution is a diagnostic habit: ask what is known, where uncertainty sits, who holds missing information, and how the organization will learn from action. In that view, teaming is not a morale program or a meeting format. It is the practical infrastructure that lets expertise become collective performance.

Summary in 30 Seconds
Management should fit the work: repeatable processes benefit from consistent routines, while uncertain projects need experiments and rapid adjustment. Teams that span shifting roles and departments need clear shared goals, active coordination, and conditions where people can raise concerns without fear. More than 85 percent of surveyed employees and managers had withheld concerns. Failures in predictable work call for prevention, while well-designed experiments can produce valuable knowledge even when they do not succeed.
Contains spoilers

Last updated:

Report Issue

Review Summary

3.93 out of 5
Average of 500+ ratings from Goodreads and Amazon.

Teaming receives mixed reviews, with an average rating of 3.93/5. Readers appreciate its insights on effective teamwork, psychological safety, and learning from failure. Many find it valuable for leaders and managers. However, some criticize it as repetitive, academic in tone, and lacking practical application. Positive reviews highlight the book's research-based approach and relevance to modern organizations. Negative reviews mention redundancy and difficulty in reading. Overall, readers find the core concepts useful but opinions vary on the book's execution and readability.

Your rating:
4.42
158 ratings
Want to read the full book?

Glossary

Teaming

Flexible collaborative work

Teaming is the active process of coordinating and collaborating with others, often across shifting or temporary groups. Unlike a fixed team, it does not depend on stable membership or extensive time to build familiarity. People recognize interdependence, exchange knowledge, adjust their actions, and make decisions together so work can proceed and improve.

Organizing to learn

Leadership for collective learning

Organizing to learn is a leadership approach that encourages people to share information, ask questions, experiment, discuss mistakes, and use feedback. It is especially important when the path to a result is uncertain or still developing. Leaders provide direction and support collective inquiry rather than relying only on fixed procedures and compliance.

Execution-as-learning

Learning during delivery

Execution-as-learning is an operating approach that combines ongoing delivery with continual improvement. Teams use action and reflection to adjust how work is done instead of separating execution from learning. The process is adapted to the work: refining established routines, solving problems in complex operations, or testing possibilities in innovation.

Process Knowledge Spectrum

Maturity of process knowledge

The Process Knowledge Spectrum classifies work by how much is known about the process needed to achieve a desired result. At one end, routine operations rely on mature procedures. Complex operations combine established methods with unpredictable events. Innovation operations pursue results for which reliable processes have not yet been discovered.

Psychological safety

Safety for interpersonal risks

Psychological safety is a shared belief that people can raise relevant questions, concerns, ideas, or mistakes without being humiliated or unfairly punished. It supports learning and coordination in work that depends on open communication. It does not mean avoiding conflict, lowering performance standards, or excusing deliberate misconduct.

Intelligent failures

Informative unsuccessful experiments

Intelligent failures are unsuccessful outcomes from thoughtful experiments in areas where knowledge is limited. They can provide useful information about what does not work and what should be tried next. They differ from preventable failures in predictable processes and from complex failures caused by interacting conditions in uncertain systems.

Boundary objects

Shared tangible reference points

Boundary objects are tangible representations, such as drawings, prototypes, models, or components, that people from different specialties can use to discuss and coordinate their work. They help teams make differences in knowledge visible, reduce misunderstandings caused by jargon, and develop a shared understanding without requiring everyone to have the same expertise.

Learning frame

A project as shared discovery

A learning frame interprets uncertain work as a shared opportunity to discover what will work, rather than as a test of whether people can execute a known procedure perfectly. It presents leaders as interdependent with colleagues, makes team members’ contributions consequential, and connects the effort to a meaningful purpose.

About the Author

Amy C. Edmondson is a prominent figure in leadership and management studies. As the Novartis Professor of Leadership and Management at Harvard Business School, she brings extensive expertise to her teaching and research. Edmondson's work focuses on crucial aspects of organizational behavior, including leadership, teamwork, and learning. Her courses in the MBA and Executive Education programs cover leadership, organizational learning, and operations management. Edmondson's position at one of the world's most prestigious business schools underscores her influence in shaping future business leaders and contributing to management theory and practice.

Download PDF

To save this Teaming summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.35 MB     Pages: 17

Download EPUB

To read this Teaming 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.39 MB     Pages: 20
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...