SlideShare una empresa de Scribd logo
1 de 13
The Communication Challenges at NASA on and before January 28 1986
      Leading to the Destruction of the Space Shuttle: Challenger

                             Prepared for
                         Dr. Margaret Smith
                     University of Texas at El Paso




                              ENGL3355
                              GROUP 6

                           GABRIEL ORTIZ
                          REBECA SANCHEZ
                          STEPHEN SIMON
 This report analyzes the deficiencies in communication at NASA which led to the
  destruction of the Space Shuttle Challenger on January 28, 1986 and what could
  have been done differently to prevent the destruction of the shuttle and the deaths
  of the seven astronauts.
Introduction

 NASA is the agency of the United States government that is responsible for the
  space program which is a civilian space program and aerospace research.
 Overall NASA space shuttle program had 135 missions in the program and on July
  21, 2011 and spanned 30 years with over 300 astronauts sent into space.
 During this history the shuttle fleet lost 2 orbiters in 14 astronauts in 2 separate
  disasters: Challenger in 1986 in Columbia in 2003.




 This informational Case Analysis highlight communications failures which lead to
  the death of astronauts and destruction of property due to managerial and financial
  pressures of government contractors who are the lowest bidders on our
  governmental projects.
SWOT Analysis Communication Challenges at
                   NASA
                   STRENGHTS
                                                                                WEAKNESS



                                                             Usually, development and implementation of projects at
It was the most important and competitive organization in
                                                             NASA took much more time and resources than originally
the space transportation business from among the Russian
                                                             thought.
and European ones.
                                                             Special projects and planned launches, before the
NASA had many projects and special programs which were
                                                             Challenger accidents, were postponed many times.
going bring important information to the earth such as
                                                             NASA is a very large and complex structure which made
Information about the Halley’s Comet.
                                                             difficult communication between departments and
It was (and still is) composed by the most brilliant minds
                                                             management.
form North America not only in the engineering and
                                                             There were many people involved form external
scientific side but also in the administrative and project
                                                             organizations and companies. NASA controls their actions
management areas too.
                                                             through written specifications and verification.


                 OPPORTUNITIES                                                   THREATS



Better planning and more realistic deadlines were needed.
NASA needed a better system of communication where           They were being threaded by the growth of European and
every participant in a process was aware of what the other   Russian space agencies. All the improvements NASA had
was doing.                                                   done before were being reached by other agencies in the
Data transparency is made available for everyone in the      world.
organization.                                                Budget could be cut if more delays were presented and
A worst scenario and contingency plans with well thought     metrics not met.
out implications.                                            Political scenario in pressuring senior management and
Final revisions before launches and systems that clearly     staff to sign off.
identify if something deviates from the plan.
THE NATURE OF NASA’S COMMUNICATION CHALLENGE


 Lack of communication during the development and launch planning for the
  shuttle Challenger was the main reason of its explosion. An O-ring in the solid
  rocket booster was the technical reason why the tragedy happens. Morton
  Thiokol was the company contracted for doing the solid rocket booster which
  contained the O-ring. The launched had been postponed two times before
  January 1986. The Morton Thiokol Company had the opportunity of informing
  NASA that there was a problem and assumption of responsibility for the
  previous delays but they did not.
THE CURRENT COMMUNICATION CHALLENGE AT NASA



 In retrospect, taking into account all the variables, we have to do analyze very
  carefully the causes and consequences of the decisions made. In this tragedy
  we identified three main communication issues that lead the Challenger
  explosion.

     Lack of organizational communication

     Lack of understanding between management and engineers.

     Lack of use of good persuasion techniques by people who knew the risks.
LACK OF ORGANIZATIONAL COMMUNICATION


 There were two companies involved in this situation, NASA and Morton-
  Thiokol.

 The problem came when in 1981 and later in 1985, Morton Thiokol did not
  inform NASA about the problems they were having with the O-rings. Here we
  see a lack of communication between organizations.

 In any human relation, communication is basic and in this case a commercial
  communication was very important since the company failed and lives were
  lost
LACK OF UNDERSTANDING BETWEEN MANAGEMENT
               AND ENGINEERS


                                       
 The day before the launch, when the temperature was not dropping down,
  engineers from Morton-Thiokol were very worried because they knew the O-
  rings failed when tested in cold wheatear.

 Engineers presented information about why was not safe for the Challenger to
  launch.

 The information presented was deemed non-conclusive for the managers from
  both sides, NASA and Morton-Thiokol.

 The main problem here is that those engineers did not explain clearly the
  effects so management thought it was not a big deal and they by passed it.
LACK OF USE OF GOOD PERSUASION TECHNIQUES BY
             PEOPLE WHO KNEW THE RISKS


 A persuasive presentation can be an effective workplace communication tool.
    No more than one very good written persuasive letter would be enough to
    convince management to delay the launch.

 The main problem here was that even when the engineers knew exactly what
    they were talking about, their method of saying it was not the most appropriate.

   They were facing very important people who had a big weight on their backs.
    But these type of people are the kind we always have to face at work.

 We have to report our work to someone and if there is something wrong with
    anything we have to report it too. The engineers were not very persuasive and
    the consequences went very bad.
THE PROPOSED SOLUTION TO THE CHALLENGE

 What could have been done differently to prevent
 such a historical catastrophe?

    The solution is a higher level of accountability for the
     communication practices used at each level of operations
     leading to safer and successful shuttle launches for future
     generations.
THE PROPOSED SOLUTION TO THE CHALLENGE

 First of all, NASA should set rigorous standards for justifying
  actions and decisions made at every department and
  appropriate level of operations participating in the mission.
     Meetings should be conducted frequently.
     A representative from every department and managerial level of
      operations must be present and work as a team.

 Secondly, before any decisions and actions were taken, there
  should have been conclusive discussions regarding the
  matters of concern.
     Having representatives from all those involved in the operation present.
      This could have enabled them to input their perspective and proposals.
     For accountability purposes, these resolutions should have been in
      writing and signed for approval in accordance to the hierarchy within
      NASA and those outside parties connected with the assignment.
CONCLUSION

 The families of those brave souls lost in 1986 on Challenger shall never forget
  nor shall the children who sat in their classroom waiting to see and speak with
  their teacher in space only to witness the major malfunction as their beloved
  teacher died in the explosion. This avoidable accident caused by
  miscommunication is a hard earned lesson and will undoubtedly save the lives
  of many astronauts in the future. There can be many causes of
  miscommunication and whether deliberate or unintentional, its lasting effect
  remains. These communication lessons are hard won and hard taught. For
  posterity, let’s try to remember them lest they repeat themselves.
REFERENCES




   Hall, J. (2003). Columbia and Challenger: organizational failure at NASA. Space Policy, 19(4) 239-48.
   (1986). Pressure May Have Influenced Decision to Launch. Science, 231(4745), 1495-49.
   (2011). NASA history. Congressional Digest, 90(7), 196-224.
   (2012). NASA Fellowship in the History of Space Technology. Technology & Culture, 53(1), 146-160.

Más contenido relacionado

La actualidad más candente

La actualidad más candente (18)

Stranded on the Moon - Team Engagement Activity.pptx
Stranded on the Moon - Team Engagement Activity.pptxStranded on the Moon - Team Engagement Activity.pptx
Stranded on the Moon - Team Engagement Activity.pptx
 
Eis simulation team 3
Eis simulation team 3Eis simulation team 3
Eis simulation team 3
 
TerraCog GPS
TerraCog GPSTerraCog GPS
TerraCog GPS
 
Bermuda Triangle By Tupesh ( BE_MECH )
Bermuda Triangle By Tupesh ( BE_MECH )Bermuda Triangle By Tupesh ( BE_MECH )
Bermuda Triangle By Tupesh ( BE_MECH )
 
Bermuda triangle
Bermuda triangleBermuda triangle
Bermuda triangle
 
SpaceX Case Study
SpaceX Case StudySpaceX Case Study
SpaceX Case Study
 
Bermuda Triangle
Bermuda TriangleBermuda Triangle
Bermuda Triangle
 
MH 370
MH 370MH 370
MH 370
 
Risk management plan tyre recycling plant
Risk management plan  tyre recycling plantRisk management plan  tyre recycling plant
Risk management plan tyre recycling plant
 
DC-10
DC-10DC-10
DC-10
 
Crisis manual template en
Crisis manual template enCrisis manual template en
Crisis manual template en
 
Project Management Plan Template
Project Management Plan TemplateProject Management Plan Template
Project Management Plan Template
 
A content about Bermuda Triangle
A content about Bermuda Triangle A content about Bermuda Triangle
A content about Bermuda Triangle
 
Malaysian airline MH-370
Malaysian  airline MH-370Malaysian  airline MH-370
Malaysian airline MH-370
 
WP3 Quality Management Plan
WP3 Quality Management PlanWP3 Quality Management Plan
WP3 Quality Management Plan
 
Bermuda triangle/Devil's Triangle
Bermuda triangle/Devil's TriangleBermuda triangle/Devil's Triangle
Bermuda triangle/Devil's Triangle
 
Terracog gps
Terracog gpsTerracog gps
Terracog gps
 
The Bermuda Triangle
The Bermuda TriangleThe Bermuda Triangle
The Bermuda Triangle
 

Destacado

Engl3355 case analysis group 6
Engl3355 case analysis group 6Engl3355 case analysis group 6
Engl3355 case analysis group 6Aneth Sanchez
 
Tata communications
Tata communicationsTata communications
Tata communicationsPele Dcosta
 
Nasa Space Shuttle Challenger disaster: Remembering the tragedy on its 30th a...
Nasa Space Shuttle Challenger disaster: Remembering the tragedy on its 30th a...Nasa Space Shuttle Challenger disaster: Remembering the tragedy on its 30th a...
Nasa Space Shuttle Challenger disaster: Remembering the tragedy on its 30th a...guimera
 
Columbia Space Shuttle Disaster
Columbia Space Shuttle DisasterColumbia Space Shuttle Disaster
Columbia Space Shuttle DisasterNazish Khalid
 
Nasa Challenger Explosion
Nasa Challenger ExplosionNasa Challenger Explosion
Nasa Challenger Explosiontylerfreas
 
Organizational Communication
Organizational CommunicationOrganizational Communication
Organizational Communicationamanideutsch
 
Strategic Planning For Healthcare Services
Strategic Planning For Healthcare ServicesStrategic Planning For Healthcare Services
Strategic Planning For Healthcare Servicesalberpaules
 

Destacado (10)

Bad Infographics: Some Examples
Bad Infographics: Some ExamplesBad Infographics: Some Examples
Bad Infographics: Some Examples
 
Engl3355 case analysis group 6
Engl3355 case analysis group 6Engl3355 case analysis group 6
Engl3355 case analysis group 6
 
Tata communications
Tata communicationsTata communications
Tata communications
 
Nasa Space Shuttle Challenger disaster: Remembering the tragedy on its 30th a...
Nasa Space Shuttle Challenger disaster: Remembering the tragedy on its 30th a...Nasa Space Shuttle Challenger disaster: Remembering the tragedy on its 30th a...
Nasa Space Shuttle Challenger disaster: Remembering the tragedy on its 30th a...
 
Hp Life Small Business Communications Plan
Hp Life Small Business Communications PlanHp Life Small Business Communications Plan
Hp Life Small Business Communications Plan
 
Columbia Space Shuttle Disaster
Columbia Space Shuttle DisasterColumbia Space Shuttle Disaster
Columbia Space Shuttle Disaster
 
Nasa Challenger Explosion
Nasa Challenger ExplosionNasa Challenger Explosion
Nasa Challenger Explosion
 
Whistleblowing
WhistleblowingWhistleblowing
Whistleblowing
 
Organizational Communication
Organizational CommunicationOrganizational Communication
Organizational Communication
 
Strategic Planning For Healthcare Services
Strategic Planning For Healthcare ServicesStrategic Planning For Healthcare Services
Strategic Planning For Healthcare Services
 

Similar a The communication challenges at nasa

PAD 502 Organization DynamicsReadings Themes Class Discussion.docx
PAD 502 Organization DynamicsReadings Themes Class Discussion.docxPAD 502 Organization DynamicsReadings Themes Class Discussion.docx
PAD 502 Organization DynamicsReadings Themes Class Discussion.docxgerardkortney
 
Due August 7,2019First, watch the video Personal Potential The.docx
Due August 7,2019First, watch the video Personal Potential The.docxDue August 7,2019First, watch the video Personal Potential The.docx
Due August 7,2019First, watch the video Personal Potential The.docxmadlynplamondon
 
Montazar AlmashamaEnglish 102Kevin Leaverton8-3-14.docx
Montazar AlmashamaEnglish 102Kevin Leaverton8-3-14.docxMontazar AlmashamaEnglish 102Kevin Leaverton8-3-14.docx
Montazar AlmashamaEnglish 102Kevin Leaverton8-3-14.docxmoirarandell
 
Mandell.humboldt
Mandell.humboldtMandell.humboldt
Mandell.humboldtNASAPMC
 
A C C I D E N T I N V E S T I G A T I O N B O A R DCOLUM.docx
A C C I D E N T  I N V E S T I G A T I O N  B O A R DCOLUM.docxA C C I D E N T  I N V E S T I G A T I O N  B O A R DCOLUM.docx
A C C I D E N T I N V E S T I G A T I O N B O A R DCOLUM.docxransayo
 
3309_Space_Situational_Awareness_2015_4pp
3309_Space_Situational_Awareness_2015_4pp3309_Space_Situational_Awareness_2015_4pp
3309_Space_Situational_Awareness_2015_4ppTiziana Casinelli
 
NASA Case Study JPL Knowledge Management
NASA Case Study JPL Knowledge ManagementNASA Case Study JPL Knowledge Management
NASA Case Study JPL Knowledge ManagementPuneet Bhalla
 
Investigation on Columbia space shuttle disaster
Investigation on Columbia space shuttle disasterInvestigation on Columbia space shuttle disaster
Investigation on Columbia space shuttle disasterMahmudul Hasan Rifat
 
NASA Advancing Climate Strategy 2023
 NASA Advancing Climate Strategy 2023 NASA Advancing Climate Strategy 2023
NASA Advancing Climate Strategy 2023Dr. Pankaj Dhussa
 
The Challenger and Columbia Shuttle DisastersTo be considered co.docx
The Challenger and Columbia Shuttle DisastersTo be considered co.docxThe Challenger and Columbia Shuttle DisastersTo be considered co.docx
The Challenger and Columbia Shuttle DisastersTo be considered co.docxmamanda2
 
Columbia ccm assignment
Columbia ccm assignmentColumbia ccm assignment
Columbia ccm assignmentKavita Patil
 
y Charles ZalabakGraduating with a bachelor’s degree in enginee.docx
y Charles ZalabakGraduating with a bachelor’s degree in enginee.docxy Charles ZalabakGraduating with a bachelor’s degree in enginee.docx
y Charles ZalabakGraduating with a bachelor’s degree in enginee.docxadampcarr67227
 
Fletcher risk vs_innovation_120220
Fletcher risk vs_innovation_120220Fletcher risk vs_innovation_120220
Fletcher risk vs_innovation_120220NASAPMC
 
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI
C H A P T E R 6Organizational CultureNASA’s ORGANIZATIC H A P T E R 6Organizational CultureNASA’s ORGANIZATI
C H A P T E R 6Organizational CultureNASA’s ORGANIZATIjenkinsmandie
 
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docxC H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docxdewhirstichabod
 
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docxC H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docxjasoninnes20
 

Similar a The communication challenges at nasa (20)

PAD 502 Organization DynamicsReadings Themes Class Discussion.docx
PAD 502 Organization DynamicsReadings Themes Class Discussion.docxPAD 502 Organization DynamicsReadings Themes Class Discussion.docx
PAD 502 Organization DynamicsReadings Themes Class Discussion.docx
 
Due August 7,2019First, watch the video Personal Potential The.docx
Due August 7,2019First, watch the video Personal Potential The.docxDue August 7,2019First, watch the video Personal Potential The.docx
Due August 7,2019First, watch the video Personal Potential The.docx
 
Montazar AlmashamaEnglish 102Kevin Leaverton8-3-14.docx
Montazar AlmashamaEnglish 102Kevin Leaverton8-3-14.docxMontazar AlmashamaEnglish 102Kevin Leaverton8-3-14.docx
Montazar AlmashamaEnglish 102Kevin Leaverton8-3-14.docx
 
Mandell.humboldt
Mandell.humboldtMandell.humboldt
Mandell.humboldt
 
A C C I D E N T I N V E S T I G A T I O N B O A R DCOLUM.docx
A C C I D E N T  I N V E S T I G A T I O N  B O A R DCOLUM.docxA C C I D E N T  I N V E S T I G A T I O N  B O A R DCOLUM.docx
A C C I D E N T I N V E S T I G A T I O N B O A R DCOLUM.docx
 
3309_Space_Situational_Awareness_2015_4pp
3309_Space_Situational_Awareness_2015_4pp3309_Space_Situational_Awareness_2015_4pp
3309_Space_Situational_Awareness_2015_4pp
 
NASA Case Study JPL Knowledge Management
NASA Case Study JPL Knowledge ManagementNASA Case Study JPL Knowledge Management
NASA Case Study JPL Knowledge Management
 
Investigation on Columbia space shuttle disaster
Investigation on Columbia space shuttle disasterInvestigation on Columbia space shuttle disaster
Investigation on Columbia space shuttle disaster
 
NASA Advancing Climate Strategy 2023
 NASA Advancing Climate Strategy 2023 NASA Advancing Climate Strategy 2023
NASA Advancing Climate Strategy 2023
 
The Challenger and Columbia Shuttle DisastersTo be considered co.docx
The Challenger and Columbia Shuttle DisastersTo be considered co.docxThe Challenger and Columbia Shuttle DisastersTo be considered co.docx
The Challenger and Columbia Shuttle DisastersTo be considered co.docx
 
AAS
AASAAS
AAS
 
DARPA 50 YEARS
DARPA 50 YEARSDARPA 50 YEARS
DARPA 50 YEARS
 
Columbia ccm assignment
Columbia ccm assignmentColumbia ccm assignment
Columbia ccm assignment
 
y Charles ZalabakGraduating with a bachelor’s degree in enginee.docx
y Charles ZalabakGraduating with a bachelor’s degree in enginee.docxy Charles ZalabakGraduating with a bachelor’s degree in enginee.docx
y Charles ZalabakGraduating with a bachelor’s degree in enginee.docx
 
Launch Pad Communications Plan Book
Launch Pad Communications Plan BookLaunch Pad Communications Plan Book
Launch Pad Communications Plan Book
 
Fletcher risk vs_innovation_120220
Fletcher risk vs_innovation_120220Fletcher risk vs_innovation_120220
Fletcher risk vs_innovation_120220
 
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI
C H A P T E R 6Organizational CultureNASA’s ORGANIZATIC H A P T E R 6Organizational CultureNASA’s ORGANIZATI
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI
 
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docxC H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
 
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docxC H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
C H A P T E R 6Organizational CultureNASA’s ORGANIZATI.docx
 
RTM VI flyer
RTM VI flyerRTM VI flyer
RTM VI flyer
 

Último

DevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenDevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenHervé Boutemy
 
Dev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebDev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebUiPathCommunity
 
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmaticsKotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmaticscarlostorres15106
 
Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Scott Keck-Warren
 
Scanning the Internet for External Cloud Exposures via SSL Certs
Scanning the Internet for External Cloud Exposures via SSL CertsScanning the Internet for External Cloud Exposures via SSL Certs
Scanning the Internet for External Cloud Exposures via SSL CertsRizwan Syed
 
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationBeyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationSafe Software
 
AI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsAI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsMemoori
 
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr LapshynFwdays
 
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks..."LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...Fwdays
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024Lorenzo Miniero
 
Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piececharlottematthew16
 
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostLeverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostZilliz
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Commit University
 
Are Multi-Cloud and Serverless Good or Bad?
Are Multi-Cloud and Serverless Good or Bad?Are Multi-Cloud and Serverless Good or Bad?
Are Multi-Cloud and Serverless Good or Bad?Mattias Andersson
 
Gen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfGen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfAddepto
 
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your BrandWordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brandgvaughan
 
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)Wonjun Hwang
 
CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):comworks
 

Último (20)

DevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache MavenDevoxxFR 2024 Reproducible Builds with Apache Maven
DevoxxFR 2024 Reproducible Builds with Apache Maven
 
Dev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio WebDev Dives: Streamline document processing with UiPath Studio Web
Dev Dives: Streamline document processing with UiPath Studio Web
 
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmaticsKotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
Kotlin Multiplatform & Compose Multiplatform - Starter kit for pragmatics
 
Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024Advanced Test Driven-Development @ php[tek] 2024
Advanced Test Driven-Development @ php[tek] 2024
 
Scanning the Internet for External Cloud Exposures via SSL Certs
Scanning the Internet for External Cloud Exposures via SSL CertsScanning the Internet for External Cloud Exposures via SSL Certs
Scanning the Internet for External Cloud Exposures via SSL Certs
 
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry InnovationBeyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
Beyond Boundaries: Leveraging No-Code Solutions for Industry Innovation
 
AI as an Interface for Commercial Buildings
AI as an Interface for Commercial BuildingsAI as an Interface for Commercial Buildings
AI as an Interface for Commercial Buildings
 
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
"Federated learning: out of reach no matter how close",Oleksandr Lapshyn
 
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks..."LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
"LLMs for Python Engineers: Advanced Data Analysis and Semantic Kernel",Oleks...
 
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptxE-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
E-Vehicle_Hacking_by_Parul Sharma_null_owasp.pptx
 
SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024SIP trunking in Janus @ Kamailio World 2024
SIP trunking in Janus @ Kamailio World 2024
 
Story boards and shot lists for my a level piece
Story boards and shot lists for my a level pieceStory boards and shot lists for my a level piece
Story boards and shot lists for my a level piece
 
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage CostLeverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
Leverage Zilliz Serverless - Up to 50X Saving for Your Vector Storage Cost
 
Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!Nell’iperspazio con Rocket: il Framework Web di Rust!
Nell’iperspazio con Rocket: il Framework Web di Rust!
 
Are Multi-Cloud and Serverless Good or Bad?
Are Multi-Cloud and Serverless Good or Bad?Are Multi-Cloud and Serverless Good or Bad?
Are Multi-Cloud and Serverless Good or Bad?
 
Gen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdfGen AI in Business - Global Trends Report 2024.pdf
Gen AI in Business - Global Trends Report 2024.pdf
 
WordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your BrandWordPress Websites for Engineers: Elevate Your Brand
WordPress Websites for Engineers: Elevate Your Brand
 
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
Bun (KitWorks Team Study 노별마루 발표 2024.4.22)
 
DMCC Future of Trade Web3 - Special Edition
DMCC Future of Trade Web3 - Special EditionDMCC Future of Trade Web3 - Special Edition
DMCC Future of Trade Web3 - Special Edition
 
CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):CloudStudio User manual (basic edition):
CloudStudio User manual (basic edition):
 

The communication challenges at nasa

  • 1. The Communication Challenges at NASA on and before January 28 1986 Leading to the Destruction of the Space Shuttle: Challenger Prepared for Dr. Margaret Smith University of Texas at El Paso ENGL3355 GROUP 6 GABRIEL ORTIZ REBECA SANCHEZ STEPHEN SIMON
  • 2.  This report analyzes the deficiencies in communication at NASA which led to the destruction of the Space Shuttle Challenger on January 28, 1986 and what could have been done differently to prevent the destruction of the shuttle and the deaths of the seven astronauts.
  • 3. Introduction  NASA is the agency of the United States government that is responsible for the space program which is a civilian space program and aerospace research.  Overall NASA space shuttle program had 135 missions in the program and on July 21, 2011 and spanned 30 years with over 300 astronauts sent into space.  During this history the shuttle fleet lost 2 orbiters in 14 astronauts in 2 separate disasters: Challenger in 1986 in Columbia in 2003.  This informational Case Analysis highlight communications failures which lead to the death of astronauts and destruction of property due to managerial and financial pressures of government contractors who are the lowest bidders on our governmental projects.
  • 4. SWOT Analysis Communication Challenges at NASA STRENGHTS WEAKNESS Usually, development and implementation of projects at It was the most important and competitive organization in NASA took much more time and resources than originally the space transportation business from among the Russian thought. and European ones. Special projects and planned launches, before the NASA had many projects and special programs which were Challenger accidents, were postponed many times. going bring important information to the earth such as NASA is a very large and complex structure which made Information about the Halley’s Comet. difficult communication between departments and It was (and still is) composed by the most brilliant minds management. form North America not only in the engineering and There were many people involved form external scientific side but also in the administrative and project organizations and companies. NASA controls their actions management areas too. through written specifications and verification. OPPORTUNITIES THREATS Better planning and more realistic deadlines were needed. NASA needed a better system of communication where They were being threaded by the growth of European and every participant in a process was aware of what the other Russian space agencies. All the improvements NASA had was doing. done before were being reached by other agencies in the Data transparency is made available for everyone in the world. organization. Budget could be cut if more delays were presented and A worst scenario and contingency plans with well thought metrics not met. out implications. Political scenario in pressuring senior management and Final revisions before launches and systems that clearly staff to sign off. identify if something deviates from the plan.
  • 5. THE NATURE OF NASA’S COMMUNICATION CHALLENGE  Lack of communication during the development and launch planning for the shuttle Challenger was the main reason of its explosion. An O-ring in the solid rocket booster was the technical reason why the tragedy happens. Morton Thiokol was the company contracted for doing the solid rocket booster which contained the O-ring. The launched had been postponed two times before January 1986. The Morton Thiokol Company had the opportunity of informing NASA that there was a problem and assumption of responsibility for the previous delays but they did not.
  • 6. THE CURRENT COMMUNICATION CHALLENGE AT NASA  In retrospect, taking into account all the variables, we have to do analyze very carefully the causes and consequences of the decisions made. In this tragedy we identified three main communication issues that lead the Challenger explosion.  Lack of organizational communication  Lack of understanding between management and engineers.  Lack of use of good persuasion techniques by people who knew the risks.
  • 7. LACK OF ORGANIZATIONAL COMMUNICATION  There were two companies involved in this situation, NASA and Morton- Thiokol.  The problem came when in 1981 and later in 1985, Morton Thiokol did not inform NASA about the problems they were having with the O-rings. Here we see a lack of communication between organizations.  In any human relation, communication is basic and in this case a commercial communication was very important since the company failed and lives were lost
  • 8. LACK OF UNDERSTANDING BETWEEN MANAGEMENT AND ENGINEERS   The day before the launch, when the temperature was not dropping down, engineers from Morton-Thiokol were very worried because they knew the O- rings failed when tested in cold wheatear.  Engineers presented information about why was not safe for the Challenger to launch.  The information presented was deemed non-conclusive for the managers from both sides, NASA and Morton-Thiokol.  The main problem here is that those engineers did not explain clearly the effects so management thought it was not a big deal and they by passed it.
  • 9. LACK OF USE OF GOOD PERSUASION TECHNIQUES BY PEOPLE WHO KNEW THE RISKS  A persuasive presentation can be an effective workplace communication tool. No more than one very good written persuasive letter would be enough to convince management to delay the launch.  The main problem here was that even when the engineers knew exactly what they were talking about, their method of saying it was not the most appropriate.  They were facing very important people who had a big weight on their backs. But these type of people are the kind we always have to face at work.  We have to report our work to someone and if there is something wrong with anything we have to report it too. The engineers were not very persuasive and the consequences went very bad.
  • 10. THE PROPOSED SOLUTION TO THE CHALLENGE  What could have been done differently to prevent such a historical catastrophe?  The solution is a higher level of accountability for the communication practices used at each level of operations leading to safer and successful shuttle launches for future generations.
  • 11. THE PROPOSED SOLUTION TO THE CHALLENGE  First of all, NASA should set rigorous standards for justifying actions and decisions made at every department and appropriate level of operations participating in the mission.  Meetings should be conducted frequently.  A representative from every department and managerial level of operations must be present and work as a team.  Secondly, before any decisions and actions were taken, there should have been conclusive discussions regarding the matters of concern.  Having representatives from all those involved in the operation present. This could have enabled them to input their perspective and proposals.  For accountability purposes, these resolutions should have been in writing and signed for approval in accordance to the hierarchy within NASA and those outside parties connected with the assignment.
  • 12. CONCLUSION  The families of those brave souls lost in 1986 on Challenger shall never forget nor shall the children who sat in their classroom waiting to see and speak with their teacher in space only to witness the major malfunction as their beloved teacher died in the explosion. This avoidable accident caused by miscommunication is a hard earned lesson and will undoubtedly save the lives of many astronauts in the future. There can be many causes of miscommunication and whether deliberate or unintentional, its lasting effect remains. These communication lessons are hard won and hard taught. For posterity, let’s try to remember them lest they repeat themselves.
  • 13. REFERENCES  Hall, J. (2003). Columbia and Challenger: organizational failure at NASA. Space Policy, 19(4) 239-48.  (1986). Pressure May Have Influenced Decision to Launch. Science, 231(4745), 1495-49.  (2011). NASA history. Congressional Digest, 90(7), 196-224.  (2012). NASA Fellowship in the History of Space Technology. Technology & Culture, 53(1), 146-160.