Learning to Lead Inside the Chaos
A disclaimer before we begin this morning: I make no promises about the quality of the thinking that follows. I discovered, with more disappointment than I care to admit, that I was completely out of my normal coffee and had to make do with whatever beans were left in the cabinet. I ground them, brewed them, stared at the cup for a moment, and decided we would all simply have to lower expectations together.
That minor morning crisis aside, it got me thinking about something I have come to believe very strongly over the years. One of the biggest misconceptions about leadership is that great leaders thrive because they are good at creating order and maintaining control. There is some truth in that, of course, but I think it misses the harder part of leadership. The leaders I have respected most were not distinguished by how well they operated when everything was orderly. They distinguished themselves by how well they functioned when order disappeared.
Great leaders learn to operate inside chaos.
That does not mean they enjoy chaos, and it certainly does not mean they create it. It also does not mean that they somehow become immune to stress, fear, confusion, or uncertainty. The best leaders I have known felt all of those things. The difference was that they learned how to keep those emotions from becoming the defining force in the room.
One of the most powerful examples of that principle comes from Lieutenant Colonel Hal Moore during the Battle of Ia Drang, later chronicled in We Were Soldiers Once... and Young. The circumstances around him were extraordinarily violent and confused. Soldiers were being killed and wounded, communications were difficult, units were under enormous pressure, and decisions had to be made with incomplete information while the situation changed by the minute.
The environment was anything but controlled.
What has always stayed with me is the description of Moore's presence in the middle of it. He was not detached from what was happening, nor was he reckless about the danger. He was simply steady. In a moment when everyone around him had every reason to become overwhelmed by the chaos, he understood that his responsibility was not to add his own fear and confusion to the problem.
His responsibility was to help create enough order inside the chaos for other people to function.
That distinction has followed me throughout my career because it applies far beyond a battlefield.
Hospitals experience their own versions of chaos. A census surges, staffing collapses, an unexpected clinical event occurs, a system goes down, or several problems arrive at the same time and compete for limited attention. Executive teams experience it during financial crises, acquisitions, restructurings, regulatory problems, public scrutiny, or sudden changes in leadership. Businesses experience it when markets move, contracts are lost, customers leave, or a seemingly manageable issue becomes something much larger.
The setting changes, but the leadership requirement does not.
When everyone else is reacting emotionally to the situation, the leader has to be able to see through enough of the noise to understand what is actually happening. That requires more than intelligence or technical competence. It requires emotional regulation, judgment, situational awareness, and the ability to separate what is urgent from what merely feels urgent.
Those are not the same thing.
Some of the worst leadership decisions I have seen were made by people who were not lacking experience or knowledge. They simply became absorbed by the pressure around them. Once that happened, they stopped leading the situation and began reacting to it.
Reaction feels active, which is why it can be deceptive.
A leader can move quickly, issue instructions, schedule meetings, demand updates, and create an enormous amount of activity while still failing to bring any meaningful order to the problem. Motion is not necessarily progress, and decisiveness is not necessarily judgment.
The leaders I respect most seem to understand that intuitively.
They slow the situation down mentally, even when the environment itself is moving quickly. They listen before deciding. They ask what is known, what is assumed, and what is still unclear. They distinguish between the things that require immediate intervention and the things that can wait long enough for better information.
Most importantly, they remain aware that everyone else is watching how they respond.
People read leaders constantly during periods of uncertainty. They notice tone, body language, patience, frustration, and where the leader's attention goes first. If the leader becomes visibly consumed by panic, anger, or self-protection, the organization absorbs that reaction almost immediately.
That is one of the reasons leadership under pressure is less about having perfect answers and more about becoming a stabilizing presence.
Calm does not mean passive.
It does not mean pretending the situation is less serious than it is, and it certainly does not mean avoiding difficult decisions. In many cases, calm leadership requires making harder decisions because the leader is willing to look at reality without flinching.
There is a difference between panic and urgency.
Urgency recognizes that something matters and acts appropriately.
Panic simply transfers anxiety from one person to everyone else.
I have seen leaders confuse those two throughout my career.
The loudest person in the room is not necessarily the person taking the problem most seriously. Sometimes volume is simply evidence that someone has lost control of their own response. The leader who remains composed enough to ask one useful question may accomplish more than the person issuing ten frantic directives.
That same principle applies to how leaders treat their people during difficult moments.
Pressure has a way of revealing priorities.
When circumstances deteriorate, some leaders immediately begin protecting themselves. They distance themselves from unpopular decisions, avoid difficult conversations, shift blame, or spend more time managing how they will be perceived than managing the problem itself.
That response is understandable at a human level because self-preservation is powerful.
It is also destructive to trust.
People notice quickly when leadership's first instinct is to protect the leader rather than serve the mission and the people responsible for accomplishing it. They notice when someone disappears during the hardest part of the problem and reappears once the situation stabilizes. They notice who accepts responsibility and who searches for someone else to carry it.
Those observations become part of the organization's memory.
In the military, one of the most important expectations placed on leaders is that they remain present when conditions become difficult. That presence matters because people need to know that the person asking them to carry risk is willing to remain alongside them while they do it.
Civilian organizations are no different in that regard.
Leaders do not need to experience every problem personally, and they should not insert themselves unnecessarily into work that belongs to someone else. But when a team is under significant pressure, employees need to know that leadership is engaged, informed, and willing to share the burden rather than merely evaluating performance from a safe distance.
That is one of the reasons chaos can become such an important leadership test.
Anyone can appear competent when the environment is predictable, the budget is healthy, performance is strong, and everyone generally agrees on what needs to happen next. Those conditions make leadership considerably easier.
The real test arrives when the assumptions stop working.
When the information is incomplete, when the people are tired, when the choices are imperfect, and when every available option carries some consequence, leadership becomes less about following a plan and more about maintaining enough clarity to make a sound decision anyway.
That is where experience becomes valuable, but only if experience has produced self-awareness.
Experience alone does not guarantee steadiness. I have seen very experienced leaders become remarkably reactive under pressure because they never learned how to manage themselves when circumstances moved outside their control.
That is why I increasingly think one of the most important leadership disciplines is learning how to regulate your own response before attempting to regulate the environment around you.
You cannot create stability for other people if you are contributing to the instability yourself.
That lesson sounds simple, but it is difficult to practice because chaos has a way of making us believe that every emotion requires action. Fear demands movement. Frustration demands a response. Anger demands confrontation. Uncertainty demands an answer.
Mature leadership creates a little distance between the emotion and the decision.
That distance may only be a few seconds.
It may be one breath before speaking.
It may be asking one additional question before deciding.
It may be taking five minutes to understand what has actually happened before calling everyone into a room.
Those small pauses can change outcomes because they allow judgment to catch up with emotion.
I think that is part of what people recognized in leaders like Hal Moore. His effectiveness did not come from being unaffected by chaos. It came from being disciplined enough not to surrender himself to it.
That distinction matters.
Leadership is not about eliminating chaos because much of life and organizational leadership will never be fully controllable. There will always be variables we did not anticipate, people who behave differently than expected, events that disrupt the plan, and moments when the information available is simply not enough to guarantee the right answer.
The job is not to create a fantasy of perfect control.
The job is to create enough clarity, enough trust, and enough direction that people can continue to function even when the environment remains uncertain.
The longer I lead, the more convinced I become that this is one of the defining differences between someone who merely occupies a leadership position and someone people genuinely trust under pressure.
When the room becomes chaotic, one adds to the noise.
The other helps people see through it.
That is the kind of leader worth becoming.
So, as you head into the week ahead, the goal is probably not to eliminate every source of chaos around you. That would be unrealistic, and depending on your organization, possibly impossible.
The better goal is to become someone who can stand inside it without becoming part of it, recognize what actually matters, and help everyone around you move with greater clarity than they had before you arrived.
That is not controlling chaos.
That is learning how to harness it.
Now I am going to finish this questionable cup of coffee and hope tomorrow's morning crisis can be resolved with a better bag of beans.