Endorsements
"Jennifer did an excellent job leading the usability test effort for the feature for which I am currently the development lead. She was well-organized, professional, and enthusiastic about ensuring the success of our feature."
- Elise Matefy, Principal Software Engineer, RSA Security
September 5, 2007
Usability Reporting
My Philosophy
I write usability reports in three basic formats: (1) a formal report; (2) a visual presentation page by page, calling out what users apreciated and where they had trouble; or (3) an informal list of improvements and their potential for impact upon the user experience.
The type of report which follows any usability test should be determeined by the needs of the project. If the usability testing is done on a project in it's early stages, with available time, and the desire to track changes and user experience over time, then the project should be given a formal usability report. If on the other hand time is short and the product needs to ship, an informal list of improvements can be both effective and economic. If stakeholders and decision makers are geographically dispersed, a visual report with call-outs may be most appropriate.
Samples
Excerpt of a report with screenshots and call-outs
Excerpt of a formal usability report
Excerpt of a report with prioritization and issue tracking