Here is an excerpt from on five things business leaders can learn from engineering failures and then a book review on To Forgive Design: Understanding Failure by Henry Petroski.

Henry Petroski is a professor of history at Duke University with a dark specialty: engineering failures. His first book, To Engineer is Human, dissects the anatomy of several disasters, from the Tacoma Narrows Bridge to the walkways at the Kansas City Hyatt Regency Hotel. If you’re squeamish about flying or driving over bridges, this book won’t make you feel better. But it’s a captivating window into how engineers think, valuable for anyone in business.

Engineers are natural skeptics. They treat each new engineering project as a hypothesis to be disproven. By imagining a structure under every conceivable situation, engineers are forced to think in the negative. How could this building collapse? How could this bridge fail?  What could go wrong? Even a structure as rigid as the Brooklyn Bridge should be treated as an accident waiting to happen. That it has stood for over one hundred years is no guarantee that it will stand tomorrow, despite its structural soundness today.

To think like an engineer is to think critically about success and failure. If you’re seeking business wisdom but you’re sick of the business aisle, Petroski’s books are a good place to look. I’ve curated five insights from To Engineering is Human, Success Through Failureand his latest, To Forgive Design.

Five things business leaders can learn from engineering failures

1)  Success Does Not Imply Soundness

2) Be Aware of “Organizational Drift”

3)  Good Engineers Crave Counterexamples

4) The Innovator’s Dilemma

5) Failure is Good (In the Long Run) Because it Reveals Latent Errors

Full article via , more on the book below

To Forgive Design: Understanding Failure

Five Things Business Leaders Can Learn From Engineering Failures

To Forgive Design: Understanding Failure by Henry Petroski

To Forgive Design – Description

When planes crash, bridges collapse, and automobile gas tanks explode, we are quick to blame poor design. But Henry Petroski says we must look beyond design for causes and corrections. Known for his masterly explanations of engineering successes and failures, Petroski here takes his analysis a step further, to consider the larger context in which accidents occur.

In To Forgive Design: Understanding Failure he surveys some of the most infamous failures of our time, from the 2007 Minneapolis bridge collapse and the toppling of a massive Shanghai apartment building in 2009 to Boston’s prolonged Big Dig and the 2010 Gulf oil spill. These avoidable disasters reveal the interdependency of people and machines within systems whose complex behavior was undreamt of by their designers, until it was too late. Petroski shows that even the simplest technology is embedded in cultural and socioeconomic constraints, complications, and contradictions.

Failure to imagine the possibility of failure is the most profound mistake engineers can make. Software developers realized this early on and looked outside their young field, to structural engineering, as they sought a historical perspective to help them identify their own potential mistakes. By explaining the interconnectedness of technology and culture and the dangers that can emerge from complexity, Petroski demonstrates that we would all do well to follow their lead.

To Forgive Design – Review

[An] authoritative text about the interrelationship between success and failure in the engineering enterprise…Petroski’s most gripping passages are his Sherlockian dissections of engineering fiascos and the importance of learning from the vast archive of forensic analyses. (Kirkus Reviews 2012-02-01)Though his focus here is primarily on bridges, Petroski extends his analysis to include the sinking of the Titanic, the mid-flight explosion of TWA Flight 800, the Challenger tragedy, the Y2K computer programming crisis, and the Deepwater Horizon spill in the Gulf of Mexico. Each has its own unique set of human, mechanical, and engineering failures, and Petroski does a terrific job of identifying and communicating not only what went wrong, but what was learned from the failure and how that knowledge has since been put into practice. Fellow engineers and armchair scientists will get the most out of the book, but even the layman will find Petroski’s study to be accessible, informative, and interesting. (Publishers Weekly 2012-02-06)Petroski follows up his first book, To Engineer Is Human: The Role of Failure in Successful Design, with this examination of human failure. In the previous title, he primarily considered mechanical and structural failures. Here, he looks not only at how people contribute to the failure of engineering designs but also at how analyzing those failures can improve subsequent models. He considers many different types of failures, from several infamous bridge collapses to carefully designed intentional failures, which are engineered specifically to prevent greater failures. In each case, Petroski goes beyond an explanation of the mechanical failure itself to point out how humans created these and other problems through systemic mistakes. (Carla H. Lee Library Journal 2012-02-15)

When a plane crashes or a bridge collapses, faulty engineering is the usual suspect. But in seeking the roots of failure, we should look beyond design, says engineer Henry Petroski. We must probe the political and economic imperatives that shape purposes and use. In this follow-up to his influential To Engineer is Human, Petroski argues that accidents such as the Deepwater Horizon oil spill are the result of faults as much in “human machinery” as in mechanical devices. He praises software developers for learning from structural engineering about how to report and analyze mishaps. (Nature 2012-03-01)

A rewarding read. (Jonathon Keats New Scientist 2012-03-17)

By critically examining the interdependency of people and machines related to bridge collapses, airplane crashes and space shuttle failures, Petroski discovers that understanding failure is the only way to bring successful design and engineering into the future. (Megan Wood Salon 2012-03-25)

Nonengineers needn’t worry that the book will be too dense with details; Petroski makes the science easily understandable…[This is] a book that satisfactorily explains why our determination to push the boundaries guarantees both failure and triumph. (James F. Sweeney Cleveland Plain Dealer 2012-04-05)

[A] fascinating and occasionally unnerving history of engineering failures…After reading this book, one might be tempted never to venture across a bridge again. But of course that would miss Petroski’s goal: to show how engineers learn from failure and improve their designs…For those who enjoy reading about girders and trusses, To Forgive Design is, yes, riveting…[Petroski] amply shows the wisdom of the proverb that failure is a good teacher. Even a collapsed bridge leads somewhere. (Matt Ridley Wall Street Journal 2012-04-10)

Engineering is interesting when it works, but much more compelling when it doesn’t. Petroski may be one of his profession’s establishment figures, but his key finding is highly critical: because most engineers don’t know much about the history of engineering, complacency and gee-whizz design software is likely to foment a fairly regular incidence of potentially catastrophic structural failures…Much of the information will be of great interest to engineers and designers…The most brilliantly explained engineering failure concerns the ocean-bed blowout involving the Deepwater Horizon oil rig in 2010. Petroski’s exposition is immensely detailed and benefits from being linear in its narrative. This section of the book is exemplary in its remorseless exfoliation of the technical and commercial reasons for the

1, 2  - View Full Page