Learning from failure in systems engineering: A panel discussion

This paper summarizes the discussion of the Learning from Failure in Systems Engineering panel that was held in Huntsville, AL on November 8, 2010. The panel objective was to discuss how systems engineers respond to and learn from failure and identify future directions important to the community. The panel consisted of four representatives with experience in government, industry, and academia: (1) Ronald Kadish from Booz Allen Hamilton and former director of the Missile Defense Agency, (2) Gary Payton, retired Deputy Under Secretary of the Air Force for Space Programs, (3) John Thomas from Booz Allen Hamilton and President‐elect of INCOSE, and (4) Michael Griffin from the University of Alabama, Huntsville and former NASA Administrator. Each panelist was asked to (i) provide an opening statement and elaborate on their experience with failure, (ii) describe when failure is appropriate, (iii) describe how we learn and react to failure, and (iv) identify and discuss techniques to improve how systems engineers react to failure. Several common themes arose from the discussion including: failure is an option, the importance of failure to allow reassessment, and more process is not the solution. Each of these is discussed in turn along with future directions identified for reacting to and learning from failure. © 2011 Wiley Periodicals, Inc. Syst Eng

[1]  Philip John,et al.  Systems engineering in an age of complexity , 2004, IEEE Engineering Management Review.

[2]  Robert L. Wears,et al.  Automation, interaction, complexity, and failure: A case study , 2006, Reliab. Eng. Syst. Saf..

[3]  Madeleine L'Engle Walking on Water: Reflections on Faith and Art , 1980 .

[4]  William B. Rouse,et al.  Car wars: Factors underlying the success or failure of new car programs , 2010, Syst. Eng..

[5]  Gene Kranz,et al.  Failure Is Not an Option: Mission Control from Mercury to Apollo 13 and Beyond , 2000 .

[6]  Richard d. Sissonjr. Failure analysis and the need for enhancing communications , 2005 .

[7]  T. C. McKelvey How to improve the effectiveness of hazard and operability analysis , 1988 .

[8]  Michael J. Kuchinski VERDICT : A distributed Virtual Environment for system engineering , 2000 .

[9]  Henry Petroski,et al.  To Engineer Is Human: The Role of Failure in Successful Design , 1986 .

[10]  Henry Petroski,et al.  Design Paradigms: Failure as a Source of Engineering Judgment , 1994 .

[11]  Robert L. Collins Process hazard analysis quality , 2010 .

[12]  Michael Griffin,et al.  Delta 180/Vector Sum - The first powered space intercept , 1988 .

[13]  A. J. McEvily,et al.  Failures in inspection procedures: case studies , 2004 .

[14]  T. Chalcraft Overcoming failure , 1999 .

[15]  A. G. Hessami Risk management: A systems paradigm , 1999 .

[16]  T. E. Strikwerda,et al.  The Space Telescope alternate fine guidance sensor , 1984 .

[17]  D. Oxley Design Paradigms: Case Histories of Error and Judgment in Engineering , 1997 .

[18]  Satoshi Nagano Space systems verification program and management process: Importance of Implementing a Distributed-Verification Program with Standardized Modular-Management Process , 2008 .

[19]  Satoshi Nagano Space systems verification program and management process: Importance of Implementing a Distributed-Verification Program with Standardized Modular-Management Process , 2008, Syst. Eng..