loading . . . Why NASA flight director Gene Kranz is the gold standard for incident commanders Who was the greatest incident commander of all time? My money is on Gene Kranz.
If you’ve seen the 1995 movie _Apollo 13_ (and if you haven’t, you should; it’s a gripping tale even though you know the outcome, and along the way it’s a master class in incident command), you’ve seen Ed Harris portray Kranz during one of the most harrowing incidents in the history of human spaceflight. In April 1970, an oxygen tank explosion crippled the Apollo 13 spacecraft roughly 200,000 miles from Earth, turning what was supposed to be the third Apollo landing on the Moon into a desperate fight to bring three astronauts home alive. Kranz was NASA’s lead flight director in Mission Control throughout the multi-day crisis.
What makes Kranz the gold standard for incident command isn’t what he knew. It’s what he _did_ (and more importantly, what he _didn’t_ do).
# His job wasn’t to solve the problem
Watch the crisis scenes in the movie closely. Kranz doesn’t try to solve the technical problems himself. He has a room full of brilliant engineers for that. Each of those engineers, in turn, is backed by a “back room” of specialists focused on specific spacecraft systems. Kranz’s job isn’t to solve the problem. His job is to ensure that the problem gets solved, and that’s a subtle but critical difference.
That distinction is fundamental to effective incident command, and many companies get it wrong.
The incident commander role often falls to the most senior engineer by default, with no regard for the practical consequences. The technical work suffers because their best problem-solver keeps getting pulled away to handle logistics and communication, and the overall response suffers because nobody is focused full-time on running it.
# What he actually did instead
Kranz was technical enough to understand what his engineers were telling him, and trying to tell each other, but he wasn’t running the calculations himself. So if he wasn’t personally solving the problem, what was he doing instead? His focus was on ensuring that the right people were working the right problems at the right time, not on directly working any of the problems himself.
Watch the movie scenes carefully, and you’ll see a masterclass in incident command:
**He organized the response.** He set priorities, assigned responsibilities, and made sure every critical task had someone working on it. When the crisis began, he immediately reframed the mission: “From this moment on, we are improvising a new mission: how do we get our people home?”
**He demanded clear information.** He asked sharp questions and required his team to give him straight answers, not hedged guesses. When the crisis began and readings were contradictory, his instinct was to cut through the speculation: “Let’s work the problem, people. Let’s not make things worse by _guessing_.”
**He made decisions under uncertainty.** His engineers disagreed about whether to attempt a direct abort or use the Moon’s gravity to slingshot the crew home. Both options carried enormous risk. Kranz listened to the competing proposals, weighed the tradeoffs, and decided. Then he explained his reasoning so everyone was on the same page.
**He kept them looking for possibilities, without being fixated on problems.** While his engineers were focused on the individual failures they were trying to address, Kranz stepped back and asked: “What do we have on the spacecraft that’s good?”, challenging them to look for opportunities to use capabilities in unexpected ways to further the mission. When told that a certain system wasn’t designed to do what they needed, he shot back: “I don’t care about what anything was designed to do, I care about what it CAN do.”
**He facilitated, not dictated.** When engineers brought counter-proposals, he considered them and changed his mind when they were right. When discussion got heated, he reasserted calm: “Let’s hold it down, people.” He allowed debate when it was productive and cut it off when it wasn’t.
**He managed the emotional temperature.** In military and emergency management circles, this quality is called “command presence.” It doesn’t mean barking orders or being stoic. It means being the steady center of gravity for the response. Responders unconsciously look to the incident commander for cues about how bad things are and whether the situation is under control. If they’re calm and focused, that calmness radiates to the team. If they’re frantic, the team gets frantic too.
Kranz was the calmest person in the room precisely when the room needed calm the most. Not because the situation wasn’t dire, but because he understood that if he lost his composure, everyone else would too.
# “Failure is not an option”
Kranz’s famous line from the movie has become a cliché, but it’s worth revisiting. Watch the scene again. It’s not bravado. It’s a statement of intent from someone who has assessed the situation, accepted the constraints, and decided that the team is going to find a way through. He doesn’t pretend the situation isn’t terrible. He tells his team exactly how bad it is, exactly what they need to do, and then sets the expectation that they will find a way to do it.
That’s what good incident command looks like. Not magical thinking, not denial, not heroics. Clear-eyed assessment, clear decisions, and relentless follow-through.
# The lesson for your incident response
Your incidents probably don’t involve life-or-death stakes while the whole world watches anxiously. But the model is the same.
The incident commander’s job is to ensure that the problem gets solved, not to solve the problem themselves. That means organizing the response, making decisions, tracking what’s been tried and what hasn’t, communicating with stakeholders, and being the steady center of gravity so everyone else can do their best work.
Many companies default to making their most senior engineer the incident commander. It seems reasonable: they have the most authority, the most experience, the most knowledge.
But your incident commander doesn’t need to be your top engineer. They need to be the person who can stay calm, make decisions with incomplete information, facilitate a room full of smart people who disagree, and ensure that nothing falls through the cracks while everyone else focuses on the technical work.
Gene Kranz showed what incident command looks like when it’s done right. More than half a century later, he’s still the gold standard to aspire to.
* * *
_I’m writing a book about incident management for software engineering teams, drawing on lessons from both the tech industry and public safety (and movies about NASA!). If you’d like to hear when it’s available, visitim4ds.com._
_If your company needs help with incident management right now, my consulting practice isGreatCircle.com/im._ https://greatcircle.com/blog/2026/04/07/gene-kranz-gold-standard/
