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
Leading Teams

Leading Teams

Setting the Stage for Great Performances
Better team performance starts before the work begins. Find the conditions that make it more likely.
by J. Richard Hackman 2002 336 pages
3.92
400 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Build the conditions for performance instead of managing every move

Two airlines, two failures. One airline tightly scripted cabin service, delivering predictable quality but leaving little room for initiative. Another gave flight attendants broad discretion, enabling ingenious service but also allowing misconduct to go unnoticed for months. The contrast points to Hackman’s central argument: leaders cannot make teams perform well by directing every action. They can create conditions that make strong performance more likely.

Judge the whole result. An effective team produces work acceptable to its clients, grows more capable through working together, and gives members more learning and fulfillment than frustration. A team that serves customers brilliantly by exhausting its members, or enjoys itself while disappointing clients, is not fully effective. All three measures matter.

Analysis

What's striking is that the airline contrast is not a simple argument for more freedom. Control can protect consistency while suppressing judgment; autonomy can unlock judgment while creating risks of drift or self-interest. The useful question is therefore not whether a team should be trusted, but what the work system makes easy, visible, and accountable. The three-part definition of effectiveness also prevents organizations from mistaking a single impressive metric, such as customer satisfaction or output volume, for durable team success.

Call it a team only when members own interdependent work

Names do not create teams. Hackman calls a group a real team when members share a task that requires collaboration, know who belongs, have clear authority over their work, and remain together long enough to develop as a unit. A group of telephone operators once labeled a supervisor’s team actually performed separate individual jobs. Their only shared feature was their boss.

Give the team actual work. A financial institution’s task force repeatedly revisited settled ideas because attendance and membership kept changing. It never developed a shared working identity, and its leader ultimately wrote the proposal alone. Leaders should not use team language while assigning individual tasks and supervising each person separately. Some work, such as creative writing, may be better performed by one person than by a committee.

Analysis

The distinction between a team and a group of coworkers is a practical test of organizational honesty. Collective accountability without genuinely interdependent work can make people answerable for outcomes they cannot influence. Conversely, calling a set of individual contributors a team may obscure who owns decisions and who can help when work goes wrong. The test also guards against team enthusiasm becoming a default ideology. If a task does not benefit from joint work, an individual assignment may be the more respectful and effective design.

Set an ambitious destination, then let the team choose its route

Specify the end, not the recipe. Strong direction is clear enough to focus effort, challenging enough to energize people, and consequential enough to draw on their abilities. David Mathiasen, who led economic analysts at the Office of Management and Budget, united staff with opposing political views around the purpose of giving public officials complete, trustworthy analysis. He defined what good work meant without dictating every analytic method.

Leave room for judgment. A goal that is vague cannot guide choices, but a fully specified target can invite narrow optimization or distortion. Hackman recommends clear purposes with latitude over methods, plus explicit limits where safety or ethics require them. A useful challenge is difficult but credible for the team, not so easy that it is dull or so extreme that effort seems pointless.

Analysis

This balance resembles the difference between setting a destination and scripting every turn. Clear ends let members coordinate and evaluate choices, while discretion over means preserves local knowledge that distant planners may lack. Yet autonomy is not automatically empowering: without enough information, expertise, or authority, it can become abandonment. The strongest direction therefore defines both the result that matters and the boundaries that cannot be crossed, while leaving room for members to make the route their own.

Give teams whole work, real autonomy, and feedback they can use

Design work that matters. Teams are more motivated when they can complete a meaningful piece of work, make decisions about how to do it, and see reliable results. At Butler Manufacturing, teams built entire grain dryers, moved among different production tasks, tested their products, and sometimes visited farmers who used them. Members could connect their daily work to a functioning product and to the customer’s needs. The plant reported better quality and profits roughly 10 percent above comparable operations.

Autonomy has a cost. When individual effort disappears inside a large group, social loafing can reduce contribution. When procedures are dictated in detail, initiative and adaptation are lost. Good design gives a team substantial control over its work, keeps accountability visible, and provides feedback that members can use to improve together.

Analysis

The grain-dryer example shows why task design can motivate without relying entirely on speeches or incentives: people can see the product, understand its use, and learn from its consequences. It also makes customer contact part of the feedback loop rather than a distant survey result. Still, whole-task design is not feasible for every kind of work, and autonomy without clear accountability can hide free riding. The aim is not maximal discretion, but a meaningful range of choices tied to outcomes the team can actually affect.

Keep capable teammates together long enough to learn one another

Familiarity improves coordination. In an analysis of aviation incidents, 73 percent occurred on a crew’s first day flying together, and 44 percent of those happened on its first flight. In a NASA simulator study, crews who had just completed several days of flying made fewer team errors than rested crews who had not yet worked together. Experience together can build shared expectations, knowledge of who knows what, and smoother coordination.

Stability creates memory. Members become one another’s reminders and resources, a process called transactive memory. Training people together can accelerate this learning, but it pays off only if the team stays intact. Stability is not an absolute rule: research and development groups may benefit from new perspectives after a few years. For most teams, leaders should weigh the costs of stable staffing against the hidden costs of constant rebuilding.

Analysis

Team continuity is an operational resource, not simply a perk for people who enjoy familiar colleagues. It lets members anticipate one another and coordinate without turning every interaction into a fresh negotiation. The aviation evidence makes that value unusually visible because small coordination failures can have serious consequences. Stability can also preserve outdated assumptions, so it should not become a ban on renewal. The relevant distinction is between deliberate changes that add needed knowledge and routine turnover that repeatedly destroys accumulated team learning.

Make teams scan the environment and respect clear operating limits

Look outward before acting. Teams often fall into familiar routines and react only to whatever demands attention. Hackman argues that their basic norms should instead encourage members to monitor changing conditions and adjust their work strategy, while also making clear what they must always do and must never do.

The flight is not the same each time. A domestic airline crew noticed that one flight carried vacationing families and adapted its service to be playful. On a delayed, crowded flight full of business travelers, the same crew worked quickly and kept conversation brief. In both cases, members followed required safety procedures and did not give away liquor. Their outward focus helped them adapt without losing sight of organizational limits.

Analysis

The contrast between the two flights shows that consistency need not mean identical behavior. A team can maintain stable standards while changing how it meets them in response to the people and conditions in front of it. That is a more demanding form of reliability than rote compliance because it requires both attention and judgment. The boundary rules matter for the same reason: adaptation is valuable only when members understand which constraints are genuinely nonnegotiable, rather than treating every instruction as equally rigid.

Keep teams small, varied, and skilled enough to use their differences

More people mean more coordination. In a study of groups from two to seven members, the researchers’ estimates of ideal size crossed at 4.6. Hackman uses six as a practical upper limit for student project teams. Larger groups bring more possible knowledge, but coordination demands and the chance that members will fade into the crowd also rise.

Avoid comfort-driven sameness. Similar members may find it easy to get along, but a team can lack perspectives and capabilities it needs. Diverse skills and viewpoints can improve decisions when members can work through task disagreements constructively. Teams also need adequate interpersonal skills. Before labeling someone disruptive, leaders should ask whether the group’s design is flawed or whether that person is raising a perspective the rest of the team has excluded.

Analysis

Small size is not a magic number; the task determines how many people are necessary. The deeper lesson is to treat membership as a design decision, not a stakeholder census or popularity contest. Difference is useful only when a team can hear and apply it, and smooth interaction is not proof that a team has the right mix. The caution about scapegoating is equally important: a person who seems difficult may expose a missing perspective, although genuine interpersonal problems can still require direct attention.

Align rewards, information, and training with the work teams own

Support must reach the work. Teams need rewards that recognize collective results, timely information about their task and constraints, training or technical help to fill skill gaps, and the material resources to do the job. At a semiconductor plant, manager Hank secured permission to reward strong teams and arranged closer technical support from maintenance staff. He used personal relationships and persistence because standard channels were not getting his teams what they needed.

Make contribution visible. Rewards work best when teams value them and can see how their actions affect the result. A distant company-wide bonus may feel unrelated to a team’s daily effort. Information can also be too scarce, inaccessible, or overwhelming. The goal is not to distribute every possible datum, but to make useful, trustworthy information and assistance available in a form teams can act on.

Analysis

These supports are often treated as administrative details, yet they determine whether a team can convert its effort into results. A reward that members cannot connect to their contribution is weak motivation; data that arrive in an unusable format are functionally absent. The same applies to training: assigning broader responsibility without supplying the required expertise is not empowerment. The harder organizational question is whether support departments see frontline teams as legitimate users of their services, rather than as interruptions to their own priorities.

Coach at launch, midpoint, and finish, not through constant interference

Match coaching to the moment. At a team’s start, members are especially receptive to help building commitment and a shared understanding of their task. Around the midpoint of a project, they have enough experience to examine whether their strategy is working. At the end, they can learn from results. Research by Connie Gersick found that teams often maintain an initial approach until close to the midpoint, then make a concentrated transition.

Coach the work, not just the mood. Hackman focuses on effort, task strategy, and the use of member expertise. A coach can encourage commitment, help members rethink an ineffective plan, or help them learn from performance. Constantly stepping in to manage the work can weaken a team’s ability to manage itself. Good coaching depends on timing and on a sound team design; it cannot repair a fundamentally broken assignment or context.

Analysis

The timing principle offers a useful alternative to the idea that coaching means continuous supervision. A team needs different help when it is forming, when its first plan meets reality, and when it can finally reflect without the task pressing on every minute. The approach also treats process conflict carefully: disagreement about how to do the work may reveal a better strategy, even when it feels uncomfortable. But timing alone is not enough. A coach must distinguish useful tension from breakdown and avoid turning reflection into another ritual with no effect on work.

Change the surrounding system, not just the team label

Teamwork changes who holds power. Effective teams may require new answers to who decides, who is accountable, who receives rewards, and who gets opportunities to learn. People Express Airlines grew rapidly with self-managing teams, but its leaders resisted adding structures and systems as the company expanded. Vision and coaching could not replace the supports its teams needed. In contrast, Hank’s successful team redesign eventually threatened established interests, and he lost his job.

Prepare, then act when change is possible. Hackman describes organizational change as difficult during stable periods and more possible when disruption opens a window. Leaders need to develop the knowledge, plans, and relationships to use that opening. Leadership is not a fixed personality style: anyone who helps create effective conditions can lead, but doing so may require persistence, political skill, and courage.

Analysis

The two cases make clear that team design is not a neutral technical adjustment. It redistributes authority, responsibility, recognition, and access to learning, so resistance may reflect threatened interests as much as doubts about performance. Waiting for an opening can preserve a coherent change effort, but it can also delay needed action; the timing judgment is consequential. The lesson is to treat implementation as organizational work in its own right, not as a rollout followed by a motivational speech.

Analysis

Hackman’s central contribution is to shift attention from the leader’s personality to the conditions surrounding collective work. That move is powerful because it makes team performance diagnosable: before blaming communication or motivation, ask whether the group has a genuine shared task, clear boundaries, legitimate authority, a useful direction, a workable structure, and organizational support. The model also resists a common management shortcut, treating a team as a label or a training intervention rather than a redesigned unit of work.

The framework’s strength is its integrated view of performance. Teams are judged not only by their output, but by whether they become more capable and whether members benefit from participating. This makes the model harder to game with a single metric. Its account of autonomy is similarly balanced: discretion creates room for adaptation, but requires boundaries, useful information, expertise, and accountability. That is a more realistic prescription than either centralized control or unqualified empowerment.

The book is careful to say that enabling conditions increase probabilities rather than guarantee results. That qualification matters. A team can be well designed and still be defeated by external events, internal choices, or circumstances that leaders cannot control. The framework is also strongest when work is genuinely interdependent. Organizations can misuse it by forcing individual tasks into teams, or by interpreting every problem as a design flaw and neglecting direct interpersonal repair when it is needed.

The book’s deeper implication is political: teams cannot flourish through local enthusiasm alone. Reward systems, information access, technical support, and decision rights are controlled by people and units with their own priorities. Leaders therefore need both analytical judgment and influence skills. The model is not a recipe for producing team magic on command. It is a way to make capable performance less dependent on luck, charisma, and heroic last-minute effort.

Summary in 30 Seconds
Effective teams deliver work clients value, grow more capable together, and support members’ learning and fulfillment. A real team needs interdependent work, clear membership, authority, and time together. Give it a meaningful task, a clear destination, decision-making latitude, useful feedback, and support. In aviation data, 73 percent of incidents occurred on a crew’s first day together. Groups of about five balance skills with coordination demands. Coaching is most useful at launch, midpoint, and finish.
Contains spoilers

Last updated:

Report Issue
Want to read the full book?

Glossary

Real team

Interdependent, bounded work group

A real team has a shared task that requires members to work together, clear membership boundaries, specified authority over its work, and sufficient membership stability to develop as a unit. The term distinguishes an actual performing group from people who share a supervisor or workplace but carry out separate individual tasks.

Co-acting groups

People doing separate jobs

Co-acting groups consist of people who may work near one another or report to the same manager, but whose tasks do not depend on one another. They may be called teams, yet members are individually responsible for separate outputs rather than jointly accountable for a shared product or service.

Compelling direction

Clear, challenging purpose

A compelling direction defines a team’s important objectives in a way that is clear enough to guide choices, challenging enough to motivate effort, and consequential enough to engage members’ abilities. It specifies the ends the team should achieve while generally leaving members room to choose the means.

Enabling structure

Design that supports teamwork

An enabling structure makes competent teamwork easier through the design of the task, the team’s core norms, and its composition. It gives members meaningful work, appropriate autonomy and feedback, norms that support active attention to task conditions, and a group size and mix suited to the work.

Supportive context

Organizational help for teams

A supportive context gives teams the organizational resources needed to perform. Hackman emphasizes reward systems that recognize team results, information systems that provide useful and timely data, educational systems that supply training and technical assistance, and access to material resources.

Team coaching

Help improving group processes

Team coaching is interaction intended to help members use their shared resources more effectively. It can strengthen collective effort, improve the fit between work strategies and task demands, or develop members’ knowledge and skills. Its value depends on addressing the team’s work and arriving when members can use the intervention.

Process losses

Inefficiencies within teamwork

Process losses are reductions in a team’s actual performance caused by the way members work together. They can include social loafing, poor coordination, habitual strategies that no longer fit the task, or failure to use members’ expertise. Such losses mean the team produces less than its resources could support.

Process gains

Benefits created through teamwork

Process gains occur when interaction creates resources or capabilities that individual members did not possess separately. Examples include stronger shared commitment, an innovative task strategy, and learning that expands the team’s collective knowledge and skill. Gains can help a team outperform what would be expected from simply adding up individual contributions.

Transactive memory

Knowing who knows what

Transactive memory is a team’s shared knowledge of where expertise resides among its members. People become resources for one another’s recollection and problem solving, so the team can draw on a wider pool of knowledge than any individual holds alone. Familiarity and repeated work together help this system develop.

Team shell

Team’s initial design framework

The team shell is the basic structure in place before members begin working together. It includes the task, expectations for conduct, and membership design that shape how the group can operate. The shell provides a starting framework, but members bring it to life through their first interactions and subsequent work.

Leader attribution error

Overcrediting leaders for results

The leader attribution error is the tendency to explain a team’s success or failure mainly through its leader’s personality or behavior. This can hide the effects of task design, team composition, authority, resources, or organizational conditions, and can cause observers to blame or praise one person for outcomes produced collectively.

Punctuated equilibrium

Long stability, abrupt change

Punctuated equilibrium describes a pattern in which a system remains relatively stable for an extended period, then changes rapidly during a shorter period of disruption or transition. Hackman applies the idea to organizational change: leaders may find it difficult to alter established structures during calm periods, while moments of turbulence can create openings.

Download PDF

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

Download EPUB

To read this Leading Teams 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.37 MB     Pages: 20
Want to read the full book?
Follow
Listen2 mins
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...