Guerrilla testing
What it is
A means of gathering user feedback by taking a design or prototype into the public domain and asking passers-by for their thoughts.
Pros & Cons
Pros:
- Quick turn around
- Inexpensive compared to formal testing.
- Identify any UX barriers or validate design assumptions early in the process.
- This iterative testing works well in the agile project approach.
Cons:
- You may not get the right target audience.
- Sessions are short so you will lose some of the insights that you would get from formal user testing.
- Might not be appropriate for all types of websites or apps.
How to use
Checklist:
- Portable version of the product
- Notepad and pen
- A location where you can find plentiful and available users
- Script: an encouraging intro, a list of test scenarios and questions
Time: at least one day (prepare, carry out and analyse the research), 10-15mins (per test)
Participants: 6 to 12
Steps:
- Come up with a list of tasks; prioritize the tasks and turn them into scenarios.
- Start the guerrilla testing: Approach a person. Ask them if they would like to answer a few questions about your product. Then give them a couple of tasks to complete. Observe their interaction. Ask about their experience.
- Capture user testing insights and fix your usability problems.
- Test again, validate and make user tests a habit.
Recommended reading
- See 7 Step Guide to Guerrilla Usability Testing by Markus Pirker at UserBrain
- User testing on the cheap by Charlotte Brewer, Digital Communications, University of Bristol
- And Talking Out Loud Is Not the Same as Thinking Aloud by Mike Hughes