The vibes illusion

It's June. A team just won a championship, and the cameras find the general manager on the ice, confetti in his hair, and a reporter shoves a microphone at him and asks the question everyone asks. How did you do it? And he says the word. Culture. We built a culture here. And everybody nods, because we all believe we know what that means — some magic in the room, some brotherhood, some vibe you can feel when you walk into the building but can't quite explain.

Here's my problem with that moment. Nobody ever asks the follow-up question. Built it out of what?

I'm Dr. MCB. I'm a psychiatrist, I've spent my career inside elite sport working on mental health and peak performance, and I co-wrote a book about exactly this — it's called The Psychology of High-Performance Sports Organizations. This series is the companion to that book, translated out of textbook language and into yours. And the whole argument starts with one uncomfortable claim: culture is not a vibe. It's not chemistry, it's not mystique, it's not the leadership group having a players-only meeting. Culture is an operating system. It's the invisible software running underneath everything you can see — and like any operating system, it was designed, whether or not anyone designed it on purpose.

So let's go down beneath the ice, into the machine room.

The myth of the right captain

Let's start with the myth, because it's a good one. It's the myth almost every fan, and honestly most front offices, carry around.

The myth goes like this: championship culture comes from having the right people. The right captain. A couple of strong personalities who "hold the room accountable." And once you win, winning takes over — success breeds culture, culture breeds success, the flywheel spins forever.

It's a beautiful story. Now watch it collapse.

A team wins it all. Same captain, same leadership group, same vibes. Eighteen months later, that same room is toxic. Guys are leaking to the media, the coach is fired mid-season, and everyone's asking what happened to the culture. Or run it the other way. A franchise goes out and signs the heart-and-soul veteran from a championship team — pays a premium specifically for his leadership — and nothing transfers. He's the same man. Same habits, same speeches, same standard. And the room doesn't move.

If culture lived inside the captain, it would travel with the captain. It doesn't. If culture came from winning, winners would never rot. They rot all the time.

Unless the captain was never the culture to begin with. Unless he was just the most visible app running on an operating system nobody could see — and when you moved him to a machine running different software, the app crashed.

That's the reframe this whole series hangs on. When you walk into a team's facility, everything you notice — the effort, the accountability, the way guys talk to each other — those are the apps. They're visible, they're what gets praised and blamed. But underneath the apps there's an operating system: who actually gets to know things, who's allowed to say things, what happens to the last person who said something, and how decisions really get made when the pressure spikes. That layer is invisible. And that layer decides whether the apps run or crash.

In the book, we call this whole architecture the High-Performance Culture Operating System. And the starting premise is blunt: organizations pour extraordinary money into the athlete's body — training, nutrition, sports science, video — and almost nothing into the system around the athlete. The investment in the body far outpaces the investment in the machine the body has to perform inside.

Dysfunction is adaptation, not failure

So if culture is an operating system, what's it made of? In the book we map it as seven layers, each one answering a question, and each one stacked on the one below it. I'm not going to march you through all seven like a syllabus. But I want you to feel the shape of it, because the shape is the point.

The bottom layers are diagnostic — they're about seeing clearly. The first question is simply: what are we actually dealing with? What pressures is this environment loaded with? The second question — and this one is load-bearing for everything above it — is: can anyone here tell the truth? Can a person in this building say a hard thing to a person above them without paying for it? And the third: what's actually broken? Because the problem everyone's complaining about is rarely the real problem.

The middle layers are operational — they're about how the machine runs. When pressure rises, does your decision-making hold, or does it fracture into improvisation and panic? And are the systems that touch actual human beings — how rookies arrive, how veterans exit, how injuries get disclosed — designed for people, or designed just to extract performance from them?

And the top layers are protective. Can you stay grounded when the outside world — fans, media, sponsors, agents — is screaming? And the last question, my favorite: will any of this survive you? Because if the culture leaves when the leader leaves, it was never a system. It was a personality with a whistle.

Here's why the stacking matters. You cannot skip a layer. And yet skipping layers is the entire culture-change industry. A team has a scandal or a losing streak, so leadership buys the middle layers — new values on the wall, a leadership retreat, maybe a mental-skills workshop — while the foundation question, can anyone here tell the truth, is still a no. And when the answer to that question is no, every layer above it is running on bad data. The organization is navigating on false information and doesn't know it.

Which brings me to the single most important sentence in the book, the central reframe everything else depends on: dysfunction is adaptation, not failure.

Let me say that in plain language. When people in a high-performance environment go silent, hide injuries, hoard information, think short-term — we love to call that a character problem. Weak people, selfish people, bad apples. The book's argument is that it's almost never that. Those behaviors are rational responses to the structure. The athlete who hides an injury is doing math, and the math is correct. The staffer who stops reporting bad news upward learned — by watching what happened to the last person who did — that honesty costs more than silence. Nobody's broken. The software is producing exactly the output it was designed to produce. So diagnose the structure before you label the person. Stop trying to make individuals braver, and start redesigning the architecture that made silence the smart move.

Nadia, and the rules nobody wrote down

Let me make that concrete with a story from the book. It's a composite — details changed, no real names — but if you've worked anywhere, you'll recognize it.

Nadia was a video coordinator. Five seasons with the club — she'd outlasted three head coaches and a full front-office shake-up. Every night she built overnight clip packages, tactical breakdowns, and she'd developed something no dashboard can replicate: five years of pattern recognition about how opponents actually behave. Then a new coach arrives with his own analytics staff. First week, he tells her the packages she'd built for four years are "not what we need going forward" — and doesn't say what he needs instead. His analytics lead starts quietly duplicating her work. When she raises it, she's told not to step on toes.

So Nadia adapts. She stops staying past midnight. She stops flagging the cross-game patterns. And one day she notices something real: a divisional rival has changed its fourth-quarter defensive scheme three games in a row. She mentions it — once — to the analytics lead. He says, we've got it covered.

They lose that game by six points, on exactly the pattern she flagged. And Nadia sits in the back of the post-game review, hears the loss blamed on "adjustments we didn't anticipate" — and says nothing. Her contract was up in April. The structure had already told her what speaking would cost and what it would not change. Her contract wasn't renewed, five years of institutional knowledge left the building in a cardboard box, and the next video coordinator started from scratch.

Was Nadia a coward? No. She ran the numbers. In the book we call this the silence calculus: on one side of the ledger, everything speaking up could cost you — your job, your standing, your identity. On the other side, the odds the organization will actually act on what you say. When the cost outweighs the benefit, silence is the rational answer. And the structure — not the person — sets both sides of that equation.

And here's the mechanism underneath it, the engine of every culture on earth: people learn the rules not from what leaders say, but from what happens to the last person who spoke up. One person raises a concern and gets frozen out of the next meeting — silence spreads through the whole building. One person flags a problem and watches the organization actually act on it — voice becomes normal. That's it. That's culture. Not the words on the wall. The consequences in the hallway.

Why elite sport eats culture for breakfast

Now, you might be thinking — fine, but every workplace has politics and silence. Why does elite sport need its own book? Because elite sport isn't just a harder version of a normal workplace. It breaks the basic assumptions that normal workplaces are built on. In the book we map eight distinct pressure dimensions that make this environment uniquely hostile to healthy culture. Let me give you the four or five that hit hardest.

First: everyone is on a clock, and the clocks don't synchronize. The athlete's clock is biological — a body with maybe ten or fifteen good years, running out in real time. The coach's clock is his record — two to four years before the owner's patience expires. The owner's clock is an investment measured in decades. The agent's clock resets with every transaction. Everyone acts rationally inside their own window — the coach in a contract year genuinely cannot afford a three-year development plan — but the sum of those individual logics doesn't add up to a strategy. And the loudest clock always wins. During a playoff push, the coach's clock runs the room. The athlete's biological clock ticks underneath it all, unheard, until something breaks.

Second: it's zero-sum. There are always more players than roster spots, which means your teammates are also your competitors. That one fact reshapes everything — information gets hoarded instead of shared, because what you know might be the thing keeping you employed. And looming over every locker room is what the book bluntly calls the cliff: the average professional career is over before age thirty, and when it ends, income, structure, identity, and physical capacity all change at once. The cliff shapes behavior years in advance — every contract year, every injury, every moment an athlete weighs whether honesty is worth risking the only professional identity they've ever had.

Third, and this one I find people never really sit with: in this industry, the body is the workplace. In most jobs, the employee uses tools to create value. In elite sport, the employee is the tool — worker, instrument, and asset in one, depreciating with every use. So pain stops being a warning signal and becomes a variable in a career calculation. And notice the structural twist: the medical staff deciding whether you're fit to play are usually employed by the team that benefits from you playing. Most of those clinicians are careful, decent people — the problem isn't their judgment, it's the architecture that judgment sits inside. Athletes don't underreport concussions because they don't understand the risk. They underreport because the incentive structure around telling the truth is, at best, ambiguous.

Fourth: nothing is permanent. Rosters churn — some leagues turn over close to forty percent of a roster in a single offseason. Coaches cycle through in two or three years. Every relationship in the building carries an expiration date, so trust never gets past its earliest stage, and institutional memory keeps leaving in cardboard boxes, like Nadia's.

And fifth — the psychiatrist in me has to include this one — the pressure doesn't stay outside people. It gets inside their brains. Under sustained stress, the brain shifts resources away from the prefrontal cortex, the machinery for long-range planning, nuance, and weighing competing perspectives, toward fast threat response. Brilliant for a physical emergency. Terrible for a contract negotiation. The coach in month fourteen of a losing season is not making decisions with the same brain that started in September. And here's the cruel loop: the ability to notice your own judgment slipping runs on the same circuitry that's offline. Which is exactly why this book argues for structural safeguards over individual willpower — the system has to catch what the people inside it can no longer see.

Stack those pressures together and you get the answer to the question we opened with. Why do talent and money keep failing? Because talent and money buy better apps. They do nothing — nothing — for the operating system.

Three vital signs

So how would you actually know whether an organization's operating system is healthy? You can't survey vibes. But in the book we track three things you can watch — think of them as vital signs, three readings of the same underlying thing: how information flows under pressure.

The first is speed of truth: how long does it take between someone in the building knowing something and the organization being able to act on it? In healthy systems, problems surface in hours. In sick ones, they fester for months — and Nadia's fourth-quarter pattern loses you a game it never had to.

The second is whether speaking up is normal: do concerns and bad news get raised before they escalate, without the person raising them paying a social or career price?

The third is decision clarity: does everyone actually know who decides what, on what basis — and what happens when two values collide?

And here's where I want to be honest with you, because most hot takes about culture never are. Not everything in this book is proven to the same standard. Sport-specific research on these interventions is thin — one systematic review found only eleven qualifying studies on elite-athlete psychological interventions across twelve years. Eleven. So a lot of this architecture is adapted, carefully, from fields that faced the same problem and solved it at enormous human cost. Aviation built crew resource management after realizing communication failures in the cockpit — not mechanical defects — were killing people. Healthcare built non-punitive incident reporting for the same reason. And here's the detail I love: aviation didn't build its safety systems because flying was terrible. It built them because flying was valuable enough to justify making it survivable. That's the posture. Sport shares those industries' conditions — high stakes, compressed timelines, everything public — and is still catching up on the infrastructure. In the book, every tool is labeled honestly: validated instrument, or practitioner-developed heuristic. We tell you which is which. Confidence should be earned, not performed.

Back to you

Before we close, I want to take this out of the arena, because none of this is really about sport. You have an operating system too. Your company has one. Your kid's team has one.

So try this during your week. In your workplace, ask yourself the foundation question: can anyone here tell the truth? Not in theory — in practice. What happened to the last person who brought your boss genuinely bad news? Because everyone watched, and everyone updated their math. If you're a parent standing at the rink or the pitch, watch what actually gets rewarded on your kid's team — not what the coach says matters, but what earns playing time and what earns the bench. That's the real operating system, and your child is learning to read it faster than you are. And if you lead anything — a team, a department, a family — hold this question up to it: if I left tomorrow, what would still be standing? If the answer is nothing, you don't have a culture. You have a dependency.

This is the first of six. The next goes to the load-bearing layer — psychological safety, what it actually is and what it absolutely is not, because it is not softness. Then a toxic room and the road from dysfunction to championship standard. Then leadership under pressure, and what actually happens to decision-makers when the heat rises. Then the people inside the machine: the rookies, the veterans on the way out, the invisible staff like Nadia who hold the whole thing together. And finally the hardest question — how you build something that survives the next firing, the next budget cut, the next regime.

Culture is not a vibe. It's an operating system. And the system is producing exactly what it was designed to produce.

The only question is whether anyone designed it on purpose.