{"id":10222,"date":"2018-10-11T03:39:00","date_gmt":"2018-10-11T03:39:00","guid":{"rendered":"http:\/\/abstracta.us\/blog\/?p=10222"},"modified":"2025-05-05T21:23:37","modified_gmt":"2025-05-05T21:23:37","slug":"9-tips-successful-user-testing-gifs","status":"publish","type":"post","link":"https:\/\/abstracta.us\/blog\/software-testing\/9-tips-successful-user-testing-gifs\/","title":{"rendered":"9 Tips for Successful User Testing (and some GIFs)"},"content":{"rendered":"

User testing helps avoid costly mistakes and unsuccessful product launches. Here are some tips\u00a0for getting started.<\/span><\/h1>\n

When we access an application and can\u2019t find the information we are looking for in a short amount of time or don\u2019t like the way it\u2019s designed, most of the time, we abandon it. Good usability is the fundamental key for users to enjoy applications and use them for longer periods of time. So, knowing and putting into practice the fundamental factors for developing a highly usable application is essential. <\/span><\/p>\n

There are several methods for evaluating how usable an application is, one of them being user testing.<\/span><\/p>\n

<\/span>Why Test with Users?<\/span><\/strong><\/span><\/h2>\n

Testing with real users is one of the most common evaluation methods in web and mobile applications. The purpose of user tests<\/a> is to observe and analyze how real users interact with an application, while the test administrator takes note of the problems encountered along the way.<\/span><\/p>\n

Here are some things that Abstracta’s usability expert, Lisandra Armas<\/a>, has shared to remember before you run user tests (accompanied by GIFs from GIPHY<\/a>!):<\/span><\/p>\n

\"test<\/a><\/p>\n

<\/span>9 Tips for Successful User Testing<\/span><\/strong><\/span><\/h2>\n

<\/span>1. Find the right tools to facilitate testing<\/span><\/strong><\/span><\/h3>\n

These days, thanks to new tools, user testing doesn\u2019t have to cost an arm and a leg. <\/span><\/p>\n

Some paid tools include <\/span>Lookback<\/span><\/a>, <\/span>Loop11<\/span><\/a> and <\/span>UserTesting<\/span><\/a> which all enable software testers to perform these tests remotely, obtain metrics and create surveys. There are also free alternatives that you may already be familiar with such as <\/span>Zoom<\/span><\/a>, <\/span>Jing<\/span><\/a> and <\/span>Screenpresso<\/span><\/a> for web apps and simply using the<\/span> “Screen Recording” option for iOS 11 and for Android v4. 3 or higher.<\/span><\/p>\n

<\/span>2.\u00a0Explain the purpose of the test<\/span><\/strong><\/span><\/h3>\n

The user should be told that the <\/span>purpose of the test is to evaluate the quality of use of the application<\/b> and that he or she will not personally be evaluated, taking into account they’ve never had any prior exposure to the application,\u00a0which is why they are the ideal test participant. <\/span><\/p>\n

\"Millie<\/a><\/p>\n

<\/span>3. Don’t explain the app beforehand to the user<\/span><\/strong><\/span><\/h3>\n

The user shouldn\u2019t be given information related to the application since the goal is to know how easy and understandable the app is on its own.<\/span><\/p>\n

<\/span>4.\u00a0Ask relevant questions about the user<\/span><\/strong><\/span><\/h3>\n

Before starting, you can ask questions to know a little more about the user. These questions should be related to the business use of the application to verify if they have interacted with similar applications in the past.<\/span><\/p>\n

<\/span>5.\u00a0Encourage the user to think out loud<\/span><\/strong><\/span><\/h3>\n

It should be made clear to the user that during the test he or she should think out loud, commenting on everything they are thinking when interacting with the application in order to help identify areas for improvement. In case the user doesn\u2019t say anything when performing the test (maybe they are shy or simply forgot), the test administrator can intervene and ask the user what they are thinking as they move through the application. <\/span><\/p>\n

\"talking<\/a><\/p>\n

<\/span>6.\u00a0Ask the user to complete specific tasks<\/span><\/strong><\/span><\/h3>\n

It\u2019s a good practice to base the tasks on the functionalities that the final users will perform the most. <\/span><\/p>\n

Don\u2019t ask the user at this time if the design is the most appropriate, since, at this point,\u00a0the objective is to first find problems, not solutions.<\/span><\/p>\n

<\/span>7.\u00a0Test the areas with the greatest risk<\/span><\/strong><\/span><\/h3>\n

Guide the user to test the parts in which the team has identified possible weaknesses in usability. To measure how usable a particular aspect or certain functionality is, the tasks given to the user should be related to it.<\/span><\/p>\n

<\/span>8.\u00a0Let the user move on if they get stuck<\/span><\/strong><\/span><\/h3>\n

If the user gets stuck or blocked in any task, thank them for trying and ask them to continue with the next task. The fact that they got stuck should give you plenty of information right there, and don\u2019t get frustrated! It\u2019s your usability issue, not theirs. <\/span><\/p>\n

\"giphy<\/a><\/p>\n

<\/span>9. Take note of everything<\/span><\/strong><\/span><\/h3>\n

Remember to record everything the user was commenting and the time it took to perform each task. It\u2019s then useful to compile a summary of this information to share with the team later on and brainstorm ways to make the app more user friendly.<\/span><\/p>\n

\"dog<\/a><\/p>\n

<\/span>Don’t Skip User Testing<\/span><\/strong><\/span><\/h2>\n

With the\u00a0abundance of good tools that\u00a0exist for user testing and the tips mentioned above, software delivery teams can:<\/span><\/p>\n

    \n
  • Obtain relevant information\u00a0about an app\u2019s\u00a0degree of usability <\/span><\/li>\n
  • Identify problems in a short period of time<\/span><\/li>\n
  • Reduce costs by detecting issues before going to market<\/span><\/li>\n
  • Know how users will interact with the app and\u00a0if it’s UX\/UI design is well thought out<\/span><\/li>\n<\/ul>\n

    We invite you to apply these tips for your usability testing and then share your experiences with us. <\/span><\/p>\n

    Remember, if your users are asking for a manual to use your application, something is most likely wrong!<\/span><\/p>\n

    \"homer<\/a><\/p>\n

    What are some tips you have discovered for great user testing?<\/span><\/p>\n

    \n

    <\/span>Recommended for You<\/span><\/span><\/h2>\n

    5 iPad Gestures Testers Should Know<\/span><\/a>
    \n    [Infographic] What is Mobile Accessibility and Why Is it Important?<\/a><\/span><\/p>\n