Challenger Case Study
Essay Preview: Challenger Case Study
Report this essay
This paper examines the different areas of Organizational Behavior that went wrong with the challenger case. It will touch down on how the type organizational culture at NASA contributed to the disaster, how the organizational structures and communication patterns contributed to flawed decision making and the role that leadership also played in the disaster. Also, the paper will cover how ethics apply to the case, and the many different ethical levels that can be discussed regarding the disaster and finally, it will discuss who was responsible for the “seriously flawed” decision making process and how it played its role in the disaster. By the end of this paper you will see how each of these factors played an integral part in the organizational disaster of the Challenger.
NASAs Organizational Culture
“Success breeds confidence and fantasy” (Starbucks-Milliken, 1988).
Prior to the Challenger disaster, NASA completed twenty-four successful launches. “When an organization succeeds, its managers usually attribute this success to themselves, or at least to their organization, rather than to luck. The organizations members grow more confident, of their own abilities, of their managers skill, and of their organizations existing programs and procedures” (Starbucks-Milliken, 1988). That is the organizational culture which gradually grew at NASA after the first launch in 1958. With repeated successful launches, NASA grew an image of themselves as an organization that does not commit any errors or mistakes. NASA did not perceive themselves as a typical organization. “It had a magical aura. NASA had not only experienced repeated successes, it had achieved the impossible. It had landed men on the moon and returned them safely to earth. Time and again, it had successfully completed missions with hardware that supposedly had very little chance of operating adequately” (Boffey, 1986a). With these perceptions and beliefs, it comes as no surprise that the NASA management would not accept the statements made by engineers that the Challenger launch would not become their twenty-fifth successful take-off. For instance, “during a teleconference on 27 January, 1986, Thiokols engineers said that NASA should not launch the shuttle if the ambient temperature was below 53 degrees because no previous launch had occurred with an ambient temperature below 53 degrees. Lawrence Mulloy protested: . . . there are currently no Launch Commit Criteria for joint temperature. What you are proposing to do is to generate a new Launch Commit Criteria on the eve of launch, after we have successfully flown with the existing Launch Commit Criteria 24 previous times (Commission, 1986, I-96). Mulloy spoke as if he had come to trust the Launch Commit Criteria that had always produced successes. (Starbuck-Milliken, 1988) This shows that NASA had no intention to delay the launch as it believed there was no chance of failure.
Therefore, as the Presidential Commission remarked “NASAs attitude historically has reflected the position that ÐWe can do anything”. Similarly, a former NASA budget analyst, Richard C. Cook, observed that “NASAs Ðwhole culture calls for Ða can-do attitude that NASA can do whatever it tries to do, can solve any problem that comes up” (Boffey, 1986b). The NASA organization would not accept the fact that it could fail, and this ÐWe can do anything culture contributed greatly to the Challenger disaster. If the management at NASA would have realized that the shuttle was not ready to launch on January 28, 1986, the lives of seven astronauts including ÐAmericas teacher in space would not have been lost. This disaster shows the effects of repeated successes, gradual acclimatization and the differing responsibilities between engineers and managers. NASAs past successes blinded their decision makers beliefs about probabilities of future successes (Starbuck Ð- Milliken, 1988). The management at NASA was so occupied with staying consistent to their culture that they ignored the possible threat to the seven astronauts on board the Challenger shuttle. Sadly, this disaster did not serve as a lesson for the organization. There are reports stating the organizational culture at NASA was a major factor which contributed to the Columbia disaster on February 1st, 2003, which claimed the lives of another seven astronauts (Aero Space Guide). If loss of human life is not enough to change NASAs culture and values, then what will?
Organizational Structures and Communication Patterns Contribution to Flawed Decision Making
There are many different reasons why the Space Shuttle Challenger disaster occurred. These causes include low temperature, O-ring failure / erosion, and growing pressure from the military, government, and the media. However, one of the most significant reasons for the Challenger disaster is the lack of communication and understanding between the various levels of employees at both Morton Thiokol and the NASA chain of command. Though the explosion of the Challenger was due to a technical flaw, problems within the organizational structure surrounding the Challenger were what ultimately led to the unsound decision to go ahead with the shuttle launch.
The decision making process around the launch of the Space Shuttle Challenger followed a narrow span of control Ð- a single chain of command A key example of this organizational structure was the Flight Readiness Review System, a four level, step-by-step process for certifying that the launch was a “go” to the Mission Management Team. Under this system, it was very difficult for staff from lower levels to communicate any concerns upward in the chain of command. Staff members did not want to be responsible for issues outside of their level in the organization, and were hesitant to go above their superiors with any concerns. As Ben Powers, a Marshall engineer stated “you dont override your chain of command” (Maier, 1992, P.31).
Breakdown in communication occurred between engineers, the lowest levels of the shuttle launch, and their managers, who ranked higher. When problems were communicated to higher levels, the issues were often modified, misinterpreted, or lost, depending on the interests of management. For example, the engineers were aware for a long time that O-ring tests revealed erosion problems, which could led to “Ðloss