World Usability Day

wudLogo2006.gif

The evening started off with some light snacks in a conference room off the library, which I believe is part of the new construction gong on at the Cleveland Museum of Art. Very nice location.

Also interesting was the amount of people from Kent State that I went to school with, including my advisor! It was just like old times... Hard to believe those 4 years went by so fast. I digress.

The evening was was non-traditional with different areas designated for certain talks. 10 minute reminders were given for you to change locations and join different discussions.

The most appealing was a discussion by Chris Braunsdorf(sp?) from Progressive Insurance, discussing usability with Web 2.0. Since it was more free-form, here are just some bullet-point take-away's from the talk.

  • A Step Backward: One point was made that I hadn't considered before, how the web was a step backwards in terms human-computer interaction and usability. We had gone from the likes of DOS to Windows based operating systems. Things were becoming more usable and dynamic, then when the web appeared and we were thrown back to single flat pages with long menus of pages. Just now are we getting back to the more dynamic and interactive behaviors that we've been used to on computers, on the web.

  • Follow the leader: It's obvious that companies like Google, Yahoo ! and Flickr have all taken the lead using Web 2.0 technologies, and for us smaller guys, we often have to just follow the lead when it comes to figuring out how to create sites using these interactive web technologies. How people have come to learn how to use these sites is the same understanding and expectation they'll bring to your site.

    The example provided was that of the Delete key on the keyboard, and how Apple proved through usability studies that it was most efficient on the left side. However Microsoft placed it on the right (presumably without any studies as to why), and that's the way it stayed. So what's always the BEST may not be what works in the long run.

  • Better Use of Space: It's easily understood just how valuable screen space is when dealing with the web. (scrolling=bad). But using new dynamic technologies such as Flash or AJAX can prove to be a valuable space saver. Now with the ability to right-click with web-application specific options, dragging & dropping, roll-overs, and pop-ups that aren't really pop-ups, the options for space-saving is greatly increased (but then so does the challenge grow for developing a more usable site)

  • Platforms: Of course the discussion had to lead to Flash versus AJAX. While I have never programmed in either environment, from this discussion I've gleaned that each has their highs and lows. AJAX (a favorite of Google) is open source and Java-based. However it carries a heavier "weight" as compared to the proprietary Flash. You can get more info here, including a list of alternatives (though it's an AJAX site).

  • Standards: Chris kept mentioning "standards" throughout our discussion, so I decided to ask him if he'd seen any of these standards published anywhere. He hadn't, but he was able to point us to a great resource over at Yahoo! Developer Network, the Design Pattern Library. In case you're curious at what a "pattern" is (from IAWiki):

    Patterns are optimal solutions to common problems. As common problems are tossed around a community and are resolved, common solutions often spontaneously emerge. Eventually, the best of these rise above the din and self-identify and become refined until they reach the status of a Design Pattern.

    He equated the lack of documentation of these standards as an example of the shoemaker's son going shoe-less.

The rest of the night was spent seeing what my former colleagues were up to with the Usability lab down at Kent State. This was just getting completed when I was attending classes there. It was pretty amazing to see what they could do with eye-tracking using their Tobii device. That along with what they can do within their controlled lab environment is pretty impressive. You can read more about it at the Kent Stater Online.
upa_logo.gif
For more information on World Usability Day or Usability in General, check out the Usability Professionals' Association (http://www.upassoc.org/).

Trackbacks

Trackback URL for this entry is: http://blog.case.edu/roger.zender/mt-tb.cgi/11330

Comments

Thanks very much for the nice comments about my talk on usability and Web 2.0 at the World Usability Day event a few months ago. I'm glad you found the discussion useful. Just wanted to clarify a couple of items in your writeup:


  1. The Apple/Microsoft example actually dealt with the Cancel button as in pages that have Submit | Cancel at the bottom of the page. Apple has the Cancel button on the left and action/default button goes on the right, while MS does the opposite. You can read their respective user interface guidelines on dialog boxes here and here. On the web, you tend to find a mixture of both depending on which convention the designer chooses to follow.

  2. Ajax is actually JavaScript and XML based. The "Ajax" name was coined by Adaptive Path partner Jesse James Garrett and stands for "Asynchronous JavaScript and XML."

Thanks very much for the nice comments about my presentation on usability and Web 2.0 at the Cleveland World Usability Day event a few months back. I'm glad you found the discussion useful.

I just wanted to clarify a couple of items in your post:

  1. The Apple/Microsoft example was actually about the Cancel button in dialog boxes. You can read more here and here about their respective user interface guidelines on this issue. On the web, you tend to see a mix of these standards depending on which convention the web designer chooses to follow.
  2. AJAX is JavaScript and XML-based. The term "AJAX" was coined by Jesse James Garrett from Adaptive Path, and stands for "Asynchronous JavaScript and XML."

Post a comment





If you have entered an email address in the box, clicking this checkbox will subscribe your email address to this entry so that you are notified if any updates or additional comments occur on the entry.