Leadership When Things Fall Apart
Most leadership books treat crisis as some special state that requires a completely different playbook. That's not how it works. The same decisions you make on a normal Tuesday are what matter when everything is breaking. The pressure changes the environment. The decisions don't. I learned this the hard way during a deployment that went sideways in 2021. We had a production outage that cascaded through three microservices at 2 AM. My lead engineer was two time zones away and unreachable. I had to decide whether to kill the feature that was causing the bleed or keep it running and risk total system failure. There was no framework for that call. There never is. I pulled the feature. It cost us about 40% of our monthly revenue for that sprint. We recovered within two weeks. The decision was correct even though it felt like failure at the time.
In Crisis The Power Of Courageous Leadership In Turbulent Times
Courageous leadership isn't about bravery. It's about the willingness to absorb uncertainty that other people will actively avoid. Most managers in a crisis spend their energy looking for the right answer. They should be spending it on gathering enough signal to make a defensible one. Speed and precision trade off against each other. You rarely get both. Here's what beginners miss. The first instinct in a crisis is to communicate more. Send updates. Call meetings. Write status documents. This is usually wrong. Cognitive load among your team is already at capacity. Extra communication adds noise, not clarity. The most effective leaders in these situations say less and mean it when they speak. I cut my update cadence from hourly to once every four hours during the incident above. My team got faster at resolving the issue once they stopped waiting for permission to move. The second thing people get wrong is that they try to maintain morale by being optimistic. Forced optimism erodes trust faster than honest bad news ever will. Telling your team "we'll get through this" when you have no data to back it up sounds like manipulation. Telling them the actual state of play, the gaps in your knowledge, and what you're going to do about it builds something stronger. Confidence based on competence lasts longer than confidence based on vibes.
What actually works: First, establish a single source of truth for information. This doesn't need to be elaborate. A shared doc or a Slack channel where only verified updates go. Everything else gets ignored. I've seen teams waste hours chasing rumors in group chats during outages because no one owned the narrative. Second, make decisions public with reasoning attached. Even if the decision is wrong, the team learns something. Even if the reasoning is imperfect, it gives people a model to challenge and improve. Decisions made in private and announced in full look arbitrary, even when they aren't.
Get the Full Details
Third, protect your people from external pressure. When senior leadership or clients start circulating panicked messages, that energy has to stop at your door. You take the heat. Your team takes the work. This isn't heroic. It's structural. A team that's answering emails from five different directors will produce worse results than a team that gets one coherent priority. There's a limit to this approach. Courageous leadership requires a baseline of trust that takes months or years to build and seconds to destroy. If your team doesn't trust your judgment, telling them to follow you through a crisis doesn't work. They'll comply superficially and disengage. In those situations, the better move is handing off authority to someone who has it, not trying to manufacture it on the spot. The other hard truth is that this doesn't scale well. The kind of direct, personal leadership that works in a crisis is unsustainable as a default mode. You can't run your organization this way day to day. It burns you out and it prevents anyone else from developing decision-making muscle. The goal isn't to be the hero in every emergency. The goal is to build systems that reduce the number of emergencies where individual heroics are the answer.
I track how many times per quarter I find myself making unilateral crisis decisions. If that number is above four, something is broken in the operating structure. Most teams I work with run at twelve to fifteen. That's not a leadership problem. That's a design problem. If you're dealing with a current situation and need something concrete to reference, there's a checklist that covers the first sixty minutes of a crisis response. It's available at crisisleadershipframework.com/download. It's not a theory document. It's the same thing I used during that 2021 incident, refined over three years of real events. It takes about ten minutes to work through and it covers decision rights, communication protocols, and the escalation paths most organizations forget to establish until they need them. The longer-term reading on this is lighter than the genre suggests. Most books on crisis leadership are written by people who managed to avoid personal risk in whatever situation they describe. The ones worth reading are the ones that acknowledge the possibility that your best decision still leads to a bad outcome. That's the part nobody sells you on. Courage isn't the guarantee of a good result. It's the willingness to act clearly when the result is unknown.
