Skip to main content

Lessons from great leaders, Lovell, Kranz and Liebergot #failureisnotanoption

No alt text provided for this image"Failure is not an option" and "Houston, we have a problem" are phrases from the movie Apollo 13 (one of my greatest movies ever, review it here). Lovell, Kranz and Liebergot have a close association to the Apollo programme, especially Apollo 13, and these great leaders are central to the story of "Failure is not an option."

  • Lovell is the spacecraft commander
  • Kranz is the flight director
  • Liebergot is Apollo EECOM

The following provides great insight into the Apollo 13 flight.

The leadership displayed during the Apollo 13 flight is commendable. It is also the perfect example of virtual teams. Kranz, in charge of flight operations in Houston, and Lovell, commander of the lunar mission are separated by thousands of miles of space. They were required to display their leadership skills, especially those of communication, when an explosion occurs on the Apollo 13 spacecraft. Ably assisted by Liebergot, and through teamwork, ingenuity, and rational process these leaders solve a nearly impossible problem.

Between them they maintain control in a chaotic situation which inspires confidence among the group. Although leaders desire loyalty and passion, it is important to secure their group's confidence first. Additionally, below are the lessons from these three great leaders and the examples:

  • Effective and efficient communications. Even as chaos reigns in Houston, Krantz asks the Mission Control team to "Work the Problem." He then listened to the experts report in on their areas of the mission. Effective communications set the stage for a successful recovery. Krantz says that "Failure is not an option" and Lovell told his flight crew "I intend to go home." Clear precise communications are required in certain situations, not rambling debate.
  • Operational proficiency. When the accident happened Krantz rely on the skills and expertise of his technicians while Lovell initiates actions in the spacecraft. Proficiency is required, especially in a highly technical environment.
  • Conflict management. Lovell display exceptional leadership to deal with stress and conflict in the LEM. Team members are less prone to conflict when they are occupied solving problems such as the Co2 challenge but the best example is when Kranz and Lovell disconnect the medical sensors when the medical team creates conflict.
  • Building a team.. Lovell agrees with Mattingly to practice the docking procedure again after three hours of practice. Leaders build a strong team to make critical decisions.
  • Vision. JFK’s vision was the one that inspired the United States and one that underpinned the Apollo programme: "I believe that this nation should commit itself to achieving the goal, before this decade is out, of landing a man on the moon and returning him safely to Earth." Lovell had a simple vision "Columbus, Lindberg, and Armstrong; it is not a miracle for man to walk on the moon, we just decided to go."
  • Decision making and problem solving. Right after the explosion Krantz’s asks Mission Control "What do we have on the spacecraft that’s good?" Good leaders work with what they have, not with what they do not.
  • Creativity and innovation. Apollo 13 is the essence of creativity. The LEM was designed to act as a vehicle to land on the moon but during the flight is was used as a deep space lifeboat. Great leaders can re-purpose what they have around them. All you need to do is look, and be able to do the same.

Please comment below any of your thoughts on the Apollo 13 flight or else read my articles on problem management here.

Ronald Bartels on twitter
This article was published over on LinkedIn: Lessons from great leaders, Lovell, Kranz and Liebergot #failureisnotanoption

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

Updated: Articles by Ron Bartels published on iot for all

  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all .  These are articles that I published during the course of the past year on one of the popular international Internet of Things publishing sites, iot for all . Improving Data Center Reliability With IoT Reliability and availability are essential to data centers. IoT can enable better issue tracking and data collection, leading to greater stability. Doing the Work Right in Data Centers With Checklists Data centers are complex. Modern economies rely upon their continuous operation. IoT solutions paired with this data center checklist can help! IoT Optimi