I once watched a CEO — someone I'd admired from a distance for years — publicly dismantle a junior employee's presentation in a way that was, to my mind, unambiguously cruel. Not deliberately cruel — I'm confident he didn't intend to damage anyone. But the impatience had gotten ahead of the judgment, the room had gone quiet in the specific way rooms go quiet when something wrong is happening, and by the time the meeting ended the damage was done. The employee left the company within three months. Two other team members I spoke with said the incident was a turning point in how they thought about their future there.
What struck me most, in retrospect, was not the behavior itself — most leaders I've worked with have had moments they're not proud of under pressure. It was the apparent lack of awareness that the moment had happened. In a conversation a week later, the CEO had no particular recollection of the interaction. He'd been frustrated, he'd expressed it, he'd moved on. The incident that the room was still processing didn't register for him as a significant event.
That asymmetry — between the leader's experience of their reactive moment and the organization's experience of it — is the central problem this essay addresses. What leaders experience as a brief, minor expression of frustration, their teams often experience as a significant signal: about what's safe, about the leader's stability under pressure, about whether this is a place where honest information can be shared without risk. The threshold for "this person is unpredictable" is much lower than most leaders assume, because the power differential makes people more attentive to the leader's emotional signals in exactly the way that heightens small variations into significant data.
What happens neurologically
The neuroscience of reactive behavior under pressure is well established enough to be worth taking seriously. The work of Joseph LeDoux, popularized by Daniel Goleman under the term "amygdala hijack," describes a circuit in which the brain's threat-detection system — the amygdala — activates in response to perceived threat or high stress and, under sufficient activation, can effectively bypass the prefrontal cortex, the part of the brain responsible for deliberate reasoning, perspective-taking, and impulse control.
The result is a reactive response that feels urgent and completely justified from the inside but that is frequently disproportionate and often counterproductive. The person experiencing it is not, in the relevant sense, choosing to be reactive. The deliberate reasoning system that would normally evaluate the proportionality of the response has been partially overridden. The response happens faster than the evaluation can occur.
This is not an excuse — it's a mechanism description. Understanding the mechanism is important precisely because the intervention for reactive behavior is not primarily about willpower or intention. Leaders who try to address reactivity through the pure force of wanting to respond better typically find that wanting to respond better doesn't help much when the amygdala has already fired. The intervention has to happen earlier: building the pause that makes deliberate choice possible before the reactive response has completed.
What's particularly relevant for leaders is that the amygdala's threat detection is not finely calibrated to organizational hierarchy. It responds to challenge, to criticism, to the perception of being undermined or dismissed or wrong — all experiences that are entirely normal in senior leadership settings and that carry significant social threat regardless of their actual danger. The leader in the boardroom whose idea is being challenged is not in physical danger, but the threat-detection circuitry doesn't make that distinction reliably. The activation is real, the bypass is possible, and the reactive response is available.
The pause as a genuine leadership practice
The most reliable intervention for reactive behavior under pressure is one of the simplest in description and most difficult in execution: the deliberate pause between the stimulus and the response. Not "I'll respond tomorrow" in most situations — just a two-to-five-second gap, a breath, a brief internal check-in before responding, that creates the space in which the prefrontal cortex can rejoin the process.
Two to five seconds doesn't sound like much. Under real pressure, in a setting where silence can feel like weakness or uncertainty, two to five seconds can feel like an eternity. The social pressure to respond immediately — to have the answer, to address the challenge, to fill the silence — is strong. The internal pressure to defend yourself, correct the misunderstanding, address the accusation, is stronger. The pause requires overriding both of those pressures with something that doesn't feel as urgent as they do: the commitment to respond deliberately rather than reactively.
Leaders who've developed this practice consistently report that it required an explicit, sustained commitment to build. The first times they tried it felt awkward and unnatural. The pause that created space in their processing often landed, in the room, as uncertainty or hesitation. They had to get comfortable with that perception, and with the reality that a two-second pause followed by a calibrated response is more credible than an immediate reactive response, even when the immediate reactive response feels more confident in the moment.
The practices that make the pause more accessible are often physical: taking a deliberate breath before responding, shifting posture slightly, making a brief written note. These physical cues serve as reminders that a choice is available — that the stimulus doesn't have to produce the response automatically. With repeated use, the cue activates the pause reliably; without some cue, the reactive response has a head start.
The identity of steady
There's a reframe I've found genuinely useful in the development of this skill, and it's about what the job actually is under pressure. The default assumption is that a leader's job under pressure is to manage the situation — to fix the crisis, solve the problem, address the challenge. But in many high-pressure situations, the situation is not immediately fixable. The crisis will take time to resolve. The problem requires more information. The challenge is genuinely uncertain.
In those situations, the most important thing a leader can do is not manage the situation — it's manage themselves. The team's capacity to navigate the situation is directly affected by the leader's emotional state. A leader who amplifies the anxiety of a crisis — who becomes visibly rattled, who projects urgency that tips into panic, who loses the measured quality of their communication — reduces the organizational capacity to respond. People begin to manage the leader's emotional state as a parallel task alongside whatever the crisis is actually requiring, and that tax is expensive.
The inverse is equally powerful and better attested. Teams navigating genuinely difficult situations with a leader who maintains visible steadiness — not false reassurance, not performed calm, but genuine regulation of their own emotional state — report higher confidence, clearer thinking, and better decisions than teams whose leader amplifies the difficulty of the situation through their own reactive response. The steadiness doesn't make the crisis smaller. It makes the team's capacity to respond larger.
This reframe — that under pressure, the primary leadership job is self-management — changes what "performing well" means in the hardest moments. It's not about having the perfect answer or projecting unshakeable confidence. It's about maintaining enough internal regulation that the people around you can do their best thinking about what's actually happening, rather than spending bandwidth managing the emotional environment you're creating.
What reactive leadership actually costs
The costs of reactive leadership are disproportionate to the incidents that create them — and this is something that leaders who are not attentive to the phenomenon frequently underestimate.
The most visible cost is the direct damage to specific interactions: the meeting that becomes about managing the leader's reaction rather than addressing the actual topic, the one-on-one where the direct report leaves having withheld the most important information because the opening moments of the conversation were reactive enough to close down the honesty.
The less visible but more consequential cost is what reactive leadership teaches people about what's safe. In organizations where senior leaders are reactive under pressure, the most important information — bad news, early warning signals, honest assessment of problems — tends to get filtered, delayed, softened, or withheld entirely. People learn through experience that bringing the leader bad news at the wrong moment, or in the wrong frame, produces a reactive response that is worse than the alternative. So they find the alternative: they bring the news later, when it's undeniable, when the options for responding to it are more limited.
The leader who is reactive under pressure is therefore not just having bad moments — they are systematically degrading the quality of information that reaches them. And the information environment they've created is one in which they are, progressively, making decisions with less accurate and less timely information than the leaders around them who haven't made this mistake.
This is the crisis leadership dimension of reactive behavior that rarely gets surfaced in development conversations: the most significant cost is not to the leader's reputation, but to the organizational information system that leadership depends on.
Building the capacity: practice and feedback
Developing the capacity to manage your reactions under pressure requires two things that are both harder to find than they should be: consistent practice and accurate feedback.
Practice, in this context, means the regular repetition of the pause under real pressure — not in training exercises, but in the actual situations where the reactive response is available. Every time the pause is built and the deliberate response is chosen, the neural pathway is reinforced. Every time the reactive response fires without the pause, the existing pattern is reinforced instead. The development is incremental and requires sustained commitment, but the direction is consistent: with enough practice, the pause becomes more accessible and the reactive response becomes less automatic.
Accurate feedback is harder to come by than practice, because the people who observe reactive leadership most directly — direct reports, peers, people in the room — typically do not volunteer honest assessments of the leader's reactive moments. The power differential that makes reactive moments consequential is the same power differential that makes people reluctant to provide feedback about them. The leader who wants accurate information about their reactive behavior has to actively create conditions for it: explicitly asking trusted people whether they observed anything in specific interactions, building relationships where this kind of honesty is genuinely welcome, and responding to the feedback they receive in ways that demonstrate that honesty is safe.
The self-awareness work that underlies reactive behavior management is, in this way, relational rather than purely individual. You cannot build an accurate picture of your reactive patterns from introspection alone — the blind spot that reactive behavior creates is specifically about the gap between how you experience the moment and how others experience it. That gap can only be closed by the other people who were in the room.
What genuine progress looks like
Leaders who make genuine progress on managing reactions under pressure often describe it in similar terms. Not as a transformation — not as the elimination of reactive impulses or the disappearance of the amygdala's activation under threat. But as a change in the relationship to the impulse: from being driven by it to having a choice about it.
The reactive impulse still fires. The frustration is still real. The desire to defend or correct or push back is still present. What changes is the gap between the impulse and the response — from essentially zero, where the impulse produces the response automatically, to something small but real, where the pause creates enough space for deliberate choice.
That gap is the difference between reactive leadership and regulated leadership. And it's the difference, organizationally, between teams that are managed carefully around the leader's emotional state and teams that can direct their full attention toward what actually needs addressing. The latter is not only better for the team — it's better for the leader, who is no longer the primary obstacle to the quality of organizational thinking in the moments when organizational thinking matters most.
Building that gap is patient work. It requires honest self-observation, reliable feedback from trusted people, and enough repetitions of choosing the pause over the reactive response that the choice starts to feel natural rather than effortful. The emotional regulation framework underlying it isn't complicated. The practice is simple. But simple is not the same as easy, and the leaders who make genuine progress on this are the ones who treat the development with the same seriousness they bring to any other aspect of leadership performance — because the stakes are just as high, and the organizational returns are just as real.