Home Blog Building Psychological Safety
NeuroCoaching & Team Performance

How Do You Build Psychological Safety on a Team?

A team in a working meeting where members are leaning in and engaged in open discussion.
Dan Docherty
Dan Docherty
Chief Coaching Officer, Braintrust
8 min remaining
Dan Docherty
Chief Coaching Officer, Braintrust

About

Dan Docherty is the Chief Coaching Officer at Braintrust and author of NeuroCoaching. He applies the neuroscience of trust, communication, and behavior change to how leaders develop their teams. Dan partners with CHROs, CLOs, and executive teams at enterprise organizations to build coaching cultures that stick.

Experience Highlights

  • NeuroCoaching methodology and leadership development
  • Manager-as-coach program design
  • Executive coaching and succession planning
  • Building coaching cultures at enterprise scale

Areas of Expertise

NeuroCoachingLeadership DevelopmentExecutive CoachingManager EffectivenessPsychological SafetyTalent DevelopmentBehavior ChangeL&D Strategy

Psychological safety is the most cited idea in modern leadership and the most misunderstood. Most teams treat it as a mood to create. It is actually a neurological state to protect, and the difference decides whether your people speak up or shut down when it matters most.

Ask a room of managers how to build psychological safety and you will hear the same answers. Be approachable. Say there are no dumb questions. Tell the team it is okay to fail. All well intentioned, all mostly useless, because they treat safety as a message the leader broadcasts rather than a signal the brain detects. Your team is not listening to what you say about safety. Their nervous systems are reading what you do, moment to moment, and drawing conclusions faster than anyone can consciously process.

This is why the manager who insists "my door is always open" is often the same manager whose team withholds bad news until it becomes a crisis. The words say safe. The behavior says something else, and the brain believes the behavior.

What psychological safety really is

Amy Edmondson of Harvard defined psychological safety as a shared belief that the team is safe for interpersonal risk taking. That definition is correct, and it is where most leaders stop. They hear "belief" and assume they can install it through communication. They cannot, because the belief is downstream of something more primal.

Underneath the belief sits the brain's threat detection system. The amygdala continuously scans the social environment for signs of danger, and it does this before the prefrontal cortex, the rational, deliberate part of the brain, has any say. When the amygdala registers a social threat, a raised eyebrow, a dismissive tone, a colleague being cut off in a meeting, it triggers a protective response in a fraction of a second. Blood flow reroutes. Attention narrows. The capacity for creative, exploratory thinking drops.

So when a team member decides in a meeting not to raise the concern they came in with, that is rarely a considered choice. It is a threat response that already fired. By the time the rational brain could weigh the pros and cons of speaking up, the amygdala had already voted, and it voted for silence.

6x
The amygdala can initiate a threat response roughly six times faster than the prefrontal cortex can complete a deliberate evaluation. In a tense meeting, the decision to stay quiet is often made before conscious reasoning begins.

This reframes the entire problem. Psychological safety is not a culture you announce. It is the absence of unmanaged threat signals in the environment your people operate in. You do not add safety. You remove the things the brain reads as danger.

Why most safety efforts fail

Once you understand safety as a threat state rather than a mood, the standard playbook starts to look backward. Consider the three most common moves leaders make.

The first is the values poster. Teams write down that they value candor and respect, then hang it on the wall. But the amygdala does not read posters. It reads whether the last person who challenged the boss got interrupted, corrected, or quietly frozen out. A stated value that contradicts observed behavior does not create safety. It creates cynicism, because now the team has evidence that the leader says one thing and rewards another.

The second is the open door. "Come to me with anything" sounds generous, but it puts the entire burden of risk on the person with the least power. Walking into a superior's office to deliver an uncomfortable truth is one of the highest threat scenarios a professional faces. Offering the door does not lower the threat. It just relocates it.

The third is the reassurance reflex. When someone raises a hard issue, the anxious leader rushes to smooth it over. "I'm sure it's fine, let's not worry about it." This feels supportive. To the brain of the person who took the risk, it registers as dismissal, and the lesson encoded is that raising concerns leads to being brushed aside. The next concern stays unspoken.

Each of these fails for the same reason. They operate on the conscious, verbal layer while the actual decision to speak or stay silent is being made on the fast, threat-detecting layer underneath. You are sending memos to a system that only responds to signals.

The neuroscience of trust

If threat is the problem, trust is the mechanism that turns it off. And trust, like threat, has a biological basis that leaders can work with directly.

When people experience genuine connection and reliability from another person, the brain releases oxytocin, a neurochemical associated with bonding and reduced threat vigilance. Paul Zak's research on organizational trust found that people in high-trust environments report dramatically lower stress and higher engagement than those in low-trust ones. The felt sense of "I can take a risk here" is not a personality trait of the team. It is a physiological state the leader's behavior either enables or blocks.

Trust is not built in the big moments. It is built in the hundreds of small ones where a leader's response to risk teaches the brain whether it is safe to try again.

Here is the part most leadership training misses. The oxytocin response is driven far more by consistency than by warmth. A leader who is reliably direct is easier for the brain to trust than a leader who is unpredictably nice. Unpredictability is itself a threat signal, because the amygdala cannot calibrate what response to expect. This is why the "nice" manager whose mood swings can generate less safety than the demanding manager whose reactions are steady and known.

What the brain is looking for is not a leader who never causes discomfort. It is a leader whose response to interpersonal risk is predictable, proportionate, and free of punishment. Once that pattern is established, the threat system quiets, the prefrontal cortex comes back online, and people start bringing their full thinking to the table.

How to build it in practice

Building psychological safety, then, is not a campaign. It is a set of repeated behaviors that teach your team's nervous systems that risk is survivable here. Three of them do most of the work.

Manage your reaction to the first risk

The single most important moment for safety is the instant after someone takes an interpersonal risk. They challenge your idea, admit a mistake, or float a half-formed thought. What you do in the next three seconds gets encoded by everyone watching. If your face tightens or your first word is a correction, you have just taught the room that risk carries a cost. The move is to lead your response with genuine curiosity before evaluation. "Say more about that" buys your rational brain time to engage and signals to the group that the risk was received, not punished.

Model fallibility from the top

Teams read the leader's relationship with their own mistakes as the ceiling for how safe it is to have any. When you say "I got that wrong, here is what I missed," you are not undermining your authority. You are lowering the threat threshold for the whole team, because you have demonstrated that error is discussable rather than dangerous. Do this out loud and specifically. Vague admissions of general imperfection do not register. A concrete owned mistake does.

Make small risks routine

The brain generalizes from repetition. If the only time anyone takes an interpersonal risk is when the stakes are enormous, the threat response will always dominate, because the moment is rare and loaded. Leaders who build durable safety create frequent, low-stakes reps. They ask for dissent on small decisions. They invite the quietest person to react to a proposal. They normalize the phrase "what am I missing" as a standing question, not a crisis signal. Each small rep tells the amygdala that speaking up is a normal, low-cost event, and that learned expectation is what holds when the stakes finally get high.

None of these require a program, a budget, or a culture initiative. They require a leader who understands that every reaction they have is a teaching signal, and who chooses that signal deliberately.

What changes when you get it right

A team with real psychological safety does not look like a team that is comfortable. It looks like a team that argues well, surfaces problems early, and recovers from mistakes fast. The comfort is a byproduct, not the goal. The goal is a group whose threat systems are quiet enough that their best thinking is actually available when the organization needs it.

This is the deeper point that gets lost when safety is treated as a soft skill. Psychological safety is not about being nice to people. It is about removing the neurological interference that stops capable people from contributing what they know. In complex, high-stakes work, the cost of that interference is enormous, and it is almost entirely invisible until something breaks.

The leaders who build it are not the warmest ones. They are the ones who understand what their team's brains are reading, and who take responsibility for the signal they send. If building leaders who create that kind of environment is something your organization is working toward, that is a conversation worth having. You can start one here.

About the Author: Dan Docherty is the Chief Coaching Officer at Braintrust and the author of NeuroCoaching. He works with CHROs, CLOs, and executive teams across financial services, insurance, life sciences, software, manufacturing, and private equity to apply the neuroscience of trust and communication to how leaders develop their people. Connect with Dan at dan.docherty@braintrustgrowth.com or reach him directly on LinkedIn.

Serving sales teams at enterprise organizations

Braintrust is a communication skills-based growth consulting firm offering programs rooted in neuroscience and behavioral psychology — designed to develop the consistent communication habits proven to drive higher sales performance and leadership effectiveness.

Financial Services Insurance Life Sciences Software Manufacturing Private Equity