User Testing

7 Videos
status pause Introduction to User Testing 02:46 status pause Getting Started 02:29 status pause Building a Plan - Tasks 02:12 status pause Building a Plan - Questions 02:09 status pause Common Testing Errors 02:20 status pause Compile and Analyze 02:06 status pause Conclusion 01:02
previous Select Series

User Testing Part 1: Introduction to User Testing

85 views • March 12, 2020

User Testing
Part 1: Introduction to User Testing


Just what is it we're trying to find out through user testing? Why do we do it?
Transcript User testing is a way to get feedback from real people during the design and development process. Whether you're designing an app or making a website, you can devise different user tests to evaluate the whole product or just a small part of it.
User testing for digital products can either be done remotely or on site. Remote user tests are often done through a commercial platform. Paid users test the software on their home computers and give spoken feedback as they go. You can then download the screen recordings of the users' interactions as well as the audio recordings of their answer to your pre-scripted questions. In on-site testings, you're able to observe the user directly and interview them in real time. This gives you a better sense of their emotional response and you could follow up with situations as they arise, though this is obviously more costly and more complex to manage.
When you are in the early design stages of your project, user testing can save time and money by keeping you from going down the wrong path. Later, during the development and quality assurance phases, getting feedback from real users ensures that everything works seamlessly. Because, the last thing you want to do is release a product with obvious usability errors.
When it comes to planning user testing,
you want to start by defining your objective. What are we trying to find out about this particular piece of software at this time? If your project is still in the planning stages, your objective could be as basic as finding out whether new users will be able to find the information they need.
As your project moves through development,
you should be asking more pointed questions. For instance, does this page lead my visitors towards making a purchase?
As you near the end of development and start to focus on quality assurance, you'll be looking at very specific questions, things like, would it be easier to find this button if we made it yellow?
You want to avoid trying to test for everything in one study. At first, it may seem like you can save some time and money by including more questions and variables, but it's usually not a good idea. If you test for too many variables at once, your results may end up jumbled and telling which variable is causing what reaction becomes more difficult.
No matter what stage of the project you're in,
you always want to keep coming back to your user objectives. What do they care about? To sum up, plan to carry out multiple studies. Test for different learning objectives at different stages of the project. Begin with testing your broadest questions, and as development proceeds, gradually focus on more and more specific questions.
Design tests to verify that the product is meeting your stakeholders objectives. If you can ask the right questions at the right time, the answers will give you a better product at a lower cost, and you will look that much smarter.

Other videos you may like

Want to get Started?

Tell us about your project
Contact Us