Inside the Team Brain: How Leaders Impact Performance
“The nervous system is the original social network.”
The other week I spoke at HRA26 in San Diego, the HR Advisory annual meeting, on a talk titled "Inside the Team Brain: Neuropsychology of Leadership, Safety, and Cohesion."
What I did not expect was how much the audience would talk back. People stayed after, came up to the mic, and found me at coffee, sharing their own stories of teams and leaders not functioning, sometimes not functioning at all.
One man told me about taking his first real vacation in years. He had been at his company for a long time, dedicated to the work, the kind of dedicated where you skip things and stay late and tell yourself it is worth it. He finally went away. When he came back, nothing had moved. Nobody had stepped up. Nobody had offered to help. He had known the whole time he was gone that a mountain would be waiting, which made the vacation itself hard, and the message of the experience was unmistakable. You are in this alone.
Another conversation was shorter and somehow harder. An HR leader at a scaling tech company asked what I did. When I told her, she said, "This is so needed." Then she said she was buying time until she could leave the industry entirely. The teams are too dysfunctional, the leaders too unprepared. She did not say it with bitterness. She said it with exhaustion. I have been thinking about her ever since, and about how under-trained most leaders are in the neuropsychology of leading cohesive, high-performing teams.
These two stories are not the same, but they are connected. One person was left alone with too much. One person is leaving because too many people are left alone with too much. And in both cases, the missing piece is not strategy or talent or pay. It is something much earlier in the chain. Teams are neurobiological systems. Trust, safety, and cohesion are not soft skills layered on top of the real work. They are the literal conditions the human brain requires before it can do hard thinking, take creative risks, or tell the truth.
The Team Brain
Every brain in your meeting is doing the same thing, every second, below conscious awareness. It is scanning. Is this safe? Is my status intact? Can I trust the person in front of me?
The amygdala fires first, in milliseconds, faster than thought. When it detects threat, the prefrontal cortex, the part responsible for reasoning, complex problem-solving, and perspective-taking, loses bandwidth. Naomi Eisenberger at UCLA ran a now-famous study showing that social rejection activates the same brain region as physical pain, the dorsal anterior cingulate cortex (Eisenberger, 2003). The brain does not file "left out of the meeting" and "twisted my ankle" under different categories. It uses the same alarm system for both.
This is the piece leaders most often underestimate. The eye-roll in a meeting, the interruption, the email that goes unanswered, the person who never gets called on, none of these register as small events in someone's nervous system. They register as pain. And the brain does what brains do with pain. It learns to avoid the source. People stop volunteering ideas, stop raising concerns, stop bringing the hard stuff forward. From the outside it can look like disengagement. From the inside it is self-protection. The man from San Diego, the one who came back from vacation to a mountain of work no one had touched, his nervous system was telling him something his colleagues' words were not. He was on his own.
And the team's brain is not just the sum of its members. We co-regulate. Mirror neurons mean we sync nervous systems with the people around us, instantly. In any group, the most powerful regulatory signal in the room is the leader. Your tone, your face, your presence either sends safety or sends threat, and the rest of the team adjusts in real time.
Why Safety Is a Performance Variable
Google's Project Aristotle studied 180 teams over two years, looking for what separated the high performers from the rest. It was not talent, tenure, or how senior the people on the team were. The single biggest predictor was psychological safety, what Amy Edmondson defines as the belief that one will not be punished or humiliated for speaking up with ideas, questions, concerns, or mistakes (Edmondson, 1999; Duhigg, 2016).
The finding that has stayed with me, and the one I think leaders most often miss, is the paradox. Safe teams reported more errors, not fewer. They actually made fewer, because problems surfaced early instead of staying hidden until they were expensive.
A team that never tells you about mistakes is not a team without mistakes. It is a team that has decided, somewhere in its collective nervous system, that silence is safer than honesty. The bad news does not disappear. It goes underground, and the cost of finding out late is almost always higher than the cost of hearing it early. This is what psychological safety is actually buying you. Not comfort. Not consensus. Earlier information.
The Loop Leaders Run, Whether They Know It or Not
Here is the loop I see every day. A leader is calm and present. The team feels safe. The team opens up and contributes. Results improve. Or a leader is anxious or critical. The team detects threat. The team protects itself and withdraws. Problems stay hidden until they cannot anymore.
The leader is always running one of these loops. There is no neutral. Tone, presence, response to mistakes, and access to airtime are not personality features. They are broadcast channels, and your team is reading every one of them, adjusting their nervous systems accordingly. This is why one tense Monday can undo weeks of careful culture building, and it is also why a single steady leader can change the operating temperature of an entire team.
Big decisions broadcast too. A third person at HRA26, a senior HR leader, told me her founder had just mandated a full return to office. Not because of a business need or a cultural one. Because she had raised concerns and data and the risk of losing people, and none of it landed. The policy itself was not what she kept circling back to. It was the message underneath it. Her voice did not matter. And if her voice did not matter, sitting in the seat she sat in, what did that say about everyone else's? That is a broadcast, and the team's nervous system received it loud and clear.
To Be Sure
None of this means leaders need to perform calm, or suppress real reactions, or pretend the work is not hard. Teams read inauthenticity quickly, and a leader who is regulating from a place of disconnection will not settle anyone's nervous system. The goal is not a flat affect. The goal is a leader who has done enough of their own work to stay present when the room gets hard, who can name what is difficult without dramatizing it, and who can take in bad news without making the messenger pay for delivering it.
Safety is not the absence of accountability. It is what makes accountability possible. High-performing teams have conflict. They just fight safely.
Something to Try: The Safety Signal Audit
This is a five-minute weekly self-check, not a performance review. One question a day, asked honestly.
1) Tone: Was my tone this week calm and consistent, or did it shift based on my stress?
2) Presence: Did I give my full attention in 1:1s and team meetings, or was I distracted?
3) Mistakes: When someone made a mistake, did I respond with curiosity, or criticism?
4) Inclusion: Did every person on my team have a real voice this week, or did some get more airtime than others?
5) Acknowledgment: Did I name what is hard right now, or did I pretend things are fine?
You will not get five clean yeses. Nobody does. The point is to see your own pattern, because your team has already seen it.
The Groops Take
Most organizations measure engagement, which tells you how people feel about their job. It does not tell you how the team is functioning. Engagement can stay flat while cohesion is quietly collapsing, and by the time the number moves, the damage has been compounding for months. The HR leaders in San Diego are some of thousands of people watching this happen in real time and not being given the language, the diagnostic, or the training to address it.
What we measure at Groops is different. We diagnose the conditions of the team functioning itself, at a real-time cadence rather than annually, because nervous systems do not work on annual cycles and neither do teams. Strategy does not usually fail because people lack intelligence. It fails because teams lack the psychological conditions to execute it together. The future of leadership is nervous system regulation, and it can be learned.
References
Duhigg, C. (2016, February 25). What Google learned from its quest to build the perfect team. The New York Times Magazine.
Edmondson, A. (1999). Psychological safety and learning behavior in work teams. Administrative Science Quarterly, 44(2), 350–383.
Eisenberger, N. I., Lieberman, M. D., & Williams, K. D. (2003). Does rejection hurt? An fMRI study of social exclusion. Science, 302(5643), 290–292.
Porges, S. W. (2011). The polyvagal theory. W. W. Norton & Company.