Flew Dublin – Heathrow again last week – this time with BMI (British Midland International). It’s what all Java consultants do – pop on the plane to London to see a client. Now I like BMI, not least because they provide a bit of competition for Aer Lingus. I like Web Checkin. A lot. See my post on how to use Web Checkin to solve Dublin Airport’s problems. But BMI have a (bad) secret about their online check-in that they don’t tell you until after you have paid for your flight.

Online or Web checkin means you print your boarding card before you leave home. It means you arrive at the airport , walk straight through security and enjoy a coffee while waiting for your flight to board. For Aer Lingus it’s great on a day trip; print both boarding cards the night before you leave. For BMI there’s a glitch; you cannot print your return boarding card until after you arrive in London.

What? On your busy-day-with-client-not-one-second-to-spare you are expected to start printing pieces of paper. What is worse, you only find this out after you pay your money. Called the Flight Helpdesk ‘we have a lot of people complaining about that Sir’. Mail to BMI customer service, no reply.

The moral of this story is not to complain about BMI (although here’s my Ajax related Rant about Scandanavian Airlines if that’s your thing , or Mulley’s lost baggage saga if you prefer). And yes, I should be glad of a choice of flights to Heathrow (see Limerick Bloggerand Bock the Robber)

No, the moral of the story is that IT systems (yes the geeky bits) can have a huge impact on customers in traditional business (you know, the ones that pay you money). Being the helpful people we are, we’ll even show BMI how to fix this using Business Rules. Somewhere, deep in the bowels of the BMI system code, Someone, a long long time again decided ‘no one will ever want to check in before they leave’ . And now that it’s spaghetti code, it can’t be fixed, leaving a lot of unhappy customers.