Hello.

Chris BushUX Practice Lead

@wearesigma / @suthen

Guerrilla

user testing

Chris BushUX Practice Lead

@wearesigma / @suthen

Guerrilla

testing

Chris BushUX Practice Lead

@wearesigma / @suthen

A

D Taking your research further

B

A bit about Sigma (our services and clients)

C

Why talk about guerrilla testing?

Topics

Getting started with guerrilla testing

E Wrap up

User Research & Testing

Interface & Interaction Design

Web, Mobile & Application Development

Enterprise Content Management

Training & Support

A bit a Sigma

Our clients

Why do a talk about

Guerrilla testing?

Nux &

user

experience

Survey 2013

http://northern-user-experience.org/2013/09/05/

ux-challenge-choose-right-approach-guest-blog-ian-franklin-

freelance-ux-consultant

http://econsultancy.com/uk/reports/

user-experience-survey-report

USER EXPERIENCE SURVEY 2013

USER EXPERIENCE SURVEY 2013

Expensive- no budget

Time / Resource

consuming- delays

development

Not a primary concern

- Focus ontraffic

acquisition

USER EXPERIENCE SURVEY 2013

Lab Vs.

Guerrilla

Lab based testingPros:

• Users are often in a more informal environment(comfortable and relaxed)

• Great for bringing in teams together to observe users (and discuss)

• Help and support when defining tasks and scenarios

• Less likely to introduce moderator bias

• Detailed external provider analysis and reports

• More likely to use advanced data collection(Eye tracking)

Cons:

• Can be costly

• Less likely to want to invest in early stage testing (Prototypes and early beta code)

• Less likely to perform iterative tests

Pros:

• Requires no specialist equipment - only low cost software

• Very portable (on location, café, office, home)

• Great for early stage testing (Prototypes, etc.)

• Great for Rapid Iterative Testing and Evaluation (RITE)

• Minimal overhead (Time, People, Cost)

Cons:

• Moderator or reviewer bias

• The team takes on responsibility for ensuring everything is organised (Users, Room, Tasks, Write up)

• Finding a good testing room is sometimes tricky

Guerrilla testing

Getting started

• Any users are better than none but aim for two rounds: 5-10 per round

• Aim for a good cross-section of representative users

• Max 30-45 minutes to complete (around 5 tasks)

• Create meaningful tasks – word tasks as scenarios *

• Think aloud and retrospective think aloud

• Discussion guide – consistency is important• Rotate tasks (ABC / BCA / CAB) to remove bias

• Use a scribe *

Where do we start?

• Don’t be to specific

“Find and fill in the customer returns form.”

• Allow users the opportunity to decide what the most suitable solution is to the same problem

“After receiving your new camera you have noticed the lens is cracked. Using the site can you request a replacement.“

• Be pragmatic about leading questions

• But, always do a control test. (you’re testing your questions at this point)

Designing your tasks

On the day

DON’T DO THIS!

This works well

This works well

Sit back from the

participant

Screen projection

can be useful

Scribe sits away from the main

study

• Use the most comfortable room you can find

• Sit back from the user• Try to be out of their field of view

• Use reflective questions

• Don’t be a Monster! • If the user is struggling help them

On the day

• A second set of eyes helps to remove any bias

• It can save you hours of review time

• Define a coding system to help identify themes when taking notes

• .N – Navigation• .S – Search• .C – Content / Information• .D – Design• .T – Trust and credibility

• Time code your notes

• Spend 30mins after each session doing light analysis.

Use a scribe

Use a textexpander

Software: Silverback

Device testing

Software: UX recorder

Software: AirServer

http://www.90percentofeverything.com/2010/05/07/quick-tip-make-your-own-iphone-usability-testing-sled-for-5/

£5 device mount

SOFTWARE: POP

Make your

research go

further

Blended research

Interviews

SurveysUser

testing

RemoteUser

testing

Interviews

SurveysUser

testing

RemoteUser

testing

Blended research

Conclusions

• Always aim to test on five to ten people and for best results run two iterations of your tests

• Test your questions on real people before you do your test. They nearly always need refinement

• Take time to set up your room to make it as comfortable as possible.

• Remember to sit back from the user so they don’t feel like they are being watched too closely.

• Use reflective questioning. Participant: “Why did that happen when I clicked there?”You: “Why do you think that happened?”

Conclusions

• Use a scribe to ensure you get the most out of the session. It also helps remove any moderator bias.

• Code your notes as you go to save you time in analysis.(-n for navigation issues, -f for form issues, etc.)

• Take 15mins after each session to review the analysis and categorise the results. Do not try to solution new ideas at this point, if you’re not careful you could end up distorting the results of following studies.

• Lastly, If your project requires impartial validation consider using a lab for your final round of testing

Conclusions

Thanks!Any questions