The biggest threat to performance isn’t incompetence – it’s fear
When I sit down with executive teams to diagnose why performance has stalled, the conversation almost always starts in the wrong place. Leaders assume skill gaps, process breakdowns, misaligned strategy or the wrong people in the wrong seats are the cause of their performance challenges.
However, after nearly two decades as a performance coach and culture specialist, I have seen how infrequently the impact of fear is recognized and addressed. And this has shifted how I think about performance: the greatest threat to a team’s ability to think, adapt and perform is not incompetence – it’s fear.
Why fear is so hard to see
This isn’t just a theoretical idea; it’s biological. Neuroscience shows that when people experience threat – real or perceived – it can disrupt the connection between the amygdala (the brain's threat-detection center) and the prefrontal cortex. This reduces access to critical leadership capabilities, including executive functioning, sound decision-making, and emotional regulation.
When people have learned, sometimes years earlier, that mistakes invite shame or that speaking up involves risk, the brain interprets ordinary pressure as a threat. As a result, a fight, flight, freeze or appease response takes over, and in an instant – however capable your people are on paper – they lose access to the cognitive flexibility and composure needed for high performance.
When an athlete or executive who has spent years honing their skills suddenly begins to underperform, this is often what’s happening. They haven’t lost their skills or knowledge – they’ve lost access to them.
What makes fear so dangerous in organizations is that it rarely announces itself.
What makes fear so dangerous in organizations is that it rarely announces itself. It doesn't show up as overt conflict or obvious dysfunction. Instead, it manifests in what I call micro-behaviors – the small, often unconscious, frequently non-verbal actions and relational cues that unfold in the moment: withholding a perspective, a defensive tone or someone disengaging without a word rather than voicing what they see.
When viewed individually, these consequences may seem trivial; however, the cumulative effect of micro-behaviors is to teach your entire team what is and isn’t safe to say.
Over time, the energy that should be directed toward innovation, collaboration, problem-solving, and driving the core business gets redirected toward self-protection and impression management.
How psychological safety impacts behavior
The work on psychological safety by Harvard Business School professor Amy Edmondson supports this. Her research has shown that when people perceive that speaking up carries interpersonal risk, they adapt by engaging in self-protective behaviors, including withholding concerns, questions and ideas.
This is the invisible tax that fear places on performance. Teams are still working hard, but they are no longer working openly. Innovation narrows. Coaching is seen as compliance. Accountability gets outsourced. Talent gradually disengages or simply leaves.
While psychological safety is necessary, it is insufficient on its own.
And when real pressure arrives – a market shift, a must-win close game, a failed launch, a leadership restructure – the very team that looked capable in calm conditions reverts to old, protective patterns, because the underlying fear was never addressed. It was only ever managed around.
This is why, while psychological safety is necessary, it is insufficient on its own. It addresses how safe an individual feels to speak up, but it doesn't automatically build the ongoing capability to stay open when the stakes are highest. That capability is what I call Adaptive Safety: the collective ability of a team to continually generate trust, connection and inclusion as conditions change, not just when things are calm.
This distinction is critical; it's the difference between a team that can perform when conditions are predictable and one that is able to access its skills and knowledge under pressure or in a crisis.
What leaders can do
Addressing fear at this level isn't about a training program or a values poster. It requires deliberate, ongoing practice.
Here is where I encourage leaders to start:
1. Do the internal work first. Your own nervous system sets the ceiling for your team's openness. Notice your early warning signs under pressure – the tightness, the urge to control, the tendency to withdraw – and build the self-awareness to choose a response rather than react on reflex.
2. Treat micro-behaviors as leadership levers, not background noise. Pay attention to tone, the pacing, who gets interrupted, how dissent or challenge is received, and how mistakes are handled. These moment-to-moment signals are the actual mechanism through which trust and connection are built or broken – far more than any strategy document.
3. Reward the behaviors that expand honesty. When someone names uncertainty, recognizes complexity, offers dissent, or owns an error, acknowledge it directly: ‘That was a hard thing to say – thank you.’ This is how a team learns that candor is welcomed, not punished.
4. Interrupt what erodes safety, calmly and consistently. Sarcasm, eye-rolling, blame-shifting and side conversations shouldn't be tolerated as ‘just how things are.’ A simple, steady correction in the moment does more than any policy.
5. Build learning rhythms that develop the capability to reflect and immediately integrate. Don't just ask what happened. Keep asking why it happened until the real cause – of failure or success – is revealed. Then the necessary shifts in behavior, assumptions or design can be embedded, so failure doesn't recur and success becomes repeatable. This is what separates learning fast from learning deep.
Incompetence can be trained. Fear, left unaddressed, erodes everything that training is meant to build. The leaders who understand this distinction – and act on it – are the ones building organizations that don't just perform, but also adapt in our fast-paced, ever-changing corporate landscape.