This document describes a method for rapid-turnaround usability testing that allows product teams to get customer feedback more quickly without the time and expense of traditional usability testing. Key aspects of the method include conducting short usability tests with 1-3 participants over 3 days, improvising tasks based on interviews with participants, debriefing with the product team immediately after each test, and revising prototypes based on findings within 2 weeks to start the next iteration. The rapid approach aims to keep product teams and decision makers aligned through involvement in testing and debriefing, and provides quick feedback to guide design iterations.

1. RAPID-
TURNAROUND
USABILITY TESTING:
NOT JUST
A PIPE DREAM
IA Summit 2010
Holly Phillips & Kyle Soucy

2. Over the last two years, we’ve
conducted 88 usability tests
together while doing rapid
design iterations and…
we’ve never met before now!

3. Q. How do you get
more customer input
into your designs
without the time and
expense of
traditional usability
testing?

4. A. Rapid-turnaround
Usability Testing

5. RITE Usability Testing
e e
R evis e R evis e
Test otyp Test otyp Test
Prot Prot

6. How do you make
design decisions
based on only testing
1 person?

7. Process Overview
Define Scope Define Tasks Prototype
2 week iteration Conduct Testing
Debrief
Report/Present Findings
Revise Prototype

8. Key to Success…
Attendance of product
decision makers during testing!

9. A different way to think about
usability testing…

10. Where’s the “rapid” in the process?
Define Scope Define Tasks Prototype
2 week iteration Conduct Testing
3 DAYS!
Debrief
Report/Present Findings
Revise Prototype

11. Benefits
• Team stays on the same page -- no working in
a vacuum!
• Rapid feedback from end users
• Produces rapid findings 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” Process
1. Interview participant about how they use the
product.
2. Use the answers given in the interview to
create tasks on the fly.
When in doubt just ask, “what was the last thing you did
when you used this product? Can you show me?”

15. Benefits
• 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 Debriefing

17. Why debrief?
photo by agit8

19. How to debrief
• Do nothing
• Informal discussion
• Affinity diagramming.

20. • Structured
• Quote/Observation
• Implication: H2, W4, Wif
• Round-robin or lead + additions
• After every 3-6 respondents.

21. Benefits
Generalizations
Jumping to solutions
I'm right you're wrong.
photo by subboard.com

22. Benefits
Generalizations
Jumping to solutions
I'm right you're wrong
photo by subboard.com
Different perspective
ootb thinking
Immediate "transcript" and importance.

23. http://www.apw.cnyric.org/teacherpage3.cfm?teacher=438

24. Report Findings
• fast-turnaround
• no surprises
• recommendations, not just problem
• speeds up start of next round of designs.

25. Gotchas!

26. Gotchas!
• Not getting the team involved
• Not finding a moderator comfortable with
interview-based tasks
• Not sticking to the structure in the debrief.

27. Go for it.
photo by nike

28. Thank You!