Why Things Bite Back: Technology and the Revenge of Unintended Consequences [Paperback]

The Chiles book Inviting Disaster is thoroughly entertaining. The author is a professional writer with a readable style who often tries out equipment, goes on site, or goes along with technicians in order to do his research. He is by no means given to just armchair research and that makes for a very exciting narration.

I did have some difficulty getting used to his method of pairing recent and 19th Century tales of disaster, especially his habit of jumping back and forth between the two narrations. It does focus ones attention on the similarities between the two events and the degree to which we have learned little from experience! It would appear that leaning from mistakes has been given more lip service than practice over the years. This may well be due to the fact that it's only been more recently that failure itself has been made a subject in its own right with a proper examination of how systems "go off the rails" and what can be done about it.

The author includes an interesting variety of situations, and the list makes it clear that complexity itself gives rise to surprising new outcomes. Just as the authors of Figments of Reality note, complex systems can give rise to emergent characteristics which are entirely unexpected and therefore not planned. (In their book intelligence/mind arising from brain/nerve.

In Inviting Disaster, Chiles focuses on the effects of top down management, the over riding desire to accomplish records and goals, and the disenfranchisement of front line workers who have important information about front line conditions as the primary cause of disaster. He also notes that with very complex systems, the Devil can be in the details, and it tends to be these that get overlooked or ignored. In the final chapters, he suggests that successful companies have tended to focus on customer satisfaction and safety, and not only value but reward bottom up communication.

The book has a very extensive bibliography that the interested reader might enjoy following up for further information on the technology/human interface. The appendix also includes a list of disasters and near disasters and brief descriptions of each; an eye opener.

Why Things Bite Back is by a historian turned science editor, Edward Tenner. This volume focuses on what the author calls "revenge effects" of technology, the reverse or worse outcomes arising from applications of technology that were intended to eliminate or mitigate problems. Tenner's book takes a more holistic look at the unexpected outcomes of science and technology rather than at specific disasters. Medicine, Environmental Disasters, Computerized Offices, and Sports are among the facets of modern life that are examined.science and technology. In general Tenner sees there has been an exchange from the overwhelming, localized disaster affecting a few to a few thousand individuals to the chronic, more socially distributed effects of negative outcomes that require more sustained vigilance and therefore more expense distributed over an entire society or over the world's population as a whole.

One of the more interesting aspects of the book is the point made that there has been a major change for the worse in the level of satisfaction with life that has arisen as an unexpected outcome of reduced risk. Apparently as life becomes easier and we are less threatened by major problems, we begin to magnify minor problems. He also notes the odd relationship between computers and productivity; their promise doesn't seem to have lived up to the expectations of the industry, and he suggests that our dependence upon them has created complications. He admits, however that some of this may be due to the lag between the introduction of new equipment and the full embracement of the technology, noting that there was also a problem created by the lag between introduction of electrical motors and the abandonment of steam power in industry during the earlier part of the 20th century.

The book has a small annotated bib for "further reading", but the more extensive notes to the chapters with their resources, include titles that might interest the reader too.

Normal Accidents by Charles Perrow, a professor of sociology at Yale, is the most detailed of the three. I found it more difficult to get into this book, however, because of its more technical discussions of industry failures, particularly those in the nuclear power industry. The book was reverently referred to by both of the above authors, however, so when I had finished reading them, I returned to this book and got much more out of it than I had on my first reading. (See my individual review on this book under the title.)

Because of his overall approach as a sociologist to the subject of the human/technology/organization interfaces, Professor Perrow tended to look more closely at how human goals, preconceived notions of reality, and social structures set up some types of failure. He also notes that in some instances, had the various individuals actually tried to cause the accidents of which they became a part, they probably would have had difficulty doing so.

The final chapter of the book is very interesting for the author's social commentary and his suggestions for resolution of dangerous situations. Although I'm not entirely sure I believe that his position is a strong as it seems on first reading, I think it's definitely something that should be considered; certainly to do so would cause us less harm than not doing so might.

The bibliography contains a wide range of references and demonstrates the thoroughness of the academic research. I would make an excellent starting point for anyone who wanted to do their own similar study.

Drawing on a rich variety of sources, Tenner shows quite clearly how and why we have unintended consequences. Once you read this book, you will find yourself thinking about many of the technological fixes in your life and wondering what unintended consequences they begat.

The next step - and maybe this can be Tenner's next book - is ask, what can we do about this situation? We cannot and should not stop innovation or problem-solving. But maybe we can do two things. One, explore how feedback loops can be enhanced, especially now that we are living in a digital world. It sounds silly when you read that someday, your refrigerator will order milk from a grocery store when it "senses" you are low on milk, but the faster and more efficient the feedback loops, the better we can be at forecasting danger ahead. Secondly, when a new solution or invention comes to fruition, look back for a moment, not ahead. Something is always lost when a new tool comes into human hands. Maybe the old tool had positive attributes we should try to keep. For a great example of this, read the little essay on railroads in George Kennan's Around the Cragged Hill. As he describes it, at the very point in history that the railroads had created a magnificent system, uniting the country while allowing it to spread, maximizing speed and safety, the car was invented. And the railroads withered. A sad story, the way he tells it. And while Kennan may be a little too romantic when it comes to 19th century rails, I am sure that there are many things about the rails that we have lost, now that we drive or fly.

I always appreciate a book that makes me think. This one does and is recommended.