User testing involves watching people use your site or app to see what difficulties they have. Guerrilla user tests can take a few different forms (covered below) but what they have in common is that they are relatively unplanned and quick to conduct. They're also usually done in-person rather than remotely.
Guerrilla tests are good for checking a work-in-progress in the form of a clickable/tappable prototype. Of course you could test finished websites or apps but there are other methods for this, which can better reflect the user’s actual experience.
The main purpose of these tests is for sense-checking your work as you go along and for testing out ideas on people who are coming to the project afresh. You'll discover usability issues with your work and whether people understand what they're interacting with.
It's probably the most useful evidence method for ‘works-in-progress’ as it doesn't require a completed product to gather evidence on. You can even test with sketches or paper prototypes. It's missing some of the scientific rigour of other user testing methods but it certainly beats sitting around and theorising or guessing at what users are going to do.
First off, a bit of preparation: think about what you're testing and decide the tasks you want people to carry out on your design (two or three tasks is about right for this type of test). If you're just showing a single screen then decide what your primary question to them will be (and make sure it isn't a leading one).
It’s worth noting down in a simple script what you want to say so you're consistent with each person. Also make sure you have a way of recording the feedback: write it down immediately after or—even better—make a video recording.
The main challenge for this type of test is finding relevant people and getting them to try out your design or prototype. As with most types of user testing, five users is a good number to aim for but if it's quick to get a couple more then do so.
Here are some options for finding people:
After testing you should always spend a bit of time going over your results and writing them up in some form. You might think you can remember what the issues are but it's surprisingly easy to forget one or two a few days later.
Sort the usability issues into a rough priority order of severity, and also include the things that users liked about the site. You can put your test results in a lightweight testing report so you have a record for yourself and others to refer to in future.
Testing with other people who work on your project or in your team is fairly useless as they are going to have such a clear idea of what you're doing that they won't ask the ‘obvious questions', or test your assumptions. This is precisely the kind of thing you want to find out.
Don't develop long tests with multiple tasks to go over. People's attention will wander pretty quickly and if you’re testing a prototype it will probably lack the realistic detail to sustain a long test.
You should be aiming to take about 5-10 minutes of their time. If you've got a big prototype then focus on the things you're most unsure about or run multiple guerrilla tests.
It can be hard to do it all on your own (especially in public) so you might need someone else to help. They can note-take or record while you engage with the user and build a bit of rapport. If there’s just one of you having to do both tasks then you can miss important things (and look like you’re ignoring the user).
A test that isn't recorded may as well have not happened, as you’ll have no evidence to point to if people challenge your findings. By getting it written down and having video clips you can share your findings with others. Definitely don't write a long report though or you're defeating the objective of speed.
You’ll need something to test on (your laptop, tablet, or phone) and you’ll need something to record with (another phone, QuickTime screen recording). Obviously these cost money but you’re likely to have access to them to design with so it shouldn’t cost any extra.
It can be as quick as an hour or two to run five tests but I recommend spending half a day to properly record and analyse the results.