[MUSIC PLAYING] Thanks for making it this far. By now, you know what usability testing is, how to plan for it, and how to deal with the intricate logistics. Now, we're going to talk about delivery. How do you deliver your usability test on testing day and ensure that it's successful? In my experience, success comes from teamwork. You need a great team to help you get to the finish line.
In a usability testing, it's no different. Individual roles and responsibilities are very important. One of the most important roles in usability test is the moderator, only second to the respondent themselves. But if we're going to concentrate on roles and responsibilities for delivering the test, let's look at the staff needed to make it happen. Firstly, the moderator.
The moderator delivers the test to the respondent. They sit with the respondent and help them along the way where needed. Another important role is that of the facilitator. The facilitator ensures everything is running smoothly. They welcome respondents and provide them with incentives when they leave the usability test. The role of notetaker becomes extremely important when there are technical difficulties.
But absolutely imperative to have someone constantly taking notes and ensuring that everything is captured in the written word. The notetaker becomes really important during triage as well because they've transcribed all of the data that you've just watched. Another important person to have on site is someone to provide technical support. The role of technical support can be fulfilled by the facilitator or the notetaker if needed.
The technical support person makes sure that all of the technology is functioning properly. Last, but not least, the role of the project manager is one that is extremely important to a usability test. The project manager pulls everything together and ensures everything is on track per plan, make sure everyone is doing what they're supposed to do, and is ultimately responsible for the success or failure of your usability testing project.
The next thing I want to touch on is the respondent process. The role of the respondent is ultimately the most important one. Without respondents, you're usability test isn't going to happen. So we ensure that respondents are well versed in the process before they show up. A respondent process starts with an initial contact. The user might interface with a prescreener online or via phone potentially delivered by a recruiter or by you.
After they've confirmed or passed the screening phase, we follow up with them via email or telephone prior to the usability test. We follow up with them about a week ahead of time. On testing day, we do that again. A reminder sent to the user on the day of the test is also very valuable. On the day of the test, when they arrive, they receive a video waiver, and we ensure that they understand that they're being recorded and watched during the usability test.
Then once they've completed the usability test, we present them with the form that they signed to acknowledge that they've received their incentive. This ensures that our paper trail is clean and we know who arrived, who conducted the test, and who got paid. Another extremely important piece of the puzzle to prepare ahead of the delivery of your usability testing session is a script for the moderator.
A good moderator will be familiar with the script they like to use and will likely add your task scenarios to it and probing questions. Most scripts start with a welcome statement, introducing the moderator to the respondent, and explaining why they're there. Then the moderator launches into their probing questions. What do you think of this brand, what do you notice first, where would you find this are some examples of probing questions.
Once that's complete, task scenarios begin. This forms the majority of the time spent in your usability test and could take anywhere from 20 to 45 minutes of the time allotted. Usually, in a usability test, we can get through between 5 and 10 tasks scenarios, depending on how elaborate they are. Once the test scenarios are complete, you'll hopefully have enough time to do additional probing questions.
Usually, the moderator will take the time to inquire with the merchant viewing the usability test and see if they have any additional questions they'd like to ask that user. Once the probing questions are finished, sometimes, it's followed up by a survey on how hard or easy the usability testing was, and then we're done. A thank you and an acknowledgment and a receipt of the incentive follows, and the user can go on their way.
In preparation for your usability test, you need to test your test. Once your script has been established, it's extremely valuable to recruit someone outside of the periphery of the project and conduct a mock test with them. This will ensure that the tasks that you've created are actually able to be completed and prevent any useless testing on something that may not be finished.
Testing the test may involve testing your facility as well. Ensuring that the technical setup is working flawlessly will make sure that there are no bumps in the road or interruptions throughout your usability testing session. And it's always important before your usability testing day to prepare a summary of what's going to happen, something that we like to call a usability testing dashboard. A usability testing dashboard will include the time, location, schedule, respondent information, summary of the tasks, a summary of the goals, objectives, and research objectives of your test, as well as all the roles and responsibilities on your team.
We'll also include a summary of the one-hour block or less of the test. [MUSIC PLAYING]