4 ms·
Not one mention of a fishbone diagram?
by moftz 9y ago
Not one mention of a fishbone diagram?
- com 9y agoRoot cause analysis, in the simplistic form, without a fishbone tree of events and failed controls, means that failure is inevitable. Again and again. Edit: This document is actually cool: it uses RCA as a term and actually teaches failure analysis!
- mdaniel 9y agoIn their "defense," this looks like another thinly veiled "look how are awesome tool solves problems, call now!" article and not a book in any fashion whatsoever. We've enjoyed great success with the post-mortem templates in PagerDuty, which is part of their open-source incident-response-docs https://github.com/PagerDuty/incident-response-docs/blob/130d56e2/docs/after/post_mortem_template.md https://github.com/PagerDuty/incident-response-docs/blob/130...
- emmelaich 9y agoSince I had to look it up -- https://en.wikipedia.org/wiki/Ishikawa_diagram https://en.wikipedia.org/wiki/Ishikawa_diagram
- owlninja 9y agoFMEA!
- causelink 9y agoThanks for the question. Our experience is that the causal analysis method described in the eBook is a more effective way to understand the causes of a problem and find effective solutions. We often discuss the pros/cons of different RCA methods in our free webinars and we have one about Fishbone in June. Feel free to sign up http://www.sologic.com/root-cause-analysis-training/rca-webinars http://www.sologic.com/root-cause-analysis-training/rca-webi....