The University of Texas at Austin- What Starts Here Changes the World
Services Navigation


The Final Report - Usability Findings & Recommendations

Now it is time to compile your usability data, analyze it and write your recommendations. I recommend entering all of your entrance, exit and task information into an excel spreadsheet. If you don't have MS Word and Excel, you can download free viewers for Microsoft Excel and Microsoft Word.

Sample spreadsheet of raw usability data (microsoft excel)

Sample Usability Recommendations Report (microsoft word)

Look for trends in comments and task completion. Document the impact the data shows on effectiveness, efficiency, time on tasks, errors and satisfaction. Group your recommendations in severity/priority order.

  • 1st Priority - must be fixed, brick wall
  • 2nd Priority - would be good to fix, but can wait
  • 3rd Priority - okay as is, could be improved

Don't just critique and point out what is wrong. Suggest a solution or remedy for each problem. Your suggestions could be a change in the design or the content.

If you sense that the application owners/developers will be resistant to suggestions, consider sharing the usability recommendations with them individually and in draft form, then when it comes to the formal meeting where you review the recommendations, there are no surprises.

Another key to helping developers/designers truly understand the usability issues is to actually let them observe the usability testing process. This works best when the develop/designer is behind a one way mirror (so when they scream and cry and state that "any idiot would know what to do", your innocent test subject won't have to be intimidated by them)! Since most offices don't have usability testing rooms with one way mirrors, other methods for letting them see include:

  1. audio recording the sessions and letting them listen
  2. video taping the sessions and letting them watch
  3. live webcast the sessions and let them watch from another room
  4. make sure your test facilitator/notetakers are people that your developers/designers will always believe
  5. in the rarest of cases, allow your develop/designer in the room while testing (but you may have to tie them in a chair and put duct tape over their mouth). I do not recommend this option.

In my experience, I've yet to make use of the audio recording or video taping we've done. I now just pick well trusted facilitators and note takers and pre-review my recommendations with the designers/developers before making formal recommendations.

 


  Updated 2006 July 26
  Comments to TeamWeb