Personal Playbook · Book Notes

Trillion Dollar
Coach

Bill Campbell's Leadership Playbook — Personalised for Vivid

Bill Campbell was the football coach nobody in tech hired for his football skills. An ex-Columbia offensive coordinator who became CEO of Intuit, then the invisible hand behind Google, Apple, Amazon, and half of Sand Hill Road — coaching Eric Schmidt, Larry Page, Sergey Brin, Steve Jobs, Jeff Bezos, and Sheryl Sandberg, often simultaneously, almost always for free.

He died in 2016. Eric Schmidt, Jonathan Rosenberg, and Alan Eagle wrote this book to answer a question Campbell himself would have hated: what exactly did you do in those rooms? The answer, it turns out, is deceptively human. He listened. He showed up. He made people feel they mattered. And somehow that made billions.

What follows is a chapter-by-chapter breakdown — plus scenarios mapped to your actual life at Breville, sorzero, Kingdom of Hype, and beyond.

Chapter One

The Cadence of Fellow — Management Is a Service

"Your title makes you a manager. Your people make you a leader."

Campbell's first and most confrontational idea is this: management exists to serve people, not to command them. He believed that most leaders spend their energy managing up (impressing the board) and managing processes (hitting OKRs) when the only thing that compounds is the quality of the humans on your team.

He had a ritual. Before every meeting with a direct report, he would spend the first few minutes on the person — not the work. How are you doing? How's your partner? What's stressing you out right now? This wasn't small talk. It was intelligence gathering of the most important kind: what is this person's operating state, and what do they need from me today?

He also ran 1:1s with a very specific structure: the employee sets the agenda (not the manager). The manager's job is to listen, remove blockers, and ask the question that unlocks the next level of thinking. Campbell called this being a "thought partner," not a supervisor.

Key Principles
  • People first, then strategy. If the person is broken, the strategy is irrelevant.
  • 1:1s belong to the employee. You're there to coach, not to report out.
  • Ask "how are you?" and actually wait for the answer.
  • Your job as a leader is to identify and grow the potential in others — not to be the smartest person in the room.
  • Give people space to fail and room to own their wins.
Your Scenario · Breville AI Team
The cross-pod backend engineer who's quietly stretched thin

You have an engineer shared across pods — which means they're everyone's priority and nobody's responsibility to protect. Campbell would say: even if this person doesn't formally report to you, your job is to check in on their operating state. Are they overloaded? Are they being pulled into tasks that don't serve the AI pod's goals? Start your next informal catch-up with "how are you finding the split across pods right now?" and listen without immediately trying to solve. That 90-second conversation will earn you more trust and useful information than a quarterly review.

Your Scenario · sorzero
Running an SDR agent "team" — but you're also the founder

When you're building an n8n AI SDR workflow, Campbell's management-as-service principle applies to your future customers and collaborators. Who are you serving with sorzero? Design the agent not around your preferred logic, but around the operating state of the person receiving the outreach. Service-first thinking applies whether you're managing humans or designing agents.

Chapter Two

Build an Envelope of Trust — The Foundation of Everything

"Bill would always say that trust is the most important currency you have. And once you spend it, you can't get it back the same way."

Campbell was obsessive about confidentiality. Everything said in a coaching conversation stayed there. No exceptions. He also never took credit — publicly or privately — for the outcomes he helped create. This sounds obvious until you're in a meeting where you could take a tiny bit of credit and you don't.

The deeper insight here is about consistency. Trust isn't built in grand gestures. It's built (or eroded) in the thousand tiny moments where you either do what you said you'd do, or you don't. Public praise, private feedback. Always.

Key Principles
  • Confidentiality is non-negotiable. What happens in coaching stays there.
  • Trust is built in micro-moments, not keynote speeches.
  • Praise publicly. Correct privately. Never the reverse.
  • Be radically honest — but root it in the belief that the person can improve.
  • Consistency of behaviour over time is the only real trust signal.
Your Scenario · Breville AI Team
When your UX/AI Designer's concept gets shot down in a leadership meeting

If their work gets critiqued publicly and you say nothing in the room, you've made a trust withdrawal — even if you didn't intend to. Campbell's move: defend the work (not the person's feelings) in the room, then debrief privately with the designer about what you both learned. "I backed you in there because I think the direction is right. Let's talk about how to make the case stronger next time." That's a trust deposit and a coaching moment in one sentence.

Your Scenario · Personal
Multilingual, multicultural teams and trust signals

Having lived across 12 countries and worked across cultures, you already read trust signals with unusual sophistication. Different cultures express and test trust differently — in some, it comes from demonstrated competence first; in others, from personal relationship first. Your job — and Bill's — is to read which mode the person in front of you is in, and meet them there.

Chapter Three

Create the Team First — Team Over Individual Brilliance

"If you're the smartest person in the room, you've hired the wrong room."

Campbell believed that the team is the product — not the output the team produces. Get the team dynamics right, and the right outputs follow. Get them wrong, and no amount of individual brilliance saves you.

His approach had three pillars: hire people smarter than you in their domain; create genuine psychological safety (people must feel they can say "I don't know" without consequence); and resolve conflicts fast. Unresolved conflict is a rot that spreads. He also had a rule about peer praise — recognising a colleague's contribution as a team discipline, not a performative shoutout.

Key Principles
  • Team dynamics are the product. Optimise for the team before the roadmap.
  • Psychological safety is the substrate. Without it, nothing else works.
  • Resolve conflict quickly. Sitting in ambiguity costs more than a hard conversation.
  • Peer recognition is more powerful than manager recognition. Create rituals for it.
  • Hire people whose domain knowledge exceeds yours, then trust them in it.
Your Scenario · Breville AI Team
Running ChefSteps Intelligence across a multi-disciplinary pod

You have an LLM engineer, a UX/AI designer, and a shared backend engineer — three very different people with different mental models of what "done" means. Campbell would tell you: before the next sprint planning, spend 20 minutes on team health, not project health. What does each person find energising? Where are they uncertain? What do they need from each other that they're not getting?

Your Scenario · Kingdom of Hype / Startup Mode
Building with a small founding team (or solo)

When you founded your Shanghai and Berlin game studios, a small team with high trust punched well above its weight. Campbell's lesson scales down perfectly: even a 2–3 person founding team needs explicit rituals for psychological safety. Someone has to be able to say "I think we're building the wrong thing" without it becoming a relationship crisis.

"Your job as a manager is not to make the decisions. It's to make sure the right decisions get made."
— Bill Campbell
Chapter Four

The Power of Love — Caring Beyond the Transaction

"Bill loved people. Not abstractly. Specifically. He knew their kids' names, their health scares, their career anxieties. And he acted on that knowledge."

Campbell was a genuine practitioner of what the authors call "caring the whole person." He remembered the name of your kid's school. He called you on the anniversary of a death. He showed up at your hospital. Not because it was strategic — because he thought it was the right thing to do.

The business case, if you need one: psychological safety and belonging are the two strongest predictors of team performance per Google's Project Aristotle. Campbell got there by instinct decades before the research confirmed it. Know what matters to your people outside of work, and let it matter to you too.

Key Principles
  • Care about the whole person — their life, not just their output.
  • Genuine human connection is a performance multiplier, not a soft distraction.
  • Remember the details. The name of the kid. The health scare. The dream they mentioned once.
  • Show up when it matters most, even (especially) when it's not work-related.
  • Love isn't sentimentality — it's a commitment to someone's growth and wellbeing.
Your Scenario · Breville AI Team
When a team member goes quiet in standup

It's easy to let the pace justify not slowing down for human moments. Campbell would say that's exactly backwards. If your LLM engineer has been burning the candle on a tight Bedrock integration and goes quiet, that's your cue. One Slack message — "Hey, you've been quiet, just checking in" — is a Campbell move. It costs nothing and it's the difference between someone who stays and someone who updates their LinkedIn quietly on a Tuesday.

Your Scenario · Personal
Caring as a multilingual, globally mobile person

Having lived across 4 continents, you know intuitively that "care" looks different everywhere. In some cultures it means directness and challenge. In others, it's making tea and sitting with someone in silence. Campbell's lesson isn't to import an American version of warmth — it's to stay curious about what care means to the specific person in front of you, and then actually do that thing.

Chapter Five

The Throne and the Heir — Decision-Making and Succession

"Great CEOs don't surround themselves with yes-people. They build a team that will tell them when they're wrong — and then they actually listen."

Campbell had a simple rule for meetings: everyone speaks, the leader listens last, and the decision is made explicitly before people leave the room. He hated ambiguous outcomes. Walking out without knowing who owns what next was, to him, a failure of leadership.

He also coached leaders on managing boards: tell them the truth before they hear it elsewhere. No surprises. The moment a board member learns something important from someone other than the CEO, trust begins to collapse.

Key Principles
  • End every meeting with an explicit decision and named owner. No ambiguous exits.
  • The leader speaks last in debate. Listen to the room before closing.
  • Build successors as a matter of principle, not emergency.
  • No surprises upward. Tell stakeholders bad news yourself, before they hear it sideways.
  • Disagree vigorously in the room, then commit fully once the decision is made.
Your Scenario · Breville
Presenting AI ROI to a sceptical leadership layer

You're building a Global 1–10 consumer appeal scale and a ChefSteps Intelligence product while the ROI case for AI is still being established internally. Campbell's lesson: don't wait for the board to ask hard questions. Go to them first with the uncomfortable data. "Here's what's working. Here's what isn't yet. Here's what I need." Leaders who only bring good news eventually become untrustworthy — because everyone knows the bad news exists.

Your Scenario · Startup Founder Mode
Decision-making when you're the only adult in the room

In your game studio days, you were the founder, CEO, designer, and deciding vote — all at once. Campbell's framework still applies: build the habit of naming your decision explicitly and writing down who owns what next (even if that's always you). This discipline makes you faster, not slower, because you stop re-litigating the same decisions.

Chapter Six

Help Others — The Obligation to Grow and Give Back

"Bill never sent an invoice. He coached because he believed the world got better when people grew."

Campbell spent the final decades of his life in almost pure service mode. He wasn't building his brand or writing a book. He was in rooms, asking questions, helping people think more clearly, and refusing payment. The conclusion: the most leveraged thing a leader can do is multiply others' capacity, not their own.

Leaders who hoard power — who make themselves the bottleneck, who can't be disagreed with — are ultimately fragile. Campbell's model is the inverse: the more you give, the more the network of people who trust and advocate for you compounds over time. He had no LinkedIn profile. His reputation was entirely peer-to-peer, and it outlasted him.

Key Principles
  • The most compounding investment you make is in other people's growth.
  • Help without expectation of return — that's what builds lasting influence.
  • Make yourself replaceable on purpose. Build others into the roles they're growing toward.
  • Share knowledge generously. Gatekeeping is a slow career death.
  • Your reputation is the sum of how people describe you to others when you're not in the room.
Your Scenario · Breville
Running the AI Value Proposition Workshop

The goal of this room isn't to show people that you know more about AI than they do. It's to leave every participant with a mental model they can use without you. Design the workshop so it gives the tools away, not just the answers. The measure of success isn't "did they think it was great?" — it's "are they still using this framework six months later without needing to call you?"

Your Scenario · Future AI / Side Ventures
The Synbiote / FlavourMind / Kingdom of Hype ecosystem

Across your ventures you're building things at unusual intersections — biopolymers, sensory ML, corporate fantasy RPG. Campbell's lesson: the way you grow these is by being genuinely generous with your thinking. Write the thread. Do the talk. Share the design doc. Your unusual combination of backgrounds (HCI, food science, gaming, AI, biotech) is already remarkable. Let people see it.

Situational Playbook

What Would Bill Do?

Situation 01

Your team is underperforming on a deadline

You feel the urge to step in, take over, or escalate. Campbell would do none of those first.

→ Pull each person aside individually. Ask what's blocking them. Separate performance blockers (skills, resources) from wellbeing blockers (burnout, unclear direction). Fix the root, not the symptom. Only then escalate if genuinely needed.
Situation 02

A stakeholder heard bad news before you told them

Classic trust erosion event. Don't explain. Don't defend. Don't minimise.

→ Acknowledge it directly: "You should have heard this from me first. That's on me." Then explain what happened, what you're doing, and how you'll prevent the gap. Accountability without grovelling restores credibility fast.
Situation 03

You disagree with a decision made above you

You've argued your case. The decision went the other way. Now what?

→ Disagree in the room, vigorously. Once decided: execute fully. "Disagree and commit" isn't a cop-out — it's what separates professionals from politics-players. Tell your team the decision was made, own it with them, and focus on making it work.
Situation 04

A team member comes to you with a personal crisis

Work is clearly not top of mind for them right now. The project needs them.

→ Ask about the person first. Fully. Don't segue to the project. Say: "The work can wait — what do you need right now?" Then actually wait. Often people just need to feel that someone sees them. After that, figure out the work together.
Situation 05

You're pitching an AI initiative with uncertain ROI

Leadership wants confidence. The data isn't fully there yet.

→ Lead with what you know, what you don't, and what you need to find out. "Here's the hypothesis. Here's the signal we have. Here's the experiment that will tell us if it's real." Honesty about uncertainty is more trustworthy than performed confidence.
Situation 06

Meeting ends without a clear decision or owner

Classic meeting failure. Everyone nods, nobody knows what happens next.

→ Before anyone leaves, say explicitly: "Before we close — what did we decide, and who owns what by when?" Write it where everyone can see it. This one habit, practised consistently, makes you the person people trust to run a room.
Situation 07

You're starting a new venture (again)

Founder mode. Small team, big ambitions, everyone wearing seven hats.

→ Establish trust rituals before you establish processes. A weekly check-in that starts with "how are we doing as people?" before the roadmap. Explicit naming of decisions. Peer acknowledgement of good work. Cheap to build early, expensive to retrofit later.
Situation 08

You want to grow someone into more responsibility

They're good. You want them to be great. How does Campbell do it?

→ Give them the problem before the solution. "I have a challenge I want you to think through — come back to me with your read." Then when they do, ask questions first before correcting. Let them find the gap themselves. That's how competence becomes confidence.