August 24, 2006

UXP Rant: Web Server Error Code Copy … Say WHAT????!!!!

A special guest post from Jane-Anne, our "Queen of User Experience."


You have to admire Google. I do, because they gave me an opportunity to talk about something related to User Experience (although really, everything is related to the user experience. See my follow-up post to our mascot blog entry as well for proof!).


Too often, web server error messages are full of technical-ese and don’t tell the user what is going on, what happened or what they should do. And too often, marketers are missing a really nice way to strengthen, or at least keep, the relationship with the user and build upon their brand.


All it takes is a little creativity. Say something in simple, understandable language and if you can, make sure it reflects the tone, style and culture of your organization. The DG employee who received the Google error message said it made her laugh. This is a big change from a user who would get the standard 404 error message and be left confused or worse – frustrated.  Even better, it won’t get ignored like the typical error message will, and you might even get some viral activity around it like this Google one did.


At the very least, we’ll think you’re pretty cool.

UXP Rant: Web Server Error Code Copy … Say WHAT????!!!!

A special guest post from Jane-Anne, our "Queen of User Experience."


You have to admire Google. I do, because they gave me an opportunity to talk about something related to User Experience (although really, everything is related to the user experience. See my follow-up post to our mascot blog entry as well for proof!).


Too often, web server error messages are full of technical-ese and don’t tell the user what is going on, what happened or what they should do. And too often, marketers are missing a really nice way to strengthen, or at least keep, the relationship with the user and build upon their brand.


All it takes is a little creativity. Say something in simple, understandable language and if you can, make sure it reflects the tone, style and culture of your organization. The DG employee who received the Google error message said it made her laugh. This is a big change from a user who would get the standard 404 error message and be left confused or worse – frustrated.  Even better, it won’t get ignored like the typical error message will, and you might even get some viral activity around it like this Google one did.


At the very least, we’ll think you’re pretty cool.

August 21, 2006

Screenshot: Google Tells Us to "Give our Mouse a Break"

How's this for a Google Error Screen? Giveyourmouseabreak

One of our AMs got this while trying to access a campaign in AdWords. It's very sweet that Google's so concerned about the well-being of her mouse, isn't it?

(BTW, our "Queen of User Experience" loves this because they've used plain English instead of tech-talk.)

Screenshot: Google Tells Us to "Give our Mouse a Break"

How's this for a Google Error Screen? Giveyourmouseabreak

One of our AMs got this while trying to access a campaign in AdWords. It's very sweet that Google's so concerned about the well-being of her mouse, isn't it?

(BTW, our "Queen of User Experience" loves this because they've used plain English instead of tech-talk.)

November 02, 2005

Smart New Ways to Spend Your Ad or Marketing Budget

At a time when many of us are indeed working out our 2006 budgets, our friends at AdRants have shared this great article from Creating Passionate Users.

This is brilliant in its strategy as well as its wittiness...it looks more like the What's Hot/What's Not from Teen Vogue than a marketing piece. (And fun things are always good when you're planning your marketing budget AND coordinating your ad:tech New York presence simultaneously.)

Some snippets:

Old Way - Hire a branding expert. 

New Way - Hire, no - promote from within - a User Happiness Expert. 

OId way - Ads that talk about how you're better than your competition.

New Way - Articles that talk about what you've learned from your competition.

Brilliant. Read the whole thing.

[Heard it from AdRants, which, really, everyone should read.]

Smart New Ways to Spend Your Ad or Marketing Budget

At a time when many of us are indeed working out our 2006 budgets, our friends at AdRants have shared this great article from Creating Passionate Users.

This is brilliant in its strategy as well as its wittiness...it looks more like the What's Hot/What's Not from Teen Vogue than a marketing piece. (And fun things are always good when you're planning your marketing budget AND coordinating your ad:tech New York presence simultaneously.)

Some snippets:

Old Way - Hire a branding expert. 

New Way - Hire, no - promote from within - a User Happiness Expert. 

OId way - Ads that talk about how you're better than your competition.

New Way - Articles that talk about what you've learned from your competition.

Brilliant. Read the whole thing.

[Heard it from AdRants, which, really, everyone should read.]

October 17, 2005

Jakob Nielsen on Blog Usability

Usabilty Guru Jakob Nielsen has made our creative team very happy today by posting his "Top Ten Design Mistakes" for weblogs.

Here are Nielsen's main beefs wit da blog (excerpts only - click here to read the full article):

1. No Author Biographies: Unless you're a business blog, you probably don't need a full-fledged "about  us" section the way a corporate site does. That said, the basic rationale for "about us" translates directly into the need for an "about me" page on a weblog: users want to know who they're dealing with. 

2. No Author Photo: Even weblogs that provide author bios often omit the author photo. A photo is important for two reasons:

  • It offers a more personable impression of the author. You enhance your credibility by the simple fact that you're not trying to hide. Also, users relate more easily to somebody they've seen.
  • It connects the virtual and physical worlds. People who've met you before will recognize your photo, and people who've read your site will recognize you when you meet in person (say, at a conference).

3. Nondescript Posting Titles: Sadly, even though weblogs are native to the Web, authors rarely follow the guidelines for writing for the Web in terms of making content scannable. This applies to a posting's body text, but it's even more important with headlines. Users must be able to grasp the gist of an article by reading its headline. Avoid cute or humorous headlines that make no sense out of context.

4. Links Don't Say Where they Go: Many weblog authors seem to think it's cool to write link anchors like: "some people think" or "there's more here and here." Remember one of the basics of the Web: Life is too short to click on an unknown. Tell people where they're going and what they'll find at the other end of the link.

5. Classic Hits are Buried: Hopefully, you'll write some pieces with lasting value for readers outside your fan base. Don't relegate such classics to the archives, where people can only find something if they know you posted it, say, in May 2003.

6. The Calendar is the Only Navigation: A timeline is rarely the best information architecture, yet it's the default way to navigate weblogs. Most weblog software provides a way to categorize postings so users can easily get a list of all postings on a certain topic. Do use categorization, but avoid the common mistake of tagging a posting with almost all of your categories. Be selective. Decide on a few places where a posting most belongs.

7. Irregular Publishing Frequency: Establishing and meeting user expectations is one of the fundamental principles of Web usability. For a weblog, users must be able to anticipate when and how often updates will occur.

For most weblogs, daily updates are probably best, but weekly or even monthly updates might work as well, depending on your topic. In either case, pick a publication schedule and stick to it. If you usually post daily but sometimes let months go by without new content, you'll lose many of your loyal -- and thus most valuable -- readers.

8. Mixing Topics: If you publish on many different topics, you're less likely to attract a loyal audience of high-value users. Busy people might visit a blog to read an entry about a topic that interests them. They're unlikely to return, however, if their target topic appears only sporadically among a massive range of postings on other topics. The only people who read everything are those with too much time on their hands (a low-value demographic).

9. Forgetting That You Write for Your Future Boss: ...Think twice before posting. If you don't want your future boss to read it, don't post.

10. Having a Domain Name Owned by a Weblog Service: Having a weblog address ending in blogspot.com, typepad.com, etc. will soon be the equivalent of having an @aol.com email address or a Geocities website: the mark of a naïve beginner who shouldn't be taken too seriously.

(As for #10, what can I say except "mea culpa"! We'll be domain mapping soon enough.)

This is a great article, and I have to recommend that all bloggers and skin designers go over to UseIt.com and read the whole thing. Nielsen is widely accepted as the king of usability -- even though his own site is no great miracle of design!

...and secretly, I'm glad a few of Nielsen's points also appear on our own blogging best practices list!

Jakob Nielsen on Blog Usability

Usabilty Guru Jakob Nielsen has made our creative team very happy today by posting his "Top Ten Design Mistakes" for weblogs.

Here are Nielsen's main beefs wit da blog (excerpts only - click here to read the full article):

1. No Author Biographies: Unless you're a business blog, you probably don't need a full-fledged "about  us" section the way a corporate site does. That said, the basic rationale for "about us" translates directly into the need for an "about me" page on a weblog: users want to know who they're dealing with. 

2. No Author Photo: Even weblogs that provide author bios often omit the author photo. A photo is important for two reasons:

  • It offers a more personable impression of the author. You enhance your credibility by the simple fact that you're not trying to hide. Also, users relate more easily to somebody they've seen.
  • It connects the virtual and physical worlds. People who've met you before will recognize your photo, and people who've read your site will recognize you when you meet in person (say, at a conference).

3. Nondescript Posting Titles: Sadly, even though weblogs are native to the Web, authors rarely follow the guidelines for writing for the Web in terms of making content scannable. This applies to a posting's body text, but it's even more important with headlines. Users must be able to grasp the gist of an article by reading its headline. Avoid cute or humorous headlines that make no sense out of context.

4. Links Don't Say Where they Go: Many weblog authors seem to think it's cool to write link anchors like: "some people think" or "there's more here and here." Remember one of the basics of the Web: Life is too short to click on an unknown. Tell people where they're going and what they'll find at the other end of the link.

5. Classic Hits are Buried: Hopefully, you'll write some pieces with lasting value for readers outside your fan base. Don't relegate such classics to the archives, where people can only find something if they know you posted it, say, in May 2003.

6. The Calendar is the Only Navigation: A timeline is rarely the best information architecture, yet it's the default way to navigate weblogs. Most weblog software provides a way to categorize postings so users can easily get a list of all postings on a certain topic. Do use categorization, but avoid the common mistake of tagging a posting with almost all of your categories. Be selective. Decide on a few places where a posting most belongs.

7. Irregular Publishing Frequency: Establishing and meeting user expectations is one of the fundamental principles of Web usability. For a weblog, users must be able to anticipate when and how often updates will occur.

For most weblogs, daily updates are probably best, but weekly or even monthly updates might work as well, depending on your topic. In either case, pick a publication schedule and stick to it. If you usually post daily but sometimes let months go by without new content, you'll lose many of your loyal -- and thus most valuable -- readers.

8. Mixing Topics: If you publish on many different topics, you're less likely to attract a loyal audience of high-value users. Busy people might visit a blog to read an entry about a topic that interests them. They're unlikely to return, however, if their target topic appears only sporadically among a massive range of postings on other topics. The only people who read everything are those with too much time on their hands (a low-value demographic).

9. Forgetting That You Write for Your Future Boss: ...Think twice before posting. If you don't want your future boss to read it, don't post.

10. Having a Domain Name Owned by a Weblog Service: Having a weblog address ending in blogspot.com, typepad.com, etc. will soon be the equivalent of having an @aol.com email address or a Geocities website: the mark of a naïve beginner who shouldn't be taken too seriously.

(As for #10, what can I say except "mea culpa"! We'll be domain mapping soon enough.)

This is a great article, and I have to recommend that all bloggers and skin designers go over to UseIt.com and read the whole thing. Nielsen is widely accepted as the king of usability -- even though his own site is no great miracle of design!

...and secretly, I'm glad a few of Nielsen's points also appear on our own blogging best practices list!

June 28, 2005

Who Moved Your Cheese?

Imagine this:

You’ve just left work and have five minutes to run into the food store to pick up some string cheese before you have to be at little Johnny’s Soccer Tournament of Champions. You run in the store, run down the cheese aisle and go to grab it when you suddenly realize the cheese aisle isn’t the cheese aisle anymore. It’s now the Stationary/ Paper Goods aisle. Where did the cheese go? Why did they change it? It’s your turn to bring the team snack, and string cheese is perfect. It’s low fat, high protein, easy to eat and not messy … you need your string cheese! You now have to search for the string cheese. You’re now annoyed. Suddenly your five minute quick stop turns into a twenty minute harried hunt.

Change - some people like it, some people don’t.  Sometimes it’s for the better, sometimes it’s for the worse. And then sometimes, even though it’s really for the better, it appears to be for the worse. Don’t let this be the situation with your Web site.

We design and create a lot of Web sites for our clients. When we do this, part of our process is to ask all sorts of genius-caliber questions and one of them is, “How are you planning on marketing this change to your users?” I am usually greeted by silence or asked, “What do you mean? We’re making it better, so why do I need to tell them?”

Here’s why:

Human beings are funny about change. Tons of psychological studies have been done on how people react to it, and why. Just like the food store example above, your web users are used to certain things being certain ways and in certain places. When you switch on them, even if it’s for the better, they may feel negative about it, even with something as slight as a new background color (just ask eBay). They have to take the time to relearn your site. They get disoriented. They get frustrated. And they leave. Here you’ve spent time/money to make your site great and your users are abandoning it.

So what can you do?

  1. Tell them when it’s coming. You don’t even have to use an exact date, but let them know changes are on their way. “Look for our new design in November 2006!” Post the news on your site, include it in your enewsletter or email campaigns. Spread the word!

  1. Tell them why it’s coming. Point out the benefits they will reap from this change, and be specific where you can (e.g. “… a shorter checkout process, 360 degree product views”). If you’re making changes based upon feedback from your users, tell them this!

  1. Show them what’s coming. Give them a preview of improved functionality, the cool new design. Not only will this help your users get an idea of what to expect, but it can help you gain some champions who will spread the word, which leads to my next suggestion …

  1. Get their support. When we built a new application for one of our clients, we conducted some user testing using leaders from the group of employees the app was being built for. Not only did they provide us with great input, they felt like they had a part in making it great and became internal evangelists, driving excitement and making the acceptance cycle much easier and shorter.

  1. Give them support. Offer them tools that assist them in getting used to the new setup. Use a demo, a special HELP section. Provide redirects for pages, remind them to set new bookmarks. Deliver in-person training. You get the idea.

  1. Give them the reins. If you can, (this often depends upon what types of changes you are making), let them choose when they want to switch over, or add the changes in using a phased approach. The feeling of control or time to adapt will go a long way towards acceptance.

Not only will these suggestions help your users, they also offer you great additional marketing and branding opportunities as well. But that’s a topic for another time …

Who Moved Your Cheese?

Imagine this:

You’ve just left work and have five minutes to run into the food store to pick up some string cheese before you have to be at little Johnny’s Soccer Tournament of Champions. You run in the store, run down the cheese aisle and go to grab it when you suddenly realize the cheese aisle isn’t the cheese aisle anymore. It’s now the Stationary/ Paper Goods aisle. Where did the cheese go? Why did they change it? It’s your turn to bring the team snack, and string cheese is perfect. It’s low fat, high protein, easy to eat and not messy … you need your string cheese! You now have to search for the string cheese. You’re now annoyed. Suddenly your five minute quick stop turns into a twenty minute harried hunt.

Change - some people like it, some people don’t.  Sometimes it’s for the better, sometimes it’s for the worse. And then sometimes, even though it’s really for the better, it appears to be for the worse. Don’t let this be the situation with your Web site.

We design and create a lot of Web sites for our clients. When we do this, part of our process is to ask all sorts of genius-caliber questions and one of them is, “How are you planning on marketing this change to your users?” I am usually greeted by silence or asked, “What do you mean? We’re making it better, so why do I need to tell them?”

Here’s why:

Human beings are funny about change. Tons of psychological studies have been done on how people react to it, and why. Just like the food store example above, your web users are used to certain things being certain ways and in certain places. When you switch on them, even if it’s for the better, they may feel negative about it, even with something as slight as a new background color (just ask eBay). They have to take the time to relearn your site. They get disoriented. They get frustrated. And they leave. Here you’ve spent time/money to make your site great and your users are abandoning it.

So what can you do?

  1. Tell them when it’s coming. You don’t even have to use an exact date, but let them know changes are on their way. “Look for our new design in November 2006!” Post the news on your site, include it in your enewsletter or email campaigns. Spread the word!

  1. Tell them why it’s coming. Point out the benefits they will reap from this change, and be specific where you can (e.g. “… a shorter checkout process, 360 degree product views”). If you’re making changes based upon feedback from your users, tell them this!

  1. Show them what’s coming. Give them a preview of improved functionality, the cool new design. Not only will this help your users get an idea of what to expect, but it can help you gain some champions who will spread the word, which leads to my next suggestion …

  1. Get their support. When we built a new application for one of our clients, we conducted some user testing using leaders from the group of employees the app was being built for. Not only did they provide us with great input, they felt like they had a part in making it great and became internal evangelists, driving excitement and making the acceptance cycle much easier and shorter.

  1. Give them support. Offer them tools that assist them in getting used to the new setup. Use a demo, a special HELP section. Provide redirects for pages, remind them to set new bookmarks. Deliver in-person training. You get the idea.

  1. Give them the reins. If you can, (this often depends upon what types of changes you are making), let them choose when they want to switch over, or add the changes in using a phased approach. The feeling of control or time to adapt will go a long way towards acceptance.

Not only will these suggestions help your users, they also offer you great additional marketing and branding opportunities as well. But that’s a topic for another time …