Calm is not a mood—it’s access to reality
Calm under pressure, as I use the phrase in leadership work, is the ability to keep your executive brain online when pressure spikes. It’s not a chilled-out personality, and it’s not the absence of anxiety. It’s access to reality—the capacity to see what’s true, choose what matters, and act without leaking panic into the room.
The moment that exposes your real relationship with calm is rarely cinematic. It’s the quiet spike: an OR monitor alarm that sounds slightly off, a Slack message that says “prod is down,” a board member asking the one question you didn’t prepare for. Your heart rate jumps, your thoughts scatter, and part of you wants to overreact or disappear. In my work with leaders, founders, and clinicians, the inflection point is consistent: not whether you feel stress—that’s human—but what you do in the first 30–90 seconds after it hits.
Under acute pressure, cortisol and adrenaline narrow attention, shrink working memory, and push you toward short-term, high-certainty moves. This is why unmanaged stress degrades judgment: you don’t just feel worse—you literally have fewer options available in the moment. Calm is a performance skill: it preserves cognition when everyone else’s field of vision is collapsing.
Why calm leaders outperform in high-stakes rooms
If you’ve ever been in an ICU code or a live incident bridge in tech, you’ve seen both versions of leadership. One person walks in with a tight voice, rapid-fire questions, and a frantic tempo that spikes the room. Another walks in, takes a breath, lowers her tone, and starts with: “Tell me exactly what you’re seeing.” Same urgency, completely different effect.
Teams don’t merely prefer the second style—they perform better under it. Emotional states are contagious; a leader’s tone and cadence can shift the physiological state of the entire group. In practice, calm leadership does three competitive things at once:
- It reduces noise: fewer simultaneous actions, fewer contradictory instructions.
- It restores structure: clear priorities, clear roles, clear next checks.
- It protects trust: people speak up earlier when they don’t fear an explosion.
This is why calm is a competitive edge, not a “nice to have.” In high-stakes environments—operating rooms, trading floors, high-growth product teams—the risk is often not the initial problem. It’s the confusion that follows it. Calm leaders act as decision force multipliers: they convert chaos into a small set of priorities, keep communication simple, and define who decides what. That clarity reduces errors, shortens recovery time, and prevents the secondary damage—blame, hiding, politics—that makes crises repeat.
As Irena Golob often tells clients, your state is part of your job. Not just your output or strategy, but the way your nervous system shows up in the room.
When anxiety hits and you still have to lead: the OR example
A common fear among mid-career professionals—and especially senior trainees—is: “If I feel anxious, does that mean I’m not cut out for this?” I’ve heard it from engineering managers and anesthesiology residents in almost identical language.
One resident described facing an unfamiliar complication, feeling her heart rate spike, calling for help early—and then getting the situation under control before the attending arrived. On paper, that’s a success: she recognized potential danger, activated resources, and stabilized the patient. Internally, she felt embarrassed: “I overreacted. Everyone could see I was anxious.”
Here’s the correction that changes careers: composure is not the same as never calling for help. In high-reliability settings, experienced seniors often trust you more when you call early and then stand down than when you delay and hope it’s nothing. The competitive advantage isn’t “no anxiety.” It’s “I can feel the surge and still think.”
If you’re the person who worries you called too early, use a higher-quality metric:
- Did I name the risk clearly? (signal)
- Did I activate resources appropriately? (prudence)
- Did I keep reassessing as new data arrived? (judgment)
That’s calm in action. The embarrassment is often just your ego colliding with a new level of responsibility.
Micro-practices for calm under pressure
When pressure exceeds your sense of control, your brain can flip into a threat-efficacy loop: more stress hormones, less cognitive flexibility, more black-and-white thinking. The solution isn’t slogans. It’s rehearsed structure—small behaviors that are easy to execute when your mind wants to sprint.
One useful tool from aviation (and borrowed in medicine) is the ROC mnemonic: Relax, Observe, Confirm. In a startle event, pilots are trained to do something physical to ground themselves (Relax), then state what they see (Observe), then check for confirming/disconfirming evidence (Confirm).
Translated to the OR or a high-stakes product incident:
- Relax: step back, shoulders down, one deliberate exhale.
- Observe: say out loud, “Oxygen saturation is dropping,” or “Checkout errors are spiking.”
- Confirm: “What changed in the last 60 seconds? What do we know versus assume?”
That narration is not fluff. Speaking in crisp, concrete sentences recruits systematic thinking and helps the team orient to the same map.
The “help early” rule without losing authority
If you tend to call for help prematurely, don’t try to “be tougher.” Replace vagueness with thresholds:
- Trigger: “If I see X for 2 minutes or Y trend twice, I call.”
- Request: “I need a second set of eyes while I run the next checks.”
- Update: “Stand by—if A returns to baseline, we’ll downgrade.”
This keeps you decisive and collaborative. Calm is high-intensity, low-drama.
FAQ: How do I stay composed in the OR when I feel the urge to call for help too early?
If you feel that surge, treat it as a signal—not a verdict. Take one deliberate exhale, name what’s happening out loud (“Sat is trending down” / “BP is falling”), and run your next check. Then call using a clear threshold: what you’re seeing, what you’re doing next, and what would make you downgrade the escalation. This keeps you safe, keeps you credible, and prevents anxiety from turning into scattered communication.
Calm without passivity: pair composure with decision rights
There’s a legitimate concern: can calm leadership slow teams down? Yes—if calm becomes indecision, or if decision rights are unclear. The distinction is simple:
- Calm: fast movement, low drama, closed loops.
- Passivity: slow movement, low drama, open loops.
Before the next crisis, define the infrastructure: Who decides what? When do we escalate? What’s the default playbook? What’s the maximum time before we choose a path with incomplete information? Military training, high-risk medicine, and reliable tech operations converge on the same point: you earn calm under pressure by practicing chaos in low-stakes environments.
If you want a deeper framework for building disciplined composure—without turning leadership into performance theatre—start with the resources on my Website. The emphasis is always the same: personal responsibility first, then standards, then repeatable character.
This is for informational purposes only and not a substitute for professional medical, mental health, or occupational advice. Consult a qualified professional for guidance specific to your situation.
The competitive edge that compounds quietly
Real calm is practical and unglamorous: a 5–10 second reset, a one-sentence summary, a clear next check. In 2026, when work is faster, noisier, and more publicly scrutinized than it was even a few years ago, calm becomes a differentiator. It changes what your team tells you, how quickly you see risk, and how reliably you can act on partial information.
The philosophical shift is this: decide that your inner state is part of your craft. Treat composure like infrastructure—designed, maintained, upgraded—rather than something you hope appears when you need it.
As you head into your next high-pressure moment, consider three questions:
- Where do I typically lose 30–90 seconds—reacting, over-explaining, or freezing?
- What single sentence could I practice that restores shared reality fast?
- What structure (thresholds, decision rights, rehearsals) would make calm my default instead of my exception?