User testing workshop

Joe Dollar-Smirnov @fruitskin Director of UX, Red Badger & Lead Instructor, General Assembly

USER TESTING WORKSHOP


OBJECTIVES‣ Set up scenario ‣ Run a usability test ‣ Record feedback


APPROACH


WHAT DOES IT TAKE?‣ Bravery ‣ Humble Pie


TOOLS‣ Analytics Tools - GA, Web Trends, Optimal Workshop, Qubit, Crazy Egg,

Inspectlet the list goes on…

‣ Silverback, Camtasia, Screenflow

‣ Webcam, GoPro

‣ Paper, Pens and Empathy

USABILITY & USER TESTING

METHODS‣ Formal ‣ Guerilla (Cafe Test) ‣ Remote ‣ Unmoderated ‣ Face to Face








METHODS‣ Face-to-face

‣ This is the recommended method ‣ Provide users with tasks to complete on a prototype ‣ Encourage them to talk out loud as they move through

interactions ‣ Observe their actions


PREPARATION‣ Create task scenarios

‣ Should describe the task in a clear and unambiguous way ‣ Written in the user’s language (don’t use jargon) ‣ Don’t prompt the solution


PREPARATION‣ Create a discussion guide

‣ Should keep the participant talking (think aloud protocol) ‣ You are trying to learn without leading ‣ Keep the feedback flowing ‣ Prepare to note down reactions not just words ‣ “What would you expect” not “Do you like?”


OUTPUTS‣ Notes ‣ Video, Audio ‣ Usability Labs will have highly finished reports ‣ Unmoderated tests - data reports and recorded sessions ‣ Report good and bad, don’t make conclusions (yet), stick to

what you see ‣ SUS Score?


THE TESTS‣ QUIS - Questionnaire for User Interaction Satisfaction

‣ SUMI - Software Usability Measurement Inventory

‣ PSSUQ - Post-Study System Usability Questionnaire

‣ SUS - Software Usability Scale

‣ ASQ - After-Scenario Questionnaire

‣ ER - Expectation Ratings

‣ UME - Usability Magnitude Estimation

‣ SEQ - Single Ease Question

‣ SMEQ - Subjective Mental Effort


SUS‣ Since mid-80s by John Brooke ‣ Benchmark and Summative ‣ Self Described as “Quick and Dirty” ‣ Scale of 1 - 5 (strongly disagree - strongly agree)


THE QUESTIONS 1. I think that I would like to use this system frequently.

2. I found the system unnecessarily complex.

3. I thought the system was easy to use.

4. I think that I would need the support of a technical person to be able to use this system.

5. I found the various functions in this system were well integrated.

6. I thought there was too much inconsistency in this system.

7. I would imagine that most people would learn to use this system very quickly.

8. I found the system very cumbersome to use.

9. I felt very confident using the system.

10. I needed to learn a lot of things before I could get going with this system.

EXERCISE

TIMING

DELIVERABLE

KEY OBJECTIVE(S)

ACTIVITY

Write scenarios for your test that allows you to carry out usability testing.

Scenarios

1 min

1 min

5 min

5 min

1. Split group and choose website/app or per group

2. Get in to pairs

3. Create a scenario

4. Discuss

EXERCISE

TIMING

DELIVERABLE

KEY OBJECTIVE(S)

ACTIVITY

In your pairs write a testing discussion guide.

Usability testing discussion guide

2 min

5 min

1. Write a testing discussion guide as a group

2. Refine for your own needs

EXERCISE

TIMING

DELIVERABLE

KEY OBJECTIVE(S)

ACTIVITY

Carry out a usability test , take notes and ask the participant to fill in a Software Usability Scale questionnaire

None.

1 min

8 min

1 min

10 min

1. Choose another pair

2. Tests project on the each other (take notes)

3. Ask participant to complete SUS

4. Swap and repeat

EXERCISE

TIMING

DELIVERABLE

KEY OBJECTIVE(S)

ACTIVITY

Calculate SUS as a group

None.

5 min 1. Do it on the board


THE MATHS‣ Odd numbered questions (x-1) ‣ Even numbered questions (5-x) ‣ Sum * 2.5 = Score out of a 100 (not a percentage) ‣ Average is 68 across over 5000 test results in different studies


FURTHER READING‣ Quantifying the User Experience, J. Sauro & J. R. Lewis

THANKS!

Q&A


Technology

User testing workshop