Trillion Dollar Coach: The Leadership Playbook from Silicon Valley's Bill Campbell

1. 1Establish trust before transacting: unlike most business relationships where trust sits alongside personal agendas and mutual exchange of value, make it first and foremost. Decide who you have a relationship with based on whether trust exists.
2. 2Keep your word without exception. If you say you will do something, do it — every time — so your word becomes reliably good, the way Bill's always was.
3. 3Practice loyalty as a demonstrated act, not a sentiment: stand up for people to those with power over them, especially when it costs you (Bill fought to keep Steve Jobs when he was let go in 1985).
4. 4Guard discretion absolutely: when someone shares something private, tell no one — not even the CEO who might feel entitled to know. Let people find out later that you protected the confidence.
5. 5Signal ability alongside intent — trust means people believe you have the talent, skills, power, and diligence to accomplish what you promised, not just good will.
6. 6Extend trust as freedom: free people to do their jobs and make decisions, operating from the belief that they want to do well and will.
7. 7Practice free-form (active) listening to build the safety trust requires: full undivided attention, no phone, no watch-glancing, Socratic questions — attend to the person first, then go into the issue. There is an order to it.

When Eric was CEO of Google, one of his team members was diagnosed with a serious medical condition but chose not to tell Eric or the team. The only person he told was Bill. Bill told no one — not the CEO, not the team — honoring the confidence completely. Eric later found out, and the lesson is in his reaction: rather than being annoyed that Bill had kept information from him, he was happy, because it proved Bill was so trustworthy. The discretion Bill showed the team member became the very evidence that made Bill worth trusting for everyone else. Discretion held under pressure compounds into reputation.

• If you tell someone you will do something, then treat it as binding — your word being reliably good is the foundation everything else rests on.
• If standing up for what's right for a person or team requires personal risk, then take it — loyalty is proven when it costs you (fighting to keep Jobs, Sundar speaking up).
• If someone shares something in confidence, then tell no one, even someone senior who might feel owed the information — discretion is not conditional on rank.
• If trust does not exist with someone, then you do not have a relationship worth building on — for Bill, no trust meant no relationship.
• If you trust someone, then free them to make their own decisions rather than controlling — trust means believing they want to do well and will.

• Treating trust as one currency among many (personal agenda, exchange of value) rather than first and foremost — the tell: you keep transacting with people you don't actually trust.
• Being a BSer who shades the truth to conform to their own story — the tell (per Hennessy): they start believing what they're saying, and are uncoachable because they aren't honest even with themselves.
• Extending loyalty only when it's free — the tell: you go quiet when standing up for someone would cost you politically.
• Breaking discretion by sharing 'just with' one trusted person or a superior — the tell: you rationalize a leak as harmless because of who you told.
• Claiming intent without ability — promising what you lack the skills, power, or diligence to deliver — the tell: your word is well-meant but repeatedly unmet.

• ▸Person: name the relationship you're assessing.
• ▸Word kept: list a recent commitment to them and whether you delivered exactly.
• ▸Loyalty test: where have you stood up for them at personal cost — or failed to?
• ▸Integrity check: where were you fully honest with them, and where did you shade it?
• ▸Ability match: what have you promised them that you can actually accomplish (skills, power, diligence)?
• ▸Discretion held: what did they share in confidence, and did you tell anyone?
• ▸Freedom given: which decisions have you freed them to make on their own?
• ▸Listening quality: in your last conversation, did you give full undivided attention before going into the issue?
• ▸Trust verdict: is trust present enough to be the basis of this relationship — yes or no?

1. 1Screen for coachability first: only invest in the humble, hungry, lifelong learners. If someone isn't coachable, don't build the relationship — safety is impossible without a willingness to be honest and to learn.
2. 2Practice free-form (active) listening: give full, undivided attention with no phone, no watch-glancing, no mentally rehearsing your reply. Really listen to the words, then go into the issue — there's an order to it.
3. 3Ask questions Socratically rather than dispensing answers. Get past the prepared question people bring by asking more and more questions until the real issue surfaces. Never just approve the prepared answer.
4. 4Deliver complete candor while retaining loyalty. Give hard, direct feedback (Bill used expletives and blunt confrontation) but pair it with the belief that the person can achieve remarkable things and back them when they take risks.
5. 5Make full identity welcome: encourage people to dress and be exactly as they are, because people sense when someone isn't being themselves and that breeds distrust.
6. 6Build trust by not conning people — Auerbach's rule: 'The players won't con me because I don't con them.' Depend-on-my-word integrity makes people feel secure.
7. 7Have their back on risk: the operational core of psychological safety at Google was that if you took a risk, your manager would support you. Make that backing explicit and repeated.
8. 8Combine safety with the other four Aristotle conditions — clear goals, meaningful roles, dependability, and impact — so people know the mission matters and their contribution counts.

When Jonathan Rosenberg was named to a magazine list of the tech industry's most notorious hard-asses, he showed up proud, printout on the table, and grinned. Bill did not grin: 'Jonathan, this is not something to be proud of!' He cut off Jonathan's weak defense with a stream of expletives and a dagger — 'What if I were to send this to your mother? What would she think?' The candor was total and uncomfortable, yet it worked because it sat inside a relationship of trust and loyalty; Bill then shared his 'it's the people' manifesto rather than just punishing. The safety came not from softness but from Jonathan knowing Bill was on his side even while confronting him. This is candor plus loyalty producing a climate where hard truths could be said and received.

• If the person isn't humble, hungry, or a lifelong learner, then don't coach them — you cannot build safety with someone unwilling to be honest.
• If someone asks for advice, then ask more questions first — they may only be asking for approval, and the prepared question hides the real issue.
• If you must deliver hard feedback, then pair candor with demonstrated loyalty and belief in the person, or the truth will register as attack rather than support.
• If people are hiding parts of themselves (dressing or acting like everyone else), then explicitly free them to be themselves — the pretense itself breeds distrust.
• If you want commitment and retention, then never con people — depend-on-my-word integrity is what makes them feel secure enough to take risks.

• Treating individuals rather than teams as the unit — you optimize stars and miss that almost everything great happens in teams. Tell: you invest in headcount and skills but team performance stagnates.
• Assuming safety means agreement or comfort — you avoid candor to keep the peace. Tell: no one voices dissent and problems surface late.
• Giving candor without loyalty — blunt feedback with no backing. Tell: people go quiet, defend themselves, or stop bringing hard questions.
• Fake listening — checking your phone, glancing at your watch, rehearsing your reply. Tell: people give you the prepared question and never reach the real issue.
• Answering the prepared question — dispensing advice/approval instead of probing. Tell: recurring surface problems you thought you'd solved.
• Believing best teams come from complementary skill sets or similar personalities — Google's study disproved this; the best teams are the ones with the most psychological safety. Tell: you hire for fit and skill mix but trust never forms.

• ▸Coachability check: is this person humble, hungry, a lifelong learner? (yes/no)
• ▸Full attention audit: what will I remove (phone, watch, wandering mind) in this conversation?
• ▸Real-issue questions: three probing questions to get past the prepared question
• ▸Candor point: the hard truth I owe this person, stated directly
• ▸Loyalty signal: how I'll show I have their back while saying it
• ▸Identity permission: what am I encouraging them to bring/be as their full self?
• ▸Risk-backing statement: the explicit 'if you take this risk, I'll support you' I will say
• ▸Aristotle conditions present: clear goal / meaningful role / dependability / impact (check each)

1. 1Name the tension explicitly. Accept that a senior team is populated with smart, aggressive, ambitious, strong-willed people with large egos who are natural rivals for advancement and resources. Do not pretend this rivalry away; Pichette calls it 'tension in the machine' and says you need it or you 'fade to irrelevance.'
2. 2Coach the whole team, not just the leader. Bill did not only meet Eric; he worked with Jonathan and several others and attended Eric's staff meetings regularly. Insert yourself into the group's actual working sessions, not only one-on-ones.
3. 3Work the team, then the problem. Focus on team dynamics, talent assessment, and finding the doers rather than solving the team's specific challenges — that's their job. When numbers get big and someone panics, your answer is 'we have the right team in place; they are working the problem.'
4. 4Run toward the biggest problems — the 'stinkers that fester and cause tension.' Do not let interpersonal friction sit; go straight at the source of festering conflict rather than routing around it.
5. 5Fill the gaps between people through behind-the-scenes conversations. Listen, observe, then seek people out individually and privately to bring the team back together, rather than only resolving in the room.
6. 6Build the five conditions Project Aristotle identified: psychological safety (people know their manager has their back when they take risks), clear goals, meaningful roles, dependability, and belief the mission has impact.
7. 7Align everyone on a common vision and set of goals so individual performance is subordinated to the group's — because teams that subordinate individual to collective performance generally outperform those that don't.
8. 8Show sincere, specific interest in people's lives — remember where their kids go to school. This is not sentiment; it's how you convert rivals into a community that has each other's backs.

At a Google meeting, the group was debating costs in some developing businesses. Ram Shriram raised a concern: the numbers were getting big — shouldn't they get more detail on how it was being handled? After some back-and-forth, Bill spoke up. He didn't dive into the cost analysis. Instead he said not to worry — they had the right team in place, and that team was working the problem. He worked the team, not the problem: his instinct was to reinforce trust in the group's capacity and dynamics rather than to relitigate the substance himself. Omid Kordestani described the effect of this approach across Google's senior team: 'What was very special about Google was the community aspect of the senior team. Bill was the glue in that process.' Sheryl Sandberg confirmed the pattern — 'You always had the sense he was building a team. With Bill... It was never just about me. It was always about the team.'

• If someone panics over a specific problem the team owns, then reaffirm your confidence in the team ('they are working the problem') rather than solving it yourself.
• If you sense a festering, tension-causing conflict (a 'stinker'), then run toward it immediately rather than avoiding it.
• If executives are positioning divisions against each other in status conflicts for resources and glory, then coach the whole team as a community, not just individuals defending silos.
• If a resolution requires candor people won't voice in the room, then move it to a behind-the-scenes one-on-one where you listen and observe.
• If a manager feels threatened by your coaching involvement, note that per the 2014 study it's the most insecure managers who resist suggestions — publicly accepting a coach is a sign of confidence, not weakness.

• Working the problem instead of the team — jumping in to solve the team's challenge yourself. Tell: you're doing their analytical job while the team dynamic goes untended.
• Treating internal competition as the scoreboard. Compensation, bonuses, recognition, office size and location become the way to keep score, and selfish individuals beat altruistic ones. Tell: people optimize for personal advancement over team success.
• Coaching only the leader. If you meet solely with the executive in charge, you miss the group dynamics — Bill's model was working the entire team and attending staff meetings.
• Suppressing tension entirely to keep peace. Tension is a good thing; kill it and you fade to irrelevance. Tell: the team is comfortable and conflict-free but no longer sharp or ambitious.
• Assuming talented all-stars don't need a coach. Pichette's first reaction — 'You have all these amazing people at Google. Why would they need a coach?' — is the trap; talent doesn't self-assemble into community. Tell: you leave the most capable team uncoached and let it drift into rivalry.

• ▸Common goal: state the single shared vision every member is marching toward
• ▸Rivalry map: name where members compete for advancement, resources, or glory
• ▸Biggest stinker: the festering conflict causing the most tension right now
• ▸Team dynamics vs. problem: what belongs to the team to solve vs. what you'll work on the team
• ▸Psychological safety check: can each person take a risk knowing you'll have their back? (Y/N per member)
• ▸Gap-fillers: which two people need a behind-the-scenes conversation, and what you'll listen for
• ▸Scoreboard audit: is success measured by team outcomes or by comp/office/recognition?
• ▸Personal knowledge: one specific life detail you know about each member (e.g., where their kids go to school)
• ▸Whole-team access: which staff meetings will you attend to coach the group, not just the leader?

1. 1Screen for team-first at the point of hire and staffing: the most important thing you look for in people is whether they will subjugate personal agenda to the team's, so weight this above raw résumé and skill.
2. 2Name the paramount principle out loud and repeatedly, as Bill did: 'you can't get anything done without a team' and 'the team wins has to be the most important thing.' State it until it is unmistakable culture, not decoration.
3. 3When a personal agenda collides with team need, reframe the choice as a loyalty appeal — show the person how the team needs them in a specific role, and offer a face-saving compromise rather than a fight.
4. 4Diagnose aberrant geniuses separately from the rest: keep their contribution flowing while coaching them past me-first behavior. Give them full support and space first ('Now that you fully supported him... No more arguments'), then hold them to leadership behavior.
5. 5Set a hard ethical floor: never tolerate lying, integrity lapses, harassment, or mistreatment of colleagues. Those are clean-cut removals, not coaching cases.
6. 6Track the cost side: count the hours you spend controlling one person's damage. When you are spending hours upon hours arguing and refereeing, that is the tell the behavior has exceeded the contribution.
7. 7Build trust before you demand task performance — get to know the person beyond skill set, because trusting teams disagree without emotional rancor and reach better decisions.

In 2004 Google faced raw feelings over the pending IPO, how to structure the company, and pressure for Eric Schmidt to step down as chairman. Bill assessed that Eric was hurt but that the team needed him to stay, and judged Eric the best person to remain chairman for the foreseeable future. Rather than fight the whole battle at once, Bill slept on it and called Eric back the next day. He led with the loyalty appeal — 'You can't leave, the team needs you' — then offered a reasonable compromise: step down as chairman for now, stay as CEO, and Bill would see to it that Eric got reinstated as chairman before long. He explicitly told Eric this was not a fight to have today. The move subordinated Eric's wounded pride to the team's need for stability while preserving his standing.

• If a person's personal agenda conflicts with the team's need, then appeal to loyalty and offer a face-saving compromise before treating it as a fight to win today.
• If a talented person shows me-first behavior but does not cross ethical lines, then coach them and give full support first — do not remove them.
• If someone lies, breaches integrity, harasses, or mistreats colleagues, then remove them; this is the easy, clear-cut case.
• If you are spending hours upon hours controlling one person's damage or arguing with them, then their behavior has gone too far to tolerate.
• If a relationship is new, then invest in trust and knowing the person before pushing on the task, because trust makes later disagreement productive rather than corrosive.

• Confusing loyalty with softness — Bill diagnosed his own coaching failure at Columbia as 'too much compassion,' lacking the 'dispassionate toughness' the team needed. Tell: you protect a person from hard truth to spare feelings and the team underperforms.
• Getting straight to the task and skipping trust — the technologist reflex of 'first prove how smart you are, then maybe I'll trust you.' Tell: task conflict keeps spilling into personal, emotional rancor and morale drops.
• Tolerating an aberrant genius indefinitely because their output is dazzling. Tell: resentment creeps through the team, people go quiet in meetings, and management time gets swallowed.
• Winning the argument instead of the person. Tell: hours spent arguing that are 'rarely constructive' — you were right but the team is still fractured.
• Rewarding individual credit-seeking. Tell: members put energy into personal gains at the expense of peer relationships, and the me-first attitude barges in.

• ▸Situation: one line naming the personal agenda vs. team need in tension
• ▸Team need at stake: what the team specifically loses if this isn't resolved
• ▸Person's stake / pride: what this person is protecting (status, credit, role)
• ▸Ethical-line check: has any line been crossed (lying, integrity, harassment)? Yes = remove, stop here
• ▸Contribution vs. cost: hours/week you spend controlling their damage vs. value they add
• ▸Loyalty appeal: the exact 'the team needs you' sentence you'll say
• ▸Compromise offered: the reasonable, face-saving trade that serves the team
• ▸Timing: is this a fight to have today, or one to defer? Note why

1. 1Before deciding, gather the team and surface every perspective in the room—make the debate real, not a formality. Bill insisted on airing 'the elephants in the room,' the biggest problems, first.
2. 2Anchor the decision to an immutable first principle rather than the loudest voice or short-term pressure. For Bill at Intuit, the principle was that 'anything less than operational excellence wouldn't be tolerated.'
3. 3Distinguish between short-term optics and the durable cause. Ask what you are actually protecting—the numbers, the project, the team, or the culture—and name it explicitly.
4. 4Recognize when the time for debate is over. Strong managers close the discussion decisively rather than letting it drift or festering into false conflict.
5. 5When the best idea does not emerge on its own, break the tie yourself and commit to it out loud so the team stays aligned and moving.
6. 6Fill the communication gaps that follow a hard call—address misread comments and slights fast, before an inadvertent 'fissure' turns into a crisis.
7. 7When things are going badly, lead harder: recommit to the cause, show loyalty, and make the decision that keeps people from bailing.

When Bill was CEO of Intuit, a rough quarter threatened the revenue and profit targets. Most of the board was willing to tolerate the miss, arguing that long-term growth mattered more than short-term numbers. Bill surfaced their view, then disagreed and made the call: get leaner and make the numbers. His reasoning wasn't the numbers themselves—it was the first principle: 'That is the culture we want to have around here,' where anything less than operational excellence wouldn't be tolerated. He reframed the trade-off, arguing that instilling operational discipline was itself an investment in long-term success, not a sacrifice of it. He broke the tie against the board and kept the company aligned around delivering results for the team, customers, and shareholders.

• If the debate has fully aired every perspective and no best idea emerges, then break the tie and decide yourself—do not let it drift.
• If a choice pits short-term optics against an immutable principle like operational excellence, then rule on the principle and explain why.
• If the company or project is failing, then decide based on protecting what you've built and the cause, even if it costs you your job—as Bill did in choosing to sell GO.
• If things are going badly, then increase your visible loyalty, commitment, and decisiveness rather than retreating or venting anger.
• If a decision left a communication gap or a misread slight, then close it immediately before it festers into a false crisis.

• Venting instead of leading in a low moment. Bill yelled at his Columbia team after a tough loss and 'lost them'—the tell is a leader assigning blame in the locker room instead of making a decision that helps.
• Deciding to please the room or the board rather than on principle. The tell is a leader tolerating a miss because it's 'more important to invest in the future' without naming the culture cost.
• Letting debate run without a close. The tell is unresolved issues carried over meeting to meeting with no owner making the call.
• Ignoring inadvertent fissures. Eric misread one comment and stewed for a full week, arriving 'gunning for battle'—the tell is emotional escalation far out of whack with reality.
• Confusing loyalty to the entity with loyalty to the cause. The tell is clinging to a dying company for financial salvage instead of protecting the work, as Bill did by selling GO to preserve the project.

• ▸Decision to be made: state the single question in one sentence.
• ▸Perspectives surfaced: list every stakeholder view, including the elephant in the room.
• ▸Governing first principle: name the immutable value this call must honor (e.g., operational excellence).
• ▸Short-term vs. cause: write what looks costly now vs. what you're actually protecting long-term.
• ▸Best idea emerged? yes/no—if no, you break the tie.
• ▸The decision + owner: state the call and who owns execution.
• ▸Alignment message: one line you'll say aloud so the team stays moving.
• ▸Communication gaps to close: name any misread comment or slight to address before it festers.

1. 1Coach the whole team, not just the leader. Attend staff meetings on a regular basis, walk the halls, and get to know every member — Bill worked with Jonathan and several others at Google, not only Eric.
2. 2Screen for and demand a 'team-first' attitude. Look for people who will subjugate their personal agenda to the team's when necessary; make it the top thing you expect in people.
3. 3Convert a team of rivals into a community by aligning them around a common vision and shared goals, so members put aside status conflicts and internal competition.
4. 4Build strong mechanisms for making decisions and resolving conflicts so ambitious, strong-willed egos don't default to keeping score via bonuses, recognition, or office size.
5. 5Diversify the team deliberately — put your bias blinders on and include more women, because the most effective teams have everyone contribute, read emotional states well, and include more women.
6. 6Use compensation as a signaling device for recognition, respect, and status. Pay generously; the money isn't only about money — it ties people to the goals of the company.
7. 7Tolerate and even protect high-value difficult people as long as their behavior isn't unethical or abusive and their value outweighs the toll it takes on colleagues and the team.
8. 8Ensure everyone contributes in discussions rather than letting one or two people dominate — this is what makes a team smarter than the sum of its individual IQs.

In 2004, feelings were rubbed raw at Google over the pending IPO and discussions about whether Eric should step down as chairman. Eric called Bill and, full of pride and hurt, said he was going to quit Google. Rather than argue, Bill asked simply, 'When?' — a coach's question that surfaced the real stakes. Recognizing that 'the greatest team in technology was about to break up,' Bill treated the situation as a team problem, not an individual grievance. With the deciding board meeting only two days away, he 'got to work' shaping the team and putting the right players in the right positions. Bill acted on his guiding principle that 'you can't get anything done without a team' and that the team is paramount, keeping Google's executive team intact.

• If a member repeatedly subjugates team success to personal career advancement, then treat it as a team-first failure, not a performance nuance.
• If a difficult person's behavior is unethical or abusive, then remove them; if not and their value outweighs the toll, then tolerate and even protect them.
• If one or two people dominate discussions, then intervene so everyone contributes — dominance lowers the team's collective intelligence.
• If a senior role opens, then keep searching for qualified women — 'you can always find a woman for a job, it may just take a little longer.'
• If an executive resists having a coach sit in on staff meetings, then reframe it: publicly accepting a coach is a sign of confidence, while insecure managers feel threatened by suggestions.

• Coaching only the leader. Tell: the executive team still fractures because you never worked with the whole team the way Bill sat in Eric's staff meetings.
• Letting internal competition take center stage. Tell: compensation, bonuses, recognition, and office size/location become ways to keep score, and selfish individuals beat altruistic ones.
• Treating compensation as purely economic. Tell: you pay 'fairly' but people feel unrecognized, because you missed that money signals respect and status.
• Building a homogeneous team. Tell: discussions are dominated by one or two voices and the team is no smarter than its individual IQs — a sign you skipped the diversity and contribution factors.
• Cutting every difficult person. Tell: you lose high-value contributors whose worth outweighed the toll, mistaking friction for un-tolerable behavior.

• ▸Common vision/goal: state the single shared objective the whole team marches toward.
• ▸Team members coached: list who you actually work with beyond the leader.
• ▸Meeting presence: note which staff meetings you attend regularly.
• ▸Status conflicts: identify where rivalry or silo positioning is keeping score.
• ▸Decision/conflict mechanism: describe how this team makes decisions and resolves disputes.
• ▸Contribution check: mark who dominates and who stays silent in discussions.
• ▸Diversity of team: record whether senior candidate searches included women.
• ▸Compensation signal: note whether pay is recognizing respect/status, not just economics.
• ▸Difficult-member review: name high-friction people and whether value outweighs the toll.

1. 1Treat teams, not individuals, as the fundamental building block of the organization—when you diagnose or design for results, start at the team level, because in Google's people analytics work almost everything great happened in teams.
2. 2Build the five conditions Project Aristotle identified into each team you run: psychological safety, clear goals, meaningful roles, dependability, and confidence that the mission matters.
3. 3Establish psychological safety concretely by having your team members' backs when they take risks—make it known that a manager stands up for people rather than punishing bold moves.
4. 4Adopt performance-oriented management techniques—monitoring, targeting, incentives—because the 2017 manufacturing study found they mattered as much as R&D, IT investment, and worker skill for plant performance.
5. 5Coach through management excellence, not dictation: make people feel valued by being in the room with you, listen, and pay attention, since the more talented the subordinate, the less they respond to being told what to do.
6. 6Meet with your key leaders individually every week or two, as Bill did with Eric and Jonathan, to work through their specific challenges as they grow the business.
7. 7Give credit away and take responsibility for making people better—shine the spotlight on others while helping them stand on their own, which compounds into company-level results over time.
8. 8Teach and open-source what works: institutionalize the practices via internal seminars so principles pass to the next generation of leaders rather than dying with one person.

Within nine months of joining Apple, Bill was promoted to VP of sales and marketing and put in charge of the Macintosh launch, which included a Super Bowl ad slot. Executives got cold feet, called the ad too costly and controversial, and an Apple sales executive even found a buyer to sell the airtime off. Asked by Floyd what to do, Bill said, 'Fuck it! Let's run it,' and they ran it without telling the board they had an out. It became the most popular spot of the game and, per a 2017 LA Times column, the 'only great Super Bowl commercial ever,' ushering in the modern Super Bowl ad era. The value creation here came from a leader taking a decisive bet and backing his team's judgment. Scaled across companies—Apple and Google each grew to several-hundred-billion-dollar market caps under his coaching—the same instinct to move quickly and back people produced well over a trillion dollars in value.

• If you want to improve organizational outcomes, then intervene at the team level first—individual optimization misses where most great work actually happens.
• If a direct report is talented, then don't tell them what to do; make them feel valued, listen, and coach—command triggers less response the more capable the person is.
• If someone takes a risk you asked for, then have their back—psychological safety is what keeps risk-taking alive.
• If you're weighing what drives results, then invest in good management practices alongside R&D and IT, because studies rate them as comparably important (22 percent of revenue variance in video games versus 7 percent for creative design).
• If knowledge lives only in one leader's head, then run seminars to transfer it, or the value is lost when that person leaves.

• Managing as a dictator—telling people what to do; the tell is that talented subordinates quietly don't respond or comply.
• Optimizing individuals in isolation instead of teams; the tell is strong solo performers but weak collective output and no shared sense of mission.
• Taking credit for accomplishments you coached; the tell is that people stop bringing you their real problems and blind spots go unaddressed.
• Underinvesting in management because you assume the creative or technical work is what matters; the tell is that strong design or R&D still fails to convert into revenue—recall design was only 7 percent of video game revenue variance.
• Chasing 'hard-edged dispassion' from a zero-sum playbook in a business context; the tell is disengagement, because compassion and putting people first is what actually drove Bill's business success where it failed on the football field.

• ▸Team & mission: name the team and the outcome it exists to produce
• ▸Psychological safety: how do members know you'll back their risks? (list one concrete action)
• ▸Clarity: state the team's goals in one sentence each member could repeat
• ▸Meaning: for each role, note why it matters to the person doing it
• ▸Dependability: identify who reliably delivers and where handoffs break
• ▸Impact: what evidence shows the mission makes a difference?
• ▸Management practices in place: monitoring / targeting / incentives (mark which exist)
• ▸Coaching cadence: date of last 1:1 with each key leader and next scheduled
• ▸Knowledge transfer: what practice here is documented/taught to the next generation?

1. 1Reframe your job: your title makes you a manager, but your people make you a leader. Measure success by how successful you make the people around you, not by your own output or spotlight.
2. 2Show sincere interest in each person's whole life, not just their work. Learn where their kids go to school; remember the details of their lives and return to them in conversation.
3. 3Treat everyone you meet—regardless of rank—with dignity and respect. Practice this in small daily choices, not just formal reviews.
4. 4Reject cookie-cutter development. Read each person's story and background, then tailor your growth and leadership approach to the individual (Scott Cook's 'technicolor rainbow,' not 'any color as long as it's black').
5. 5Combine support with challenge: tear apart weak proposals, push people to produce something stronger, then stand behind them publicly. That is tough love, not softness.
6. 6Build psychological safety so people know that if they take risks, you will have their back. Pair that with clear goals, meaningful roles, and a mission people believe matters.
7. 7Take responsibility for making people better without taking credit for their accomplishments. Shine the spotlight on them; stay in the shadows yourself.
8. 8Coach in the moments a formal coach never sees—get in the arena, roll up your sleeves, hold up a mirror to blind spots, and hold people accountable for sore spots.

When Donna Dubinsky, a young Apple manager, challenged a distribution plan from Steve Jobs himself in the mid-1980s, her boss's boss was Bill Campbell. Bill did not simply protect her or simply crush her. He dished out tough love: he tore her proposal apart and pushed her to come up with something stronger. Once she produced better work, he stood up for her against the pressure from above. This is people-first management in one act—he prioritized her development and eventual success over comfort, and over deference to power. He challenged her hard because he believed in her potential, then used his own position to have her back. The result was a stronger proposal and a manager who grew, which is what a coach exists to produce.

• If someone brings you a weak proposal, then tear it apart and demand a stronger version—but only if you also commit to backing them once they deliver.
• If a person takes a legitimate risk and it goes wrong, then have their back, so they know the safety is real and keep taking risks.
• If you're tempted to apply one standard development approach to everyone, then stop and start from that person's individual story and background instead.
• If success is being credited to you, then redirect it—take responsibility for making people better without taking the credit for their wins.
• If you only know a report's work output but not their life, then invest in the personal (family, background) until you can remember details like where their kids go to school.

• Confusing kindness with only-softness: Bill named 'dispassionate toughness'—the willingness to be hard when needed—as the thing he lacked as a football coach. The tell: you avoid tearing apart weak work because you don't want to upset people, so people stop growing.
• Support without challenge: you provide safety but never push, so people never produce the stronger version. The tell: proposals never improve after your feedback.
• Taking the spotlight: you make people successful but then absorb the credit. The tell: your name is on the wins and your team feels invisible.
• Cookie-cutter development: 'any color as long as it's black.' The tell: you use the same growth playbook on every person regardless of their story.
• Fake people-first: giving lip service to putting people first without the daily behaviors. The tell: you claim to value people but can't recall a single personal detail about them or a time you had their back under pressure.

• ▸Person: name of the report or teammate you're focusing on
• ▸Their story: one thing about their background/life that shapes how you coach them
• ▸Personal detail I know: e.g., where their kids go to school—fill it, don't leave blank
• ▸Challenge given: the weak spot I pushed them to make stronger this week
• ▸Support given: how I had their back / stood up for them
• ▸Credit routed to them: the win I made sure went to their name, not mine
• ▸Safety test: a risk they took—did I back it, yes/no?
• ▸Tailored next step: the individualized growth move for this specific person

1. 1Practice free-form listening: when someone brings you an issue, put your full attention on them, listen to whatever is going on before offering anything. Bill would give a hug, listen, and only then respond.
2. 2Lead with questions rather than answers. Get off strategy and onto leadership and people—ask about the person's story, background, and growth challenges instead of prescribing a fixed 'cookie-cutter' solution.
3. 3Treat each person as unique. Reject the 'any color as long as it's black' approach; adapt your coaching to each individual's career goals and life choices ('a technicolor rainbow').
4. 4Give candid feedback coupled with caring: hold up a mirror so people see their blind spots, hold them accountable for their sore spots, and do it while making clear how much you care.
5. 5Tell a story instead of dictating. When someone faces a decision, spin a story that helps them gain perspective, draw insight, or reach the decision themselves.
6. 6Take responsibility for making people better without taking credit for their accomplishments—get in the arena to help them realize potential, don't just praise it from the sidelines.
7. 7Be an evangelist for courage: push people to stand on their own so you 'build them to last,' remaining available for the many moments a formal coach never sees.

When John Doerr introduced Bill to Intuit's Scott Cook, who was looking to replace himself as CEO, Scott wasn't impressed at first. Their first meeting stayed on business and strategy and went nowhere. A couple of months later, with still no new CEO, Scott agreed to meet again, and they walked a Palo Alto neighborhood together. This time they got off strategy and talked about leadership and people—and clicked. Scott saw that other candidates had a 'cookie-cutter approach to developing people,' while Bill 'appreciated that each person had a different story and background' and was nuanced in how he approached growth challenges. Scott had wanted a way to grow his people that he couldn't manage himself; Bill was great at exactly that, and became Intuit's CEO in 1994. The lesson: the coaching relationship formed not over the transactional business talk but over the walk about people.

• If a formal coach only sees a fraction of the coachable moments, then it's on you to coach employees, colleagues, and even sometimes your boss.
• If someone brings you a problem, then listen free-form and ask questions first—don't dictate the answer.
• If each person has a different story and background, then abandon the cookie-cutter approach and tailor growth challenges individually.
• If a team member's behavior isn't unethical or abusive and their value outweighs the toll, then tolerate and even protect them while coaching.
• If you're compensating someone, then treat pay as emotional signaling of recognition, respect, and status—not just economic value—because money's not about money.

• Doling out words of wisdom like a mentor instead of rolling up your sleeves—the tell: you believe in someone's potential but never get in the arena to help them realize it.
• Using a cookie-cutter, 'any color as long as it's black' approach—the tell: you give everyone the same advice regardless of their story, goals, or life choices.
• Giving candor without care (or care without candor)—the tell: feedback lands as criticism, or nobody's blind spots ever get named.
• Overlooking management culture when chasing performance—the tell: you treat people as an asset in slogans but never invest in being 'a good coach,' the top behavior in Google's 2008 study.
• Dictating decisions instead of coaching toward them—the tell: people can't stand on their own and aren't 'built to last' when you leave.

• ▸Person + their story: one-line reminder of their background, career goals, and life choices
• ▸Listen-first note: what's actually going on for them (fill after free-form listening, not before)
• ▸Open questions to ask: 2-3 questions that get off strategy and onto people/leadership
• ▸Blind spot to mirror: the sore spot to name candidly, plus how you'll show you care
• ▸Accountability ask: the specific thing they'll own working through
• ▸Story to tell: a relevant story that helps them draw the insight themselves
• ▸Credit check: how you'll make them better without taking credit
• ▸Courage nudge: where they need encouragement to stand on their own

1. 1Deliver feedback in the moment or as close to it as possible — don't bank it for the performance review. As Scott Cook says, 'A coach coaches in the moment. It's more real and more authentic.'
2. 2State exactly what you think, holding a strict standard of no gap between statement and fact. Say the hard thing plainly, even if it's a harsh opinion (Bill: 'Your website is a piece of shit!').
3. 3Pair every negative message with a genuine signal of caring — a grin, a hug, humor, a prop — so the person knows the criticism comes from wanting them to succeed, not from ego.
4. 4Keep critical feedback private and one-on-one; reserve public statements for the message being safe to hear in front of others. If the feedback is negative, deliver it privately.
5. 5Make the point task-specific: name the exact behavior or artifact (the interception, the website, the nongrowth outcome), not the person's character.
6. 6End by asking questions and listening rather than prescribing the fix — don't 'stick it in their ear.' Tell a story about why, then let them figure out what to do.
7. 7Anticipate the emotional aftermath. Where the message is bruising, arrange follow-up support so the person leaves charged up, not diminished.

Dan Rosensweig had just saved his company from failure and his team was celebrating. Bill walked in wearing an accountant's green eyeshade, greeting people by name, then arrived at Dan's door and said, 'Congratulations, you saved the company. You are now the most successful nongrowth CEO in the valley! The accountants may be happy, but that's about it, because that's not what you came here to do, is it?' He hugged Dan and chucked the eyeshade at him. The message was a slap — Dan had solved only one problem when he'd come to grow the company — but it landed because the humor and the prop signaled Bill cared enough to wear that thing. Dan felt the truth, not the sting, and got back to work. The formula: candid message (nongrowth CEO) + caring delivery (humor, hug) = the person feels better, not crummy.

• If the feedback is negative, then deliver it privately and one-on-one — never chew someone out in front of the team.
• If you're tempted to wait for the review cycle, then give it now instead; delayed feedback is 'too little, too late.'
• If the message is brutal, then attach an explicit caring signal (humor, hug, story of why) so it 'comes from a place of caring.'
• If someone will be shaken by a hard message, then arrange follow-up support in advance — as Bill did by asking Dave Kinser to check on the executive afterward.
• If you're about to tell someone exactly what to do, then stop and tell a story about why instead, then let them figure out the how.

• Softening the truth to protect feelings — creating a gap between your statements and fact. Tell: the person leaves reassured but unchanged, and the real problem persists.
• Saving feedback for the annual review. Tell: your 'coaching' arrives long after the moment that mattered and feels like judgment, not help.
• Delivering candor with no caring attached. Tell: the person leaves deflated and diminished rather than 'charged up about it.'
• Criticizing someone publicly. Tell: the person feels humiliated and defensive instead of supported; trust erodes.
• Attacking the person instead of the task, or immediately prescribing the fix ('sticking it in their ear'). Tell: no buy-in, no ownership, and they don't internalize the lesson.

• ▸Person + setting: name them and confirm it's private if the message is negative.
• ▸Task/behavior observed: the specific thing (artifact, decision, play), not a character trait.
• ▸The honest statement: what you actually think, said plainly — no gap from fact.
• ▸Caring signal: the humor, gesture, or 'why I want you to win' line you'll pair it with.
• ▸Why it matters (story, not order): the story that helps them connect and buy in.
• ▸Timing check: is this now / today? If not, why the delay is acceptable.
• ▸Question to hand it back: the open question that lets them figure out the fix.
• ▸Follow-up support: who checks in afterward, and when.

1. 1Learn each person's life outside work: their family members' names, where they come from, what they care about. Bill knew Bruno the caddie's wife and sons, hosted them at his Palo Alto and Montana homes.
2. 2Open team meetings with socioemotional communication before business — trip reports, thank-yous, or stories about family and weekends. This warms the room and improves the decision-making that follows.
3. 3Walk the halls and get to know people beyond your direct reports. Bill's remit at Google wasn't just Eric and a few individuals; he got to know the whole team and made the entire team better.
4. 4Encourage people to bring their full selves to work, especially those who feel out of place. Tell them their background is a source of strength, not something to shed — an asset to be front and center.
5. 5Show up physically and warmly. Bill's signature was the bear hug that meant it; he treated everyone — CEO or caddie — exactly the same way.
6. 6Sustain community outside the office through recurring rituals: standing trips, dinners, neighborhood walks, coaching kids' sports together with the families.
7. 7Cheer successes and stay present through the hard times, so relationships hold true through many ups and a few downs.

When David (head of corporate development and legal affairs, an African American) told Bill about the pressure in Silicon Valley to conform — you're supposed to be technical or from a fancy business school, and if you're black you don't typically fit in — Bill didn't advise him to blend in. Instead he counseled David that so much about him was where he came from, and that he should hang on to that as a source of motivation and strength. Bill himself was neither technical nor a fancy-business-school type, yet he put his full identity front and center. As David puts it, Bill 'made me less self-conscious about the fact that I wasn't the same as everyone.' Bill gave the same advice to Brad Smith about his West Virginia accent ('it's not a bug, it's a feature') and to Shellye Archambeau. He cared about the whole person's identity, not just their functional role.

• If a team meeting starts with hot topics and no social talk, then insert a ritual (trip report, thank-you, story) first — the dynamic changes, you get more empathy and a better mood.
• If someone feels they don't fit and is pressured to conform, then affirm their background as strength and tell them to bring their whole self.
• If your remit is 'coach the leader,' then extend it to the whole team — knowing individuals as human beings, not just role-owners, is what makes the team better.
• If you meet anyone — regardless of title or status — then treat them the same way, because community is built on genuine care, not pedigree.
• If a relationship matters, then invest in it outside work through recurring rituals and showing up, so it survives the downs as well as the ups.

• Knowing people only as experts and owners of their roles, never as human beings — the tell: you can't tell how well your team works together or connects.
• Skipping the social opening as a waste of time — the tell: meetings feel jarring, low-empathy, and decisions get worse (Dick Costolo initially thought trip reports 'really weird' before seeing the difference).
• Pushing everyone toward a cookie-cutter mold — 'any color you want as long as it's black.' The tell: talented, different people shrink and shed what makes them strong.
• Giving the pat-on-the-back, don't-really-mean-it version of care — hugs, thank-yous, and interest that are performative rather than felt. The tell: people sense you don't mean it.
• Caring only about high-status coachees and networking contacts, not the caddie or the sports-bar staff. The tell: your circle is professionals who 'sort of knew' you, not people who love you.

• ▸Person & role: name and what they own at work
• ▸Family & home: partner, kids, where they're from — names you actually know
• ▸What they care about: interests, passions, life outside work
• ▸Their 'feature not a bug': the difference/background to affirm as strength
• ▸Recent hard time: what they're going through and how you showed up
• ▸Recent success: what to cheer and how you acknowledged it
• ▸Meeting-opener ritual: trip report / thank-you / story used to warm the room
• ▸Shared ritual: recurring trip, walk, dinner, or sport that sustains community

1. 1Treat the team, not the individual, as the fundamental building block — when a problem surfaces, first ask whether the right people are on it before touching the substance of the issue.
2. 2Work the team, then the problem: audit team dynamics, assess talents, and find the doers rather than solving the challenge yourself; solving it is their job.
3. 3Coach the whole group, not just the leader — sit in on staff meetings, walk the halls, and get to know people so your remit covers the community, not one executive.
4. 4Establish psychological safety by modeling relentless candor coupled with caring: state your mind directly, but do it so people leave charged up rather than deflated.
5. 5Fill the gaps between rivals through behind-the-scenes conversations — listen, observe, and seek people out privately to bring warring parties together instead of adjudicating who is right.
6. 6Run toward the biggest, festering, tension-causing problems (the 'stinkers') rather than avoiding them, and double down on core values when things turn south.
7. 7Extend the community beyond work through recurring shared gatherings — annual trips, meals, and events that mix people from different walks of life and generate bonds outside the office.

When Google and Apple clashed over phone features — with Bill close to Jobs and coaching Google's leaders, like his two children fighting — he refused to weigh in on the merits of either side, even though he knew the issues well. Instead of working the problem, he worked the team: he counseled Eric to put the right person, Alan Eustace, in charge as chief diplomat interfacing with Apple, whose job became ensuring the relationship didn't implode. Years later, during the Alphabet restructuring when the head of sales role sat empty, Bill again ignored operations, tactics, and strategy when talking with Omid Kordestani. He talked only about the team, wanting someone who cared about the company and its people to steer the transition — which described Omid exactly. In both cases the move was identical: ensure the right players are in place before anyone works the substance.

• If a problem or opportunity appears, then first confirm the right team is in place and working on it before diving into the details yourself.
• If negative feedback is warranted, then deliver it immediately, privately, and paired with genuine caring — never 'stick it in their ear' in public.
• If two people or divisions are in status conflict, then don't pick a winner — fill the gap through private, behind-the-scenes conversations that bring them together.
• If you want people to buy in, then tell them a story about why they're doing it rather than prescribing exactly what to do.
• If an executive resists having a coach involved in staff meetings, then remember that publicly accepting a coach signals confidence — it's the insecure who feel threatened.

• Working the problem instead of the team — jumping in to solve the substance yourself; the tell is that you're offering opinions on merits while team dynamics quietly fester.
• Letting internal competition become the scoreboard — compensation, bonuses, office size, and recognition become how people keep score; the tell is selfish individuals beating altruistic ones.
• Coaching only the leader and ignoring the group — the tell is that you never attend staff meetings or walk the halls, so you don't actually know the team.
• Delivering candor without caring, or caring without candor — the tell is people leaving feedback either crushed or unclear on what was actually wrong.
• Avoiding the 'stinker' problems that cause tension — the tell is unresolved friction between people that no one names, quietly poisoning the community.

• ▸Problem/opportunity on the table: state it in one sentence.
• ▸Right players check: are the right people on this? Name them.
• ▸Gaps between people: where is unresolved tension or rivalry sitting?
• ▸Psychological safety read: can members take interpersonal risks without fear? Evidence?
• ▸Behind-the-scenes moves: who do you need to seek out privately to fill a gap?
• ▸Candor-plus-caring feedback owed: to whom, said now, said privately?
• ▸Story to tell: what 'why' story replaces the instruction you were tempted to give?
• ▸Community touchpoint: what recurring shared event or gathering builds bonds beyond the task?