December 22, 2005
Usable vs. Useful
imagined by: James Mathias
On today’s Internet the term usability is flooding web design firms, design freelancers and standards Blogs alike. Usability is an important task in developing web-sites and web based software applications, however, I believe that the real term or keyword we should be focusing on is not “usability” but “usefulness”. You can have a useable web-site or application but if it’s not useful it’s not going to give the user much benefit or value. In the long-term, big picture scheme of things; the application or web-site, will fail its audience.
Usability allows developers to make applications and web-sites usable to a variety of possible end users. Usability allows a blind or other differently-abled individual to access, read and/or view our content and features on their terms not ours. Without usability we cannot reach the same amount of people as when we utilize its core function. Without it we’ll be pigeon-holing or type-casting ourselves for no reason aside from inept laziness or any of the other classic excuses we use to keep ourselves from learning and implementing something that hurts no one and helps everyone. I’m an enormous believer in the ideal of usability and I try and make all my projects maintain and utilize a high level of usability. That’s all we, as developers need to do. Just try.
Usability is a fantastic and–I believe–necessary part of any project’s development and in the long run it makes our projects so much better, but without coupling usability with usefulness you’re short changing yourself, your clients and both your user groups.
Usefulness directly correlates to the content and information your web-site or application produces, if you produce nothing of use, your usability matters not. The best way to make your usable web-site useful is to tone it down, make it simpler, and increase the features worth by making them more useful and less specific. Think from the point of view of the average user not the average developer. Increase your usefulness by making examples and giving instruction that is inline but unobtrusive (it’s there if they need it). Tell people how to use the web-site or application, don’t assume your audiences level of expertise and make it useful to all possible users.
Stating what may seem obvious to you or other developers will be not obvious and useful to another user. Build software and applications as if you personally were going to depend on them to get your job done daily, make them useful and usable.
Usefulness should be on your to do list, usability should be there too, but just under usefulness, or better yet on the same line, as if they are the same thing. Thinking of it in those terms your products and services will increase in value and usefulness as well as usability and accessibility.
I sincerely hope you found this useful.
Usable vs. Useful
- 12.22.05 at 6:19pmthrown down:
- James Mathiasimagined by:
- Developmentally Ablestored in:
- 245 peeps, 4 of whom commentedenjoyed by:
More of the Same
10 recent “Developmentally Able”
- Big Business Bulli…
⇒ on: Aug. 26, 2007 - 6pins has launched…
⇒ on: Apr. 19, 2007 - Steal Ma.gnolia
⇒ on: Apr. 4, 2007 - Getting Logitech…
⇒ on: Feb. 3, 2007 - Can I get that ico…
⇒ on: Dec. 21, 2006
- Help Wanted
⇒ on: Dec. 6, 2006 - 13 Applications of…
⇒ on: Nov. 16, 2006 - Will The Real Styl…
⇒ on: Jul. 9, 2006 - Mr. Alan Jax is an…
⇒ on: Jul. 9, 2006 - Links to Me Will b…
⇒ on: Jun. 27, 2006





your comments
add comment
4 comments
Dec. 22, 2005 (10:17pm) [#1]
Kennedy
Great post!
I’m really enjoying your posts of late. Fantastic!
Dec. 22, 2005 (10:24pm) [#2]
James Mathias
Thanks Kennedy! I appreciate it.
Dec. 22, 2005 (11:12pm) [#3]
Chris Griego
“Usability allows a blind or other differently-abled individual to access, read and/or view our content and features on their terms not ours.”
I have to disagree, with the understanding that this is probably more of an opinion or personal preference. Accessibility and usability tend to mingle, but I like to define the two seperately. Accessibility is being able to get the information at all, if you can get to the content, it’s accessible (which is on an element basis (paragraph, image, Flash embed), not page/site basis). I define usability as being able to do something with that information once accessed. What that does for me is it sets accessibility as more of a science (must do’s and must not do’s) and usability more of an artform.
Usefulness on top of that is another aspect, being defined as is the information even worth using? I file all the portals popping up, Ajax or not, under not useful even though some of the Ajax ones are more usable.
Persuadability is another aspect in itself, one that is often over-looked by web developers or “left to the marketing department.”
This forms in my mind a Hierarchy of User Needs, alluding to Maslow’s Hierarchy. I wish I could say I was the first to think of that, but I discovered that week that someone has beat me to it.
Dec. 23, 2005 (10:10pm) [#4]
James Mathias
I see your point Chris, but I don’t agree 100%, which is odd seeing how we normally see eye to eye on most things.