• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Usability Testing: analyzing data
 

Usability Testing: analyzing data

on

  • 469 views

 

Statistics

Views

Total Views
469
Views on SlideShare
469
Embed Views
0

Actions

Likes
0
Downloads
2
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    Usability Testing: analyzing data Usability Testing: analyzing data Presentation Transcript

    • • Compile • Summarize data • Analyze data • Develop recommendations • Produce the final reportWednesday, March 28, 12
    • Data AnalysisWednesday, March 28, 12
    • next 2 weeks:Wednesday, March 28, 12
    • Wednesday, March 28, 12
    • Wednesday, March 28, 12
    • Step 1: CompileWednesday, March 28, 12
    • Wednesday, March 28, 12
    • Get it into a pile.Wednesday, March 28, 12
    • Get your piles sorted.Wednesday, March 28, 12
    • Ideally:Wednesday, March 28, 12
    • compile as you test.Wednesday, March 28, 12
    • further test the test.Wednesday, March 28, 12
    • keep the data legible.Wednesday, March 28, 12
    • • Type handwritten notes • Verify data captures • Back up filesWednesday, March 28, 12
    • Organize raw data.Wednesday, March 28, 12
    • Do whatever it takes to get it done.Wednesday, March 28, 12
    • • lists • tallies • matrices • stories • structure models • flow diagramsWednesday, March 28, 12
    • Wednesday, March 28, 12
    • Wednesday, March 28, 12
    • Wednesday, March 28, 12
    • Wednesday, March 28, 12
    • Goal:Wednesday, March 28, 12
    • Wednesday, March 28, 12
    • Step 2: summarizeWednesday, March 28, 12
    • 1. task accuracyWednesday, March 28, 12
    • number of errors made per taskWednesday, March 28, 12
    • • categorize errors by type • ommission • commissionWednesday, March 28, 12
    • # of participants who performed: • successfully • successfully but with some assistance • assistance types, tasks, productsWednesday, March 28, 12
    • Vital Statistics:Wednesday, March 28, 12
    • % performing successfully, including those who needed assistance • regardless of time limits • regardless of assistance neededWednesday, March 28, 12
    • If this percentage is very low, you’ve got a serious problem.Wednesday, March 28, 12
    • % performing successfully • including those who corrected errorsWednesday, March 28, 12
    • % performing successfully within benchmark • indicative of efficiencyWednesday, March 28, 12
    • 2. task timingsWednesday, March 28, 12
    • Wednesday, March 28, 12
    • summarize preference dataWednesday, March 28, 12
    • Limited choice questions: • Sum by choice • Chart trendsWednesday, March 28, 12
    • Free-form questions: • Group into meaningful categories • Ex: particular screen, doc section, etc.Wednesday, March 28, 12
    • Summarize other measures • Unnecessary returns to main navigation • Number/type of hints and prompts • Times site map was accessed • Points of hesitation (and for how long)Wednesday, March 28, 12
    • Summarize by Group/VersionWednesday, March 28, 12
    • (see pages 255 - 259)Wednesday, March 28, 12
    • 3: analyze dataWednesday, March 28, 12
    • What didn’t succeed?Wednesday, March 28, 12
    • Wednesday, March 28, 12
    • What were the difficulties?Wednesday, March 28, 12
    • What were the error sources?Wednesday, March 28, 12
    • Prioritize problems by severityWednesday, March 28, 12
    • Severity descriptions & definitions: p. 262Wednesday, March 28, 12