1 00:00:00,000 --> 00:00:01,114 [MUSIC] 2 00:00:01,114 --> 00:00:03,341 Hi, everyone, I'm Anya. 3 00:00:03,341 --> 00:00:10,269 I started as a UX researcher and designer before joining Google and 4 00:00:10,269 --> 00:00:14,847 being a UX manager there until very recently. 5 00:00:14,847 --> 00:00:20,780 I'm now excited to share with you what I've learned. 6 00:00:20,780 --> 00:00:25,800 Specifically, I wanna talk to you about an essential a part of the Helix process, 7 00:00:25,800 --> 00:00:27,422 evaluating your design. 8 00:00:27,422 --> 00:00:32,200 Together, we'll see how AB testing and surveys help us determine whether or 9 00:00:32,200 --> 00:00:34,194 not our designs are effective. 10 00:00:34,194 --> 00:00:38,361 And we'll take a critical look at usability testing so 11 00:00:38,361 --> 00:00:44,350 that you can learn how to prepare, run and report on your own usability study. 12 00:00:44,350 --> 00:00:49,671 User research falls into three phases that span your project timeline, 13 00:00:49,671 --> 00:00:52,904 generative, tactical, and evaluative. 14 00:00:52,904 --> 00:00:56,727 The generative phase is about researching user needs. 15 00:00:56,727 --> 00:01:00,134 The intention of this first phase is to inspire and 16 00:01:00,134 --> 00:01:05,500 to uncover the needs of the users well in advance of starting your design work. 17 00:01:05,500 --> 00:01:10,571 For example, if you're working for a medical device company, you may observe 18 00:01:10,571 --> 00:01:15,738 surgeons to understand how they work and what unresolved needs you can address. 19 00:01:15,738 --> 00:01:19,385 At this phase, you don't even need to have a product idea. 20 00:01:19,385 --> 00:01:24,580 The tactical phase is about evaluating what you've created so far. 21 00:01:24,580 --> 00:01:27,356 For example, if in your previous research, 22 00:01:27,356 --> 00:01:32,479 you discovered that the surgeons need help staying awake during long procedures. 23 00:01:32,479 --> 00:01:36,097 The tactical phase should include a prototype of how you plan to keep your 24 00:01:36,097 --> 00:01:36,996 surgeons awake. 25 00:01:36,996 --> 00:01:39,905 You may even set up a mock surgery environment, 26 00:01:39,905 --> 00:01:44,141 where the surgeons experiment with your idea and give you feedback. 27 00:01:44,141 --> 00:01:49,116 The third and final phase of testing is evaluative. 28 00:01:49,116 --> 00:01:53,099 This is the chance to see how your product is doing in the real world. 29 00:01:53,099 --> 00:01:57,221 Let's say that your device has been approved for use in actual surgery. 30 00:01:57,221 --> 00:01:59,090 Your job is still not done. 31 00:01:59,090 --> 00:02:03,230 Now's your chance to collect data on whether your product is improving 32 00:02:03,230 --> 00:02:06,686 the surgery success rate and the surgeons' well-being. 33 00:02:06,686 --> 00:02:11,052 You may tweak the device along the way to make incremental improvements. 34 00:02:11,052 --> 00:02:14,751 For this course, we'll focus on tactical research, but 35 00:02:14,751 --> 00:02:19,899 we'll also touch on using evaluative methods after your product has launched. 36 00:02:19,899 --> 00:02:23,399 After looking at all of those opportunities for research, 37 00:02:23,399 --> 00:02:27,251 you might wonder, when do I actually design and build a product? 38 00:02:27,251 --> 00:02:31,078 Isn't it better to put my ideas out there and fail fast? 39 00:02:31,078 --> 00:02:35,168 How will I convince my team to wait for me to do this research? 40 00:02:35,168 --> 00:02:39,960 Well, imagine developing your products for months, or maybe even years. 41 00:02:39,960 --> 00:02:44,408 Then you find a critical design flaw after launching. 42 00:02:44,408 --> 00:02:48,186 Maybe the surgeons didn't want to wear any additional devices. 43 00:02:48,186 --> 00:02:52,171 All they really needed were more frequent cups of coffee. 44 00:02:52,171 --> 00:02:53,722 Now what? 45 00:02:53,722 --> 00:02:58,507 Alternatively, you could have tested early and discovered the critical design 46 00:02:58,507 --> 00:03:02,392 flaw before any of your hardware was built, or code was written. 47 00:03:02,392 --> 00:03:04,966 So quick recap. 48 00:03:04,966 --> 00:03:11,743 Test early so that you can make sure you are addressing a real user need. 49 00:03:11,743 --> 00:03:17,341 Designing something only you are excited about is not enough. 50 00:03:17,341 --> 00:03:20,059 Confirm your design is usable. 51 00:03:20,059 --> 00:03:25,042 Are you making it easy for people to Save total development time. 52 00:03:25,042 --> 00:03:30,769 Discovering issues early means you won't need to build the thing twice. 53 00:03:30,769 --> 00:03:33,728 Minimize the cost of product support. 54 00:03:33,728 --> 00:03:39,074 A usable product simply doesn't require as much customer support. 55 00:03:39,074 --> 00:03:42,034 Remember, people expect great design. 56 00:03:42,034 --> 00:03:45,210 Imagine downloading a new calendar app. 57 00:03:45,210 --> 00:03:49,698 You install it, add your dinner plans for Friday night, 58 00:03:49,698 --> 00:03:54,106 save it, and realize you forgot to add the restaurant. 59 00:03:54,106 --> 00:03:58,130 You look for the Edit button, but you don't see it right away. 60 00:03:58,130 --> 00:04:01,769 How long will you search before abandoning this app for something else? 61 00:04:01,769 --> 00:04:06,806 What's going to convince you to try this app again later? 62 00:04:06,806 --> 00:04:10,651 If only someone tested their design before launching, 63 00:04:10,651 --> 00:04:13,119 you might still be their customer. 64 00:04:13,119 --> 00:04:17,129 So if you want to practice user-centered design, 65 00:04:17,129 --> 00:04:19,935 always keep the user at the center. 66 00:04:19,935 --> 00:04:24,129 And that means making sure to test your ideas early.