On the use and abuse of Technology and its Management from the perspective of an academic at UCL specialising in Project Management, Systems Engineering and Space Science/Technology.

Thursday, December 04, 2008

Invention by Design, Petroski

Henry Petroski, Invention by Design
Harvard,1996

Henry Petroski has written a number of books that cluster around the craft and process of engineering. This one sets out to illustrate the inventive process of engineering design. I picked it up hoping to know more about innovation in other fields than my own.

In the ten or so case studies presented, the theme of the problem-as-impetus clearly emerges. Engineers, as critics of existing products, are driven to devise further inventive steps to reach toward a more excellent product. With some exceptions (the Boeing 777 case, which although probably the most contemporary, seemed to be lacking an undefinable quality of fidelity: does he really get what's going on there?), the cases revolve around the thoughts and craft of individuals. In some cases (the drinks can) their identities are obscure, whilst in others (the bridges of San Francisco) they spring from the pages dramatically. Exhibitions of patent documentation provides the bare bones, Henry P re-constructs the whole animal.

It's also clear that teams of engineers, or even distant collaborations, don't simply progress by cutting through an underlying bedrock of physical properties to get to the solution they seek. Rather, at each inventive stage, a higher order product, an improvement from the last, emerges from a mist. Thus we step from toggles to buttons, thence to what must have a been a nightmare of "automatic" clothes-tieing devices, to the zip as we know it. A series of hops then to the Ziplok bag, and yet another string of manoeuvres to Velcro.

But perversely, despite each invention begetting more invention, at the same time each enlargement of the scope and scale of the products seems to make it harder to analyse the next-generation design. Boeing's exponentially growing development budgets attests to this. Not all of the added complexity comes from within the product though, as there are network effects and social or legal changes concerning the use of the products that add further layers of requirement to each iteration.

The idea of resources as enablers, such as materials or tools, for certain types of design activity is also strongly exposed. He exemplifies this all through the book, pointing to CAD as a key technology for Boeing, standardisation for the Crystal Palace among many others. He seems to be too early to notice much use of computing in architecture though.

The chapter on buildings as systems shows how the problem complexity rises with each generation. Perhaps there is an inherent bias in these works, forgetting the industrialisation of innovation in mundane structures. The wonder of the local supermarket, reproduced thousands of times, as opposed to the award-seeking skyscrapers of the capital.

He uses terrorist attacks on the World Trade Center as an example of resilience of design. He refers of course to the 1993 bombs in the basement. What would he make of the later total failure of the designs in 2001, and was this indeed a failure of that particular building as a system, but a failure of a wider, un-designed system?

No comments: