 I'm not sure if you can tell us the answer to that. OK. Yeah, first of all, what is guerrilla usability testing? When I was looking for pictures of guerrilla, I pretty much only found Che Guevara. And I thought, well, maybe I don't really want to promote someone who, yeah, himself promoted violent uprisings. But then I found this guy called Che Guevara. And yeah, he's pretty well representing what this is about. So guerrilla testing is called a fast and low-cost way to gain sufficient insights to make informed decisions. So yeah, some key aspects there, fast and low cost. That's very important benefit, but also to gain sufficient insights. So yeah, what guerrilla user testing or user research in general is about, just the goal to some place can be a bar, can be your office, can be your home, whatever, grab someone who somewhat resembles at least your target audience. And then you just show them something and let them play with it to test it. I will go into a bit more detail later, but just for the context. So what is it good for? It can identify clear usability issues, so those kinds of issues that you can already see after a few minutes of using something. You can test assumptions with real users. So you probably have had the situation quite often where you have some discussion about whether something is useful for the user, whether something will be understood, easy to use. And then you have three different people with three different opinions. And everyone thinks that his or her opinion is the closest to the user. But you never know who's right. But if you test with real user who aren't you, then you can get some actual insights. And yeah, so just getting quick feedback when in doubt. So will users prefer one or the other or why? And yeah, it's best for short tasks that don't need a lot of prior knowledge and experience. Because yeah, as I said, you just walk up to someone, show them a device with something running on it. So usually they don't have any prior knowledge or experience. And yeah, it should be a quick and easy task. So on the reverse, what is it not good for? Yeah, as I said, it's not good for complex your eyes or tasks. So if you have something that you have to spend half an hour with to even understand anything or where the task itself is very long and complex, then yeah, gorilla testing is not good for that. Then you should do a proper lab test where you invite people for an hour or more to really do that complex task. It's also not good for measuring things. Because yeah, you're not in a lab. You don't have any equipment for measurement. I mean, you can cause measure clicks or taps. But even then, it's not a controlled environment. So the results are not likely going to be very reliable. So better not do that there. And it's also since you usually only do it with about five people, it's not good for extrapolating distribution of attitudes to the target audience as a whole. So if three out of five people liked variant A better than variant B, you can't say all 60% are going to prefer this variant. But you still can do things about attitudes, but it's more qualitative. So you should then care about why people like this better or that better. This will give you much more insight than just looking at numbers. So who can do it? The nice thing is that you don't need to have a user research specialist to do guerrilla user testing. Basically, anyone can do it who is outgoing and friendly, especially if you do it with strangers. Of course, you have to be ready to really talk to someone and ask them to do something for you. Have to be observant, because it's most insights that you gain from this kind of user testing is through observation, really seeing what people do, listening to them, what they are listening to their thoughts. So you really have to be observant. And of course, you also have to be patient, especially if you test your own product and you see people struggle, then that you will be likely to just quickly do it for them or tell them how to do it. But this will, of course, ruin your whole test. So really, even if people struggle, even if you think you should help them just refrain from doing it, let them struggle, clear it up in the end, but really watch how they try to solve the problem themselves. And yeah, who to test with. In the end, it can be anyone matching your target audience. And of course, if you are doing some application for a very specific use case, for example, for a scientific application, it doesn't give you much if you test it with people with no scientific background. But the more broad your target audience is, the easier you can just take whoever you find. Yeah, again, if your test needs some prior experience with the product that you're testing, then, yeah, of course, you will need current users. And yeah, in general, for example, it can be people, so this is the most traditional approach people you meet at a pub or at a cafe. That's why Maria user testing is often called a pub test. It works pretty well because they are pretty open. They are usually going to give you honest feedback because they don't have any relationship with you. It can also be coworkers. It can be fellow students. It can be friends and family. Of course, especially if you do repeated tests with the same product, unless it's completely different features, then, of course, it shouldn't be the same people. So make sure that you have enough people to always have fresh testers. And yeah, what do we need? A UI UX design, it doesn't have to be implemented. It can be anything from just a sketch on a piece of paper to a prototype of a UI. It can also be a finished product. But of course, always the earlier you do the testing, the better because the easier it is to change things based on the test. Of course, you need a place where those people who mention a target audience are. You need time. And if you do it, especially if you do the test with strangers, then you should have some incentive. The usual thing is, yeah, I'll buy you a coffee, a beer, wherever you are doing the test. So make sure that you have some money for that. Yeah, what do you need to do? Of course, the first thing is define your research question. So it shouldn't be just, yeah, I want to test this, but really define what am I going to find out with this thing. And based on that, you should define your test tasks and questions. Then, yeah, bring a device or a piece of paper with your eye on it. And then, yeah, you go ahead and, yeah, ask people that like to try out your product for a few minutes. Yeah, usually in exchange for beer. Although, people tend to actually enjoy this and really want to see all shiny, new, cool things that I can try out. And then, yeah, quickly introduce what the UI is about. But don't say too much. So really only say as much as it's absolutely necessary to get some context. Try to not explain anything beforehand. And, yeah, then, yeah, you explain the test procedure to them, which is usually pretty simple. So they do the tasks. And they ask them to think aloud if the environment allows that. Because that can give you a lot of insights into the way they are thinking. If you're testing a full application, a more complex product, then give people a few minutes to familiarize them with it beforehand. After that, just grab the specific task that they are supposed to do. And, yeah, watch users perform the task. Take notes. If it's possible, you can also record them. Of course, ask for the permission first. And, yeah, recording the screen and, ideally, also the interactions with the screen or with the application is also useful. But if you can't do any of these things, even just taking notes will already give you a lot of valuable information. Yeah, so for that, I'd really encourage you to let, yeah, let's go testing. So when the next time we have one of these conversations where they're just about to fight, because every each one of the discussion things, they know it, then just say, well, let's not continue discussing. Let's first really test it with users. And you can easily split the work within the team. So if you have five people and every one of you just takes one test, then it won't take that much time and will still be very useful. Yeah, if you have any questions, just talk to me. Send me an email. I'll be happy to answer questions. Thank you.