For this first entry, I will be introducting the annoyance rating. 0 being not annoying at all to 10 being really freaking annoying. This is totally inspired by my UI colleague who used to scream "How obnoxious" when something was particularly poorly done.
So I'd like to begin the error messaging section with this qoute from an anonymous source.
Good usability error message should be expressed in plain language (no codes), precisely indicate the problem, and constructively suggest a solution.
Here is my analysis. Click on them for a larger version.
So here are some rules I came up with.
1) Make sure a user has something to help let them know they are at the right place.
2) Be human, say "Hi"
3) Don't use negative words like "crashed, failed, or problem"
4) Avoid graphics that represent issues like the exclamation point in the yellow warning triangle or the RED X.
5) Give a reason if you can.
6) Let people know you are working on it.
7) Give them a call to action such as, "visit our site blog to get up to the minute status of the site" or "come back in 20 minutes."
8) Make sure the page has some structure. Even tho everything is down, doesn't mean the error has to look that way.
9) Graphics are cool however just be aware that the graphics you use will be associated with this error.
10) And of course! the best kind of error is none at all. Strong design has things thought through to avoid the error message scenario.
Cheers,
JT
---
Other links (Thanks BIG John):
http://www.smashingmagazine.com/2007/07/25/wanted-your-404-error-pages/
http://www.smashingmagazine.com/2007/08/17/404-error-pages-reloaded/
No comments:
Post a Comment