home | books | articles | gleanings | case studies | hire
other sites: widgetopia | blueprints for the web | metafooder


 


 


« interesting paper | main | more porn »

testing tips

My flash-usability research has led me to Girlzilla's Usability Testing Tips. Even if you couldn't do usability testing, if you did the first four tasks you'd probably improve your product.


  1. Define Business Goals


  2. Determine the User's Goals


  3. Identify Your Users


  4. Create Usability Tasks



If you create a list of tasks (#4) based on the user and business goals, then go through them yourself with #3, your target user, in mind you will probably quickly spot many usability problems....


Also interesting was their "Flash Usability Tips," though the reason it interested me was that it wasn't much different than most web usability lists. I know there must be usability challenges unique to Flash-- anyone want to share a few?

Posted at August 06, 2001 01:10 PM


Comments

 

here's a site with a few.

Posted by mrs. sarrazin of des moines at August 6, 2001 01:44 PM


~~~

I was hoping some EH readers have had thoughts along these lines...

Posted by Adam Greenfield at August 6, 2001 11:52 PM


~~~

Adam -- I would suggest taking a couple steps back from storyboarding and set the ideas, concepts, context, and flat information we want to provide. From this point build a functional flow of the information, which is essentially an outline of how the the components fit together and look at it from the perspective of a user (or better yet have a user walk-through the flow). The functional flow will help us establish logical content steps and find holes in the logical flow, which is done by having the user walk through the flow. The next step is to storyboard the functional flows where objects/images/animations are used to augment words (in some cases replace words) to help explain concepts and ideas to assist the user's understanding. The storyboarding is when we can use Flash to put very rough concept screens together or build wireframe layouts of the screens. Get user feedback at this point too before we begin digging deeper. After making the modifications to the functional model (we can return to build traditional pages from this information at a later point if we need to) and storyboard. Now we can flesh out the graphics, transitions, scripting, and animation.

Posted by vanderwal at August 7, 2001 05:54 AM


~~~

Come to think of it, there's something appealing about the image of hordes of IAs and usability testers sweeping down on a mass of users, testing their products with them, and disappearing before the users know what's hit them.... :-)

Posted by ralph at August 7, 2001 08:29 AM


~~~

As for usability, I suggest that you head to Flazoom.com and look in the Features section and the Usability section.

Posted by Chris MacGregor at August 8, 2001 11:43 AM


~~~

Oh, I'm spending quality time wiht the excellent flazoom. I'm also been turned on to quintus

Posted by Christina at August 8, 2001 01:59 PM


~~~



Post a comment
*Name:


*Email Address:


URL:


Remember me?

Comments:

bold italic underline link


posting can be slow; please wait a few seconds before hitting the button again.

The extra-fine print
wording stolen by the more-eloquent-than-I kottke
The bold, italics, and link buttons (and associated shortcut keys) only work in IE 5+ on the PC.
Hearty discussion and unpopular viewpoints are welcome, but please keep comments on-topic and *civil*. Flaming, trolling, and ass-kissing comments are discouraged and may be deleted.
All comments, suggestions, bug reports, etc. related to the comments system should be directed to me.


mail entry to a friend

Email this entry to:


Your email address:


Message (optional):




« interesting paper | main | more porn »

 

 

 

home | books | articles | gleanings | case studies | hire
other sites: widgetopia | blueprints for the web | metafooder