- \n
- Performance testing<\/a><\/li>\n
- Card sorting<\/a><\/li>\n
- Tree testing<\/a><\/li>\n
- 5-second test<\/a><\/li>\n
- Eye tracking<\/a><\/li>\n<\/ul>\n<\/li>\n
- How to learn more about usability testing<\/a><\/li>\n<\/ol>\n
Ready? Let\u2019s dive in.<\/p>\n
1. What is usability testing and why does it matter?<\/h2>\n
Simply put, usability testing<\/a> is the process of discovering ways to improve your product by observing users as they engage with the product itself (or a prototype of the product). It\u2019s a UX research method specifically trained on\u2014you guessed it\u2014the usability of your products. And what is usability<\/a>? Usability is a measure of how easily users can accomplish a given task with your product.<\/p>\n
Usability testing, when executed well, uncovers pain points in the user journey and highlights barriers to good usability. It will also help you learn about your users\u2019 behaviors and preferences as these relate to your product, and to discover opportunities to design for needs that you may have overlooked.<\/p>\n
You can conduct usability testing at any point in the design process when you\u2019ve turned initial ideas into design solutions, but the earlier the better. Test early and test often! You can conduct some kind of usability testing with low- and high- fidelity prototypes<\/a> alike\u2014and testing should continue after you\u2019ve got a live, out-in-the-world product.<\/p>\n
2. Usability testing vs. user testing<\/h2>\n
Though they sound similar and share a somewhat similar end goal, usability testing and user testing are two different things. We\u2019ll look at the differences in a moment, but first, here\u2019s what they have in common:<\/p>\n
- \n
- Both share the end goal of creating a design solution to meet real user needs<\/li>\n
- Both take the time to observe and listen to the user to hear from them what needs\/pain points they experience<\/li>\n
- Both look for feasible ways of meeting those needs or addressing those pain points<\/li>\n<\/ul>\n
User testing essentially asks if this particular kind of user would want this particular kind of product\u2014or what kind of product would benefit them in the first place. It is entirely user-focused.<\/p>\n
Usability testing, on the other hand, is more product-focused and looks at users\u2019 needs in the context of an existing product (even if that product is still in prototype stages of development). Usability testing takes your existing product and places it in the hands of your users (or potential users) to see how the product actually works for them\u2014how they\u2019re able to accomplish what they need to do with the product.<\/p>\n
![\"Designer](\"\/en\/wp-content\/uploads\/old-blog-uploads\/paperprototype.jpg\" "\\"Usability")
<\/p>\n3. Formative vs. summative usability testing<\/h2>\n
Alright! Now that you understand what usability testing is, and what it isn\u2019t, let\u2019s get into the various types of usability testing out there.<\/p>\n
There are two broad categories of usability testing that are important to understand\u2014formative and summative<\/a>. These have to do with when you conduct the testing and what your broad objectives are\u2014what the overarching impact the testing should have on your product.<\/p>\n
Formative usability testing:\u00a0<\/strong><\/p>\n
- \n
- Is a qualitative research process\u00a0<\/a><\/li>\n
- Happens earlier in the design, development, or iteration process<\/li>\n
- Seeks to understand what about the product needs to be improved<\/li>\n
- Results in qualitative findings and ideation that you can incorporate into prototypes and wireframes<\/li>\n<\/ul>\n
Summative usability testing:<\/strong><\/p>\n
- \n
- Is a research process that\u2019s more quantitative<\/a> in nature<\/li>\n
- Happens later in the design, development, or iteration process<\/li>\n
- Seeks to understand whether the solutions you are implementing (or have implemented) are effective<\/li>\n
- Results in quantitative findings that can help determine broad areas for improvement or specific areas to fine-tune (this can go hand in hand with competitive analysis<\/a>)<\/li>\n<\/ul>\n
4. Attitudinal vs. behavioral research<\/h2>\n
Alongside the timing and purpose of the testing (formative vs. summative), it\u2019s important to understand two broad categories that your research (both your objectives and your findings) will fall into: behavioral and attitudinal.<\/p>\n
Attitudinal research<\/strong> is all about what people say\u2014what they think\u00a0 and communicate about your product and how it works. Behavioral research<\/strong> focuses on what people do\u2014how they actually do interact with your product and the feelings that surface as a result.<\/p>\n
What people say and what people do are often two very different things. These two categories help define those differences, choose our testing methods more intentionally, and categorize our findings more effectively.<\/p>\n
5. Five essential usability testing methods<\/h2>\n
Some usability testing methods are geared more towards uncovering either behavioral or attitudinal findings; but many have the potential to result in both.<\/p>\n
Of the methods you\u2019ll learn about in this section, performance testing has the greatest potential for targeting both\u2014and will perhaps require the greatest amount of thoughtfulness regarding how you approach it.<\/p>\n
Naturally, then, we\u2019ll spend a little more time on that method than the other four, though that in no way diminishes their usefulness! Here are the methods we\u2019ll cover:<\/p>\n
- \n
- Performance testing<\/a><\/li>\n
- Card sorting<\/a><\/li>\n
- Tree testing<\/a><\/li>\n
- 5-second test<\/a><\/li>\n
- Eye tracking<\/a><\/li>\n<\/ul>\n
These are merely five common and\/or interesting methods\u2014it is not a comprehensive list of every method you can use to get inside the hearts and minds of your users. But it\u2019s a place to start. So here we go!<\/p>\n
Performance testing<\/a><\/h3>\n
In performance testing, you sit down with a user and give them a task (or set of tasks) to complete with the product.<\/p>\n
This is often a combination of methods and approaches that will allow you to interview users, see how they use your product, and find out how they feel about the experience afterward. Depending on your approach, you\u2019ll observe them, take notes, and\/or ask usability testing questions<\/a> before, after, or along the way.<\/p>\n
Performance testing is by far the most talked-about form of usability testing\u2014especially as it\u2019s often combined with other methods. Performance testing is what most commonly comes to mind in discussions of usability testing as a whole, and it\u2019s what many UX design certification programs<\/a> focus on\u2014because it\u2019s so broadly useful and adaptive.<\/p>\n
While there\u2019s no one right way to conduct performance testing, there are a number of approaches and combinations of methods you can use, and you\u2019ll want to be intentional about it.<\/p>\n
It\u2019s a method that you can adapt to your objectives\u2014so make sure you do! Ask yourself what kind of attitudinal or behavioral findings you\u2019re really looking for, how much time you\u2019ll have for each testing session, and what methods or approaches will help you reach your objectives most efficiently.<\/p>\n
Performance testing is often combined with user interviews<\/a>. For a quick guide on how to ask great questions during this part of a testing session, watch this video:<\/p>\n
- Card sorting<\/a><\/li>\n
- Is a qualitative research process\u00a0<\/a><\/li>\n
- Card sorting<\/a><\/li>\n