Leading Teams

1. 1Design the team's task around the three states that produce collective internal motivation: make the work meaningful, give the team genuine responsibility for work procedures, and build trustworthy feedback directly into the work so members can tell how well they are doing without waiting for a supervisor's verdict.
2. 2Stop trying to raise effort by fixing individuals. Instead set up and support the group itself, because a healthy group promotes competent member behavior while a sick group invites bizarre behavior. Redirect any effort you were spending on personality/style interventions into structural design.
3. 3Give the team latitude to make real decisions about how the work gets done, not just what to do. The domestic airline CSM teams held responsibility for 'complete, clean, communicate' and decided themselves whether that meant doing extra work, persuading others, or lending a hand outside their formal role.
4. 4Check whether the organization is actually asking the team for its full effort. At the international airline, competent people had 'much more to offer than the company asked them—nay, allowed them—to give,' and the work drifted into 'just a job.' Widen the mandate so extra ingenuity has somewhere to go.
5. 5Lead the team as both leader and follower at once: convey direction from above with conviction rather than perfunctorily relaying it ('give our best effort' delivered flatly kills commitment), and do not stage a covert coup by ignoring legitimate direction. Both extremes drain collective effort.
6. 6Build in periodic review of how the team has been operating so members milk experience for learning, catch and correct errors early, and notice emerging opportunities. This turns effort into a growing capability rather than a repeated struggle.

Vic's international flight hit an emergency landing. When it mattered, the cabin crew 'immediately got themselves organized, started making calls and negotiating with local innkeepers, and within a couple of hours they had arranged meals and lodging for everyone on board.' That is process gain: high shared commitment converting a crisis into coordinated action. But when the author asked how the service had been *before* the emergency, Vic could only recall it as 'routine. Nothing really memorable.' The same talented crew, on ordinary days, gave only competent effort because the airline's engineering approach asked little thinking, planning, or team decision making of them. The contrast shows collective effort is not a fixed trait of the people; it rose when the task suddenly demanded and permitted their full ingenuity and collapsed to baseline when routine design removed meaning, responsibility, and challenge.

• If members experience the work as 'just a job' despite being talented and non-alienated, then the design—not the people—is capping effort; widen the mandate and raise the challenge.
• If you're tempted to fix effort through a personality or communication workshop, then stop and instead ask what structural condition of the group is inviting the poor behavior.
• If the task is trivial, gives the team no procedural latitude, or provides no direct feedback, then internal motivation will disappear—restore whichever of the three is missing before expecting more effort.
• If you catch yourself relaying direction from above perfunctorily ('their job is to tell us, our job is to do it'), then you are abdicating; reframe the direction so the team can commit to it.
• If the team only performs well under dramatic pressure but coasts in routine conditions, then the everyday work is under-designed—engineer meaning and responsibility into the normal task, not just the emergency.

• Blaming or crediting single individuals ('Whose fault was it?', crediting the 'star'). The tell: post-mortems that name a person rather than examine how the group was set up and supported.
• Treating effort as an individual-attitude problem and running style/awareness interventions. The tell: hope that coordination will 'come about more or less automatically' once each member understands their personal style—an assumption with no supporting evidence.
• Under-asking the team so competent talent goes unused. The tell: descriptions of the work as 'routine, nothing really memorable' and people who arrived rich with talent now treating it as 'just a job.'
• The covert coup—leader lets the team do what it wants because higher-ups 'won't find out.' The tell: rationalizing that headquarters has 'zero comprehension' so their instructions can be discounted.
• Abdication—leader relays new direction flatly and undermines it. The tell: language like 'I don't think this makes a whole lot of sense... but it's what they want,' delivered as mail delivery rather than leadership.

• ▸Meaningfulness: What makes this team's whole task matter, and to whom?
• ▸Felt responsibility: Which work procedures does the team actually decide, versus have imposed?
• ▸Knowledge of results: What direct, trustworthy feedback reaches the team without a supervisor's judgment?
• ▸Effort baseline: On a routine day (not a crisis), what does the team's effort look like?
• ▸Under-ask gap: What could this team offer that the organization currently doesn't ask for or allow?
• ▸Individualizing pull: Where are we tempted to fix a person instead of the group's setup?
• ▸Leader-follower stance: How am I conveying direction from above—with conviction, as a coup, or as flat relay?
• ▸Review rhythm: When and how does the team examine its own operating process for learning?
• ▸Trade-off note: How does raising effort here affect client output, team capability, and member well-being?

1. 1Feed the team live information about task requirements and client expectations before it commits to a method — access to the president's policy agenda and bill status let OMB analysts pick strategies that mattered. Without this, the team flies blind and may adopt a way of proceeding that seems reasonable but is grossly inappropriate on execution.
2. 2When a member proposes a new or altered method, force an explicit feasibility-and-appropriateness discussion before implementing. Listen for the phrases that anchor judgment to reality — 'the people down the line need a continuous flow' or 'it's extremely important our documentation be perfect' — because those name the actual constraint the strategy must satisfy.
3. 3Test any candidate strategy against the standards the client will actually use to assess the work, not against what feels efficient internally. OMB teams minimized wasted effort precisely because they knew the assessment criteria in advance.
4. 4Build in real-time fine-tuning: schedule contact points (the Xerox CST morning breakfast meeting, telephone check-ins through the day) so the team can revise the plan in response to unanticipated problems or opportunities rather than executing a fixed routine mindlessly.
5. 5Coach the strategy process — ask reflective questions about why members made a particular decision so they use their knowledge better — but do not confuse coaching with doing the work; personally coordinating or negotiating outside resources is help, not strategy-building.
6. 6Watch for habitual routines hardening into defaults. When predictability becomes valued for its own sake, invite members to invent task-appropriate procedures and grant explicit discretion to vary normal duties when doing so serves the goal.
7. 7Capture what members learn each cycle — have each person note problems encountered and lessons learned for the next meeting — so strategy improves across cycles and creates process gains rather than repeating losses.

A Xerox customer service team responsible for a set of machines in one geographical area starts each day with a breakfast meeting to plan the day's work. As the day progresses they stay in frequent telephone contact to see how things are going and to fine-tune the strategy in response to unanticipated problems. When one member gets stuck on a hard job that may need expensive replacement parts, the member with the most experience on that machine type heads off to assist, and the team leader confers with others about revising the work plans to accommodate the development. Each member notes problems and lessons for the next morning's meeting. The result is a strategy continuously matched to actual conditions — fixing machines efficiently, inexpensively, and well — rather than a fixed routine applied blindly, and the team stands high on the effectiveness criteria.

• If the team lacks information about task requirements and client expectations, then delay strategy selection and supply that information first — otherwise its plan is driven by chance.
• If a proposed method cannot be tied to a named downstream constraint ('the people down the line need...') or a client standard, then treat it as untested and require the appropriateness discussion before adopting it.
• If unanticipated problems or opportunities arise mid-cycle, then convene to revise the plan rather than pushing the original routine through.
• If members default to a well-established routine because predictability is comfortable, then intervene to grant discretion and prompt invention of a task-appropriate procedure.
• If the basic enabling conditions (real team, direction, structure, context) are badly flawed, then fix those first — no amount of strategy coaching compensates.

• Mindless reliance on habitual routines: the tell is that exhortation to change (the international carrier's new directives) produces no actual change on the job because the rhythm of standard routines is too strong.
• Formulating strategy by guessing at what clients want: the tell is wasted effort and work that fails the client's actual assessment standards because the team never obtained the requirements.
• A method that seems reasonable to members but is grossly inappropriate on execution: the tell surfaces only downstream — e.g., generating output in irregular batches when the people down the line need a continuous flow.
• Confusing leader action with coaching: the tell is a leader personally coordinating work or negotiating outside resources while member strategy skills never develop.
• Underutilizing members' intelligence, initiative, and ingenuity: the tell is a heavily engineered, over-specified process that leaves members no room to invent — the same crew capable of improvising hotels during an engine-fire diversion never varies routine in normal operation.

• ▸Proposed method: state the way of proceeding in one line.
• ▸Downstream constraint it must satisfy: name what the people down the line actually need.
• ▸Client assessment standard: how will the client judge this work?
• ▸Information gaps: what do we still have to guess about?
• ▸Fit test: does the method meet the constraint and the standard, yes/no?
• ▸Discretion points: where may members vary the routine to serve the goal?
• ▸Fine-tuning checkpoints: when will we reconvene to revise (e.g., daily call, midpoint)?
• ▸Lessons captured: problems and learnings to raise at the next meeting.

1. 1Set direction about ends, not means: specify the end states the team must achieve and, per Table 3-1, make the direction consequential so it 'fosters full utilization of knowledge and skill'—then leave the means to the team.
2. 2Design the work and structure as a 'frame,' not a finished house: put in place the handful of critical structural features, then leave 'lots of room' for members to mold their own ways of operating so their intelligence, initiative, and ingenuity get used.
3. 3Distinguish critical from unnecessary structural constraints. Before you standardize a procedure, ask whether it removes discretion members need; the flight-deck 'glass cockpit' case shows how well-intentioned constraint quietly restricts crews' latitude to manage their own work.
4. 4Grant explicit discretion to override standard routines when doing so serves the real purpose—as the airline's directive did in giving the senior cabin crew member authority to vary allocated duties for higher passenger satisfaction—and then verify on-board behavior actually changes.
5. 5Weight contributions by demonstrated expertise. Compose the team and assign roles based on what members can actually do (the choosy hiring, demanding training, and staged promotion from Flight Attendant I to II), and use tenure to build, not erode, a shared pool of knowledge.
6. 6Treat the team as a setting where members 'learn from one another and thereby build an ever-larger pool of knowledge and expertise'; sustain intact membership long enough for that pool to compound rather than reshuffling constantly.
7. 7Audit for underutilization directly: watch whether members improvise competently in novel situations. If they can self-organize under an unfamiliar emergency but revert to rote routine day-to-day, the capacity exists and your structure is suppressing it.

On the airline being studied, cabin crews had 'more than enough knowledge and skill to execute the work'—the carrier hired selectively, trained demanding, and promoted in stages. Victor Vroom saw that latent capacity surface during an emergency: an engine-fire warning forced a landing at an airport the airline didn't serve, with no company employees on the ground and a full plane of passengers. The crew, off the aircraft, 'immediately got themselves organized, started making calls and negotiating with local innkeepers,' and within a couple of hours had arranged meals and lodging for everyone. That is member knowledge and skill fully drawn upon. Yet in normal service the same crews executed a rigid choreographed ballet, and management's written invitation to vary procedures 'did not generate much change'—the standard routines were too strong. The lesson: the talent was there all along; ordinary structure simply never called on it.

• If you're tempted to specify the means, stop—specify end states insistently and unapologetically, and refrain from prescribing the details of how the team pursues them.
• If a procedure is being standardized and diffused, then check first whether it 'sharply reduces discretion' for the people who actually do the work; if it does, keep the frame and drop the detail.
• If members improvise well in a crisis but run on autopilot routinely, then your everyday structure—not their ability—is the constraint to loosen.
• If you're weighting a contribution by status, seniority title, or demographic surrogate rather than demonstrated expertise, reassign based on who actually holds the relevant knowledge.
• If the work itself is essentially trivial, then no rhetorical device will engage members' full knowledge—redesign the work rather than dress it up as building a cathedral.

• 'Engineering' the work so tightly that you underutilize members' intelligence, initiative, and ingenuity; the tell is a well-established routine that persists even after management explicitly authorizes variation.
• Trying to change behavior by exhortation instead of structure—the directive is issued, but 'the rhythm of the standard routines' overwhelms it and nothing on board actually changes.
• Over-specifying under a quality or process program, sliding into the 'one best way' of scientific management; the tell is documented, diffused procedures that leave front-line producers with almost no discretion.
• Letting technology or designers do the deciding so members only monitor—like glass-cockpit crews literally unable to exceed preset parameters; the tell is that people can no longer manage their own work even when they should.
• Assuming bigger or more harmonious automatically means better use of resources; the tell is a team that 'barely works at all' or that more individuals working alone outperform, because pooled talent is present but never actually drawn upon.

• ▸Task/decision under review: name the specific piece of work.
• ▸Expertise actually required: what knowledge or skill does doing it well demand?
• ▸Who holds it: name the member(s) with demonstrated (not titular) expertise.
• ▸Basis of current weighting: is influence assigned by expertise, or by status/seniority/demographic surrogate?
• ▸Discretion available: does the current procedure leave room to vary means, or dictate the 'one best way'?
• ▸Crisis-vs-routine gap: do members improvise competently under novelty but run rote day-to-day? (yes/no)
• ▸Structural fix: which single constraint will you remove to open latitude here?
• ▸Development plan: how will this task build the member's/team's knowledge pool over time?
• ▸Verification: what on-the-ground behavior change confirms the talent is now being used?

1. 1Confirm you have a real team first: verify the work requires interdependent effort toward a shared outcome, then that boundaries are clear, then that authority is specified. Stability only pays off once these are in place.
2. 2Determine the minimum core the work requires at its lowest demand level. Designate those individuals as core members and give them employment security so their tenure is protected from routine fluctuation.
3. 3Assign the core team the responsibility for managing its own expansion and contraction. When demand rises, the team draws from a pre-developed pool rather than management dumping in strangers.
4. 4Have core members invest deliberate time in developing the skills of the augmenting pool so newcomers can join the work quickly and smoothly, and so they come to identify with and feel loyalty to the team.
5. 5Keep intact groupings together across assignments rather than composing them anew each cycle. Where scheduling systems assign people as individuals (e.g., seniority bidding), fight to schedule the unit as a unit.
6. 6When membership must change, run a team-oriented briefing at the start of each engagement to reduce the liabilities of newness — get names, roles, and expectations explicit before the work begins.
7. 7Reject the intuition that long-tenured teams decay. Treat stability as a performance asset that builds shared mental models and transactive memory, and design retention deliberately rather than letting churn happen by default.

A semiconductor production team faced membership that yo-yoed with order volume: management hired when backlogs grew and laid off junior members when capacity exceeded demand, leaving only occasional stretches of stability. When the production manager pushed responsibility down to teams, one new responsibility was boundary management. The manager calculated the number and mix of members needed at absolute minimum production and designated those people as 'core,' guaranteeing they would not be laid off unless the whole area shut down. In exchange, core members had to manage the expansion and contraction themselves as business shifted. After initial resistance — adding and cutting staff is emotionally demanding and had always been management's job — members handled it well. They built their own pool of people to invite in during peaks, invested in developing those people's skills so they could join smoothly, and over time the temporary staff came to identify with and feel loyal to the team.

• If the work does not require interdependent effort toward a shared outcome, then design it for individuals — stability is irrelevant for a co-acting group like Supervisor Szczarba's operators who share only a supervisor.
• If demand genuinely fluctuates and you cannot eliminate it, then protect a stable core and let the periphery flex, rather than churning the whole team.
• If members are assigned as individuals by seniority or scheduling systems, then override or work around it to keep intact units together — individual competence does not substitute for a team that has flown together.
• If a crew or team must form fresh, then require a team-oriented briefing before work starts, because most trouble concentrates on the first day of working together.
• If your intuition says a long-tenured team has grown careless and needs shaking up, then distrust that intuition — the evidence favors keeping stable membership intact.

• Believing the myth that intact teams decay into carelessness and forgiveness of mistakes, and rotating members to 'freshen' them — the tell is a stated rationale about members getting 'too comfortable' with no evidence of actual decline.
• Assigning people as individuals via seniority bidding so composition changes constantly — the tell is a single day producing two or three different crew configurations, or a captain who shrugs 'every pilot knows his job' at a last-minute swap.
• Letting management own all expansion and contraction, so the team never develops its own trained pool — the tell is new members arriving cold and slowing the work each cycle.
• Protecting no core at all, so every demand swing hits the whole team — the tell is a yo-yo of expansion and contraction with only occasional stability and no continuity of learning.
• Treating stability as automatic once boundaries look clear at a single moment, ignoring that membership is likely to change at the next moment — the tell is a roster that is accurate today but unpredictable tomorrow.

• ▸Team task: state the interdependent shared outcome that requires this group to work together.
• ▸Minimum viable core: number and mix of members needed at lowest demand level.
• ▸Core member names: list the individuals designated as protected core.
• ▸Core security terms: what employment/assignment guarantee protects the core.
• ▸Core obligation: what the core owes in exchange (managing expansion/contraction).
• ▸Augmentation pool: named people trained and ready to join during peaks.
• ▸Skill-development plan: how core members build the pool's readiness before they're needed.
• ▸Newness safeguard: the briefing or onboarding ritual run whenever composition changes.
• ▸Scheduling override: how you keep intact units together despite individual-assignment systems.

1. 1State the task's real work requirements first, then set the smallest number of people who can actually cover them—do not staff to an idealized 'typical' load. The airline optimized routines for a 275-passenger, five-hour flight and paid for it whenever the flight didn't match.
2. 2Count potential productivity gains and process losses separately. Each added member adds capability at a decreasing rate but adds coordination and motivation losses at an accelerating rate; add a member only when the marginal capability clearly exceeds the marginal loss.
3. 3Bias deliberately toward slightly understaffed. When members have more work than can be done comfortably, they stay in motion and engaged; when they have too little, they disengage (the crews who closed the galley curtain and complained about management on eight-hour, 100-passenger flights).
4. 4Test size against variability of the work, not the average. If the same team must handle both a short full flight and a long empty one, size for the demanding case and give the team latitude to redeploy—not to a mean that fits neither.
5. 5Pair any size decision with the enabling structure condition: a bounded, stable membership so members know who is on the team. Size only produces benefit when it is a real team, not a loose collection of individuals like the crew that stays 'a collection of individuals' until night one at the hotel.
6. 6Re-examine size at natural review points rather than continuously. Establish the count when the team starts, then make small adjustments—resist the reflex to keep adding heads mid-cycle to fix performance problems that are actually design problems.

At the international airline, work-system designers sized and scripted cabin crews for a 'typical' flight of about five hours with roughly 275 passengers. On flights that matched, the ballet of 747 service ran smoothly with very few service disasters. But on eight-hour flights carrying only 100 passengers, the same crew finished quickly, retired to the galley, closed the nonsoundproof curtain, and spent the slack time discussing how poorly the airline was managed—process losses from having more hands than the work required. On short flights with every seat full, the same crew was constantly in motion with not a minute to chat with passengers. The tell that size was wrong was managers noticing crew members merely 'reading their lines,' neither attentive nor responsive. The lesson: sizing to an average, rather than to the demanding case with latitude to adjust, produced disengagement at one extreme and strain at the other.

• If adding a member yields less capability than the coordination and motivation cost it introduces, then stop adding—you are past the point where more resources help.
• If you are unsure whether to include one more person, then leave them out; a slightly understaffed team generally outperforms a fully or over-staffed one.
• If members have visible idle time (galley chatter, disengagement), then the team is too large or the work is mis-sized—cut headcount or restore challenge.
• If the work varies widely across occasions, then size for the demanding case and grant redeployment latitude rather than optimizing for the mean.
• If the group still behaves as a 'collection of individuals' late into the work, then size is not the problem—fix boundedness and being a real team first.

• Believing larger teams perform better because they have more and more diverse resources—the passage names this as a common assertion that is simply wrong; the tell is a leader justifying every added head by 'more resources.'
• Sizing to the average case, so routines fit no actual occasion; the tell is crews either racing through short full flights or idling on long empty ones.
• Adding people to rescue a struggling team, which raises process losses at an accelerating rate; the tell is performance flattening or worsening as headcount grows.
• Confusing a large roster with a real team; the tell is members 'keeping mostly to themselves, each occupied with his or her own thoughts.'
• Reading the individuals-outperform-teams research as proof teams are useless rather than as a warning to keep teams small and well-designed; the tell is abandoning teamwork instead of right-sizing it.

• ▸Real work requirements: list the tasks that genuinely need doing at the demanding case.
• ▸Minimum viable count: fewest members who can cover those requirements.
• ▸Demanding-case load: the hardest occasion (e.g., short + full), not the average.
• ▸Marginal capability of next member: what one more person actually adds.
• ▸Marginal process loss of next member: added coordination/motivation cost.
• ▸Add or hold decision: keep the member only if capability clearly beats loss.
• ▸Understaffing check: is the team slightly stretched rather than slack? (target yes)
• ▸Redeployment latitude: what can members re-adjust when the occasion differs from plan?
• ▸Review point: when will size be re-examined (start / midpoint / after a cycle)?

1. 1Identify who actually receives, reviews, or uses your output — not your manager, not you, not outside evaluators. At OMB the real client was the political staff who used the reports in the budget process, not the economics-journal editors whose standards the analysts personally respected.
2. 2Extract the client's operative standards on all three dimensions: quantity, quality, and timeliness. The OMB political officials cared about bulletproof analysis (quality) but weighted timeliness and usefulness to the president's agenda even higher — a publishable report arriving the day after the director testified was worthless.
3. 3Where the team's definition of 'good' differs from the client's, name the gap explicitly rather than defaulting to your own criteria. Use the gap as a prompt for a new performance strategy instead of quietly serving yourself.
4. 4Choose a response to misalignment: educate the client, apply pressure, realign clients toward your standards, or replace recalcitrant clients. The 'sandwich' orchestra placed new music between an engaging opener and a major closing work to draw audiences in and shift their taste over time.
5. 5Deliver against the client's timeliness constraint first — a late, self-serving product gets ignored and can freeze the team out of future work entirely (OMB political staff could commission their own analyses instead).
6. 6When a legitimate client requests something wrong or inappropriate, do not comply and do not simply refuse. Go remind the client why complete, trustworthy output serves their own interest, and enlist your own manager to reaffirm the team's protected purpose upward.
7. 7Reinforce the team's core purpose and norms of conduct directly with members so they can deflect improper pressure themselves when it recurs — client-shaping is never-ending and never sufficient on its own.

OMB's fiscal analysis teams, staffed by economists with advanced degrees, produced reports whose fate depended on the political officials who used them. During budget season those clients hinted the reports should be more supportive of the administration — could the team omit unreliable projections about the proposals' effect on the national debt? Rather than comply or flatly refuse, branch chief David Mathiasen toured the political side to remind clients it was in their own interest to have reports as complete and trustworthy as possible, and asked his own manager to reaffirm with the director the importance of non-politicized civil servant staff. This reduced inappropriate requests — for a time. Because such pressure recurs, Mathiasen also worked directly with his teams to build deep understanding of their ultimate purposes and consistent norms of conduct, strengthening their ability to deflect political pressure when they met it. The teams kept their unique contribution to a political process without being captured by it.

• If the manager, the team, and the outside evaluator disagree with the actual recipient about what 'good' means, then the recipient's standards govern — unless the team is genuinely the client of its own work.
• If the client's standards differ from the team's, then treat the gap as a strategy prompt (educate, pressure, realign, or replace clients), not as license to substitute your own criteria.
• If a report is publishable-quality but late or focused on the team's own interests, then it will be ignored — prioritize timeliness and usefulness to the client's real agenda.
• If a legitimate client asks for something wrong or inappropriate, then reduce the pressure at its source and fortify the team's purpose internally, rather than complying or issuing a bare refusal.
• If your product comes to look useless or self-serving, then expect the client to route around you entirely — protect against this by anchoring to their use of the output, not your craft pride.

• Serving your own craft standards over the client's use. The tell: the team is 'quite comfortable' being judged by its professional guild's criteria while the actual users quietly stop reading the output.
• Making the manager a surrogate client. The tell: work is optimized to please the boss, who rarely receives or uses the output the way the real client does.
• Capitulating fully to client wishes and stretching no one — or ignoring the client entirely to please yourselves. The tell: the pops orchestra filled seats but stretched no one; the self-governing orchestra played what it wanted and watched audiences dwindle toward insolvency.
• Treating client-shaping as a one-time fix. The tell: inappropriate requests drop after an intervention, then return because the process is 'never ending and never sufficient.'
• Meeting quality while missing timeliness. The tell: a bulletproof analysis lands the day after the director already testified and gets ignored.

• ▸Actual client — who receives, reviews, or uses this output (not manager/team/evaluator)
• ▸Quantity standard — how much the client needs and by what count
• ▸Quality standard — the client's real test of 'good,' in the client's words
• ▸Timeliness standard — the deadline and what makes output worthless if missed
• ▸Team's own standard — where our definition of 'good' differs from the client's
• ▸Gap and strategy — educate / pressure / realign / replace, with the chosen move
• ▸Improper-request check — is any client ask wrong or inappropriate, and the two-step response
• ▸Purpose anchor — the ultimate purpose and norm that lets the team deflect pressure

1. 1Design the task so members must think, plan, and decide together in real time — not just execute pre-scripted routines. At the international airline, teams performed competently but their work required 'relatively little thinking, planning, or team decision making,' so their capability never grew.
2. 2Keep membership stable enough that members can learn one another's specific strengths and weaknesses; over time this lets them coordinate by anticipating each other's next moves and initiating responses even as those moves occur.
3. 3Bound the team clearly — distinguish core members from partial members, resource-providers, and non-members. Ambiguous boundaries (the 'undifferentiated gradient' Haas found) prevent members from building the mutual knowledge that coordination depends on.
4. 4Build in periodic review: have the team milk its experiences for learning, examine how it has been operating, and turn errors into corrections rather than piles of failures from which nothing is learned.
5. 5Treat every leg of work as a chance to detect and correct errors before serious damage and to notice and exploit emerging opportunities — the habits that make the unit more capable when work ends than when it began.
6. 6Do not substitute size or structure for shared understanding when coordination breaks down; when People Express outgrew hallway coordination, adding trained leaders to deepen the shared vision preserved the self-managing capability, though even that had limits.
7. 7Give teams the room and mandate to give more than 'competent' service — allow the extra ingenuity and improvisation that separates memorable performance from adequate performance.

Contrast the two 737 cockpit crews. In one, a two-person crew got off to a bad start the previous day and let tension deteriorate leg after leg; by their last leg together, when the captain nodded almost imperceptibly to signal 'raise the gear,' the first officer kept his eyes forward and did not respond — coordination had collapsed instead of grown. The opposite pattern is the seasoned team whose members come to know one another's special strengths and weaknesses and become skilled at anticipating moves and initiating appropriate responses as those moves are occurring. The difference is not personality or authority but whether the social process built or eroded shared capability over the shifts they worked together. Growing teams also periodically review how they've been operating, so a bad start becomes a learning input rather than a downward spiral. That is why the assertion 'long-intact teams deteriorate as members get careless' is wrong: teams that review and correct get better, not worse.

• If the work is fully scripted and leaves no room for joint thinking or decision making, then members' collective capability will stagnate even when performance is competent — redesign the task to require interdependent judgment.
• If you cannot get a definitive membership list from the team or its leader, then the team is under-bounded — resolve who is core before expecting coordinated growth.
• If a shift or leg ended badly, then require a review that extracts learning, rather than letting tension carry into the next leg.
• If coordination is failing as the team scales, then deepen shared understanding and coaching before assuming more structure and systems will fix it.
• If members stay intact for a long time, then assume capability can rise — don't rotate them apart on the false premise that longevity breeds carelessness.

• Confusing competent execution with growth: teams perform to spec but never learn, because the design 'asked them—nay, allowed them' to give nothing more. Tell: the initial excitement wears off and 'it became just a job' with no angst but no development either.
• Letting interpersonal tension go unaddressed across successive work periods. Tell: signals that used to be answered (the captain's nod) get no response, and coordination visibly breaks down on the final leg.
• Leaving membership ambiguous. Tell: leaders can't name who is on the team; work depends on people whose participation is undefined.
• Skipping post-work review, so errors pile up as failures from which little is learned. Tell: the same mistakes recur and opportunities go unnoticed.
• Answering coordination breakdowns from growth with more edicts, systems, or size instead of deeper shared understanding. Tell: operational problems become 'frequent and severe' while everyone assumes structure alone will cure them.

• ▸Core members (named): who is unambiguously on this team
• ▸Boundary check: any partial/resource members creating membership ambiguity? (Y/N + who)
• ▸Interdependence in the task: where did the work require joint thinking or real-time decision, not scripted execution
• ▸Coordination moments: where did we anticipate/answer each other's moves — or miss them (cite the specific hand-off)
• ▸Errors caught/missed: what did we detect and correct before damage, and what slipped through
• ▸Emerging opportunity: what did we notice we could exploit next time
• ▸Learning extracted: one thing about how we operate that we will change
• ▸Capability delta: are we a more capable unit than when this work began? (evidence)

1. 1Treat individual learning and well-being as one of three co-equal effectiveness criteria, alongside serving clients and becoming a stronger performing unit over time. Do not trade it away for output.
2. 2Set up the group so it operates as a real team with a compelling direction — passages tie member fulfillment to the same five conditions that drive performance, so build those first rather than managing well-being directly.
3. 3Design roles so members' distinct resources get used, not left on the table. Audit the group as the in-charge does at briefing ('What foreign languages do we have?') so each person's knowledge has a place to be applied.
4. 4Build periodic review into the work cycle: teams that 'milk their experiences for whatever learning can be had' convert the group into a learning site rather than a source of angst.
5. 5Time your interventions — some acts belong at start-up, some at the midpoint, some after a work cycle. Establishing conditions at the wrong moment 'rarely makes a constructive difference, and sometimes backfires,' including for members' morale.
6. 6Acknowledge honestly when the experience risks becoming 'more frustrating than fulfilling,' then name the specific conditions you are putting in place so members trust this group will differ from past bad ones.
7. 7Preserve members' motivation and creativity as an explicit target: the international airline achieved control 'at considerable cost in motivation and creativity' and underutilized talent — check you are not doing the same.

The author recalls a faculty search committee that succeeded on its task: the president liked and appointed the recommended candidate. Yet by the time that happened, the author had vowed never again to work with those members — the committee had 'destroyed itself in the process of doing its work.' The output was fine, but individual well-being and any capacity for future collaboration were wrecked, with 'mutual antagonisms and trails of failures from which little is learned.' Contrast the classroom groan: students groan at group projects not because groups can't teach, but because they've experienced groups that turned angst into the main product. The lesson is that a good product does not certify a healthy process. An effective team leaves members more capable and more willing to work together, not vowing to avoid each other.

• If the task is done but members are alienated or vow never to collaborate again, then count the effort a failure on this criterion regardless of output quality.
• If a member's distinct resource (a language, a skill, prior experience) never gets deployed, then redesign roles — underutilized talent signals lost learning and lost engagement.
• If you are tempted to preprogram work to eliminate downside risk, then check whether you are buying control at the cost of motivation and creativity, as the international airline did.
• If members are groaning or citing past bad group experiences, then name the specific enabling conditions you'll install rather than promising this time will magically be different.
• If the work cycle ends without a review of how the team operated, then insert one — otherwise the experience yields little learning even when the result was good.

• Judging success only by whether the job got done. Tell: leaders celebrate the deliverable while members privately resolve never to work together again.
• Trying to manage well-being directly through morale talk instead of installing the underlying conditions. Tell: pep talks rise as engagement keeps falling.
• Over-engineering the work for predictability. Tell: consistent output but flat, underutilized members with little energy or innovation left on the table.
• Assuming harmony equals a healthy experience, so real conflict about how to do the work gets suppressed. Tell: surface politeness while learning and error-correction quietly stop.
• Intervening at the wrong time. Tell: a well-meant leadership move around the middle or end backfires and members feel micromanaged rather than helped.

• ▸Member and distinct resource: name the skill/knowledge each person brings
• ▸Where it was used: cite the concrete task moment, or mark 'left on the table'
• ▸New skill or perspective gained: what this member can now do that they couldn't before
• ▸Belonging signal: evidence the person feels they have a secure place in the group
• ▸Frustration flag: any sign of angst, alienation, or 'never again' sentiment
• ▸Review conducted: did the team examine how it operated and extract learning (y/n)
• ▸Willingness to collaborate again: would this member choose to work with these people (y/n)
• ▸Condition to strengthen: which of the five conditions most threatens this member's experience
• ▸Timing of next fix: start-up, midpoint, or post-cycle

1. 1Stop trying to manage team behavior in real time; instead invest your effort up front getting the team onto a good trajectory, then make only small adjustments along the way. The passages are explicit: no leader can make a team perform well, but all can raise the odds.
2. 2Diagnose which of the five enabling conditions are missing or weak before acting: a real team, compelling direction, enabling structure, supportive context, expert coaching. Focus scarce energy on the conditions great in impact, not on the wrong things that cause poor performance.
3. 3Time each intervention to the work cycle. Set up the team and its structure at launch, coach process at the midpoint, and reflect/consolidate learning after a significant piece of work finishes. Doing the right act at the wrong time rarely helps and can backfire.
4. 4Set compelling direction the way the second airline did: give thorough training in objectives and clear outer-limit constraints, then get out of the way. Translate abstract precepts into memorable, operational language you reinforce at every opportunity (the chairman's 'Three C's': complete, clean, communicate).
5. 5Choose your control point deliberately. You can engineer the work into a tight choreography (international carrier) to guarantee consistency with no manager present, or grant crews authority over how they do the work (CSM crews) to gain motivation and creativity. Name the trade-off you are accepting.
6. 6Recognize that anyone can supply the missing condition—designated leader, member, external manager, consultant, or client. Do not wait for authority; act on whichever condition you can strengthen, because what matters is that the condition gets in place and stays there.

The director of in-flight services controls flight attendant work but has no manager aboard and no leverage over price or schedule. The international carrier answered this by engineering a choreographed 'ballet': each seat lettered A through D with detailed duties—A, B, and D tend unaccompanied children, mothers with infants, and elderly or sick passengers; C tidies galleys and tracks equipment—executable with no manager on board. It hired selectively from an oversupply of applicants and trained heavily, so members had more than enough skill; the result was seamless, consistent service but at a cost in motivation and creativity. The second airline instead gave crews thorough training in objectives, clear outer-limit constraints, and a diverse toolkit, then left them on their own, distilling direction into the Three C's the chairman reinforced constantly. Same leadership problem, two different quality choices: one bought consistency by removing member discretion, the other bought motivation and creativity by granting it. The lesson: quality of leadership shows in choosing which enabling condition to press and knowing the trade-off you accept.

• If the work must be identical and reliable with no supervisor present, then engineer structure tightly and accept the cost to motivation and creativity; if you want member initiative, then set direction and constraints, supply tools, and grant authority over how.
• If direction is stated only as abstract precepts, then translate it into a few concrete, memorable operational terms (like the Three C's) and reinforce them repeatedly, or the direction will not guide behavior.
• If a team is just starting out, then spend your effort on composition and structure; if it is at the midpoint, then coach process; if it has just finished, then help it consolidate learning—match the act to the moment.
• If you catch yourself trying to control team behavior moment-to-moment, then stop and instead fix the standing conditions, because you cannot make a team perform well, only raise the likelihood.
• If a needed condition is missing and you are not the formal leader, then supply it anyway—member, manager, or consultant—since who creates it does not matter, only that it stays in place.

• Focusing on the wrong things when designing or supporting the team; the tell is a team that barely works, takes longer, or never finishes despite effort—the poor performance the whole book traces to misplaced leadership focus.
• Assuming more people equals better output; the tell is a team being outperformed by an equivalent number of individuals working alone, which research 'almost always' finds.
• Waiting for team 'magic' as the normal case; the tell is repeated disappointment because magic, however wondrous, is rarely seen while longer or unfinished work is the common result.
• Intervening at the wrong time; the tell is that a well-intentioned leadership act 'rarely makes a constructive difference' and sometimes backfires because it was done at launch when it belonged at midpoint, or vice versa.
• Trying to continuously manage behavior in real time rather than setting the trajectory; the tell is a leader constantly firefighting instead of making small course adjustments, exhausting themselves without improving results.

• ▸Team and task: name the team and the live, real-time output it must produce
• ▸Real team? note stable membership and clear boundary, or the gap
• ▸Compelling direction: state the objective in concrete operational terms (your 'Three C's')
• ▸Outer-limit constraints: list what members must not do
• ▸Enabling structure: is 'how' engineered tight or left to the crew, and why
• ▸Supportive context: what tools, training, and resources are actually supplied
• ▸Expert coaching: who will coach and at which point in the cycle
• ▸Control-vs-motivation trade-off: name which you are buying and the cost you accept
• ▸Timed action: the single next intervention and whether it belongs at launch, midpoint, or end

1. 1Test the task first: ask whether the identifiable collective outcome genuinely requires members to work together interdependently, or whether it is better done by individuals working alone. If interdependence is not real, design for individual performers and stop here.
2. 2Draw the boundary explicitly: write a definitive membership list distinguishing who shares responsibility and accountability for the outcome from those who merely help out, provide information, or supply resources. If you cannot name the members, you do not yet have a team.
3. 3Apply Haas's core-versus-everyone-else test: identify the small set of 'core' members, then treat partial contributors, information providers, and critical outsiders as environment, not membership.
4. 4Calibrate permeability: keep boundaries clear but moderately open. Guard against underboundedness (endless flow of people in and out, deputies sent to meetings) and against overboundedness (an island cut off from environmental changes and cross-boundary exchange).
5. 5Delimit authority: state which decisions the team owns and which it does not, so the group knows its scope. The CEO's team failed partly because no one knew why they met or what they were to do as a team, and running the company stayed the CEO's job.
6. 6Protect stability over time: keep membership reasonably intact rather than reforming it like sand dunes on a windy beach, because settled specialized roles, shared norms, and collective momentum take time to form.
7. 7Verify a real team exists by checking for specialized roles, shared norms of conduct, and collective momentum toward a client-satisfactory product; if these are absent, you have people who have meetings, not a performing unit.

A senior vice president at a financial institution formed a task force to standardize policies across multiple locations, appointing representatives from several functional areas plus individuals he knew and trusted from other countries, and permitting the team to recruit still more members. The boundary was never fixed: membership stayed uncertain and permeable, with a continuous flow of people, so the group could not reliably tell members from helpers. As a result the task force never jelled — members never developed specialized roles or shared norms, and no collective momentum formed. Frustrated, the leader eventually went off alone, wrote the proposal himself with input from a couple of members, and submitted it. There was never a team product because there was never a team — a textbook Alderfer 'underbounded' system that lost its sense of identity in environmental turbulence.

• If the task can be done well by an individual (like creative writing or executive leadership) or does not require interdependent work toward a shared outcome, then design for individual performers, not a team.
• If you (or the team leader) cannot produce a definitive membership list, then the boundary is not yet real — resolve who is core before proceeding.
• If people flow endlessly in and out or deputies stand in for members, then treat the unit as underbounded and tighten the boundary before expecting a coherent strategy.
• If the team is geographically isolated (remote plant startup, consultant at a distant client site) and closed off, then treat overboundedness as the risk and force cross-boundary exchange.
• If someone provides information or resources but does not share accountability for the collective outcome, then classify them as environment, not membership.

• Using a team for work best done by individuals — the tell is that members can produce identifiable outputs independently and coordination feels like overhead rather than necessity.
• Leaving boundaries ambiguous — the tell is that managers answer 'it depends how you define the team' and even the leader cannot list members (Haas's finding).
• Overpermeable membership — the tell is a never-ending flow of people in and out and no stable set that develops specialized roles or norms (the financial-institution task force).
• Overboundedness — the tell is a team that has clear identity but misses environmental changes and does no cross-boundary exchange, common in remote or isolated units.
• Confusing a standing meeting with a team — the tell is co-actors whose real accountability is to their own units, no shared purpose, and members sending deputies (the top-management group).

• ▸Collective outcome: state the one identifiable result the team is accountable for.
• ▸Interdependence check: name specifically why members must work together rather than alone.
• ▸Core members: list every person who shares responsibility and accountability for the outcome.
• ▸Environment (not members): list helpers, information/resource providers, and critical outsiders kept off the roster.
• ▸Authority scope: state which decisions the team owns and which it does not.
• ▸Permeability setting: note how membership may change and the rule for adding/removing people.
• ▸Under/overbounded risk: mark which failure this team leans toward and one countermeasure.
• ▸Stability horizon: state expected lifespan and how intact membership will be kept over time.
• ▸Real-team evidence: note whether specialized roles, shared norms, and collective momentum are present or absent.

1. 1Specify ends, not means: state the outcome the team must produce (the quality/consistency of on-board service that surpasses competitors) and deliberately leave the how to the team. The International Airline erred by scripting every lettered position and galley procedure — that clarity killed motivation and creativity.
2. 2Anchor direction in the client's actual standards, not the team's own. For the OMB fiscal analysis teams, direction meant timeliness and usefulness to the president's agenda plus bulletproof rigor — not the publishable-quality criteria the analysts themselves respected.
3. 3Make the purpose challenging enough to energize: set an ambitious end-state (every passenger committed to the airline by the end of the flight) rather than a comfortable minimum.
4. 4Make it consequential so it engages: connect the work to something that matters to those who receive it, so members see why their output counts and can be frozen out if it doesn't.
5. 5Set direction authoritatively — from a position of legitimate power. The VP grants the cabin-services head a clean slate; the head must then exercise that authority to name the ends clearly rather than negotiate them away.
6. 6Hold clarity and incompleteness in tension: specify the destination precisely while leaving the route open. Test each directive by asking whether it names an end or dictates a means, and strip the means.
7. 7Maintain direction over time by continuously shaping clients' views of what good performance means, as Mathiasen did — this work is 'never ending and never sufficient.'

David Mathiasen led fiscal analysis teams at OMB whose direction was constantly distorted by political clients making inappropriate, self-serving requests. He first toured the political side of the house, reminding clients why complete, trustworthy reports served their own interest, and met with his own manager to have the director reaffirm that civil-servant staff should not be politicized. These moves reduced inappropriate requests — but only for a time, because shaping clients' expectations proved never-ending. So Mathiasen also worked directly with his teams, ensuring members held a deep understanding of their ultimate purposes and norms of conduct consistent with those purposes. That combination gave the teams the direction they needed to deflect political pressure while still contributing to an inherently political budget process. The lesson: direction is not set once; it is authoritatively established and then defended.

• If a directive names how the team should do the work rather than what it must achieve, then cut it — specify ends, leave means to the team.
• If the team's standards and the client's standards diverge, then direction follows the client's — it is the client's assessments that count.
• If the purpose feels safely achievable, then raise it until it is challenging enough to energize; a modest 'acceptable output' floor is not compelling direction.
• If clients keep pushing the team off purpose, then work both sides: reshape client expectations AND deepen the team's own understanding of its ultimate purposes.
• If members cannot state why their work matters to whoever receives it, then the direction is not consequential enough to engage them — reconnect the work to its stakes.

• Over-specifying means: dictating exact procedures and lettered positions (as the International Airline did) buys control at the cost of motivation and creativity. Tell: high compliance, low initiative, no improvisation when situations deviate from script.
• Letting the team set its own standards: analysts default to publishable-quality criteria while the client needs timely, agenda-useful reports. Tell: technically excellent output that arrives too late or misses what the client cares about, and gets ignored.
• Vague direction with no clear end: leaving both ends and means open is not compelling incompleteness, it's abdication. Tell: members debate what they're even supposed to accomplish.
• Treating direction as a one-time announcement: assuming a stated purpose stays set. Tell: gradual drift as clients inject inappropriate requests that go unchallenged.
• Under-ambitious purpose: setting a comfortable target that clears the 'acceptable' bar but doesn't energize. Tell: teams meet the minimum and stop, with no stretch or pride in the work.

• ▸Ultimate end-state: the outcome the team must produce, stated as a result not a method
• ▸Who the client is: name the party whose standards and assessments actually count
• ▸Client's real criteria: timeliness, usefulness, and quality thresholds as the client defines them
• ▸Challenge check: why this purpose stretches the team beyond a comfortable minimum
• ▸Consequence check: what happens (to the work and the team) if the purpose is met or missed
• ▸Means left open: list the decisions explicitly delegated to the team
• ▸Authority source: who has legitimate power to set this direction and how it was set
• ▸Direction-maintenance plan: how you will keep reshaping client expectations and deepening team understanding over time

1. 1Design the task so it is a whole, meaningful piece of work with a visible outcome: the international carrier's flight attendants owned the entire in-flight service passengers actually see and judge — build tasks with that kind of end-to-end ownership rather than fragmented sub-tasks.
2. 2Decide how much of the 'how' to specify versus leave to the team, and know the trade-off: the international airline specified the 'one best way' in choreographed lettered positions and got predictability and low risk, but paid in slow innovation and no tailoring to a given flight. The CSM airline specified objectives plus outer-limit constraints plus tools, then left the method to crews.
3. 3Set core outward-looking norms of conduct: tell the team clearly what the outer-limit constraints on behavior are, then direct their attention outward toward objectives (the CSM 'Three C's': complete, clean, communicate) rather than inward toward rigid procedure.
4. 4Keep the team small and composed with the right mix: the 747 crew of fourteen included at least three senior flight attendants — build in enough seniority and experience to coordinate and handle the unanticipated.
5. 5Staff for both task skill and the ability to work interdependently: the international carrier could be choosy because applicants far exceeded positions, then ran a demanding initial training course so every member could execute any lettered position competently.
6. 6Name coordination roles inside the team — designated leaders to coordinate the work and deal with unanticipated problems — and give members a diverse set of tools to pursue the objective.
7. 7Set a workload that is demanding but not exhausting; the international carrier's schedule was calibrated exactly this way.

The international carrier engineered its 747 cabin service as a fully specified structure. Each position was labeled by letter and every flight attendant was trained to execute any lettered role. Positions A, B, and D handled unaccompanied children, mothers with infants, and sick or elderly passengers; C tidied galleys and tracked equipment. The result was a choreographed 'ballet' that looked seamless to customers and ran with no manager on board. Composition was strong: applicants far outnumbered positions so hiring was selective, training was demanding, and crews of fourteen carried at least three seniors, with designated leaders to coordinate and absorb surprises. This structure produced predictability, competent performance, and very few service disasters — but its tight specification of method meant crews would not tailor service to a short full flight versus a long light one, and matching a competitor's innovation could take months while procedures were rewritten and crews cycled through semiannual training.

• If the work environment is stable and errors are catastrophic, then specifying a detailed 'one best way' buys predictability and low risk — but accept slower innovation as the cost.
• If conditions vary flight-to-flight and responsiveness matters, then specify objectives and outer-limit constraints plus tools (the CSM model) and leave method to the team.
• If you specify method in detail, then invest heavily in selection and training so every member can execute any assigned role competently.
• If the task requires real-time coordination with no manager present, then designate leaders inside the team to coordinate and handle unanticipated problems.
• If you want members outward-looking, then anchor norms to the customer-facing objective (complete, clean, communicate) rather than to internal procedure compliance.

• Over-specifying every procedure: the tell is crews that won't adapt to a full short flight versus a light long one, and innovations that take months to field because the workflow must be reengineered first.
• Fragmenting the task into meaningless sub-parts instead of a whole piece of work with a visible outcome — members lose the sense of owning something customers actually judge.
• Composing for glamour or task skill alone while ignoring seniority and interpersonal coordination — the tell is a crew that executes individually but cannot absorb the unanticipated problem.
• Leaving norms unstated so the team drifts inward; without clear outer-limit constraints plus outward objectives, teams either freeze or improvise beyond acceptable bounds.
• Setting a schedule that is exhausting rather than merely demanding, degrading the competent execution the design assumed.

• ▸Whole task defined: state the complete, visible outcome the team owns end-to-end
• ▸Method latitude: mark where you specify 'one best way' vs. leave to the team, and name the trade-off accepted
• ▸Outer-limit constraints: list the hard boundaries members must not cross
• ▸Outward objective: one line of customer/user-facing purpose (e.g., complete, clean, communicate)
• ▸Team size: number of members, kept as small as the work allows
• ▸Composition mix: required task skills + seniority/experience count (e.g., seniors per crew)
• ▸Coordination roles: named in-team leaders responsible for coordination and surprises
• ▸Skills gap plan: selection and training steps ensuring every member can execute assigned duties
• ▸Workload check: demanding-but-not-exhausting confirmation

1. 1Audit the reward system for team-level recognition. Ask whether your reward and recognition structures reward team excellence or only individual output — if judgments about the team's fate come from a different source than the standards the team respects, name that gap explicitly.
2. 2Trace who actually judges the team's output and what standards they use. At OMB, the reports could have been judged by 'generally accepted standards for economic research,' but what actually determined the teams' fate was the views of the political officials. Map the real evaluator before you tune anything.
3. 3Supply the information and data the work requires without corrupting it. The fiscal analysts needed to keep extrapolations and debt projections in their reports even when clients wanted them omitted; protect the completeness and trustworthiness of the data flow rather than let it be shaped to please.
4. 4Furnish training and technical assistance matched to the task. At the international airline, management 'conducted rigorous training programs' and used full-scale cabin mockups so every flight attendant understood both objectives and procedures — decide the level of detail your task actually demands.
5. 5Supply the material wherewithal — the tools, forecasts, and specifications the team needs. The airline generated 'detailed specifications for food, beverage, and entertainment services' and laid out exact delivery procedures; give the team the concrete resources to perform.
6. 6Manage the client relationship as ongoing context work. When clients ask for something inappropriate, do what Mathiasen did: reduce the pressure at the source, then reaffirm standards up the chain, then work directly with the team — treat client-shaping as 'never ending and never sufficient.'
7. 7Shape the client's view of what 'good performance' means. The orchestra used a 'sandwich' program and preconcert discussions to alter clients' views; use programming, education, and reminders to bring clients' standards into alignment with defensible ones.

In the Fiscal Analysis Branch of OMB, teams of civil-servant economists prepared analyses for the director. During budget season their political clients began signaling that reports would be 'more helpful' if they were more directly supportive of the administration — perhaps omitting projections about the national debt on the grounds that such extrapolations were 'almost certainly unreliable.' Chief David Mathiasen treated this as a context problem, not a content concession. He made an informal tour of the political side to remind clients why complete, trustworthy reports were in their own interest, and he met with his own manager to have the importance of unpoliticized civil servants reaffirmed with the director. These moves reduced inappropriate requests — but only for a time, so Mathiasen also worked directly and extensively with his analysis teams to keep their understanding deep. The lesson: a supportive context protects the team's information integrity against pressures that reward the wrong output.

• If the standards the team respects differ from the standards the real evaluator uses, then close that gap by shaping the evaluator's view — don't quietly bend the team's work.
• If a legitimate client asks the team to do something inappropriate (like omitting reliable-enough projections), then reduce pressure at the source and reaffirm standards up the chain before ever asking the team to comply.
• If the task offers little room for error and must be performed live, then invest heavily in training, specifications, and forecasts up front, because there is no chance to go back and try again.
• If client-shaping seems to have worked, then assume it is 'never sufficient' and keep working directly with the team — recurring pressure requires recurring maintenance, not a one-time fix.
• If you have a good basic design in place, then supportive context is what lets the team harvest its benefits — treat it as an amplifier of good structure, not a substitute for it.

• Rewarding individual output while calling the work a team effort. Tell: members compete or coast because recognition never lands on the team's collective excellence.
• Assuming the 'objective' quality standard is the one that matters. Tell: the team produces work that meets its profession's standards yet still suffers because the real evaluator judges by different criteria.
• Letting information get shaped to please clients. Tell: reports start omitting reliable-enough projections or 'orienting just a bit' toward a preferred position — data integrity erodes silently.
• Treating client-shaping as a one-time fix. Tell: inappropriate requests drop for a while, then quietly return because no one maintained the relationship.
• Over- or under-supplying detail in training and specifications. Tell: at the extreme, the airline achieved great control but at 'considerable cost in motivation and creativity' — too much specification suppresses the team, too little leaves it unequipped.

• ▸Reward for team excellence: does recognition land on the team's collective output? (yes/no + evidence)
• ▸Real evaluator: who actually decides the team's fate, and by what standards?
• ▸Standards gap: how do the evaluator's standards differ from the standards the team respects?
• ▸Information & forecasts supplied: what data/projections does the work require, and is any of it being shaped or withheld?
• ▸Data-integrity threat: what client pressure could corrupt the work, and who can reduce it at the source?
• ▸Training & technical assistance: what does the task demand, and is the level of detail right (not so much it kills initiative)?
• ▸Material wherewithal: what specifications, tools, and resources does the team need to perform live?
• ▸Client-shaping action: what ongoing initiative keeps clients' view of 'good performance' defensible?
• ▸Direct-with-team action: what must you do with the team itself so members' understanding stays deep?

1. 1Separate coaching into its three functions before intervening: motivational (effort), consultative (strategy), educational (knowledge/skill). Diagnose which one the team actually needs rather than defaulting to your comfort zone.
2. 2Time the intervention to the team's life-cycle. Deliver motivational coaching near the beginning of a work cycle, consultative (strategy) coaching at the midpoint when members can reflect and re-plan, and educational coaching when a significant piece of work has finished and lessons can be absorbed.
3. 3Before consultative coaching, verify the team has trustworthy, up-to-date information about task requirements, resource availability, and forecasts. Coaching on strategy is empty if members lack the data to evaluate alternatives.
4. 4For educational needs, arrange training and technical assistance for the intact team, not scattered individuals, so the shared pool of skill expands where the work actually happens.
5. 5Watch for and interrupt mindless reliance on habitual routines: when data signals the current approach is failing but the team keeps executing anyway, coach them to break the routine and implement a new plan rather than merely draft one.
6. 6Understand you need not be the designated leader to coach. Position anyone credible — member, external manager, consultant, client — to supply the needed function, and only intervene where existing organizational supports fall short.
7. 7Confirm the coaching is about helping members use collective resources well, not about controlling behavior; over-controlling coaching costs motivation and creativity.

In one sales organization, customer service agents were formed into teams and given full responsibility for compiling and communicating price and availability information to customers, replacing data previously prepared by a separate department. Members welcomed managing their own database because the old reports were often inconsistent or incomplete. But they lacked the knowledge and skill to create and maintain a product information database, and the result was frustration, impatience, and managers concluding the team idea was bad because 'the rank-and-file people just can't handle the whole job.' This was an educational coaching gap, not a design failure. As Hackman notes, a few hours of training almost certainly would have solved the problem — the team had the responsibility but not the skill, and no one supplied the missing educational support at the right moment.

• If the team is drafting good plans but never executing them, then treat it as a routine-breaking consultative problem, not a knowledge gap — coaching more strategy will just repeat the cycle.
• If data shows the current approach is failing but members keep going (as with the Air Florida takeoff routine that continued despite the first officer's doubts), then intervene immediately to break the habitual routine.
• If members have responsibility for work their existing skill can't cover, then supply educational coaching (training/technical assistance) before blaming the people or the team concept.
• If it's the start of a work cycle, coach effort; if it's the midpoint, coach strategy; if a piece of work just finished, coach knowledge and skill — coaching at the wrong time rarely helps and can backfire.
• If existing organizational systems already deliver training and support, then route the team to them rather than building new coaching from scratch.

• Coaching at the wrong life-cycle moment — offering strategy help at cycle end or lessons-learned at the start. The tell: the intervention lands flat or the team resists because it doesn't match what they're doing.
• Defaulting to one function (usually motivational pep talk) regardless of the actual need. The tell: effort rises but the same strategic or skill problem recurs.
• Mistaking a skill gap for a character or capability flaw. The tell: managers say 'the people just can't handle the job' when a few hours of training would fix it.
• Providing consultative coaching without ensuring the team has real information about requirements and resources. The tell: plans are made on guesswork and never survive contact with reality.
• Coaching to control behavior rather than to help members use resources. The tell: compliance goes up while motivation and creativity go down.

• ▸Team & current work-cycle stage: beginning / midpoint / recently finished a piece of work
• ▸Presenting symptom: what looks wrong right now (one line)
• ▸Effort check: is the problem low or misdirected motivational energy? (yes/no + note)
• ▸Strategy check: is the problem an ill-fitting or never-implemented performance plan? (yes/no + note)
• ▸Skill check: does the work exceed members' current knowledge/skill? (yes/no + note)
• ▸Information readiness: does the team have trustworthy, current data on requirements and resources? (yes/no)
• ▸Matched coaching function: motivational / consultative / educational
• ▸Timing fit: does the chosen function match the cycle stage? (yes/no — if no, wait or adjust)
• ▸Coach and delivery: who provides it and via which existing support system