1. Describe the website or interface that you want to test.
WebPAC Pro enhancements to library catalog
2. Is it an existing site or a new site?
Revisions to an existing site
3. For testing purposes, will you have an "interactive" website available or will we be using "mock-up" designs or paper prototypes?
We have a test server but we may want to test with paper protoypes first.
4. What is the objective or purpose of the testing? What do you want to learn from the testing?
Determine if users can find information efficiently and understand what they are seeing.
5. What is the audience for your site?
OSU students, faculty, staff; community; other libraries
6. Who do you recommend for test participants?
Undergraduate students, graduate students and faculty
7. What specific tasks do you want to test? BE SPECIFIC!
Under development
8. Can staff from your group assist with any of the following?
- recruit test participants - yes
- screen test participants -- yes
- schedule test participants, test location, facilitator, and observer -- yes
- serve as facilitators for testing (indicate # of individuals) -- yes
- serve as observers for testing (indicate # of individuals) -- yes
9. What is the development schedule for your site? When do you need results of usability testing to incorporate into your development?
By May 31
10. Do you expect to report/publish the findings (does the testing require IRB approval)?
???
11. Will "impromptu/hallway" testing be appropriate or are you expecting more formal testing?
More formal testing
After testing is completed, the OSU Libraries Usability Team appreciates your answers to the following questions:
12. Was the testing done by the Usability Team helpful to you?
13. What changes will you make to incorporate the results of this testing? What is your timeframe for implementing these changes?
14. How will you communicate these changes to your users and the OSU Libraries faculty and staff?
