<< 1 >>
Rating: 
Summary: Root Cause?? More Like Finding a Scapegoat!!
Review: Accidents happen because of an amalgamation of errors, not simply because of one person's "human error". Design faults, management pressures, poor training, long shifts, poor device interfaces, insufficent safety guards, poor maintenance, and many other issues come together to afford an accident that would not have caused that accident alone. Finding root cause enables blame to be placed and make the rest of the system feel "safe" while latent problems still linger. Safety is created by fostering a culture that sees risks for what they are and works to minimize those risks (better training, better safety guards, lessening worker fatigue) and NOT by placing blame on one "root cause".
Rating: 
Summary: Unique approach to a traditionally reactive technique
Review: My background is information systems service delivery. I stumbled across this gem when I was searching for resources on how to structure outage investigations for applications that did not meet service level objectives.Prior to reading this book I viewed root cause analysis as a reactive tool to be used to investigate the causes of failures. The approach taken by the author is to also use this technique as a proactive tool in a manner similar to failure mode effects and criticality analysis (FMECA). Here is a summary of what how this book approaches root cause analysis: it begins with a section on defining problems and collecting data. This approach allows you to take a proactive approach, especially if you are in an environment that uses statistical process controls to measure process performance. This is augmented by a chapters on task analysis and event and casual factor charting. This is where the author's approach begins to resemble FMECA techniques, which are proactive versus reactive methods of addressing problems and risks. This is followed by chapters on interviewing and reporting. I particularily liked the chapter on interviewing techniques, which added a practical dimension root cause analysis. I also liked the way the author used hints throughout the book to reinforce methods. The rest of the brief 135-page book is devoted to forms, worksheets and checklists that significantly add to the value or the book. I would have liked an accompanying diskette with this material in electronic format, but the lack of it does not detract from the book in any way. If you want to use root cause analysis as a proactive tool in conntection with a continuous improvement initiative I recommend that you also consider Understanding Variation by Donald Wheeler. If you are seeking a more proactive approach to preventing problems in the first place you might consider augmenting Root Cause Analysis Handbook with Failure Mode and Effect Analysis by D. H. Stamatis.
Rating:
Summary: Unique approach to a traditionally reactive technique
Review: My background is information systems service delivery. I stumbled across this gem when I was searching for resources on how to structure outage investigations for applications that did not meet service level objectives. Prior to reading this book I viewed root cause analysis as a reactive tool to be used to investigate the causes of failures. The approach taken by the author is to also use this technique as a proactive tool in a manner similar to failure mode effects and criticality analysis (FMECA). Here is a summary of what how this book approaches root cause analysis: it begins with a section on defining problems and collecting data. This approach allows you to take a proactive approach, especially if you are in an environment that uses statistical process controls to measure process performance. This is augmented by a chapters on task analysis and event and casual factor charting. This is where the author's approach begins to resemble FMECA techniques, which are proactive versus reactive methods of addressing problems and risks. This is followed by chapters on interviewing and reporting. I particularily liked the chapter on interviewing techniques, which added a practical dimension root cause analysis. I also liked the way the author used hints throughout the book to reinforce methods. The rest of the brief 135-page book is devoted to forms, worksheets and checklists that significantly add to the value or the book. I would have liked an accompanying diskette with this material in electronic format, but the lack of it does not detract from the book in any way. If you want to use root cause analysis as a proactive tool in conntection with a continuous improvement initiative I recommend that you also consider Understanding Variation by Donald Wheeler. If you are seeking a more proactive approach to preventing problems in the first place you might consider augmenting Root Cause Analysis Handbook with Failure Mode and Effect Analysis by D. H. Stamatis.
Rating:
Summary: Great book about a methodology I use and know works!
Review: Provides a clear, step by step methodology, with techniques, for problem or error analysis and identifying a solution. This is an exceptionally practical work offering a methodology for problem solving that is attractive; one which I subscribe to and use. Recommended.
Rating: 
Summary: Very good introduction to root cause analysis.
Review: This book does an excellent job of quickly covering conventional root cause analysis. With an emphasis on documentation, the author takes you through a series of steps that include defining the problem, methods for collecting data and gathering information, analysis of the problem, and ultimately developing corrective action. This book moves very fast, reading more like a slide-show presentation than a book, yet the author is able to communicate a lot of good information using this minimalist approach. Rather than detailing numerous analysis methods, the author keeps it simple by sticking with a fixed path to problem solving. I found the "Pitfalls of ..." sections after each topic very insightful. In addition, the collection of forms, tables, and checklists included in the book (great appendix) are excellent. Don't look for case studies here, this is a straight forward how-to book
<< 1 >>
| 
