The Why: run task based tests with actual users of the product to check usability and satisfaction
My Approach: I mapped out a schedule to the next couple of days of testing and synthesis. My team was made clear of our goals and tasks to make the usability sessions run smoothly.
What Could Go Wrong? Preparing for errors with testing is just an important as the success of the tests. Technical difficulties are a nightmare but knowing how to respond is key.
For example: My team was ready in the design room to observe the test but Zoom didn’t want to expand and hide it’s navigation bar like I wanted it to. So my team got to watch me fumble around a bit while attempting to smooth the situation by asking about the participants weekend plans. The participant ended up knowing the ins and outs of Zoom and assisted in solving the problem. We had success and continued on to the session! I was later told by my design and development team that the whole event was humorous to them. As long as they had some entertainment and learned about user perceptions along the way, then my job is done.
Reflection: Every moment as a UX researcher is a moment to learn and refine my skills. I learned that including the design and development team in usability testing is essential. I learned participants enjoy sharing their opinions and thoughts if given the platform. I learned that not every piece of feedback is necessary for immediate iterations. Lastly, I learned that I truly enjoyed being able to speak to participants and guide these sessions.