usability

							Information Architecture
Monday, November 1 2010
Information Architecture
    Usability should be measured to make information easier to learn, more
       satisfying and more efficient for the user.
    When measuring Usability, close attention should be paid to the ease of
       learning, memorability, and error frequency.
    Usability can be tested through observation. Meaning, have users attempt to
       do several tasks while observers watch and take notes of their progress.
       It doesn’t have to be a finished product, it would actually be more helpful
       if done at several stages through the development progress.
    It may help to set goals during the usability tests to guide the observers to
         obtain the information that is required. Common goals include time,
         accuracy, satisfaction, and overall success within different areas of the
         site.




Information Architecture
Information Architecture

     There are two types of usability metrics that can be captured during a
         usability test.
     These metrics include:
     Performance data (what actually happened)
     Preference data (what participants thought)
     In more formal, rigorous usability tests, we tend to rely more on performance
         data than preference data.




Information Architecture
Information Architecture




Information Architecture
Information Architecture




Information Architecture
Information Architecture

 Conducting a Usability Study

   1. Starts with the Client
   2. Kickoff
   3. Define purpose/vision for of the site.
   4. Task analysis, scenarios, and measurables.




Information Architecture
Information Architecture

 Task Analysis, Scenarios, and Measurables

   A. Speed Kills
       Speed in which site/page loads.
       Speed in which critical tasks are completed.




Information Architecture
Information Architecture

 Task Analysis, Scenarios, and Measurables

       Understanding
       Intuitiveness
       Mistakes
       Dead-ends
       Confusion



Information Architecture
Information Architecture

 Recruiting Participants

       Demographic Study
       Age, Gender, Race, Ethnicity
       Education, Income, Occupation
       Computer Expertise
        Pre-existing Knowledge of Industry, Organization



Information Architecture
Information Architecture

 Recruiting Participants

       Advertise
       Contract a Marketing Group
       Contract, Release Forms
       Pay
       Goodies



Information Architecture
Information Architecture

 Testing Facility

        Where could we find one of these? Hmm . . .
        Computer, Mouse, Screen - Think about it.
        OS Version, Browser Version, etc.
        Atmospheric Conditions
        Amenities



Information Architecture
Information Architecture

 Testing Equipment and Personnel

       Computer, Mouse, Screen, Internet Connection
       Internet Connection
       Internet Connection
       Test Your Environment, First!




Information Architecture
Information Architecture

 Testing Equipment and Personnel

       Videotaping - Release Forms
       Screen Capturing Software
       Time Recording Device
       Testers, Observers, Roles




Information Architecture
Information Architecture

 Testing Day

       Welcome. And I mean it.
       Describe Purpose of Study
       Describe Test Facilitator’s Role
       Test Participant’s Role




Information Architecture
Information Architecture

 The Test

       Begin on time.
       End on time.
       Be clear. Prepare your participant.
       Hand’s off.




Information Architecture
Information Architecture

 Questions, Scenarios, Etc.

       What are your questions?
       What are your expectations?
       How will you measure performance?
       Who is recording this information?




Information Architecture
Information Architecture

 Exit Interview

        Follow up questions?
        Different tester? Might be a good idea.
        Recording exit interview.




Information Architecture