site map Root Cause Methodology and Tools for Improved Operations
Home
About TapRooT®
Course Info
Summit Info
Software
Equipment Troubleshooting
Weblog
Store
Company Info

TapRooT® Blog Entry Archive

« Friday Joke: NOT the TapRooT® Summit Golf Tournament | Main | FACTS: Fatigue Accident Causation Testing System »

May 14, 2007

Monday Accident & Lessons Learned - Blackberry Outage Shows Need for IT Root Cause Analysis

Several of weeks ago, the network that carries BlackBerry messages went down. Why? That's a question for a good root cause analysis.

For details see these articles ...

http://www.informationweek.com/news/showArticle.jhtml?articleID=199100624


http://www.canada.com/nationalpost/financialpost/story.html?id=fff9217c-651c-40c7-8aad-73586d2a953a&k=32960

What is the lesson learned? That IT folks need thorough, systematic root cause analysis as much as safety, equipment, environmental, or hospital quality improvement people do.

One common root cause analysis problem is that investigators stop with the symptoms of the failure and call these symptoms the cause. The don't dig deep enough to find the true system root causes. They don't know the questions to ask to get beyond the symptoms.

That's one of the benefits of TapRooT® - it helps investigators get beyond symptoms to the fixable root causes and generic causes of accident, incidents, qiality problems, equipment failures, and even IT problems.

For more information about TapRooT® see:

http://www.taproot.com/about.php

And for a success story about improving network reliability at BellSouth, see:

http://www.taproot.com/about.php?s=9

Posted by Mark at May 14, 2007 02:27 PM

Comments

Post a comment




Remember Me?

(you may use HTML tags for style)