Yes or No
I bought movie tickets from one of those automated ticketing kiosks last weekend. While the user interface certainly won’t win any design awards, it seems pretty functional. But one screen always sticks out to me: the part where it asks you to swipe your loyalty card. This would be fine, except I don’t have such a card. The only button on the screen says “Continue”, and I always get stuck reading the instructions before I figure out that you’re supposed to press that button even if you don’t have a loyalty card.
This is a perfect example of a common user interface mistake that you see on websites, kiosks, consumer electronics, and more. The designers make an assumption that they think will simplify the process, but it ends up slowing people down. In the case of the ticketing kiosk, they really ought to say “Do you have our loyalty card?” and present buttons for Yes and No. For those who choose Yes, it could then prompt you to swipe the card. Or, to keep the workflow that I think they were aiming for, just change the existing button to say “I don’t have a loyalty card”. This would eliminate any confusion.
Whenever you’re designing for an audience of diverse users, think carefully about any assumptions you make. If some customers don’t have a special card, or a password, or a membership number, your design shouldn’t assume that everyone has this data. And even if you can’t remove these data capture screens from your application, at least make it easy for people to bypass them when they don’t have the information that you’re asking for. In most cases, asking customers the right question with a simple Yes or No response can work wonders.
Filed under: Design, Usability, User Experience | Closed
For the second day in a row, I’m going to talk about product packaging. Today’s question: Why aren’t more packages resealable? I’ve seen this feature on raisins, cheese, and other small items (both perishable and non-perishable), but never on bigger things like bags of pretzels or tortilla chips. Working on the assumption that the CPG companies don’t have a secret collaboration with whoever makes those “chip clip” things, there must be something else afoot.
Maybe these large packages are some sort of “family size”, designed to be eaten by a large group in one sitting. But this would suggest that the really, really big packages (which only a football team could finish) would be more likely to be resealable, and I haven’t seen any evidence of that. Or perhaps the manufacturer hopes that once they open the bag, consumers will transfer the contents into a large Ziploc or other storage container. This would provide additional margin (since the same CPG companies often make plastic bags), but I still find such a scenario hard to believe.
When it comes down to it, I think the presence or absence of resealable packaging is mainly a factor of product positioning. I’d speculate that the leading brand in a given segment is unlikely to introduce this, since it costs more to produce and erodes margins. But once a challenger brand steps in with the feature, along with labeling that promises the food will stay fresh longer, the others are more likely to follow.
Now that I think about it, some of the products I mentioned above — like pretzels and tortilla chips — do tend to be dominated by one or two companies. Even large retailers like Target may only carry one brand of each, aside from the store brand. So, my sad conclusion is this: Even if an obviously useful feature like resealable packaging costs very little to implement, it often gets left out of consumer products because it increases unit costs and there is little competitive incentive to include it, until someone else does so first.
On the other hand, if you add a simple and useful feature like this to your own products — especially when you’re selling software — you might find that sales increase a lot more than you expect. It may turn out that customers have been waiting for it all along, but no one ever had the guts to bring it to them.
Filed under: Design, User Experience | 2 Comments
Contents may shift
Virtually every box of cereal, crackers, and other packaged foods has some sort of disclaimer that the box might not be “full” when you open it. Why? The contents may have “shifted” or “settled” during shipping. But since these items are sold by weight and not volume, the story goes, we as consumers shouldn’t concern ourselves with the empty space inside.
With that said, I’m left wondering why they don’t take this one step further. On the inside bag that contains the product, simply print a green line that says “Contents may shift during shipping, but should start out above this line.” That way, there is no confusion about what a “full” box might be, and I’ll bet that returns and exchanges would be reduced.
To generalize this a bit, don’t just tell customers that something might be different than they expect. Instead, give them a concrete way to verify that what they’re getting is correct. This might take the form of a fill-up line like I described above, a sizing guide, or a color chart. Regardless of how you do it, this approach should help you better manage customer expectations and reduce errant returns.
Filed under: Design, User Experience | Closed
Broken promises
I read an article a while back about how some companies are paying design firms to make their billing statements easier-to-read. From what I recall, the goal is to reduce the chance that people will misunderstand the bill or miss key information like the due date. Thus, they will be more likely to pay the right amount and send their payment on time.
With this in mind, it occurred to me that while a lot of bills are quite well-designed these days, most companies just don’t have the systems in place to follow through on the experience. Case in point: my phone company has a number on the bill specifically for making a payment. Yet when you call, you have to go through a big, frustrating menu. Why even have the separate number at all? My guess is that no one bothered to program their PBX to match the billing statements.
Don’t get me wrong: I think it’s great that companies are improving the design and clarity of their customer-facing documents like order forms and monthly bills. But these measures can only do so much if the other parts of the customer experience are lacking. At a minimum, it pays to have some “mystery shoppers” send emails to your customer service department and call the various phone numbers on your billing statements, just to make sure that customers are getting the type of service you expect. Otherwise, you really don’t know if the right information is being provided at the other end of the line.
Filed under: Design, User Experience | Closed
Oh, those aren’t for you
Some companies love to tell you what you can’t have. Northwest Airlines is one of them. When selecting a seat, you are presented with at least three different groups of seats that you can’t select. Some of these are only for special frequent flyers, other aren’t available until one day before the flight, etc. There’s no obvious way to upgrade to these seats, even for a fee. It’s like a candy store where all the bins are locked, with “Only for special customers” written on the top.
Maybe it’s just me, but I don’t get much value from an extensive list of things that I can’t have. Northwest should just show the seats in three categories: not available, available, and available at an extra cost. And for that last category, let customers see the cost and buy them right then and there. Otherwise, the experience is not only confusing and unproductive, but pretty demeaning as well.
Filed under: Design, User Experience | Closed
Quantifying lost sales
I’m often frustrated by the number of businesses that don’t accept American Express. When you try to use Amex, they look at you like you just presented a bundle of sheep’s wool or some fresh berries or a bottle of goat’s milk. “I’m sure they’ll use another credit card,” the merchant thinks, while rudely saying that they can’t accept your card because “the fees are too high”. But if my behavior is any indication, Amex users are a very loyal group that only carries a Visa or MasterCard for genuine emergencies, and prefers to consolidate all their spending on a single Amex bill. In short, if the merchant doesn’t take Amex, many of us won’t shop there at all. I have a personal blacklist of stores for this very reason.
I propose that American Express put up a website where cardmembers can record an entry each time they refuse to shop somewhere because that business doesn’t accept Amex. Each entry would contain the business name, location, date, and the amount of money the consumer would have spent. To make the process easy, the list of businesses and locations could be populated by licensing a local business database from Yelp, Citysearch, etc. There could also be a mobile version or a way to submit entries via email, for quick recordkeeping on the go. To encourage usage, Amex might even have a prize drawing each month, weighted towards those customers who submitted the most reports.
Then, some enterprising group at Amex could mail a quarterly statement to each business on the list, comparing their lost sales against the (tiny) processing fees they would have paid on the transactions. The biggest offenders could even have their store names published in a hall of fame type page, or in a national newspaper ad, either based on total revenue squandered or total consumer complaints. Maybe, just maybe, this would help all those ignorant business owners to understand that paying an extra one percent (or whatever it comes out to) on a transaction is a lot better than losing the entire sale.
Filed under: User Experience | Closed
I have a new pick for the most useless error message. Some web-based apps are using the phrase “Your browser is not optimized”. What they actually mean is, “We don’t support your browser so you should switch to another one.”. Why can’t they just tell you that? Beats me. Maybe they don’t want to come across as too bossy, or something like that.
As it stands, this message leaves the user wondering how they might change a myriad of browser settings to improve things, and feeling like they’ve done something wrong. Even worse, I’ve seen this same phrase used in sneaky pop-up ads on various websites, which is not something you want your product to be associated with.
I think the takeaway here is simple: Don’t say something generic just to soften the blow of a message. Either say what you mean, or don’t bother showing an error at all.
Filed under: Design, Usability, User Experience | Closed
Labeling your parts
Maybe it’s just the weird stuff I’ve been buying lately, but it seems like virtually every electronic product includes a power adapter (sometimes in two pieces), a data cable, and various other things, each using all kinds of strange plugs and connectors. Even if you’re very well organized, it’s pretty easy to misplace these parts or lose track of what goes where — especially if you take them on the road.
I won’t even get into the crazy logic that makes companies use so many incompatible parts. But I do have an easy way they can help customers keep track of all those pesky items. The solution? Labels. Each part should have a little sticker on it with a description of the product, along with a name for the part. For example, it might say “Power adapter for Linksys router” or “USB cable for Sony CD-RW drive”. And if it’s too hard to actually attach the labels to the items, just put them on a little precut sheet that says “Use these labels to keep everything organized”. Granted, this approach would add a few cents to the cost of the product. But the benefits in terms of customer satisfaction and long-term repeat purchases should be many times greater.
Filed under: User Experience | Closed
Keeping customers in the loop
I’m always amazed when airlines refuse to show the current status of delays at the gate. They apparently want dozens or hundreds of people to stand in line and ask the same questions: “Are we delayed?”, “When are we leaving?”, etc. I’ve seen this in various cities and with different airlines, including much-loved Southwest. It almost seems like an industry-wide anti-customer policy is in effect.
Here’s a radical idea: Take a black marker and a piece of white paper. On the paper, write: “As of (current time), we are delayed and expect to depart at (new departure time),” or “As of (current time), we are delayed and don’t know how long it’s going to be.” Tape it above the counter at the gate. Then, whenever new info is received, throw out the old sign and make a new one. Seems pretty easy to me.
We can apply this to software, too. When there’s a significant problem that affects your customers, tell them about it and when you think it will be fixed. If you can’t pick a time and date, just be honest and say so. And when you have new info about the issue, be sure to update the message that customers see, so they understand that it’s being worked on. Long story short, people respond a lot better to problems when you acknowledge the issue, show them what you’re doing to fix it, and provide status updates when you have them.
Filed under: User Experience | Closed
Phantom options
Ever come across a Preferences or Settings screen that shows you things you can’t change? This might be a text box where you can’t edit the text, a checkbox that you can’t uncheck, or a drop-down menu that only contains one item to choose from. In each case, the software makes it look like you have options to choose from, but these entries might as well be written in stone.
When we see any type of data entry or selection widget, our mind tries to process it and decide whether it’s something we need to pay attention to. But since these phantom options don’t actually do anything, they waste our time and effort while eating up valuable space on the screen. In short, they make the interface more cluttered and harder to use.
Here’s a simple set of guidelines to prevent this problem: If the user can’t change a particular setting and probably won’t ever be able to, then don’t make the setting look like a menu or text box (or anything else that invites you to click on it). Instead, show the data as regular text, ideally in a separate area of the page that contains the other things that can’t be changed. If the setting might be editable later, like when the user creates another template and then has two to choose from when editing, it’s probably OK to put the plain text info where the menu will go later, but don’t get carried away with this approach. Finally, if your application is designed to handle large amounts of data, like in a CRM system, it’s fine to use a standard selection box even when only a single choice exists in the early going — but be sure to give users an easy way to create more entries with a button like “Add New Contact” located next to the selection box.
Filed under: Design, Usability, User Experience | Closed
You must be logged in to post a comment.