1 00:00:01,080 --> 00:00:02,290 Hey and welcome back. 2 00:00:02,310 --> 00:00:06,900 So the last part of this canvas, and this is something that's happening throughout the entire canvas, 3 00:00:06,900 --> 00:00:08,820 is mapping your assumptions. 4 00:00:09,210 --> 00:00:14,940 Now, risky assumptions are one of the primary sources of wasted effort or building applications in 5 00:00:14,940 --> 00:00:15,340 general. 6 00:00:15,870 --> 00:00:22,110 The team has the opportunity to really help each other and reduce that risk and uncertainty involved 7 00:00:22,110 --> 00:00:28,560 in the success of the project by calling out all this information during this canvas that we're kind 8 00:00:28,560 --> 00:00:29,320 of hosting. 9 00:00:30,540 --> 00:00:36,720 Now, the recommendation is to put an asterisk next to any information gathered where the confidence 10 00:00:36,720 --> 00:00:42,000 isn't really high and it's and if proven wrong, could lead to the project goals not being met. 11 00:00:42,930 --> 00:00:48,060 So there are many common assumptions that if they're proven wrong, they can really affect the success 12 00:00:48,060 --> 00:00:48,570 of the project. 13 00:00:48,570 --> 00:00:53,970 And here are some examples if we put too much effort into minor things. 14 00:00:55,050 --> 00:00:59,340 Our assumption is that a more personalized shopping experience is going to be better for users. 15 00:01:02,880 --> 00:01:04,800 So that definitely is an assumption. 16 00:01:05,160 --> 00:01:06,900 And we're going to put this in the middle. 17 00:01:06,900 --> 00:01:10,080 Like we do know that personalized shopping experiences are generally better. 18 00:01:10,080 --> 00:01:14,040 But if we don't get it right, this is very high risk for us. 19 00:01:15,130 --> 00:01:19,860 Let's think of another example, building features of little value to end users. 20 00:01:19,880 --> 00:01:24,190 So let's think about some features within our interests. 21 00:01:24,740 --> 00:01:31,580 A. Generally, when people are searching for products, they really just want to find their product 22 00:01:31,580 --> 00:01:33,230 and they want to be served up products. 23 00:01:33,230 --> 00:01:39,690 And, you know, maybe this interest picker is a little bit too much for a minimum viable product. 24 00:01:39,950 --> 00:01:45,820 So we're a little uncertain if we need this, but the risk is a little bit lower. 25 00:01:46,070 --> 00:01:51,770 You know, we may spend a little bit time building this, but it may be risky. 26 00:01:52,840 --> 00:01:59,770 Let's think about another assumption focusing on the wrong part of the user journey first, so let's 27 00:01:59,770 --> 00:02:01,580 think about our user journey. 28 00:02:01,600 --> 00:02:02,890 We're going to go back up here. 29 00:02:03,160 --> 00:02:05,050 This is something that we quickly built out. 30 00:02:05,590 --> 00:02:12,400 If a user wants to get relevant results and that's our goal over here, maybe something that we should 31 00:02:12,400 --> 00:02:15,890 figure out first is how we're going to serve up those results. 32 00:02:15,940 --> 00:02:20,230 Maybe the onboarding experience is really in depth and so like. 33 00:02:22,250 --> 00:02:24,860 People are maybe really want to focus on deals. 34 00:02:26,050 --> 00:02:30,520 We do know people like deals, but if we focus on this now, it's going to give us less time to actually 35 00:02:30,520 --> 00:02:31,630 finish the project. 36 00:02:31,660 --> 00:02:33,680 So maybe this is in the middle as well. 37 00:02:35,630 --> 00:02:37,250 Another one, the same, another one. 38 00:02:39,230 --> 00:02:43,220 We are assuming that all users want to be on mobile, since this is the mobile app. 39 00:02:43,430 --> 00:02:46,840 Now, this is a high risk and we're definitely uncertain of this. 40 00:02:46,850 --> 00:02:48,320 We don't know the type of user. 41 00:02:48,320 --> 00:02:50,240 We don't know if they're primarily mobile users. 42 00:02:51,290 --> 00:02:56,600 These are the types of things we're going to actually be putting in this kind of like parking lot throughout 43 00:02:56,600 --> 00:02:57,530 the entire canvas. 44 00:02:57,530 --> 00:03:01,430 We're marking all these things with an asterisks as they're on the whiteboard or within Sigma. 45 00:03:01,730 --> 00:03:06,440 We're making copies of this and throwing this on our large assumption grade, probably larger than this. 46 00:03:06,720 --> 00:03:11,770 And these are the types of things at the end that we're going to do our best to validate. 47 00:03:12,320 --> 00:03:17,390 We really want at the end of the canvas to understand what the project goals are. 48 00:03:19,840 --> 00:03:22,780 We want to understand our target users are less. 49 00:03:23,110 --> 00:03:27,290 These are end users and these are our stakeholders. 50 00:03:27,940 --> 00:03:30,200 We want to understand their goals and concerns. 51 00:03:30,460 --> 00:03:35,920 We want to understand the user journey, the main user journeys that we are going to be focused on for 52 00:03:35,920 --> 00:03:37,030 this project. 53 00:03:37,440 --> 00:03:42,670 But another thing that we need to do is we need to understand the assumptions that we're making along 54 00:03:42,670 --> 00:03:43,090 the way. 55 00:03:43,120 --> 00:03:47,680 And our first goal after this and canvas is to validate all these different things. 56 00:03:48,430 --> 00:03:58,000 So one very large assumption that we all make is that we know this. 57 00:04:02,820 --> 00:04:05,370 We know what the end user wants to do. 58 00:04:08,520 --> 00:04:15,270 We may know, but this holds a lot of risk and we need to figure this out early, this is why you do 59 00:04:15,270 --> 00:04:17,010 I'm not the moment to read. 60 00:04:17,010 --> 00:04:20,600 Sometimes I'll just list them and then we can prioritize them as a team. 61 00:04:20,970 --> 00:04:22,890 That's probably quicker in the moment. 62 00:04:22,920 --> 00:04:26,250 So remember to map this out throughout the entire process. 63 00:04:26,250 --> 00:04:31,290 And that's basically the end of the first part of a product alignment cannas.