Engineers and their problems

I bought Wicked Problems: How to engineer a better world by Guru Madhavan because of a column by the author in the FT, The Truth About Maximising Efficiency: it argues that governments, like engineered artefacts and indeed our bodies need some redundancy and safety marging. How true!

I enjoyed reading the book but in terms of analysis didn’t get much out of it beyond the FT column. It advocates a systems engineering approach even to ‘hard’ problems ie. well-definable ones. It classifies problems into hard (solvable), soft (only resolvable) and messy (need redefining) and takes wicked problems as the union of these categories. It was interesting to me to read a critique of engineering similar to the one I apply to economics, namely that engineers too often ignore the normative or political context for their solutions. The book sort of makes the case that engineering is social but not in a particularly clear way.

Having said that, the book has lots of examples of messiness and wickedness from the world of engineering, and particularly aircraft training and engineering. It focuses on the career of Ed Link – whom I had never heard of – who went from making player pianos to inventing the first on the ground flight training simulator to inventing and building submersible vessels. The book is full of the kind of fact that pleases me no end – for example that black boxes are orange and were created by Lockheed Air Services along with food company General Mills and a waste disposal company, Waste King. Also – tragically relevant – that engines are tested for resilience against bird strikes by lobbing chickens at them – real birds rather than imitation ones, and freshly killed rather than frozen and defrosted. A cited paper by John Downer, When the Chick Hits the Fan, observes that birds have adapted to devices meant to scare them away, so there is a sort of arms race between engineers and birds. (The paper is fascinating – there is an expert debate about how many birds of what size and being lobbed in how fast constitute an adequate test. The resulting pulp is known as ‘snarge’.)

Most of the examples of wicked problems in the book involve engineering rather than social problems. On the one hand, that’s an issue because we tend to think of wicked problems as social and political – paying for the groing need for adult social care, for example, On the other hand, the one main example of that type, reducing homelessness among veterans in the US, discusses how to get the different agencies and stakeholder to talk to each other and respect their differences. but doesn’t in the end describe a solution. Perhaps the moral one is meant to take is that wicked problems don’t have a solution?

All in all, an enjoyable read, and I for one am on board with systems engineering approaches, resilience and organisational flexibility.

81VmZuPb1LL._AC_UY436_QL65_

Leave a Reply

Your email address will not be published. Required fields are marked *

18 + 15 =

This site uses Akismet to reduce spam. Learn how your comment data is processed.