rapid turnaround usability testing: not just a pipe dream

Download Rapid turnaround usability testing: not just a pipe dream

Post on 27-Jan-2015




5 download

Embed Size (px)


This was presented at the IA Summit in Phoenix, AZ. Talk Abstract: Is your usability testing always attached to a design project? And does it require a fair amount of planning, time, and resources to accomplish? Time for the designer to come up with his business questions and create a few prototypes; time for the researcher to develop an applicable discussion guide; time for the moderator to conduct the interviews, create and review the transcripts, make sense of it all, and finally come out with some solid findings and recommendations? If so, you’re in the norm. But there’s a better way that can enable you to get more insight quicker, cheaper, and with fewer people and headaches. This talk will describe how, with a little planning and a few innovative techniques, you can conduct regular, fast-turnaround usability interviews with a shoestring staff and budget. You can provide timely feedback to designers, uncover surprising problems with your site, and capture rich customer quotes – and do this week after week. By scheduling regular customer interviews regardless of the project timing, you can start to condition your designers and project managers to expect to be able to get customer input whenever they want. And exploring customers’ “native tasks” can give insights about parts of the site you and your designers would never even think to ask about. Finally, the unique debrief methodology will greatly simplify the analysis process, enabling you to quickly produce Findings and Recommendations that will be already bought-into by the team. This talk is aimed at IA’s, Usability professionals, and designers who want to learn how to get more customer input into their designs without the hassle, time, and expense of traditional usability interviews. You will walk away from this talk with a practical plan-of-action and some new techniques for conducting rapid-turnaround usability testing.



2. Over the last two years, weve conducted 88 usability tests together while doing rapid design iterations andweve never met before now! 3. Q. How do you getmore customer inputinto your designswithout the time andexpense oftraditional usabilitytesting? 4. A. Rapid-turnaroundUsability Testing 5. RITE Usability Testing ee R evis e R evis eTestotyp Testotyp Test Prot Prot 6. How do you make design decisions based on only testing 1 person? 7. Process OverviewDene ScopeDene TasksPrototype2 week iteration Conduct TestingDebrief Report/Present FindingsRevise Prototype 8. Key to SuccessAttendance of product decision makers during testing! 9. A different way to think about usability testing 10. Wheres the rapid in the process?Dene Scope Dene Tasks Prototype2 week iteration Conduct Testing 3 DAYS!Debrief Report/Present FindingsRevise Prototype 11. Benets Team stays on the same page -- no working in a vacuum! Rapid feedback from end users Produces rapid ndings and recommendations Team consensus on product changes Saves time and money Ingrains usability testing into the design and development process 12. Interview-based Tasks 13. Script 14. Improv Testing Process1. Interview participant about how they use theproduct. 2. Use the answers given in the interview tocreate tasks on the y.When in doubt just ask, what was the last thing you did when you used this product? Can you show me? 15. Benets Learn users true intent Gain the insight and feedback that truly matters No need to conduct an in-depth task analysis The unexpected -- enjoy the ride to enlightenment! 16. Observer Debrieng 17. Why debrief?photo by agit8 18. How to debrief Do nothing Informal discussion Afnity diagramming. 19. Structured Quote/Observation Implication: H2, W4, Wif Round-robin or lead + additions After every 3-6 respondents. 20. BenetsGeneralizations Jumping to solutions I'm right you're wrong. photo by subboard.com 21. BenetsGeneralizations Jumping to solutions I'm right you're wrongphoto by subboard.comDifferent perspective ootb thinking Immediate "transcript" and importance. 22. http://www.apw.cnyric.org/teacherpage3.cfm?teacher=438 23. Report Findings fast-turnaround no surprises recommendations, not just problem speeds up start of next round of designs. 24. Gotchas! 25. Gotchas! Not getting the team involved Not nding a moderator comfortable with interview-based tasks Not sticking to the structure in the debrief. 26. Go for it.photo by nike 27. Thank You!