Whether it’s for personal or business reasons, people move all the time. Some companies, like transportation and self-storage firms, do a good job of capitalizing on this activity. But with the exception of the annual college-dorm-stock-up sales at places like Bed Bath and Beyond, I think retailers are leaving a lot of money on the table. In particular, both mid-range and higher-end stores could benefit from offering a handy package of items to get you started after a move, which they can then use to drive upgrade sales for months and years afterwards.
When people move, there are always some things that they throw away because the items are worn out, are a pain to transport, etc. Best intentions aside, I think most of us end up buying the replacements in a marathon shopping trip at stores like IKEA or Target, where you can get nearly all the missing things at a low cost. But at least in my experience, these items end up wearing out quickly and getting replaced with higher-quality versions over time. And when it comes time to find the replacement products, at least some group of shoppers will place quality and reputation ahead of low cost and one-stop shopping. Think Crate and Barrel, rather than IKEA.
Taking things back a step, retailers who offer higher-quality products seem to be at a disadvantage when it comes to selling things to people who have just moved. Relatively few people would go to these stores to stock up a new home from the get-go, unless their budget is quite large. And when people are ready to upgrade later, it’s one store against the other in the usual game of advertising, discount offers, etc.
So what’s the solution? Simply put, even mid-to-high-priced retailers should start offering a starter kit for people who have just moved. This would bundle the common kitchen, bath, and living items together in an affordable package, probably at much lower margins than the store usually gets. The goal is to win that business away from the low-cost sellers. And then once customers buy the starter kit, they are primed for upgrade purchases down the road.
Here’s how it works. Start by including a “Good, better, best” card with every single item in the starter kit. Then, when the customer has had enough with the small skillet or 4 cup coffeemaker, they can choose an upgrade option, go to the website shown on that card, and purchase the better model. (Of course, they could also bring the card into the store.) Depending on the product, this could be accompanied by a special offer code for free shipping, a percent discount, etc. Besides offering an upgrade path for each product in the starter kit, customers could be sent a monthly or quarterly newsletter with relevant offers, especially since the store knows exactly which items the customer already has, and might be ready to replace.
Regardless of the exact implementation, the basic premise remains the same: give customers an easy way to start purchasing your products at a key time in their life (in my example, after they have moved to a new home), make it cost-competitive with other options they’re considering, and use that relationship to sell upgrades and related products over an extended period of time. Granted, that initial sale is going to be lower margin than the store is used to. But since this approach lends itself to repeat business, the margins earned on those follow-up sales should lead to considerably higher profits over time.
Filed under: Design, User Experience | Closed
Optimizing for popular tasks
While looking through restaurant reviews on the Yelp Mobile site, I noticed that they only show you a little snippet of each one. To read the rest, you have to click on a link and wait for another page to load. Granted, this approach lets you see the first part of many reviews at once, ensuring a wide sample of opinions. But if my experience is any indication, it makes the more common task of reading the most interesting or relevant reviews a lot more tedious, since you have to click each one separately.
I’m pretty sure Yelp designed it this way to make the file sizes smaller, reducing load times for each individual page on mobile devices. Or maybe they wanted to fit more entries on the small screens. But while a given page might load faster, the overall process is more complex and time consuming. Users have to look at the snippets, click the first review that looks relevant, wait for it to load, read it, go back to the list of snippets, choose the next review, etc. Do this a few times, and it becomes quite frustrating.
I recommend two changes to remedy the problem. First, when the initial review page appears (with all the snippets), provide a link that expands all the reviews on a single page. That way, those who want all the info at once can have it, without increasing load times for those who are just browsing. Second, if you’re committed to the one-review-per-page method, include links to view the previous or next review for that business. This eliminates the frustrating back-and-forth that accompanies a snippet-only design.
Filed under: Design, Usability, User Experience | Closed
There are many great articles (and even whole books) about how to design data entry forms. Despite this wide body of knowledge, the basic rules still seem to elude a lot of web designers. In particular, designers are still creating input fields that are too short to fit the data that customers typically enter.
Actually, these input boxes let you enter plenty of data. Their storage capacity is fine. The real problem is that they’re too short, so you only see the first 10 or 20 characters at once. Granted, you can use the arrow keys to see the rest of what you typed. But why make users do that? Isn’t it better to let them see all their info at a glance? Of course it is.
As a rule of thumb, start by using your log files to determine what people typically enter into these boxes. Ignore the largest 20% of entries, and make your input box big enough to fit what the remaining 80% of people are actually typing. Similar rules help dictate when you should use a multi-line text box instead of the standard, single-line version. There is a lot more to say about this subject, but even the small change I described would be a big improvement for most websites.
Filed under: Design, Usability, User Experience | Closed
Over the past few weeks, the Internet performance on my BlackBerry has degraded so much that it’s barely usable. Even simple websites take more than a minute to load, compared to the 5-10 seconds that I’m used to. From fussing around with different sites, I know the issue affects any website I try to load, and only happens with the standard BlackBerry browser. (It works fine in other browsers, like Opera Mini.) So, I’m pretty sure the issue is being caused by something at RIM, the folks who make the BlackBerry devices and provide the corresponding server backend for many of the built-in applications. Eventually, I’ll suck it up and call tech support, but one thing’s for sure: the progress bars that RIM and others use for their applications are virtually useless. This makes it much harder to diagnose the problem, and leaves even experienced users guessing.
Progress bars appear in all sorts of software programs. Generally, there are two problems with how they’re designed. First, the length of the bar (or the speed it gets filled up) has nothing to do with how long the task should actually take. Second, the text that accompanies the progress bar doesn’t mean anything. In my example, the progress bar starts to fill up from left to right, suggesting that all will be good when it reaches the end. It starts off moving quickly, and then gets slower as it approaches the right side. When it gets there, it just stays full until the process is completed or abandoned. The status text is just as useless. It says “Requesting…” the whole time, without any indication of what it’s communicating with on the other end. You can’t tell if the delay is from the website, the cell phone carrier, etc.
So if you’re going to include a progress bar in your application, try to follow a few simple rules. First, make the progress bar move at a consistent speed, so that users won’t feel tricked if it seems to take forever to get from 80% done to 100% done. Similarly, when the bar reaches the end, don’t just have it sit there. Either say the process is done, or that it failed. Next, if there’s no way to tell how long the task might take, don’t use a traditional progress bar design. Instead, go with a design like a spinning ball or hourglass. This tells the user that something is going on, and you don’t know how long it will take. And finally, make your status text as specific as possible. If you’re waiting for a reply from the website or service provider, then say so. After all, something like “Connecting to Verizon Wireless gateway” or “Waiting for reply from BlackBerry Internet service” is much more useful than the generic “Connecting” or “Waiting”. Among other benefits, this approach would make troubleshooting issues like mine a lot easier, cutting down on tech support costs.
Filed under: Design, User Experience | Closed
In the rare event that I go to the movies, I prefer to use the automated kiosk to buy tickets. Usually, it works fine. But when I tried to purchase tickets on a recent weekend, the kiosk ran out of paper right before it was my turn to use it. Perhaps it sends an automatic alert to the theater manager, or somebody’s watching from HQ and they notify the theater to replace the paper. But since the kiosk didn’t say anything about this either way, I tried to tell someone there about the issue. Nobody even acknowledged my presence, and the angry mob of a line ended up waiting a good 15 minutes for the kiosk to be fixed.
This situation highlights a process that every business should use when something goes wrong with its website, kiosks, whatever. First, provide a clear indication that the system is not available, e.g. “This kiosk is out of paper and cannot be used for printing tickets.” Next, tell the customer what steps are being taken to correct it, e.g. “A message has been sent to our theater manager and they will be correcting the problem by (some reasonable time in the future).” Then, provide alternate options for completing the transaction, like a toll-free number. And finally, if there’s any benefit in having the customer notify your staff about the issue, tell them how and where to do this, e.g. “For immediate service, please go to the Guest Services desk and tell them that kiosk number 123 is out of paper.”
This last point can easily be the most important. The theater has customers who are willing to tell them immediately about a problem, but they ignore you when you try to do so. Mostly, I think this is due to some degree of apathy, along with the lack of an established process for setting expectations and telling customers and employees how these issues should be handled. By following the steps I outlined above, issues would probably get resolved faster. But even if they didn’t, at least customers would know what to expect — and whether they should invest the time to help out in the first place.
Filed under: User Experience | Closed
During the past few weeks, I’ve eaten at two different Chipotle restaurants. In case you aren’t familiar with it, Chipotle is a fast casual chain that sells tasty burritos, tacos, etc. Generally, the food is very consistent from one location to the next. But one thing surprised me: the amount of salsa you get in a container varies widely between stores, even though the containers are exactly the same size. And when I asked why this happens, the store with the half-full containers gave me a strange answer: that’s just how big their ladle is.
So, despite all their efforts to offer a consistent experience at each site, the chain apparently has different size serving equipment in some locations. If I had to guess, they probably have a stringent auditing process in place for things like store design, cleanliness, and quality of food. But when it comes to less obvious things like the exact amount of food that you get with each order, things might be a little less cut-and-dry. Perhaps store managers are free to purchase certain supplies from local vendors, so they don’t have to call the corporate office when they need more serving spoons, for instance. In any event, I don’t think anything devious is at hand, but rather, there’s a lack of controls over seemingly inconsequential aspects of the store experience.
Granted, this sort of variance may have little impact on customer satisfaction or profits. Heck, it took me a few months to notice the difference. But I wonder what other things might be escaping their usual quality controls. Now that I think about it, you tend to get less chicken, but more peppers, at one of the locations. The next time I’m at Chipotle, I’ll have to fill out a comment card, and see if they make any changes to get things consistent again. And for other businesses that are seeking consistency, my advice would be to look not only at the final product, but also at the tools and process that are being used to create it. Sometimes, even the size of a spoon can make all the difference.
Filed under: Testing, User Experience | Closed
Unwelcome icons
If you use Windows at all, you’ve probably had a few mysterious icons appear in the taskbar at the bottom right of your screen. Sometimes these are useful, helping you keep tabs on the status of a program or utility. But more often than not, they appear there because the software vendor decided it would be nice to have their logo appear all the time, with virtually no value to the user. Making matters worse, there’s rarely a way to prevent installing this component, and removing it can be a real pain.
When it comes down to it, forcing users to accept a taskbar icon when they install your software is a bad practice. If the icon is needed to make the software work, then at least make the user aware that it’s being installed, and explain why. In cases where the icon isn’t really needed, and it’s more of a promotional or branding thing, give the user the ability to opt-out of this component during the install process.
Sure, you’ll get fewer chances to present users with your logo and messages. But at least you won’t be viewed as one of those companies that installs suspicious software without their consent. Indeed, as viruses and spyware make people more wary of what goes on their computers, preserving customers’ trust should be a top priority.
Filed under: Design, User Experience | Closed
Meals on a plane
I often buy food at the airport so I’ll have something to eat on the plane (or while I’m waiting at the gate area). Every time, I run into the same problem: The restaurant never seems to have a plate or tray to place the food on, or the plates they have are very cumbersome. So, the food gets shoved into a plastic bag, and I end up using the bag itself, or the product packaging, or even a napkin as a makeshift eating area. Clearly, there is an opportunity to provide something better — and charge customers accordingly.
What I’d like to see is quite simple: picture a small cardboard carrier with room for a drink, sandwich, snack, etc. (I’m not sure if they’re still sold this way, but Munchkins and Happy Meals used to be packaged like that.) Now here’s the slightly creative part: The carrier unfolds to form a flat tray that you can use as your plate, and should be about the size of an airline tray table. The edges of the tray might even bend upwards to prevent items from slipping off. And when you’re done eating, you simply fold up the carrier again to discard everything.
But won’t this cost more and reduce margins for the restaurant operators? No, because under my plan, they would charge for it. $1 seems like a fair price, since the materials would probably cost no more than 25 cents. Although I haven’t done any surveys, I’ll bet this would sell like crazy to business travelers. It could even be co-branded with a corporate sponsor to reduce the cost to customers, or to further increase the profit incentive for restaurants to offer the product. Plus, I suspect the improved eating conditions would help keep airports and planes cleaner, as fewer items would be dropped or spilled on the floor and seats. For virtually everyone involved in the travel process (passengers, airport restaurants, airports, and airlines), a simple food carrier makes a lot of sense.
Filed under: User Experience | Closed
While reading an article yesterday, I noticed a big error message where a Flash movie was supposed to appear. Basically, it said I should click there to upgrade to a new version of Flash. It even promised that I didn’t have to leave the page or restart my browser. But with all the viruses and spyware going around, I’m quite hesitant to click on this sort of thing. Making matters worse, there were obvious typos in the message, which made me even more suspicious about whether the message was legitimate.
I first saw spelling and grammar mentioned as ways to determine a document’s authenticity a few years back. This was around the time that those “Please verify your bank information” scams started making rounds. In response, the banks began telling customers to watch out for suspicious emails, and provided several tips to identify fraudulent messages. Among these telltale signs were a strange website address (i.e. not the bank’s website) and spelling and grammatical errors. The latter is especially interesting to me, as it arguably remains valid today.
When a piece of correspondence (email, website, ad, whatever) contains spelling errors and other mistakes, it makes the reader question the validity of it. I can’t think of the source right now (perhaps it was Steve Krug), but I once read a great study that showed how reader attention dwindled with each spelling error. Readers of an error-laden document went from highly engaged to barely even skimming the page, as the mistakes chipped away at their trust in the content.
With this in mind, my recommendation is to take the time to double-check all your correspondence. This is especially important for customer-facing documents like your website, although emails and other correspondence should be given some attention as well. Considering how few people actually do this, the benefits to those who take the time to proofread can be significant. All else equal, customers will place more trust in what you say and be more engaged by your message. You establish yourself as a person or organization that takes the time to make your words count. For at least some portion of your target customers, this will lead to more trust and increased sales.
Filed under: Design, User Experience | Closed
Jumping through hoops
Since my mom was in town last weekend, I decided to try one of those guided bus tours of the city and the surrounding areas. To save time, I bought the tickets online and had everything ready for our Sunday morning jaunt. But when it came time to hop on the bus, it was nowhere to be found.
When I called the bus company, I learned that they had cancelled all the rides that day because of inclement weather. (Since when is snow a problem in Chicago?) I would have preferred an email to let me know, but I understand the cause is beyond their control. Here’s where it gets fishy: I couldn’t just use the ticket another day, or request a refund at that time. They told me to call back on Monday and talk to some guy whose name I forgot immediately. They said they couldn’t do anything for me until I called back at that time.
On Monday, it took no less than three tries to reach this all-powerful individual. He was polite and efficient and processed the refund promptly. So what’s my complaint? Instead of being able to request a refund when I was told they cancelled the service, I had to waste time making more phone calls and tracking down the right person. I’m sure this isn’t the first time the bus company has had a weather cancellation, but apparently they’re just too lazy to put a proper refund process in place.
Generalizing this a bit, if you can’t honor the promises you made to your customer, and the only option is to refund their money, at least have the decency to make it easy for them. Requiring an already irritated customer to call you multiple times to get their money back is ridiculous. Find a way to take care of the transaction on the first call, right after you determine that a refund is due, and don’t make it drag on for days.
Ultimately, every little hassle you create for the customer is going to reduce the chance of them ever coming back. But if you handle these interactions properly, e.g. taking care of a refund on the spot, you have a much greater chance of saving face and earning their future business.
Filed under: User Experience | Closed
You must be logged in to post a comment.