- Jubilee offer: spend £10 or more on any product sold by Amazon.co.uk on or before June 6 and you can buy The Diamond Jubilee A Classical Celebration Album for just £2.50 Here's how (terms and conditions apply)
| |||||||||||||||
![]() Trade In this Item for up to £0.45
Get an extra £5 when you trade in books worth £10 or more until June 30, 2012. Trade in The Logic of Failure: Recognizing and Avoiding Error in Complex Situations for an Amazon.co.uk gift card of up to £0.45, which you can then spend on millions of items across the site. Trade-in values may vary (terms apply). Find more products eligible for trade-in.
|
Product details
|
Suggested Tags from Similar Products(What's this?)Be the first one to add a relevant tag (keyword that's strongly related to this product)
|
The book contrasts good decision making processes with bad ones, using just a few real life examples and a lot of studies. There are some best practice patterns that can be drawn out from it, but it leaves you to apply serious thought if you want to use the lessons in a "traditional" project plan, for example.
You will have to add your own industry experience to get real value out of it: I'm interested in how it can be applied to the software engineering - after reading this its made me more interested in good feedback loops and early trend monitoring during project management. Paradoxically, I am also more wary of "analysis paralysis"! I think it would make a great definitive handbook if it could be translated to real technology programmes, where there is often a strategy plan and a "traditional" technology plan running together, plus an issue/risk management plan.
Other readers might think about applying it to public policy (or, alternatively, how a politicians dogma can overcome inconvenient facts. You can probably think of a dozen examples easily - then wonder how western democracies manage their economies so successfully given the opportunities for mistakes)
Regarding the book's style, although it is a seamless translation, I wish that some of the wording was better chosen - for example, using "ballistic" instead of "linear", & "intransparent" for "opaque" - or do these new words have a special meaning that I've missed? And although it mentions the value in diagramming time-dependent systems, it doesn't have any good examples or concrete references to proven methods.
The graphic data and their analysis is very accurate.
One of the greatest chapters in the book is about time measurement. Never did I understand before reading that in general, people cannot manage time, they don't feel it. We measure it by looking at watch, we make charts, we write histories and mark milestones just because our mind is "current". It is a fascinating book to read. The somewhat academic style is very appropriate. I very strongly recommend it, especially for beginners in business, like me.
With best regards, OLEG.
Why Things Go Wrong and What We Can Do to Make Them Right
or
Recognizing and Avoiding Error in Complex Situations
by Dietrich Dörner... Read more
|