Guerrilla Usability Testing
Synonyms: Guerrilla Testing, Guerrilla User Testing, Quick Usability Testing, Street Testing, Informal Usability Testing
Definition
Use cases
- Confusing navigation: A designer wants to know whether people can find the pricing page without help.
- Unclear buttons: A team wants to check whether people understand what happens when they click a button.
- Early prototype feedback: A designer wants to see whether people can complete a basic checkout task before developers build the feature.
How it's used in practice
- Choose a clear goal: Decide what you want to learn, such as whether people can find a product or complete a form.
- Prepare 1–2 short tasks: Write simple instructions that people can follow without extra explanation.
- Find a suitable location: Visit a café, library, or campus where you may meet people who match your target audience.
- Observe the session: Ask participants to complete the tasks. Watch where they pause, get confused, or ask for help.
- Write down findings: Record repeated problems and decide what to change before testing again.
Challenges & limitations
- Wrong participants: People you approach may not match your target audience.
- Short sessions: A 10–15-minute test may not reveal problems in complex tasks.
- Public distractions: Noise, interruptions, and time pressure can affect how people use your prototype.
Free resources
- University of Edinburgh: Lessons Learned from Guerrilla Testing — a real university website redesign project and lessons from testing without formal recruitment.
- UserTesting: 17 Usability Testing Methods You Should Know — includes a dedicated section on guerrilla testing, its use cases, and limitations.
