Skip to main content

Lessons from Apollo 13 - working the problem

"Failure is not an option," has worked its way into many a group's mission and vision while, "Houston, we have a problem" has become a common colloquialism. The technicians and astronauts in Ron Howard's epic provide rational leadership during a crisis. In essence the movie is also the perfect example of virtual teams. Gene Kranz (Ed Harris), in charge of flight operations in Houston, and Jim Lovell (Tom Hanks), commander of the lunar mission display their leadership skills when an explosion occurs on the Apollo 13 craft. Through teamwork, ingenuity, and rational process these leaders solve a nearly impossible problem.

Krantz and Lovell maintain control in a chaotic situation which inspires confidence among the group. Apollo 13 shows that although leaders desire loyalty and passion, it is important to secure their group's confidence first.

Technical proficiency
  • Once the accident happened how did Krantz rely on the skills and expertise of his technicians?
  • How did Lovell work to initiate actions in the spaceship, and was he able to balance that with his technical responsibilities in the craft? How did he do it?
  • What steps does your group and you take to maintain technical proficiency?

  • How did Lovell contribute to the group process when Mattingly wanted to practice the docking procedure again after three hours of practice?
  • When Krantz had the team in the conference room how did he establish the goal and then how did he go about motivating others to achieve the goal of returning the space craft safely to earth?
  • Did Lovell make the right call when faced with the challenge of forcing Mattingly to stay behind because of the fear of measles?
  • How does a leader successfully build a strong team, to be able to make critical decisions?
  • How is your team doing?

Effective communications
  • Even as havoc reigns in Mission Control, Krantz asks his team to "Work the Problem." He then listened to the experts report in on their areas of the mission. How did his effective communications set the stage for a successful recovery?
  • Krantz says that "Failure is not an option" and Lovell told his crewmates "I intend to go home." By clearly stating their ideas and vision how did it direct the teams towards mission accomplishment?
  • Whose the best communicator you’ve had to deal with at work? What makes them different?

Vision development and implementation
  • JFK’s vision: "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."
  • How does a stated vision focus the group and bring a team together?
  • Lovell says, "Columbus, Lindberg, and Armstrong; it is not a miracle for man to walk on the moon, we just decided to go."
  • What’s the vision at your group? Has everyone decided "to go?

Conflict management
  • How did Lovell deal with stress and conflict in the LEM?
  • How did the CO2 challenge help the crew to overcome the conflict they were experiencing?
  • Is there more or less conflict when people are busy and focused or when there is less to do and they have time on their hands?
  • How did Krantz and Lovell go about alleviating conflict between the crew and the medical team?

Decision making and problem solving
  • How did the team work the “Power” problem?
  • Right after the explosion Krantz’s asks Mission Control "What do we have on the Space Craft that’s good?" Why did he ask this question?
  • How did it assist in making the correct decision to shut down the fuel cells?
  • Does everyone in your group ensure that all the correct information is available?

Creativity and innovation
  • There are many positive leadership qualities displayed in Apollo 13. How did Krantz create an environment within the Mission Control team to ensure they were able to figure out how to solve the CO2 problem with a "Square Peg in a Round Hole!"
  • Lovell states at the end of the movie; "Thousands of people worked to bring the three of us back home." How did creativity and innovation make the "Successful Failure" a reality?
  • How does your group build on lessons learned?


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