This document provides guidance on conducting usability testing to improve product design. It recommends: 1) Conducting speed tests with users to understand behaviors and issues; 2) Building a tester community from real users to provide feedback; 3) Testing frequently with small groups to incorporate feedback early. It outlines when and what to test, how to prepare by determining goals and tasks. It provides a testing protocol, including introducing yourself, having users think aloud, and asking questions without justifying designs. The key is to listen, take notes on positive and negative experiences, and use the insights to reinforce successes and address problems.

1. Fresh insights from UX community to improve your product usability
SPEED TESTING

2. Watching people try to use what you create
Understand behaviors and what’s wrong
ANOTHER WAY TO GET FEEDBACK

3. Build your own tester community with your real users
and organize testing sessions
EVERY TEST COUNTS

4. CONSTANTLY, when you get the idea,
Test frequently, with few users (up to 10)
WHEN DO YOU NEED USABILITY TESTING ?

5. WHAT YOU CAN TEST
• Your existing product
• Alpha, Beta
• Portions of your product
• A / B Versions
• Low or high fidelity Wireframes
• Statics Mockups
• Interactive Prototype
• Paper Prototype
• A scenario sketch
• Competitors’ products…

6. BE READY
• Which part of the user journey do you want to test
• WHAT do you want to know? Prepare tasks and scenarios
• HOW do you want to execute the element for the test?
• PROPS Which additional items do you need?
laptop, tablet, camera, dictaphone.. BRING YOUR OWN!
• WHO will be the tester? Which role do you need to execute the test?
• WHO will be the Test Admin?

7. TESTING PROTOCOLE
• PRESENT YOURSELF What’s your job in your startup?
• Don’t tell your company name if you want to test your brand
awareness
• Ask the tester to constantly think aloud, and be honest
• GIVE INSTRUCTIONS with an accurate context
Ex: « You are (persona 1) in a (place) at (hour) and are looking for
(specific need), tell me what do you do…
• ASK QUESTIONS on why she did something you don’t expected

8. If the tester is curious, debate about it after the test
DON’T JUSTIFY YOUR DESIGN
ASK QUESTIONS, LISTEN AND DON’T ANSWER

9. LISTEN, TAKE NOTES
You can print your screens and annotate on it

10. TEST ASSIGNMENT, TEST CONTEXT
TEST
USERS
For each activity, make a note of what the most positive and most negative experience is.
EVALUATION
See which positive and negative experiences repeatedly appear.
Think how you can reinforce the positive and adapt the negative.
ACTIVITY
TOUCH POINT
TEMPLATES CAN HELP

11. AND THEN?
No big report, email the whole team with key lesson-learnt of the tests
You can sort feedbacks in a tool like Trello, Slack, or Github
PROBLEMS YOU CAN
FIND WITH JUST A FEW
TEST PARTICIPANT
PROBLEMS YOU NEED
TO FOCUS ON

12. It’s great for telling you what you did wrong
Remember that users don’t know what they want
DON’T TAKE DECISIONS ONLY BASED
ON USER FEEDBACK

13. • Steve Krug, «Don’t Make Me Think »
• Jeff Gothelf, « Lean UX »
• UXPIN toolkit
• Service design toolkit
QUICK REFERENCES

14. @UXCOOP @NoemiePrin