One of my consulting colleagues had a scary experience with British Airways at Heathrow Airport today. It shows all too well how little service errors caused by a lack of standard processes and an over-reliance on technology can easily escalate into much larger problems.
My colleague missed his red-eye flight from Heathrow to Düsseldorf this morning due to traffic problems on the way to the airport. So he was rebooked onto another British Airways flight at around midday. He made his way to the gate where two flights were boarding at the same time. He gave his boarding card at the terminal end of the boarding ramp to the boarding agent who put it through the boarding card reader, gave him the boarding card stub back and told him to go down the ramp on the left. He followed and showed his boarding card stub to the steward at the aircraft door who told him to go forward in the cabin. Strange he thought, the flight to Düsseldorf isn’t usually on a big jet and he never gets to fly first class. So he asked the steward if the flight was going to Düsseldorf. “No” came the reply, “We are flying to San Francisco”. If my colleague had not been so suspicious, or had been tired after a long connecting flight, he might not have noticed till too late. And who knows whether British Airways would have noticed at all.
Making his way off the plane to catch his real one, he mentioned what had happened to the boarding agent. The response. Just a shrug of the shoulders. Two staff had inspected his boarding card and it had been read by the boarding card reader, all without picking up that he shouldn’t have been on the flight. This particular boarding process was very broken, both from the perspective of how staff carried it out and the technology used to support it. So was the customer recovery process (not even a sorry, an excuse or an explanation). And there was no Kaizen process to improve the broken service process so that it never happens again. It may happen hundreds of times a day with British Airways alone. Who knows if people wake up to find themselves disembarking in very strange destinations.
This true story illustrates why routine service work activities need to be standardised as far as possible, why staff need to be given the knowledge, skills and workplace training to deliver the work right first time (and to react appropriately to unusual situations), and why service failures need to be ‘Kaizened’ so that they don’t happen again. But not all service work activities are as routine and consistent as boarding an aircraft should be. Some work activities occur only irregularly, or not as part of a standard process cycle. These should be documented in details and staff given workplace training to carry them out as and when required. And some work activities only occur rarely, or may even be new to the organisation. This is where defined policies, process frameworks and knowledgeable, skilled, trained staff really come in. And where Kaizen should be applied afterwards to understand the origin of the event and how standard process should be changed to cope better next time.
So next time you find yourself boarding a strange plane, ask the steward where you are going. And ask yourself how the airline might improve its service processes next time.
What do you think? Should service processes be standardised so that little errors don’t turn into bigger problems later? Or do you like vacationing in mystery locations?
Post a comment and get the conversation going.
Independent CRM Consultant
Interim CRM Manager