Every technical leader has a moment they would handle differently.
For a CIO, it may be the board meeting where a question about technology spending feels like a judgment on years of work. For a CTO, the failed release that draws a sharp response before the team has established what happened. For a CISO, the meeting where a colleague dismisses a risk that has kept them awake for weeks.
The pressure is real. So are the consequences of how we carry it.
Technical leaders must protect the enterprise, modernize aging systems, make consequential choices about AI, and develop people while delivering results. These responsibilities compete for money, time, and attention. Knowing the technical answer is only part of the work. Remaining open, discerning, and accountable when that answer is challenged is another.
This is where leadership maturity becomes practical. It affects what we hear, which concerns reach us early, and whether capable people can exercise judgment without waiting for our permission.
Neuroscience offers a useful account of why perspective can be harder to maintain under stress. It does not offer a brain scan for maturity or a shortcut around the work of leading.
A moment I would handle differently
Midway through a large-scale agile transformation, a stakeholder challenged my delivery framework in front of the room. I noticed what I was hearing narrow to his criticism alone. I began defending my design instead of listening for the legitimate signal buried in his frustration.
After three decades of leading technology and cybersecurity programs, I had answers. What I did not have, in that moment, was attention to spare.
When pressure narrows judgment
Under acute, especially uncontrollable, stress, working memory and flexible thinking can become less reliable. Neuroscientist Amy Arnsten's reviews describe how stress affects the prefrontal systems involved in these functions.1,2 The effects depend on the person, task, and circumstances; stress does not make every capability disappear, and much of the mechanistic evidence comes from animal research.
You may recognize the experience without knowing the biology.
A colleague questions your transformation roadmap. You begin preparing your defense instead of listening for information. An engineer raises a late concern about a release. You hear resistance before you understand the risk. A funding discussion becomes an argument about whether the business values technology.
Your expertise has not vanished. Your view of the situation has narrowed.
For many technical executives, expertise has been the foundation of professional identity. Being the person who can solve the problem earned trust and advancement. Under pressure, taking control can feel like doing your job.
Sometimes it is your job. An incident may require a decision only you can authorize. A material risk may require you to stop a launch. Maturity does not mean withholding authority. It means knowing when to use it, and when your intervention prevents others from doing the work they are accountable to do.
If every difficult decision returns to you, your attention becomes an organizational constraint. The team has fewer opportunities to develop judgment, and you have less capacity to see the enterprise as a whole.
For CISOs, the pressure is often compounded by regulatory disclosure obligations and personal accountability, which can make a challenge feel less like a question and more like a threat to standing. That is precisely when an untested interpretation is most costly.
Examine the story before acting
Research on cognitive reappraisal examines what happens when people reconsider the meaning of an event to change its emotional impact. In a meta-analysis of 48 neuroimaging studies, reappraisal consistently engaged regions involved in cognitive control and language comprehension, and was associated with reduced activity in the bilateral amygdala.3 It does not support the simple story of a “rational brain” switching off an “emotional brain.” Nor does it establish that a brief pause will reliably produce a better executive decision.
The leadership application is more modest and more useful: before acting on an interpretation, ask whether you have tested it.
In that room, I caught myself beginning to defend the framework. I paused, listened again, and asked what he was seeing that I was not. His answer exposed a delivery dependency we had missed. What I had first heard as resistance contained information we needed to change the plan.
The stakeholder's challenge was a fact. “He is attacking my work” was my interpretation, and it nearly cost us the most useful information in the room.
Suppose, in a different setting, the CFO challenges the cost of replacing a legacy platform. Your first thought may be, “They still do not understand what we are dealing with.”
Perhaps. But what does the CFO need to make a responsible investment decision? Have you distinguished the exposure created by delay from the benefits of replacement? Are the assumptions behind your estimate visible? Can the organization absorb the change this quarter? Is there a credible sequence of smaller investments?
You might say:
You have not weakened your recommendation. You have made it easier for others to examine and, if warranted, support.
The same discipline matters in AI governance. A security objection may identify an exposure the delivery team has not addressed. It may also rest on an assumption that can be tested. Neither “security is obstructing innovation” nor “innovation is ignoring risk” is a sufficient basis for an enterprise decision.
Ask what is known, what remains uncertain, who is authorized to accept the risk, and what evidence would change the recommendation. Then decide, explain the trade-off, and name the owner of the next step.
One question worth carrying into a difficult conversation is:
What am I treating as fact that is still an interpretation?
A missed deadline is a fact. “This team does not care” is an interpretation. A board member's question is a fact. “They have lost confidence in me” may be an interpretation.
Inquiry is not an obligation to give everyone the benefit of the doubt indefinitely. A commitment may have been neglected. A vendor may be withholding information. A risk may justify stopping the work. Mature judgment can reach firm conclusions; it takes care to establish the grounds for them.
Your response affects what reaches you
Consider a service outage. Customers are affected, the team has incomplete information, and senior stakeholders want a restoration time no one can responsibly promise.
An executive can add clarity or confusion. Accusations before the facts are known may make candor more difficult. Changing direction with every update may fragment the response. Neither helps customers.
A more useful opening is:
These questions carry urgency without taking the incident commander's role away. They also let you communicate upward honestly: what is confirmed, what is being investigated, what the team is doing now, and when stakeholders will hear more. You need not invent certainty to demonstrate command.
After recovery, accountability matters. Examine the technical failure, the decisions and safeguards around it, and the conditions in which people worked. Address misconduct or negligence when evidence supports that conclusion. Assign corrective actions and verify that they are completed.
Compassion is not the absence of standards. People deserve fair treatment, and customers and the organization deserve reliable performance.
African philosophy offers a demanding conversation about the individual and the community. The Kenyan scholar John Mbiti wrote, “I am because we are; and since we are, therefore I am.”6 Ifeanyi Menkiti argued that personhood grows through moral life in community.7 Kwame Gyekye defended individual worth and agency alongside communal responsibilities.8 These are contributions to African philosophy, not techniques for improving team output. They leave me with two questions: What becomes possible for others because of how I exercise authority? And where must I exercise my own judgment rather than hide behind the group?
The engineer's willingness to surface uncertainty, the deputy's ability to make a sound decision, and the executive team's capacity to disagree honestly are shaped in part by the conditions you create.
Design for judgment under pressure
Personal practices help, but they have limits. In one laboratory experiment, acute stress impaired participants' use of a newly learned strategy for regulating conditioned fear.4 That does not tell us exactly how a seasoned incident leader will behave. It does caution against assuming that a technique learned in a calm setting will always be available when stakes rise.
Sleep deserves similar seriousness. A systematic review and meta-analysis of experimental studies found that sleep loss reduced positive affect and increased anxiety symptoms, among other effects.5 The study did not test executive staffing models, but it gives leaders reason to take fatigue seriously rather than treating it as proof of commitment.
For a CIO, CTO, or CISO, the response cannot be limited to “take a breath.”
If critical decisions routinely follow overnight incidents, arrange rested coverage and a second reviewer where feasible. If every architectural disagreement escalates to the CTO, clarify decision rights and escalation thresholds. If delivery, security, and operations are carrying more priorities than they can responsibly execute, make the trade-offs visible to the people setting those priorities.
A pause before a difficult conversation may help you listen. An incident process helps people act when there is little time to pause. Capable deputies, clear authority, realistic commitments, and recovery time protect judgment at an organizational level.
Your life beyond the role matters in its own right. Relationships, health, and enjoyment are not merely resources to be spent on better performance. They are part of the life leadership should allow you to live.
Practice, repair, and look for change
My own pause worked once, in one room. It is an account of experience, not evidence, and the research above is a reminder that a technique can fail when stress is high. That is why I now coach it as a practice to rehearse, not a reflex to assume.
What I took from that moment was not a promise that I could always pause my way to clarity. It was a responsibility to notice when I began defending an interpretation rather than seeking the information I might be missing, and to build decision processes that don't depend on my composure alone.
Choose one recurring moment when your response tends to narrow: a missed commitment, a challenge to your expertise, or an update that arrives without a solution.
Before it happens again, decide what you will do differently. You might ask two questions before giving your view. You might ask the accountable leader for a recommendation and its trade-offs before stepping in. You might distinguish a decision that truly requires your authority from one you are taking back out of habit.
Afterward, ask yourself:
What happened, and what did I assume it meant?
What evidence did I seek, or avoid?
How did my response affect the conversation?
What responsibility is mine now?
When you mishandle a moment, repair it directly:
The apology matters. Changed behavior gives it credibility.
Invite feedback from someone who sees you under pressure. Over time, look for observable differences. Are concerns reaching you earlier? Can your deputies make sound decisions without unnecessary escalation? Can colleagues challenge a recommendation without paying a personal price? Do decisions have clearer owners and better-stated trade-offs?
These are not clinical measures of maturity. They are practical questions about your effect on the people and work entrusted to you.
Technical leadership will continue to involve uncertainty, competing obligations, and consequential choices. Maturity is not a promise never to react. It is a growing capacity to notice a reaction without letting it make every decision for you, and to build an organization in which good judgment does not depend on one person always being at their best.
When pressure rises, make room for the facts, the people, and the responsibility in front of you. Then choose a response that serves them well.
References
- Arnsten AFT. Stress signalling pathways that impair prefrontal cortex structure and function. Nat Rev Neurosci. 2009;10(6):410–422.
- Arnsten AFT. Stress weakens prefrontal networks: molecular insults to higher cognition. Nat Neurosci. 2015;18(10):1376–1385.
- Buhle JT, et al. Cognitive reappraisal of emotion: a meta-analysis of human neuroimaging studies. Cereb Cortex. 2014;24(11):2981–2990.
- Raio CM, et al. Cognitive emotion regulation fails the stress test. PNAS. 2013;110(37):15139–15144.
- Palmer CA, et al. Sleep loss and emotion: a systematic review and meta-analysis of over 50 years of experimental research. Psychol Bull. 2024;150(4):440–463.
- Mbiti JS. African Religions and Philosophy. Heinemann; 1969.
- Menkiti IA. Person and community in African traditional thought. In: Wright RA, ed. African Philosophy: An Introduction. University Press of America; 1984.
- Gyekye K. Tradition and Modernity: Philosophical Reflections on the African Experience. Oxford University Press; 1997.
