Systems Thinking, Systems Practice: Includes a 30-Year Retrospective: Includes a 30 Year Retrospective [Kindle Edition]

Checkland's book was the first to introduce the differentiation between 'soft' and 'hard' systems analysis. Soft analysis is much more akin to a general, somewhat philosophical approach to the methodology whereas hard analysis is the development of usable engineering models.

First off, this book is actually two books - the first is a fairly long paper that neatly sums up the systems approach over the 30 years it has been explored. The consensus? Things looked really promising at the beginning but unfortunately the approach simply got hung up on the very thing it was trying to escape: science's current preoccupation with reductionism. That is, the hard systems approach attracted the most attention and it quickly succumbed to the very trap it sought to escape starting with its use of rigidly-defined symbols right up to the detailed diddling with mathematical models that, similar to earlier approaches, did not model reality at all due to assumptions and oversimplification.

Checkland is much more interested in the soft approach and he consistently laments the fact that systems methodology is not being taught even though it holds so much promise to solving many of our pressing problems. The overview presses this point home and should be required reading for anyone in management or engineering.

The second section, the original book with a few revisions, is still very relevant. Checkland's focus, soft systems, never was given a chance given our preoccupation with reductionism. Given the recent failures of reductionism, particularly the genome-mapping fiasco, cast systems theory in new light.

Checkland starts out with an excellent overview of the history of science from a (mostly) philosophical perspective. This very readable overview leads directly into his discussion of the history and early development of systems theory. He then focuses on systems methodology (soft systems theory) with some general applications.

The approach is very readable and should be easily understood by anyone - in fact, Checkland stresses the importance of having a wide base of knowledge to help solve real-world problems and points out that much work has been done by people who 'migrated' from other fields. Smuts, one of the pioneers, was actually a politician and only wrote a systems book after losing an election...

It is unfortunate that there are no references to Robert Rosen here since his work, more of a 'hard' approach to systems theory, fully supports Checkland's ideas. In fact, there is a lot of material that should be included as 'backup' for why the systems approach is important as a new direction away from reductionism. Perlovsky's work in cybernetics, Jopling's recent work on self-knowledge, Prigogine's work in thermodynamics and even Kauffman's attempts in biology now point to hypotheses that are only compatible with a systems methodology.

This book, as mentioned above, should be required reading these days. Certainly for anyone contemplating management or engineering it is a very important reference. In fact, the book could basically be used in high-school with a bit of help from Weinberg's systems books. For those looking for more application-specific information I recommend von Bertalanffy's original, Rosen's work, and perhaps a side helping of Weinberg and Gharajedaghi for more ideas.

If you're studying management of information systems or something similar, you are probably sick and tired of overly theoretical approaches to the subject which seem to be just excuses for academics to publish rubbish (eg. structuration, actor network theory, etc). This book may save you from a nervous breakdown.