Last week I was in Amsterdam for DrupalCon Amsterdam 2014. I traveled there from Sofia, Bulgaria, where I had been attending WordCamp Europe.
The Setup: I lost my luggage
I flew from Sofia to Amsterdam by way of Frankfurt, Germany, on Lufthansa, a great airline if you've not yet had the pleasure. Since I had lost my travel talisman, I fully expected something to go wrong along the way, and I was not disappointed.
My flight arrived late into Frankfurt, and I had to sprint across the airport to make my connection to Amsterdam. I made it with scarce minutes to spare; my luggage, however, was not so lucky. It got an unexpected holiday in Frankfurt for a couple of days.
This post is not about my travels or the Eli Travel Curse; I just needed to set things up. I learned something very important in all of this: as software developers and designers, we need a great deal of empathy for the people using what we build.
It is not enough to put yourself in your user's shoes; you have to put yourself in their mindset. You have to design every user interaction with an understanding of not only who is using your software, but why they are using it.
Once I knew my luggage hadn't made it, I contacted Lufthansa, and they handed me off to the company that handles lost bags. I filled out the forms, and they gave me a packet with a fresh T-shirt and a bad razor, plus a copy of the report that included a URL I could visit to check the status. Then they sent me on my way. It is this URL that is the focus of this post.
The Problem: Developers don't use their own software
The next day I still hadn't heard from Lufthansa, so I decided to check the status online. I was greeted by a form from 2004 that asked for the basic information about my incident and then showed me a status page. That page is the heart of this post. (I wish I had had the presence of mind to take a screenshot.)
The page told me that the status was "Delivery Initiated." That is all: "Delivery Initiated."
As a developer, I respect the brevity of the message. As a traveler in a strange land, wearing the same pair of boxers for the second day in a row, I did not appreciate it at all. The message was absolutely unhelpful and did nothing to ease my mind, or my discomfort.
- Did this mean they had located the suitcase in Frankfurt and it was being delivered to Schiphol?
- Did this mean it was in Amsterdam and being delivered to the hotel?
- What time did the status change?
- When could I expect to be reunited with my suitcase?
Nope. All I got was "Delivery Initiated." Lufthansa, and the developers of their lost-luggage system, forgot that nobody uses their system for grins and giggles. There is no option to track a random stranger's lost luggage for fun. If you are using this system, you are most likely a little stressed and probably angry at the company.
They had no empathy for me as the user. If they had, they would have given me more information. At the very least, a key off to the side explaining what "Delivery Initiated" means would have helped.
The Solution: Have empathy for your users
A more empathetic system would have offered more statuses:
- We found your luggage in XXX.
- Your luggage has arrived here in XXX.
- We've dispatched a courier with your luggage to your hotel or home.
- Your luggage has been delivered safely. We are sorry for the inconvenience.
Any of these would have told me what was going on. Adding a timestamp would have been even better.
It is not enough to put yourself in your user's shoes; you have to put yourself in their mindset. You have to design every user interaction with an understanding of not only who is using your software, but why they are using it.
- If you are designing a game, the interactions should be fun and entertaining. Your users are usually in a good mood or looking to kill some time.
- If you are designing an airline check-in system, the interactions should be streamlined and matter-of-fact. Your users want to get it done and get on with their travels.
- If you are designing a shopping system, the interactions should help users make a buying decision.
It is not enough to create personas and figure out who is using your software. You need to understand why they are using it and what their mindset will be while they use it. You need to have empathy for your users.
Epilogue
It turns out that by the time I checked the online status, my luggage was actually at the hotel. The hotel, however, had misplaced it. :) Eli, I really need you to give me another bottle of Pyrat Rum. I need a new talisman.