With gratitude for (and apologies to) James Lileks and his outstanding book “Gallery of Regrettable Food”, this is the second in an occasional series called “Regrettable User Experience”. In each “Regrettable” article I briefly highlight a website or application practice that should be avoided entirely or executed in a very different way.

Next on our list is the common but regrettable practice of overwhelming users with information.

“Too much information” can take many forms.  One of my favorite examples can be seen on the Joann Fabrics website. Consider the map that’s displayed as soon as a user clicks the Store Locations link from the site’s home page:

Joann Fabrics default store locator map

That’s a lot of fabric! But unfortunately this display does almost nothing to help answer the high-probability question “Where’s the nearest Joann store?”.  This is way too much information to be useful. To be fair, once users enter a zip code or other search criterion the store locator is adequate, but this map is really out of hand.

I’ll be covering store locator best practices in another article soon. In the meantime, let’s look at another example.

This one’s taken from a discussion forum. This navigation display enables users to easily switch between pages of threads within a section:

You can't see it in this image, but this multi-page navigation goes all the way to 148.

It looks familiar and similar to multi-page choices you see on many websites. But here the page numbers actually go all the way up to 148, causing a massive amount of horizontal scrolling. It looks like this:

Displayling links to all 148 pages is definitely too much of a good thing.

Yikes. I’ll be covering multi-page navigation in a future article, but for now let’s just say this isn’t the most sensible or efficient way to present these options.

Look at it this way: a glass of water and a fire hose are both capable of quenching your thirst. Which would you rather drink from?

Good, usable information displays deliver enough of the right information without overwhelming users and risking information overload.

nv879qa6t4

Related posts:

1. Regrettable User Experience: website background music

With gratitude for (and apologies to) James Lileks and his outstanding book “Gallery of Regrettable Food”, this is the first in an occasional series I’m calling “Regrettable user experience”. In each “Regrettable” article I’ll briefly highlight a website or application practice that should be avoided entirely or executed in a very different way. I’ll also give suggestions on making it less regrettable.

First on my Regrettable list is a semi-rare but still annoying “feature”: automatically triggered background music.

Let me be clear: I’m not referring to websites that employ music as part of user-triggered product demonstrations, slide shows or other multimedia displays. I’m referring to websites that begin playing a soundtrack as soon as you hit the home page, and continue playing it as you move through the site.

There aren’t a lot of websites these days that employ this “feature”, but it can be found here and there. For example I recently visited the Ethan Allen website while looking for a furniture image to use in an article.

As soon as I landed on the Ethan Allen home page, a soundtrack began playing – and I wondered where this bizarre and not terribly appealing music was coming from. I couldn’t find a button to stop the music, or a slider to control its volume.  (Side note: They seem to have killed their background music since I visited the site about a month ago).

In any event there are a few reasons why automatic background music is regrettable:

• It violates the principle of user control. As I’ve discussed before in my article on the User Operation Prohibited DVD tag, it’s important to grant users a reasonable amount of control over their experience. Playing music automatically bypasses user control.
• It’s much more likely to annoy than please users. This is especially true if the music loops or re-starts each time a new page is loaded. Keep in mind, unless you’re appealing to a very, very narrow group of users that are just like you it’s extremely likely that your taste in music is not the same as theirs. Also keep in mind that users may already be listening to music when they arrive at your website. For those users the addition of a second sound source will create an involuntary and random mashup that’s probably not going to win any Grammys.
• It can create very awkward moments. Suppose a user visits your website while in bed with their laptop, their spouse sleeping next to them. Your music starts playing and you’ve just startled a potential customer and caused them to search frantically for a way to make your website shut up! The same type of situation (minus bed and spouse) could also take place at an office, a computer lab or a library.
• It’s probably not necessary. I suppose one could argue that background music can add an element of brand identity in the right situations, but given all the drawbacks there are much better ways to reinforce brand identity visually.

Of course there are some cases where music can and should be part of the user experience. For example if you’re selling music (e.g. – a record store or band website) then it makes perfect sense to offer sound clips or even complete downloads. But importantly, sound clips like this should be triggered and controlled by the user, not triggered by default. Even on band websites I don’t advocate playing the band’s music unless a user triggers the playback.

Making background music less regrettable

There are two good – and relatively obvious – ways to address the problem created by automatically triggered background music:

1. Don’t use it at all
2. Use it but:

• Default the music player to an “off” condition and enable users to turn it on if they so choose,

and/or:

• Display a prominent control to pause or stop it and change the volume. This control needs to be clearly visible on any page that the user can visit while still hearing the music. It should also be large enough that users can easily manipulate it if they need to stop the music or change the volume in a hurry.

This will make an otherwise regrettable website feature considerably more usable, and will avoid a great deal of potential user frustration.

Image credit: Spud. Creative Commons licensed.

Related posts:

1. Regrettable User Experience: too much information