1 00:00:00,320 --> 00:00:02,440 The. Better Business analysis 2 00:00:02,480 --> 00:00:04,760 Institute. Presence the Better Business 3 00:00:04,760 --> 00:00:07,680 Analysis podcast with Benjamin. Walsh. 4 00:00:12,360 --> 00:00:15,760 Welcome back everyone. I'm your host, Benjamin Walsh. 5 00:00:16,040 --> 00:00:18,520 And today? We will continue on our BA byte 6 00:00:18,520 --> 00:00:21,800 series. And we'll jump right into 10 7 00:00:21,920 --> 00:00:26,840 essential techniques. For technical business analysts. 8 00:00:27,320 --> 00:00:28,320 Now. I've already made. 9 00:00:28,320 --> 00:00:31,160 Comments around? Technical business analysis. 10 00:00:31,400 --> 00:00:33,320 And I believe it fits. In more the. 11 00:00:33,440 --> 00:00:36,760 System or solution? Analysis side so. 12 00:00:36,760 --> 00:00:39,520 This is still a. Bit of a Gray area and a lot of 13 00:00:39,520 --> 00:00:41,680 BAS plan the space. Or have to. 14 00:00:41,680 --> 00:00:45,480 And this is actually. Where I first started doing BA, 15 00:00:46,280 --> 00:00:47,600 however. It isn't. 16 00:00:47,960 --> 00:00:50,000 Business analysis we're. Talking about here. 17 00:00:50,160 --> 00:00:52,000 It's more around the. Solution. 18 00:00:52,120 --> 00:00:54,680 OK, so. Just want to clarify that before 19 00:00:54,680 --> 00:00:57,640 we dive in, however, it's always good to know. 20 00:00:57,840 --> 00:01:00,240 And by having. Some technical skills. 21 00:01:00,360 --> 00:01:03,720 You understand how? The solution may be put in. 22 00:01:03,720 --> 00:01:05,960 Place and it helps. So some of these. 23 00:01:05,960 --> 00:01:07,560 Things like I said. Are in the. 24 00:01:07,560 --> 00:01:09,760 Twilight Zone between what may be an. 25 00:01:09,760 --> 00:01:12,880 Architect A junior. Architect would do or a 26 00:01:12,880 --> 00:01:14,520 solution. Designer would do. 27 00:01:15,640 --> 00:01:18,440 But let's jump straight in. Number one. 28 00:01:19,480 --> 00:01:23,560 Is understanding the system requirements, not business 29 00:01:23,560 --> 00:01:26,920 requirements. So first and foremost is 30 00:01:26,920 --> 00:01:30,080 essential to kind of understand what those. 31 00:01:30,080 --> 00:01:33,920 System requirements are. Before delving into. 32 00:01:33,920 --> 00:01:36,520 Business rules. Or pseudo code. 33 00:01:37,040 --> 00:01:39,920 You need to really familiarize. Yourself. 34 00:01:40,320 --> 00:01:42,480 With the technical needs of your project. 35 00:01:43,480 --> 00:01:45,800 For example, if you're upgrading an E. 36 00:01:45,800 --> 00:01:48,000 Commerce platform. You need. 37 00:01:48,000 --> 00:01:52,840 To make sure that it can handle. Thousands of concurrent users 38 00:01:54,880 --> 00:01:56,000 so. How do we? 39 00:01:56,000 --> 00:01:59,080 Do that from a traditional. BA point of view and. 40 00:01:59,080 --> 00:02:01,040 Then from a. Technical business analysis 41 00:02:01,040 --> 00:02:03,960 point of view or a systems analyst point of view? 42 00:02:04,360 --> 00:02:07,400 So #1 for that is around the fact. 43 00:02:07,400 --> 00:02:11,280 That there will should be a non. Functional requirement around 44 00:02:11,280 --> 00:02:12,640 that. OK, so that's the BA. 45 00:02:12,840 --> 00:02:15,240 Side. The traditional BA, the business 46 00:02:15,240 --> 00:02:16,240 side. And the. 47 00:02:16,240 --> 00:02:18,120 TBA side technical business analyst. 48 00:02:18,120 --> 00:02:21,080 Side or systems analysis? Side and maybe I'll just use. 49 00:02:21,080 --> 00:02:24,680 The terms BA and. Essay So essay when I'm talking. 50 00:02:24,680 --> 00:02:28,960 About technical analysis. Their job would be OK. 51 00:02:28,960 --> 00:02:30,760 Well, what does that? Mean for the solution. 52 00:02:31,560 --> 00:02:35,160 How are we going to make that? What is the analysis I need to? 53 00:02:35,160 --> 00:02:39,920 Do to make sure that can be met so. 54 00:02:40,280 --> 00:02:45,360 For example, if you're. Using say WooCommerce or Shopify 55 00:02:45,800 --> 00:02:47,600 there will be stats on that. So this is. 56 00:02:47,960 --> 00:02:49,880 The the the. System. 57 00:02:49,880 --> 00:02:52,920 Requirement here is then what? Can the system? 58 00:02:52,920 --> 00:02:54,120 Meet that. OK. 59 00:02:54,120 --> 00:02:57,400 So if you're buying a product. You need to do some analysis on 60 00:02:57,400 --> 00:02:59,200 that and if you're building a product. 61 00:02:59,200 --> 00:03:00,560 You need to. Make that clear. 62 00:03:00,760 --> 00:03:02,120 To the build. Team that, that's. 63 00:03:02,160 --> 00:03:04,200 Really important of all the. Requirements. 64 00:03:04,200 --> 00:03:05,480 That's really important. So that's number. 65 00:03:05,480 --> 00:03:07,800 One understanding the. System or solution? 66 00:03:07,800 --> 00:03:09,080 Requirements there. OK. 67 00:03:10,160 --> 00:03:12,040 So it's really taking the business requirement and then. 68 00:03:12,040 --> 00:03:15,160 Looking at the next step down. Detailed analysis. 69 00:03:15,160 --> 00:03:18,800 In the technical sense, to the hell. #2. 70 00:03:19,360 --> 00:03:21,200 And again this. Is on the border. 71 00:03:21,480 --> 00:03:23,520 It's defining the. Business rules. 72 00:03:23,520 --> 00:03:27,280 Clearly, so the business rules capital B is this this? 73 00:03:27,280 --> 00:03:31,360 Word is used all over the play, all over the show to mean 74 00:03:31,560 --> 00:03:33,480 things. That are baked into the system 75 00:03:33,480 --> 00:03:37,040 to what someone wants business. Rules the B. 76 00:03:37,040 --> 00:03:39,360 Again, aligns with. Business analysis It. 77 00:03:39,360 --> 00:03:42,000 Is the BAS job to define. The business rules. 78 00:03:42,200 --> 00:03:45,000 However, they translate sometimes to validation and 79 00:03:45,000 --> 00:03:46,720 system rules. In the system. 80 00:03:47,320 --> 00:03:50,040 So. When the BA has defined the 81 00:03:50,040 --> 00:03:51,680 rules. In business terms? 82 00:03:52,040 --> 00:03:55,800 The technical BA or SBA should be looking. 83 00:03:55,800 --> 00:04:01,920 At the rules as. Things like validation, so. 84 00:04:02,560 --> 00:04:06,760 We need a rule and the. Solution to make sure that. 85 00:04:06,800 --> 00:04:10,200 When someone enters. Their e-mail address it's a 86 00:04:10,200 --> 00:04:12,240 valid. E-mail so it has the at. 87 00:04:12,240 --> 00:04:16,000 Symbol. You can actually use pinging. 88 00:04:16,000 --> 00:04:17,680 There's ways of checking whether. 89 00:04:17,680 --> 00:04:20,480 Or not the e-mail is valid. Before you allow someone to sign 90 00:04:20,480 --> 00:04:21,839 up. And so that. 91 00:04:21,839 --> 00:04:24,080 Sys that that. Business rule around valid 92 00:04:24,080 --> 00:04:25,680 e-mail addresses. The business requirements. 93 00:04:25,960 --> 00:04:27,640 The system. Rule is around. 94 00:04:27,640 --> 00:04:30,280 Validating that and specifying that it needs to have an AT 95 00:04:30,280 --> 00:04:34,200 symbol and you know you. Need to confirm e-mail links. 96 00:04:34,600 --> 00:04:37,760 So those that's around. How you're going to do it now, 97 00:04:38,480 --> 00:04:41,160 the BA may not know. Technically how that works? 98 00:04:41,160 --> 00:04:43,480 So the essay or the technical. Designer. 99 00:04:43,920 --> 00:04:47,040 Will need to specify that in a bit more detail by writing that 100 00:04:47,040 --> 00:04:47,800 up. OK. 101 00:04:48,840 --> 00:04:50,040 So that's number two. That's the. 102 00:04:50,040 --> 00:04:52,240 Business rules, clearly. And then mapping. 103 00:04:52,240 --> 00:04:56,840 Those down to system rules. #3 is. 104 00:04:56,880 --> 00:05:00,160 If there is, it's around. Using decision tables for 105 00:05:00,160 --> 00:05:02,880 complex business rules. So our third. 106 00:05:02,880 --> 00:05:05,560 Technique is around using. Decision tables for. 107 00:05:05,560 --> 00:05:08,040 Complex business rules. So these. 108 00:05:08,040 --> 00:05:12,680 Around different scenarios, OK. So say if I say I want. 109 00:05:12,720 --> 00:05:14,000 There's a business requirement or. 110 00:05:14,000 --> 00:05:17,480 About applying a. Discount. 111 00:05:17,520 --> 00:05:20,120 For a loyalty program. On purchase amounts. 112 00:05:20,760 --> 00:05:24,160 The systems analysis. Side would actually specify 113 00:05:24,160 --> 00:05:28,320 maybe what the table looks like in terms of translating. 114 00:05:28,320 --> 00:05:30,080 You know if I said if you're tier? 115 00:05:30,080 --> 00:05:33,120 1 you get 20%. Tier 2. 116 00:05:33,120 --> 00:05:37,800 You get 7. .5 and then you get 5% for example. 117 00:05:37,800 --> 00:05:40,160 For tier 3. It might be specifying what that 118 00:05:40,160 --> 00:05:42,800 looks like in a table. For example, literally. 119 00:05:42,800 --> 00:05:44,360 Not just specifying it in written. 120 00:05:44,360 --> 00:05:47,640 Terms. And by showing that you know. 121 00:05:47,760 --> 00:05:49,520 If someone spent this, you go to. 122 00:05:49,520 --> 00:05:50,360 The you. You. 123 00:05:50,360 --> 00:05:52,520 Get this so it's. Outlining that and. 124 00:05:52,560 --> 00:05:53,880 And and lots. Of details. 125 00:05:54,080 --> 00:05:55,960 And even to a point of even writing. 126 00:05:55,960 --> 00:05:58,320 Some pseudo code. So we'll get to that point. 127 00:05:58,400 --> 00:06:00,800 Soon, so decision tables are important. 128 00:06:01,480 --> 00:06:03,760 And it's explaining. It's by. 129 00:06:03,760 --> 00:06:06,560 Having that document and by providing. 130 00:06:06,560 --> 00:06:11,320 That to the technical team. #4 is around flow diagrams. 131 00:06:12,000 --> 00:06:15,200 And flow charts. So you do this in business 132 00:06:15,200 --> 00:06:17,760 analysis? But this might actually. 133 00:06:17,760 --> 00:06:21,880 Be the system logic OK. So you're doing things like 134 00:06:23,600 --> 00:06:25,280 doing just using a. Visual aid. 135 00:06:25,360 --> 00:06:26,560 To understand the. System. 136 00:06:26,560 --> 00:06:30,000 Logic and the interaction. She might use it for. 137 00:06:30,800 --> 00:06:33,240 User registration. Process maybe? 138 00:06:33,240 --> 00:06:35,080 We've made it, really. Clear that we want. 139 00:06:35,080 --> 00:06:36,840 The user to be out of. Register, for example. 140 00:06:36,840 --> 00:06:39,200 That's the business requirement, the system. 141 00:06:39,200 --> 00:06:42,720 Requirement might talk about that whole e-mail registration 142 00:06:42,720 --> 00:06:45,840 and that what happens when they sign up. 143 00:06:46,320 --> 00:06:48,640 This is really low. Level kind of kind of stuff 144 00:06:48,640 --> 00:06:50,960 here, almost procedure level, but. 145 00:06:50,960 --> 00:06:53,240 Stating it for the. System Designer. 146 00:06:53,520 --> 00:06:56,160 So it's around saying. Like you know that they have to 147 00:06:56,160 --> 00:06:58,880 enter a valid e-mail. If they don't, then this is what 148 00:06:58,880 --> 00:07:00,240 happens and. Drawing that up. 149 00:07:00,480 --> 00:07:01,960 Like technically what's happening is. 150 00:07:01,960 --> 00:07:04,360 The system returning something. Is the backing returning 151 00:07:04,360 --> 00:07:06,360 something? Does the backing need to? 152 00:07:06,360 --> 00:07:09,640 Send the notification out the e-mail notification, Do we? 153 00:07:09,640 --> 00:07:14,120 Need to. Have some kind of mail server 154 00:07:14,120 --> 00:07:16,200 that allows us to do. That and. 155 00:07:16,280 --> 00:07:20,720 And when they click on the link, is it going to another secure 156 00:07:20,720 --> 00:07:22,600 location? What web page does it? 157 00:07:22,600 --> 00:07:23,840 Return to. So you're really. 158 00:07:23,840 --> 00:07:25,200 Getting into the design side here. 159 00:07:25,400 --> 00:07:27,320 OK, so that's. What we mean by that? 160 00:07:27,320 --> 00:07:29,800 So it's not process design, it's more the flows. 161 00:07:30,000 --> 00:07:32,040 Of how the system's going to work sequence. 162 00:07:32,040 --> 00:07:34,480 Diagrams are used in. UML as well for this. 163 00:07:35,960 --> 00:07:37,960 Number. Five, which we talked about 164 00:07:37,960 --> 00:07:40,240 earlier. Is about writing pseudocode. 165 00:07:41,240 --> 00:07:43,440 So what does that mean? This bridges the gap. 166 00:07:43,440 --> 00:07:45,720 Between business. Logic and actual. 167 00:07:45,720 --> 00:07:48,840 Code so you keep. Instructions straightforward it. 168 00:07:48,840 --> 00:07:50,920 Doesn't have to be correct. But. 169 00:07:50,920 --> 00:07:53,320 Say for the login. Process you might write down. 170 00:07:53,480 --> 00:07:58,440 If username and password incorrect allow access else show 171 00:07:58,440 --> 00:08:00,080 error. You're literally. 172 00:08:00,080 --> 00:08:06,040 Writing really low level pseudo, what we call pseudo go fake like 173 00:08:06,720 --> 00:08:09,360 code if you like and then whatever language. 174 00:08:09,840 --> 00:08:12,960 The developer is. Writing and they can write that 175 00:08:12,960 --> 00:08:15,120 same Python or whatever the technique. 176 00:08:15,320 --> 00:08:18,520 They're using so that is that's. What we call. 177 00:08:18,520 --> 00:08:22,240 Pseudocode, it's something. That a system designer would do 178 00:08:22,240 --> 00:08:29,480 or a systems analyst would do. Number six is around the. 179 00:08:29,480 --> 00:08:31,440 Fact that. Once we've defined. 180 00:08:31,760 --> 00:08:34,480 Our business. Rules and then the system rules. 181 00:08:34,799 --> 00:08:37,880 It's making sure that we. Actually validate those. 182 00:08:38,520 --> 00:08:41,159 With stakeholders. OK, so if you're. 183 00:08:41,159 --> 00:08:42,679 If there are two roles, a business. 184 00:08:42,679 --> 00:08:45,040 Analyst and a systems analyst once the systems. 185 00:08:45,040 --> 00:08:48,640 Analyst has created how? The business rule will be 186 00:08:48,640 --> 00:08:49,520 implemented. And the. 187 00:08:49,520 --> 00:08:51,440 Technical feasibility. Of that might be. 188 00:08:51,440 --> 00:08:53,840 Quite different to what the. Business asks for the business 189 00:08:53,840 --> 00:08:56,600 need. So you need to review the 190 00:08:56,600 --> 00:09:00,000 resetting of password. Technique with maybe IT and 191 00:09:00,000 --> 00:09:02,640 customer. Service around security and user 192 00:09:02,640 --> 00:09:05,760 experience, and you might go back to stakeholders and explain 193 00:09:05,760 --> 00:09:07,440 to them how it's. Going to be implemented. 194 00:09:07,680 --> 00:09:10,800 So it's validating the actual. Business rules implementation 195 00:09:10,800 --> 00:09:13,560 with stakeholders #6. It's really important. 196 00:09:13,800 --> 00:09:17,160 I've had that recently. Where the business? 197 00:09:17,280 --> 00:09:19,200 Thought one thing. And then the system was. 198 00:09:19,200 --> 00:09:21,200 Implementing it another. Way OK and. 199 00:09:21,440 --> 00:09:23,520 They didn't think about the. Stakeholders that would. 200 00:09:23,600 --> 00:09:29,400 All be affected by the. Design of the solution. #7 is 201 00:09:29,400 --> 00:09:31,680 about maintaining a glossary of terms. 202 00:09:32,320 --> 00:09:35,760 So we can't sometimes do this in pure business analysis. 203 00:09:36,000 --> 00:09:39,040 But if you've introduced new. Terms as part of the design. 204 00:09:39,280 --> 00:09:41,360 Then you. Need to define maybe what user 205 00:09:41,360 --> 00:09:43,200 means and. Admin Admin. 206 00:09:43,200 --> 00:09:44,720 'S a common one. What does admin mean? 207 00:09:44,720 --> 00:09:46,560 System admin. Does that mean full rights? 208 00:09:47,040 --> 00:09:48,880 Maybe session timeout? What does that mean? 209 00:09:49,160 --> 00:09:52,040 So that's again if you ever introduced new terminology. 210 00:09:52,040 --> 00:09:53,280 In the solution. Design you. 211 00:09:53,280 --> 00:09:55,000 Need to help clarify. What that means? 212 00:09:55,320 --> 00:09:56,600 And that's something that the business. 213 00:09:56,600 --> 00:09:58,360 Probably needs to. Understand because when you 214 00:09:58,360 --> 00:10:01,000 deliver the solution, you go. Log them as admin. 215 00:10:01,200 --> 00:10:03,920 What does that mean in terms? Of the rights of the solution. 216 00:10:04,440 --> 00:10:09,200 So it's #7. #8 is around implementing error handling. 217 00:10:09,480 --> 00:10:12,680 This is something that gets lost between business requirements. 218 00:10:12,720 --> 00:10:15,160 And the developer because developers. 219 00:10:16,400 --> 00:10:18,040 That's why we have. Testers that are. 220 00:10:18,040 --> 00:10:19,800 Always thinking about what's important. 221 00:10:19,800 --> 00:10:22,200 In terms of error handling and. Also, what the? 222 00:10:22,200 --> 00:10:24,680 User wants to see. If they do do error. 223 00:10:24,680 --> 00:10:26,480 Handling and maybe. For their own. 224 00:10:26,480 --> 00:10:29,160 Purposes and logging. But it may not be in. 225 00:10:29,160 --> 00:10:31,920 Terms of showing the error message to the user. 226 00:10:31,920 --> 00:10:35,360 For example, so with. Implementing error handling. 227 00:10:36,280 --> 00:10:38,760 You can do that through pseudocode and. 228 00:10:38,760 --> 00:10:40,880 Business rules. And you might say if payment. 229 00:10:40,880 --> 00:10:43,840 Fails show an error to the. User log default. 230 00:10:43,840 --> 00:10:45,520 In the logging. Technique. 231 00:10:45,520 --> 00:10:46,760 There's all. Things. 232 00:10:47,080 --> 00:10:50,640 That the BA may not have. Thought of but from a system 233 00:10:50,640 --> 00:10:51,600 design. Point of view. 234 00:10:52,120 --> 00:10:53,880 You can think about how error handling. 235 00:10:53,880 --> 00:10:55,920 Might be best handled. Does it need to? 236 00:10:55,920 --> 00:10:57,320 Create an alert. In your. 237 00:10:57,320 --> 00:11:02,720 Service management system to follow up things like that. #9. 238 00:11:03,360 --> 00:11:06,040 Is again your job when you're doing the system. 239 00:11:06,040 --> 00:11:08,520 Design. Is to document the. 240 00:11:08,520 --> 00:11:10,440 Assumptions and constraints. You're making. 241 00:11:11,600 --> 00:11:13,600 So if you've got an. Assumption and constraint you. 242 00:11:13,600 --> 00:11:15,640 Should be talking to the. BA and the business, right? 243 00:11:16,280 --> 00:11:18,960 But ideally the BA if you've got one. 244 00:11:20,040 --> 00:11:21,040 But. There are. 245 00:11:21,040 --> 00:11:23,240 Cases where? If you're. 246 00:11:23,240 --> 00:11:25,120 Depending on the context. It helps. 247 00:11:25,120 --> 00:11:28,760 Everyone if you document the limitations of the project. 248 00:11:28,760 --> 00:11:31,480 And the solution? So you might write down an. 249 00:11:31,480 --> 00:11:33,000 Assumption, say. All users have a. 250 00:11:33,000 --> 00:11:34,840 Valid e-mail. Address the system. 251 00:11:34,840 --> 00:11:37,800 Can process payments in. 5 seconds, so this isn't the 252 00:11:37,800 --> 00:11:38,840 requirement. Side. 253 00:11:39,520 --> 00:11:41,040 This could be. What? 254 00:11:41,160 --> 00:11:45,960 The system requires OK. So it's almost. 255 00:11:45,960 --> 00:11:49,240 Say for example, I've written a. Business requirement that says. 256 00:11:49,560 --> 00:11:54,280 That the response time of the website. 257 00:11:54,280 --> 00:11:56,320 Needs to be within 2 seconds, right? 258 00:11:56,360 --> 00:11:58,160 That's what I want. That's pretty standardized. 259 00:11:58,680 --> 00:11:59,960 Now the. System constraint. 260 00:11:59,960 --> 00:12:03,960 Because we're building it on a complicated content management. 261 00:12:03,960 --> 00:12:05,200 System that's doing lots of things. 262 00:12:05,520 --> 00:12:07,560 It may actually take up. To three seconds. 263 00:12:07,880 --> 00:12:10,960 So we just say the. Constraint is that the the 264 00:12:11,080 --> 00:12:12,840 content management system that we've decided? 265 00:12:12,840 --> 00:12:14,760 To implement as. Part of the solution will 266 00:12:14,760 --> 00:12:16,920 actually load in three. Seconds, so that's. 267 00:12:16,920 --> 00:12:21,840 The job, That's the reply. #10. Is making sure that you. 268 00:12:21,840 --> 00:12:25,280 Continuously review and improve. OK, So what does that mean? 269 00:12:25,480 --> 00:12:28,320 Technical analysis is an. Ongoing process. 270 00:12:28,320 --> 00:12:30,400 OK, after you deploy the. Solution. 271 00:12:30,680 --> 00:12:31,800 You need to gather. Feedback. 272 00:12:31,800 --> 00:12:35,320 You need to analyze the data regularly, and you need to. 273 00:12:36,360 --> 00:12:38,360 Be you might need to. Optimize the system. 274 00:12:38,560 --> 00:12:40,880 And the business? Processing might change as a. 275 00:12:40,880 --> 00:12:42,960 Result of whatever solution you put in place. 276 00:12:43,240 --> 00:12:45,120 It's about. You know, it's a, it is a bit of 277 00:12:45,120 --> 00:12:48,360 a Yang and a Yang here. So for example. 278 00:12:48,360 --> 00:12:49,280 If you're running. Stats. 279 00:12:49,280 --> 00:12:51,480 Around. How many people have like not 280 00:12:51,480 --> 00:12:53,800 checked out so it's called cart abandonment on your. 281 00:12:53,800 --> 00:12:55,400 Website right? You might. 282 00:12:55,400 --> 00:12:57,440 Tell people. That so then the business knows. 283 00:12:58,680 --> 00:13:01,480 So this is around technical business analysis, systems 284 00:13:01,480 --> 00:13:05,120 analysis, solution design. There are 10. 285 00:13:05,120 --> 00:13:07,640 Essential things you need to know when. 286 00:13:07,640 --> 00:13:09,360 You delve into that and if you've been. 287 00:13:09,360 --> 00:13:11,640 Forced to do that and you're. Come from the business side. 288 00:13:11,880 --> 00:13:13,600 You need. To learn about this this. 289 00:13:13,640 --> 00:13:15,880 Isn't just. A hack job It needs to be. 290 00:13:15,880 --> 00:13:19,400 Done properly and. Yes, it comes more from the. 291 00:13:19,680 --> 00:13:22,440 Solution World. And it's not what I would. 292 00:13:22,440 --> 00:13:25,160 Say is business. Business Analysis. 293 00:13:25,360 --> 00:13:27,400 But we've all had to do. This in some. 294 00:13:27,400 --> 00:13:29,360 Shape or form, So I hope you learned something. 295 00:13:29,360 --> 00:13:31,280 Today and I'll. See you next week.