Quick: What was the name of the bridge that collapsed this summer in the Midwest?
If five seconds have passed, face it: you don't remember that it was called the eye thirty-five double u bridge. How quick we forget such major news (I didn't remember either).
The eight-lane, 1,907 feet (581 m) steel truss arch bridge spanned the Mississippi River in Minneapolis, according to Wikipedia. Completed in 1967 and maintained by the Minnesota Department of Transportation, the bridge was that state's fifth–busiest, carrying some 140,000 vehicles daily. Tragically, 13 people died and more than 100 were injured.
Why the bridge failed is still being sorted out by the National Traffic Safety Board (NTSB). Bridge failures, of course, happen more often than we'd like (like never…). According to Henry Petroski, author of Success through Failure: The Paradox of Design (Princeton University Press, 2006, 240 pages), there's a major bridge disaster every 30 years, at least since 1847. Was the Minneapolis Bridge part of this 30-year curse? If so, it's off by eight years (or ahead by 22 years). My point is Success…is worth reading. Petroski is a good communicator because he engages his readers; he gets us to think.
His landscape of failures, however, is much wider than collapsed bridges. From the initial failed Aleve cap in 1994 to the collapse of the World Trade Center, Petroski parses the many failures that have occurred in products, structures, even Microsoft Word's Powerpoint presentation software. Author of three other books, Duke Professor Petroski challenges those of us in business, government or academia to learn from failure. In our earnings-driven (read short-term) society especially, failures are like the family's proverbial "dirty laundry," hidden and never to be talked about. The author pays homage to, "…the inventors, the engineers, the designers of the world…to these intrepid pioneers, a failure of any kind is not so much a disappointment as an opportunity."
Petroski cleverly counters our world of constant change with certain maxims that will comfort or at least make you think: "There are two approaches to any engineering or design problem: success-based and failure-based. Paradoxically the latter is always far more likely to succeed."
Think about your most recent failures. What did you learn?
|
Re: Worth Reading: "Success Through Failure"