I hope everyone enjoys this (in my opinion) very useful video podcast. The parent site WebProNews has an entire series of these (mostly dealing with Search Engine Optimization (SEO). This one is less than ten minutes long, deals with usability issues, and is definitely worth watching.
WARNING! It might start automatically, and you'll by now have turned down your speakers; if it doesn't, and you have to "push play"... do yourself and everyone in your office a favor by turning down your speakers before firing this one up. The front-end promo is a bit loud.
Some of the things I found most useful for Case Web site maintainers is the concept of "don't do what YOU want, do what's best for the client [or in this example the university]!" Also, when she talks about friends who ask her to evaluate their Web sites, she comes out and says "What difference does it make what I think about their website?" Usability rules: The most important consideration for her is, "can I properly use the web site"?
Another thing I found particularly interesting was regarding her opinion on use of images in a website. The host asks her to comment on particular problem or issues with the use of images on a Web site, and she responds "One major problem would be, too many... the other is not enough". Timely, considering a recent post by Heidi that talked about the importance of using graphics to illustrate a point -- even if using merely a thumbnail. Check out THAT earlier post by the way, if you haven't already.
One key point, and in some ways the most important thing; making something visually compelling doesn't necessarily make it better. Sure, pretty is nice, but does it "convert"?
- What navigational arrangement makes sense to the user?
- What graphics will add to the users experience and which are superfluous eye candy?
- Which bells and whistles support my communications goals and which only showcase my skills at making bells and whistles?
It's sometimes a challenge to keep our egos at bay, but if we consider the needs of our client (our department or organization at Case) as well as the end user and put those foremost in our thoughts, we'll generally produce more successful sites.Comment by Heidi Cool — January 22, 2007 @6:07 pm
Comment by Brandon — April 6, 2007 @5:55 pm
Comment by Brandon — April 21, 2007 @10:49 pm
Comment by Heidi Cool — April 23, 2007 @12:25 pm
Comment by Ryan Johnston — April 23, 2007 @3:39 pm
Comment by Brad — April 28, 2007 @6:28 pm
Comment by Helen Walker — June 19, 2007 @8:38 am
Comment by Heidi Cool — June 20, 2007 @1:23 pm
Comment by Eric Graham — June 24, 2007 @11:30 pm
Teh bit of text wll not then be shown in the style less view as it will be seen as being part of the code in the
tag so the text will not be shown to the viewer. Stupid and simple mistakes like this can kill a page off both to a search engine and to the person reading it on text only view.. She obviously knows her stuff but so should any one who is writing code for a website. I do try to validate all code on all the sites I make and I would say it is very good practice to validate and not to do it just as a badge to show off that you have taken time to write your website code. The client needing the site made is not always right( in fact they are usually dumb to what is really needed on a website)
Comment by Web Design UK - Barry Mitchell — November 12, 2007 @10:06 am
Comment by Dollar Demon - Make money online — November 18, 2007 @4:59 am
Comment by Mp4 Rob — November 27, 2007 @4:49 pm