1. Usability Testing:Understanding End-Users through Observation Frank J. Garofalo, UI Engineer

2. Outline What is Usability Testing? When is it most beneficial? Who can be involved? Who can it be most beneficial to? How is it accomplished? Format Cost Factors

3. What is Usability Testing? Observing an end-user perform scenario-based tasks Participants will typically be asked to follow the “think-aloud protocol” which asks the participant to say whatever they are looking at, thinking, doing, and feeling at each moment. Typically performed in a usability testing lab setting (controlled environment), however it can be performed remotely.

4. What is Usability Testing? Observing an end-user perform scenario-based tasks Participants will typically be asked to follow the “think-aloud protocol” which asks the participant to say whatever they are looking at, thinking, doing, and feeling at each moment. Typically performed in a usability testing lab setting (controlled environment), however it can be performed remotely.

5. What is Usability Testing? The key stakeholders of an application/system to observe actual end-users interacting with the application/system (can be a prototype, developmental iteration, production-ready, and/or pre-existing). Data collected can include: subjective-anecdotal feedback success rates task times error rates subjective-satisfaction ratings

6. When can it be most beneficial? Early stages of project requirements gathering; Early stages of project design; Throughout development; Existing applications / systems

7. Who can be involved? End-users Key Stakeholders Project Managers / Consultants Technical Leads Developers UI Engineer

8. Who can it be most beneficial to? End-users Key Stakeholders Project Managers / Consultants Technical Leads Developers

9. How is it accomplished? Meeting to determine: application / system to test specific tasks to test who the target end-users are to test timeline for conducting usability testing (pre & post) Draft scenario-based tasks for testing Recruit & schedule testing participants Run through of scenarios with actual testing equipment/systems/applications

10. How is it accomplished? Invite observers for testing (stakeholders, PM, TL, Dev Team, etc.) Conduct Usability Testing with observers Testing debrief with all observers Analysis & report deliverable, if needed

11. Format - Overall Planning & Preparation Testing Debrief & Data Analysis

12. Format – Testing with 3 participants Morning Set-up 8:00 – 8:30 am Participant 1 8:30 – 9:30 am Break (for Observers) 9:30 – 9:45 am Participant 2 9:45 – 10:45 am Break (for Observers) 10:45 – 11:00 am Participant 3 11:00 – 12:00 pm Observer Debrief Session (Working Lunch) 12:00 – 1:00 pm

13. Cost Factors Potential Budget: High Depends on the number of individuals involved and the number of observers