Results and Recommendations2:38 with Dan Gorgone
In the end, the key deliverable from your usability tests should be a set of recommendations you deliver to the people responsible for the website. They should be based on your test results as well as personal observation.
Things to Consider
- How will you review the tests after they have been completed? Do you have recordings, notes, or other information you can refer to?
- How can you best report on the results of each test? Do you have qualitative analysis to explain what happened and how problems arose?
- Are you able to provide recommendations for each problem you've found? Which ones have clear solutions? Which ones are more troublesome? Is more testing needed?
- Who is ultimately responsible for making the changes you suggest? Have you given them enough information to compel them to act?
- When will you conduct testing again, and what might you test?
Interpreting tests results in some cases will be very easy. 0:00 Simple observation can provide many clues about what website changes should be made. 0:04 Also, many users will tell you directly that something is wrong, bad, 0:10 it's not working, or that they don't like something. 0:14 These comments often relate to usability issues but it is important to separate facts from opinion. 0:18 When providing results, consider the experience each user had. 0:24 Did they successfully accomplished each task, 0:28 and in each case, where they satisfied with the results? 0:31 It's very possible for a user to eventually find what they were looking for after a long period of time. 0:34 This doesn't necessarily mean the website is in good shape. 0:39 Other times, tests just don't yield clear results. 0:43 If you're unsure what some of your data means, 0:47 make a note of it so you can review it later and then move on. 0:49 When all is said and done, the key deliverable from your test should be 0:53 a set of recommendations you deliver to the people responsible for your website. 0:57 It should be a clear list of directives based on your research, 1:02 the test you conducted, and personal observation. 1:05 The data you collect will help stir you in certain directions 1:09 when generating recommendations for improvement. 1:12 For instance, if every test user had trouble finding our return policy 1:15 on the Shirts 4 Mike's site, there must be a problem. 1:19 Sometimes the fix is obvious like adding a link in an expected location but not always. 1:23 More testing can often reveal the best way to rule out different areas 1:29 and decide upon the best solution. 1:34 Your recommendations don't have to be produced in the form of one long check list. 1:37 And in fact, a list like that can be misleading. 1:41 You should be able to provide background on each item and rank them in order of importance. 1:44 Fixing typos on a page isn't as mission critical as fixing a shopping cart that crashes every time. 1:50 Therefore, you should organize these proposed fixes into a format that make sense 1:57 and that's easy to implement especially if you are the one that has to do it. 2:02 Lastly, understand that while findings can show areas for improvement, 2:07 it can also confirm that something is working. 2:12 Neither case knowing something works or doesn't work can be equally important. 2:15 If you can run these tests with three to five people each month or two, 2:21 you'll have plenty of data to keep yourself busy with changes and improvements 2:25 especially if you end up implementing them immediately. 2:30 And if that's the case, you'll have something new to test the following month. 2:33
You need to sign up for Treehouse in order to download course files.Sign up