Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Usability Testing: Understanding End-Users through Observation

  • Login to see the comments

Usability Testing: Understanding End-Users through Observation

  1. 1. Usability Testing:Understanding End-Users through Observation<br />Frank J. Garofalo, UI Engineer<br />
  2. 2. Outline<br />What is Usability Testing?<br />When is it most beneficial?<br />Who can be involved?<br />Who can it be most beneficial to?<br />How is it accomplished?<br />Format<br />Cost Factors<br />
  3. 3. What is Usability Testing?<br />Observing an end-user perform scenario-based tasks<br />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. <br />Typically performed in a usability testing lab setting (controlled environment), however it can be performed remotely.<br />
  4. 4. What is Usability Testing?<br />Observing an end-user perform scenario-based tasks<br />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. <br />Typically performed in a usability testing lab setting (controlled environment), however it can be performed remotely.<br />
  5. 5. What is Usability Testing?<br />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).<br />Data collected can include:<br />subjective-anecdotal feedback<br />success rates<br />task times<br />error rates<br />subjective-satisfaction ratings<br />
  6. 6. When can it be most beneficial?<br />Early stages of project requirements gathering;<br />Early stages of project design;<br />Throughout development;<br />Existing applications / systems<br />
  7. 7. Who can be involved?<br />End-users<br />Key Stakeholders<br />Project Managers / Consultants<br />Technical Leads<br />Developers<br />UI Engineer<br />
  8. 8. Who can it be most beneficial to?<br />End-users<br />Key Stakeholders<br />Project Managers / Consultants<br />Technical Leads<br />Developers<br />
  9. 9. How is it accomplished?<br />Meeting to determine: <br />application / system to test<br />specific tasks to test<br />who the target end-users are to test<br />timeline for conducting usability testing (pre & post)<br />Draft scenario-based tasks for testing<br />Recruit & schedule testing participants<br />Run through of scenarios with actual testing equipment/systems/applications<br />
  10. 10. How is it accomplished? <br />Invite observers for testing (stakeholders, PM, TL, Dev Team, etc.)<br />Conduct Usability Testing with observers<br />Testing debrief with all observers<br />Analysis & report deliverable, if needed<br />
  11. 11. Format - Overall<br />Planning & Preparation<br />Testing<br />Debrief & Data Analysis<br />
  12. 12. Format – Testing with 3 participants<br />Morning Set-up<br />8:00 – 8:30 am<br />Participant 1<br />8:30 – 9:30 am<br />Break (for Observers)<br />9:30 – 9:45 am<br />Participant 2<br />9:45 – 10:45 am<br />Break (for Observers)<br />10:45 – 11:00 am<br />Participant 3<br />11:00 – 12:00 pm<br />Observer Debrief Session (Working Lunch)<br />12:00 – 1:00 pm<br />
  13. 13. Cost Factors<br />Potential Budget:<br />High<br />Depends on the number of individuals involved and the number of observers<br />

×