{"id":90664,"date":"2019-07-19T15:35:04","date_gmt":"2019-07-19T22:35:04","guid":{"rendered":"https:\/\/thegood.com\/?post_type=insights&p=90664"},"modified":"2025-05-14T15:16:00","modified_gmt":"2025-05-14T22:16:00","slug":"user-testing-part-3","status":"publish","type":"insights","link":"https:\/\/thegood.com\/insights\/user-testing-part-3\/","title":{"rendered":"How to Conduct High Impact User Testing: Part 3 – Analyzing the Results"},"content":{"rendered":"\n

This is the third and final installment of our three-part series, <\/em>How to Conduct High Impact User Testing<\/strong>. <\/em>To start from the beginning, read Part 1: Thoughtful Panel Selection.<\/a><\/span>
<\/p>\n\n\n\n

Analyzing and interpreting the results of your user testing sessions can be a daunting task. A standard test with five to ten participants can potentially produce sixty or more UX issues.<\/a> It\u2019s important that you know how to filter through these issues so you don\u2019t end up wasting your time developing solutions that don\u2019t address the broader usability issues at hand. 
<\/p>\n\n\n\n

We previously covered in parts one and two of this series how to select appropriate user testers and what questions you should be asking those users. In this final part we\u2019ll be focusing on how you can turn the data that was collected in your user testing sessions into quick wins, A\/B test ideas<\/a>, and bigger strategies. <\/p>\n\n\n\n

How to properly analyze and interpret your testing results<\/h2>\n\n\n\n

After you\u2019ve invested your time and resources into selecting a great panel of testers, formulating tasks and questions, then collecting all of the results of the testing session, you\u2019re ready to interpret those results into usable findings. <\/p>\n\n\n\n

Through our experience (listening to dozens of user recordings every day!), we\u2019ve identified a number of advantageous tips that you can use to get the most value out of your user research.<\/p>\n\n\n\n

Return to Your Original Objectives<\/h4>\n\n\n\n

As you start to analyze your user testing sessions, reflect on the objectives you created when you first launched your user tests. What were the goals that you and your team established for the test? Reflecting on these objectives will allow you to generate valuable insights that you can share with your team. <\/p>\n\n\n\n

Don\u2019t take user tester suggestions literally<\/h4>\n\n\n\n

User testers often suggest solutions to the micro-frustrations they encounter, but users are notoriously bad at thinking outside the box, and we caution you from letting these off-the-cuff \u201csolutions\u201d directly guide your design process. In our experience we\u2019ve heard some pretty wild suggestions from user testers, but oftentimes these suggestions don\u2019t address the root of the issue. <\/p>\n\n\n\n

As the old (most likely made up, but regularly cited) adage goes, Henry Ford said, “If I had asked people what they wanted, they would have said faster horses.” While user frustrations are valid, their suggestions are typically laser-focused on the problem directly in front of them and lack the data and context that researchers are armed with. <\/p>\n\n\n\n

So rather than getting caught up with tedious UX fixes, wait until enough feedback is collected to roll up these issues into a hypothesis that will address greater opportunities.<\/p>\n\n\n\n

“If I had asked people what they wanted, they would have said faster horses.”<\/em> \u2013Henry Ford<\/p><\/blockquote>\n\n\n\n

Capture quotes that synthesize misunderstandings, not just opinions <\/h4>\n\n\n\n

Direct user quotes are a great way to understand what page elements miss the mark, but make sure to capture the misunderstandings as well. Users will frequently say they\u2019re likely to do something but end up getting lost along the way. 
<\/p>\n\n\n\n

Quotes can contain more subjective feedback, but capturing the language that they’re using can be valuable as it helps you understand sentiment, both positive and negative. Even if what the user is saying doesn\u2019t necessarily match up with their actions, it allows us to see what they\u2019re noticing. This information is most easily found in the form of user feedback\/direct quotes because it\u2019s nearly impossible to tell what users are expecting to find on your site through heatmaps or analytics alone.<\/p>\n\n\n\n

Don\u2019t trust the user. Be skeptical and read between the lines<\/h4>\n\n\n\n

Listening to what your user testers are saying is important, but it\u2019s even more important to pay attention to what they do. Users will often rate their experience on a site favorably despite having struggled more than they would on a more optimized site experience. Even when users spend longer than average looking for pertinent information, they often rate ease of navigability highly. So take users opinions with a grain of salt. 
<\/p>\n\n\n\n

Users are often willing to forgive and forget a subpar site experience because they believe they have failed the site, rather than the site has failed them. Even if a user is not providing verbal feedback, pay attention to how long they spend on a task versus what they do not notice. 
<\/p>\n\n\nUsers are often willing to forgive and forget a subpar site experience because they believe they have failed the site, rather than the site has failed them. #usertesting #UXdesign <\/a><\/span>Share on X<\/a><\/span>\n\n\n

Prioritize the Identified Issues<\/h4>\n\n\n\n

It\u2019s important that you prioritize the issues you\u2019ve identified throughout the user testing sessions to help you determine which problems are more critical than others. It can be easy to underestimate the volume of problems even a handful of user testers may uncover on your site, so once you have a complete list, begin organizing them based on impact and significance. You don\u2019t want to find yourself caught up with tedious minor fixes to your UI when there are larger glaring issues that should be addressed first. 
<\/p>\n\n\n\n

Save yourself time and create a spreadsheet of all the problems you\u2019ve identified. Organize them based on the frequency that the issue occurred, and the impact it had on the overall user experience<\/a>. Then use your spreadsheet as a checklist as you determine what usability issues to tackle first on your site.<\/p>\n\n\n\n

It\u2019s time to start testing!<\/h2>\n\n\n\n

Analyzing and interpreting the results of your testing sessions is easily the most time-consuming but most valuable aspect of the user research process. Once you\u2019ve invested the time and resources into a series of user testing sessions, it\u2019s crucial that you draw as much insight and value as you can from the results. 
<\/p>\n\n\n\n

We hope the tips we provided can help you run a more successful and efficient user testing program in the future. This concludes our three-part series on user testing. If you missed parts one or two, make sure you read those as well and let us know your thoughts!<\/p>\n\n\n\n