1 00:00:00,000 --> 00:00:04,300 Interpreting tests results in some cases will be very easy. 2 00:00:04,300 --> 00:00:10,030 Simple observation can provide many clues about what website changes should be made. 3 00:00:10,030 --> 00:00:14,810 Also, many users will tell you directly that something is wrong, bad, 4 00:00:14,810 --> 00:00:18,120 it's not working, or that they don't like something. 5 00:00:18,120 --> 00:00:23,750 These comments often relate to usability issues but it is important to separate facts from opinion. 6 00:00:24,745 --> 00:00:28,570 When providing results, consider the experience each user had. 7 00:00:28,570 --> 00:00:31,400 Did they successfully accomplished each task, 8 00:00:31,400 --> 00:00:34,690 and in each case, where they satisfied with the results? 9 00:00:34,990 --> 00:00:39,930 It's very possible for a user to eventually find what they were looking for after a long period of time. 10 00:00:39,930 --> 00:00:43,640 This doesn't necessarily mean the website is in good shape. 11 00:00:43,640 --> 00:00:47,510 Other times, tests just don't yield clear results. 12 00:00:47,510 --> 00:00:49,159 If you're unsure what some of your data means, 13 00:00:49,159 --> 00:00:53,060 make a note of it so you can review it later and then move on. 14 00:00:53,850 --> 00:00:57,270 When all is said and done, the key deliverable from your test should be 15 00:00:57,270 --> 00:01:02,540 a set of recommendations you deliver to the people responsible for your website. 16 00:01:02,540 --> 00:01:05,800 It should be a clear list of directives based on your research, 17 00:01:05,800 --> 00:01:09,599 the test you conducted, and personal observation. 18 00:01:09,599 --> 00:01:12,470 The data you collect will help stir you in certain directions 19 00:01:12,470 --> 00:01:15,520 when generating recommendations for improvement. 20 00:01:15,520 --> 00:01:19,600 For instance, if every test user had trouble finding our return policy 21 00:01:19,600 --> 00:01:23,310 on the Shirts 4 Mike's site, there must be a problem. 22 00:01:23,310 --> 00:01:29,680 Sometimes the fix is obvious like adding a link in an expected location but not always. 23 00:01:29,680 --> 00:01:34,150 More testing can often reveal the best way to rule out different areas 24 00:01:34,150 --> 00:01:36,440 and decide upon the best solution. 25 00:01:37,000 --> 00:01:41,640 Your recommendations don't have to be produced in the form of one long check list. 26 00:01:41,640 --> 00:01:44,530 And in fact, a list like that can be misleading. 27 00:01:44,950 --> 00:01:50,930 You should be able to provide background on each item and rank them in order of importance. 28 00:01:50,930 --> 00:01:57,660 Fixing typos on a page isn't as mission critical as fixing a shopping cart that crashes every time. 29 00:01:57,660 --> 00:02:02,460 Therefore, you should organize these proposed fixes into a format that make sense 30 00:02:02,460 --> 00:02:06,720 and that's easy to implement especially if you are the one that has to do it. 31 00:02:07,719 --> 00:02:12,390 Lastly, understand that while findings can show areas for improvement, 32 00:02:12,680 --> 00:02:15,820 it can also confirm that something is working. 33 00:02:15,820 --> 00:02:21,200 Neither case knowing something works or doesn't work can be equally important. 34 00:02:21,200 --> 00:02:25,340 If you can run these tests with three to five people each month or two, 35 00:02:25,340 --> 00:02:30,110 you'll have plenty of data to keep yourself busy with changes and improvements 36 00:02:30,110 --> 00:02:33,470 especially if you end up implementing them immediately. 37 00:02:33,850 --> 00:02:38,810 And if that's the case, you'll have something new to test the following month.