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

Baggage Handling Root Cause Analysis?

An article in the Daily Express described the trouble at Heathrow as a “Baggage Meltdown.”

The results of thousands of “lost” bags are called a “Luggage Mountain.”

They have had to fly jumbo jets loaded with just bags across the ocean to try to unite travelers with their luggage.

And news outlets say the problem could get WORSE!

The cost of this “incident” is more than just the immediate costs to the airlines and travelers. Some say it has caused damage to the whole British reputation.

Picture 49

What is the “cause?” Everyone has an opinion. Most are looking for someone to blame.

But instead of looking for someone to blame, they should try advanced root cause analysis.

TapRooT® has been applied by many major airlines. Alaska Airlines even used it to analyze delayed flights and improve on-time departure statistics.

Perhaps British Air should try TapRooT® to stop the baggage meltdown and improve customer service?

And next time they should use root cause analysis as a PROACTIVE tool to improve performance BEFORE they open a new terminal and thus avoid a major quality of service incident.

5 Responses to “Baggage Handling Root Cause Analysis?”

  1. Ronald Says:

    I was wondering when you were going to pick up on this one. I wrote about it at http://thinkingproblemmanagement.blogspot.com/2008/03/titsup-new-heathrow-terminal-five.html

    The article written in CIO magazine on 9 Jan is really good reading seen in the context of what happened later.

  2. Mark Paradies Says:

    Often I hear of problems but don’t have time to write about them. In this case the magnitude and press coverage is so great that I couldn’t help myself.

    Do you have a link to the Jan 9 article in CIO?

  3. Chris Vallee Says:

    This was also hit on the a six sigma site blaming the six sigma team for failure to produce a contingency plan for this type of failure. The blog turned into a blame game instead of identifying that the process was not understood and who had the accountable role for communicating issues.

  4. Ronald Says:

    The link to the Jan 9 article in CIO mag is http://www.cio.co.uk/concern/change/news/index.cfm?articleid=2487&pn=1

    Chris, what is the link to the six sigma site discussing this failure?

  5. Chris Vallee Says:

    The site is www.isixsigma.com. The blog title is another six sigma failure. The “supposed tie” is a lean project with the IT process and the mass training and lead of six sigma experts.

Leave a Reply