---Presenter: Ben Swindle/Chris ReddickSubject: Lifecycle of a ProjectDetails: Goes over various steps of a project from a PM standpoint. Duration: 01:06:17---00:00:00.000 --> 00:00:03.582 I wanted to give the team kind of a00:00:03.582 --> 00:00:06.540 battle hardened veterans view of.00:00:06.540 --> 00:00:09.290 What is it like to take a self project live?00:00:09.290 --> 00:00:11.459 What is it like to take a connect project00:00:11.459 --> 00:00:13.594 lab and what are some of the things you00:00:13.594 --> 00:00:16.163 need to be thinking about and how should00:00:16.163 --> 00:00:18.274 you interpret the conversations with our00:00:18.274 --> 00:00:20.476 development team and with the client?00:00:20.480 --> 00:00:23.016 And like where things you need to be00:00:23.016 --> 00:00:25.388 pretty cynical about to make sure that it00:00:25.388 --> 00:00:27.868 gets done and what are common issues that00:00:27.868 --> 00:00:30.446 you've seen across all of the go lives.00:00:30.446 --> 00:00:32.990 And I'll certainly chime in as we go00:00:33.061 --> 00:00:35.322 as well and just kind of, you know,00:00:35.322 --> 00:00:37.450 help the team kind of get the full00:00:37.517 --> 00:00:39.755 context of what actually will happen.00:00:39.760 --> 00:00:41.315 Typically, especially for some of00:00:41.315 --> 00:00:43.165 these projects that are like, yeah,00:00:43.165 --> 00:00:46.290 we want to go live by the end of June.00:00:46.290 --> 00:00:47.865 OK, guess what?00:00:47.865 --> 00:00:51.540 Everything on this giant list needs to00:00:51.644 --> 00:00:54.490 get done now. And where is that list?00:00:54.490 --> 00:00:57.015 What? What is the list? Where is it?00:00:57.015 --> 00:00:58.905 Is it the E commerce checklist?00:00:58.910 --> 00:01:01.129 Is it this other list you know?00:01:01.130 --> 00:01:03.758 And we just kind of need to go through00:01:03.758 --> 00:01:06.178 those things so the team is equipped.00:01:06.180 --> 00:01:08.708 You know in general for what's coming up?00:01:08.710 --> 00:01:10.606 If I could get a volunteer,00:01:10.610 --> 00:01:12.978 possibly I can kind of walk you through00:01:12.978 --> 00:01:14.953 getting to a couple different checklists00:01:14.953 --> 00:01:17.240 that we have in nuclino and,00:01:17.240 --> 00:01:19.445 and it probably a good exercise anyway.00:01:19.450 --> 00:01:21.760 Who anybody want to volunteer to00:01:21.760 --> 00:01:24.216 share their screen? For me real quick.00:01:24.216 --> 00:01:27.148 Yeah, I can share mine.00:01:27.150 --> 00:01:29.607 DJ and then have you logged in,00:01:29.610 --> 00:01:33.970 logged into nuclino right, yeah.00:01:33.970 --> 00:01:34.942 Is there now?00:01:34.942 --> 00:01:37.534 It looks like you're good to go, yeah,00:01:37.534 --> 00:01:40.450 so type in the search up in the top.00:01:40.450 --> 00:01:41.100 Search for.00:01:43.110 --> 00:01:46.230 Go live checklist and there will be several00:01:46.230 --> 00:01:48.790 things that come up and we can also.00:01:48.790 --> 00:01:51.964 There's a couple others that are00:01:51.964 --> 00:01:54.080 under like prelaunch checklist.00:01:54.080 --> 00:01:57.880 And so now let's take a look at this so.00:02:01.310 --> 00:02:02.855 The these, these are all00:02:02.855 --> 00:02:04.400 things like we have to.00:02:04.400 --> 00:02:07.136 So first thing is first right that the00:02:07.136 --> 00:02:09.627 software has to have somewhere to live.00:02:09.630 --> 00:02:12.054 OK, and so at the end of the00:02:12.054 --> 00:02:14.467 day they they're coming to us,00:02:14.470 --> 00:02:17.151 and if they don't have somewhere already00:02:17.151 --> 00:02:19.318 predetermined that they want to host it,00:02:19.320 --> 00:02:21.792 then they're coming to us as the experts00:02:21.792 --> 00:02:23.604 to provide some recommendations in00:02:23.604 --> 00:02:26.236 terms of where to host their platform.00:02:26.240 --> 00:02:28.710 Now we have different requirements.00:02:28.710 --> 00:02:29.751 For different projects,00:02:29.751 --> 00:02:32.180 so like a DNN marketing site is00:02:32.252 --> 00:02:34.506 not going to have the same server00:02:34.506 --> 00:02:36.299 requirements as a SEV project.00:02:36.300 --> 00:02:38.834 So you know there's a couple different00:02:38.834 --> 00:02:40.289 recommendations for hosting surrounding00:02:40.289 --> 00:02:42.167 the type project that it is.00:02:42.170 --> 00:02:44.474 But in general we like to just give like00:02:44.474 --> 00:02:46.057 really general hosting recommendations00:02:46.057 --> 00:02:48.601 upfront along with the the server00:02:48.601 --> 00:02:50.448 requirements for the specific project,00:02:50.450 --> 00:02:53.250 and those are all documents that can be00:02:53.250 --> 00:02:56.473 found in in SharePoint where I like how I00:02:56.473 --> 00:02:59.415 was showing you PJ how to search and Sam,00:02:59.420 --> 00:03:02.115 you know you can just kind of.00:03:02.120 --> 00:03:04.448 You can find a lot of that the00:03:04.448 --> 00:03:06.400 documentation just by searching in there.00:03:06.400 --> 00:03:08.550 And I think we have a lot of the latest00:03:08.606 --> 00:03:10.082 documentation pretty well organized00:03:10.082 --> 00:03:12.296 in the operations team as well,00:03:12.300 --> 00:03:14.295 and some and spread out through some00:03:14.295 --> 00:03:16.139 of those different channels in there,00:03:16.140 --> 00:03:16.660 but anyway,00:03:16.660 --> 00:03:18.480 so the first thing you have to00:03:18.480 --> 00:03:20.594 lock in is the hosting portion and00:03:20.594 --> 00:03:22.180 that's something you can actually00:03:22.180 --> 00:03:23.508 start doing early on,00:03:23.510 --> 00:03:25.449 you can start bringing it up early00:03:25.449 --> 00:03:27.050 in the discovery process that.00:03:27.050 --> 00:03:27.330 Hey,00:03:27.330 --> 00:03:29.850 you know if you can find out if they've00:03:29.919 --> 00:03:32.367 already got a place picked or if they00:03:32.367 --> 00:03:35.017 don't then we'd at least want to early on,00:03:35.020 --> 00:03:36.151 get them over.00:03:36.151 --> 00:03:38.413 The server requirements for their project00:03:38.413 --> 00:03:40.489 and since Chris mentioned specifically00:03:40.489 --> 00:03:43.338 kind of talking about what all is00:03:43.338 --> 00:03:45.648 involved in taking a step project live.00:03:45.650 --> 00:03:47.792 In this case it would be sending00:03:47.792 --> 00:03:49.885 them the Clarity E commerce server00:03:49.885 --> 00:03:52.099 requirements and also there's a just00:03:52.099 --> 00:03:55.003 kind of a pretty standard like hosting00:03:55.003 --> 00:03:56.651 recommendations document that we00:03:56.660 --> 00:03:59.005 can send over that outlines some of00:03:59.005 --> 00:04:01.612 the pros and cons and different type00:04:01.612 --> 00:04:04.437 of building models that some of the00:04:04.437 --> 00:04:07.125 different hosting providers use and then.00:04:07.130 --> 00:04:09.380 On the project we may come in and make00:04:09.380 --> 00:04:11.790 make a few recommendations like say, OK,00:04:11.790 --> 00:04:13.820 we would recommend you either you know,00:04:13.820 --> 00:04:15.996 use Azure or you know a WS or00:04:15.996 --> 00:04:17.609 we may say you know,00:04:17.610 --> 00:04:20.520 like a liquid web would be the way to go,00:04:20.520 --> 00:04:22.840 so we may come back and say yeah,00:04:22.840 --> 00:04:25.064 here's this document and some of you may00:04:25.064 --> 00:04:27.172 have already consulted with some of the00:04:27.172 --> 00:04:29.249 senior team members like Chris or myself.00:04:29.250 --> 00:04:30.410 And we're we're saying,00:04:30.410 --> 00:04:30.991 yeah, really,00:04:30.991 --> 00:04:33.319 the ideal scenario would be hosting it here,00:04:33.320 --> 00:04:35.939 but we always want to give the client options00:04:35.939 --> 00:04:38.598 so it's their choice that they're making.00:04:38.600 --> 00:04:40.044 But as the experts,00:04:40.044 --> 00:04:42.210 we certainly want to make make00:04:42.287 --> 00:04:44.597 recommendations in the terms of.00:04:44.600 --> 00:04:46.030 This is this is 1 00:04:46.030 --> 00:04:47.460 recommendation and here's why I00:04:47.523 --> 00:04:48.750 would recommend this.00:04:48.750 --> 00:04:50.340 Here's the pros and cons.00:04:50.340 --> 00:04:51.300 Here's another recommendation,00:04:51.300 --> 00:04:52.580 but and here's why.00:04:52.580 --> 00:04:54.175 All that's pretty well laid00:04:54.175 --> 00:04:55.770 out in in those documents,00:04:55.770 --> 00:04:58.146 and you'll get to a point where you're00:04:58.146 --> 00:05:00.360 so battle hardened and doing this that00:05:00.360 --> 00:05:02.780 you just kind of have it memorized.00:05:02.780 --> 00:05:04.375 But it's really all there00:05:04.375 --> 00:05:05.970 and and it just takes,00:05:05.970 --> 00:05:07.198 you know, some repetition,00:05:07.198 --> 00:05:09.040 and you'll kind of get get00:05:09.105 --> 00:05:10.437 the concepts behind it.00:05:10.440 --> 00:05:12.348 But moving down the line once,00:05:12.350 --> 00:05:14.990 once you have a host and really quickly.00:05:14.990 --> 00:05:16.019 On the hosting.00:05:16.019 --> 00:05:18.914 One of the things that you can do00:05:18.914 --> 00:05:21.380 while you're kind of learning any00:05:21.380 --> 00:05:23.808 of these checklist items is Lupin,00:05:23.810 --> 00:05:25.585 team members who do have00:05:25.585 --> 00:05:26.650 experience with this,00:05:26.650 --> 00:05:28.780 so that's going to include Ben,00:05:28.780 --> 00:05:29.490 myself, Daniel.00:05:29.490 --> 00:05:31.265 I would say Clint Kevin,00:05:31.270 --> 00:05:33.400 I mean the list goes on,00:05:33.400 --> 00:05:36.144 but you're welcome to loop us in and00:05:36.144 --> 00:05:39.079 will join phone calls with you as well,00:05:39.080 --> 00:05:41.672 so you can kind of tag team a00:05:41.672 --> 00:05:44.347 partner to help you out with any00:05:44.347 --> 00:05:46.940 kind of explanation to the client.00:05:46.940 --> 00:05:48.584 And then it's great because you're00:05:48.584 --> 00:05:49.860 hearing how we're explaining it,00:05:49.860 --> 00:05:51.980 and we can kind of ask some questions,00:05:51.980 --> 00:05:53.918 and you can kind of hear00:05:53.918 --> 00:05:55.210 how we're thinking about.00:05:55.210 --> 00:05:57.442 You know what information we need00:05:57.442 --> 00:05:59.690 about the project to determine.00:05:59.690 --> 00:06:02.196 What kind of hosting environment I want?00:06:02.200 --> 00:06:03.640 Ultimately you're not expected00:06:03.640 --> 00:06:05.080 to know the details.00:06:05.080 --> 00:06:06.870 The technical details of the00:06:06.870 --> 00:06:09.091 hosting pieces more where are the00:06:09.091 --> 00:06:10.201 hosting requirements documents00:06:10.201 --> 00:06:13.138 and how can you get those to the00:06:13.138 --> 00:06:14.768 client as quickly as possible.00:06:14.770 --> 00:06:17.276 If they're expecting to go live soon,00:06:17.280 --> 00:06:20.870 like if they're trying to go live in a month,00:06:20.870 --> 00:06:22.670 they need those right now.00:06:22.670 --> 00:06:24.818 So where are they in Ben?00:06:24.820 --> 00:06:26.620 You're welcome to answer this,00:06:26.620 --> 00:06:29.169 or I can help with this, but.00:06:29.169 --> 00:06:31.563 Where do they find the hosting00:06:31.563 --> 00:06:33.161 requirements documents and the00:06:33.161 --> 00:06:35.147 hardening guide and all of that?00:06:38.370 --> 00:06:41.646 Yeah, no, I'm happy to kind of walk through00:06:41.646 --> 00:06:44.470 where where I see that they they live.00:06:44.470 --> 00:06:46.630 I mean they're they're in SharePoint.00:06:46.630 --> 00:06:49.334 I usually just search for them and make00:06:49.334 --> 00:06:52.009 sure that they are the latest version.00:06:52.010 --> 00:06:53.810 If there's a specific channel.00:06:55.930 --> 00:06:57.440 Yeah that yeah. Also yeah,00:06:57.440 --> 00:07:00.140 there's links to them in new clean as well.00:07:00.140 --> 00:07:01.650 Thank you. Yeah, you're right.00:07:01.650 --> 00:07:03.432 So that would be where I00:07:03.432 --> 00:07:04.960 would start then for you.00:07:04.960 --> 00:07:07.368 New folks would be checking a new clean.00:07:07.370 --> 00:07:09.785 Oh and then I mean, you can also.00:07:09.785 --> 00:07:11.615 Obviously you can search for any00:07:11.615 --> 00:07:13.389 documents you want in in SharePoint,00:07:13.390 --> 00:07:15.826 but if you click on that hosting00:07:15.826 --> 00:07:17.602 requirements and options that should00:07:17.602 --> 00:07:20.282 already be linking to it in that checklist.00:07:20.290 --> 00:07:21.090 Yeah, there we go.00:07:21.090 --> 00:07:22.998 Yeah, it looks like it is OK, great.00:07:22.998 --> 00:07:24.522 Great good deal.00:07:24.522 --> 00:07:27.484 So yeah, that's that's one place.00:07:27.484 --> 00:07:29.914 So so in new clino.00:07:29.920 --> 00:07:31.100 Pretty much like searching00:07:31.100 --> 00:07:31.985 for these keywords.00:07:31.990 --> 00:07:33.999 Here you'll find these documents to be00:07:33.999 --> 00:07:36.708 able to get him over to him pretty quickly,00:07:36.710 --> 00:07:39.014 and if it's a real urgent thing and you're00:07:39.014 --> 00:07:41.129 just really having trouble finding it,00:07:41.130 --> 00:07:42.900 definitely hit up one of the00:07:42.900 --> 00:07:44.080 more senior team members,00:07:44.080 --> 00:07:47.030 but but they should all be be right in here.00:07:47.030 --> 00:07:47.684 Do you, Chris?00:07:47.684 --> 00:07:49.664 Do you want me to have PJ demonstrate00:07:49.664 --> 00:07:52.046 searching in SharePoint real quick too?00:07:52.050 --> 00:07:54.160 Just so they have that?00:07:54.160 --> 00:07:56.320 Under there, yeah, that'll be great.00:07:56.320 --> 00:07:57.190 OK, quick too,00:07:57.190 --> 00:07:59.979 I just 'cause I had to grab my docs00:07:59.979 --> 00:08:02.394 for the first time and they're actually00:08:02.394 --> 00:08:05.499 in like the teams channel like client00:08:05.499 --> 00:08:07.665 facing documentation under the CBI.00:08:07.665 --> 00:08:09.855 Connect there in there too so00:08:09.855 --> 00:08:12.418 they're kind of all over the place.00:08:12.420 --> 00:08:12.799 Yeah,00:08:12.799 --> 00:08:13.178 there.00:08:13.178 --> 00:08:15.073 There's several several copies of00:08:15.073 --> 00:08:17.448 this and I think the main thing00:08:17.448 --> 00:08:20.098 is we just want to make sure we're00:08:20.098 --> 00:08:22.570 getting them the most recent and00:08:22.570 --> 00:08:24.276 up-to-date version 'cause there's00:08:24.276 --> 00:08:26.904 probably copies around that or not.00:08:26.910 --> 00:08:27.933 The most up-to-date,00:08:27.933 --> 00:08:29.297 but anyway not now,00:08:29.300 --> 00:08:31.340 that's that's a good point though,00:08:31.340 --> 00:08:33.422 and thanks for sharing that this00:08:33.422 --> 00:08:35.786 right here is just I wanna show00:08:35.786 --> 00:08:37.586 you guys this because this is00:08:37.586 --> 00:08:40.121 a method that you can use to00:08:40.121 --> 00:08:41.912 like just literally search all00:08:41.912 --> 00:08:43.280 of SharePoint public folders.00:08:43.280 --> 00:08:44.156 Find things so.00:08:44.156 --> 00:08:46.849 PJ will you click up there on the top00:08:46.849 --> 00:08:48.893 so when you first go to SharePoint00:08:48.893 --> 00:08:51.236 it takes you to that landing page00:08:51.236 --> 00:08:53.628 that you were seeing there you have00:08:53.628 --> 00:08:55.408 to actually get into SharePoint.00:08:55.410 --> 00:08:55.902 Anne.00:08:55.902 --> 00:08:58.854 And not the CBI landing page.00:08:58.860 --> 00:09:01.464 So once you actually get into SharePoint,00:09:01.470 --> 00:09:03.810 you may notice.00:09:03.810 --> 00:09:04.674 Up there,00:09:04.674 --> 00:09:08.740 the top is a search bar my seeing that.00:09:08.740 --> 00:09:11.548 Up there in the top in the search,00:09:11.550 --> 00:09:13.650 just type in a posting recommendations.00:09:24.980 --> 00:09:27.400 So you can see there's00:09:27.400 --> 00:09:29.336 there's a few different.00:09:29.340 --> 00:09:32.196 Iterations that come up and you can kind00:09:32.196 --> 00:09:35.269 of see where they live in SharePoint,00:09:35.270 --> 00:09:37.245 so those are the SharePoint00:09:37.245 --> 00:09:39.220 sites which are also teams.00:09:39.220 --> 00:09:42.238 A SharePoint site is a team, same thing,00:09:42.238 --> 00:09:44.830 and so you kind of see like there's00:09:44.906 --> 00:09:46.674 clarity hosting recommendations right00:09:46.674 --> 00:09:49.880 there that was sent to the client.00:09:49.880 --> 00:09:51.232 August 3rd of 2020.00:09:51.232 --> 00:09:53.260 You can almost bet those are00:09:53.330 --> 00:09:55.808 probably pretty current, but yeah,00:09:55.808 --> 00:09:58.566 that that's this is something you guys,00:09:58.570 --> 00:09:59.713 it's it's clarityventures.sharepoint.com.00:09:59.713 --> 00:10:01.999 If you don't already have that00:10:01.999 --> 00:10:03.660 bookmark bookmark that it's it's a.00:10:03.660 --> 00:10:04.928 It's a great resource00:10:04.928 --> 00:10:05.879 because SharePoint teams,00:10:05.880 --> 00:10:07.788 files and OneDrive or their base,00:10:07.790 --> 00:10:09.686 they are all the same thing.00:10:09.690 --> 00:10:11.195 They're all integrated and such00:10:11.195 --> 00:10:13.490 that it's all the same file storage.00:10:13.490 --> 00:10:15.570 So if you don't know where to find00:10:15.570 --> 00:10:17.617 something and you're instead of searching00:10:17.617 --> 00:10:19.825 through each channel or asking somebody,00:10:19.830 --> 00:10:22.133 you can always come here and try00:10:22.133 --> 00:10:24.268 to search for it and find it.00:10:24.270 --> 00:10:25.522 And then, of course,00:10:25.522 --> 00:10:28.094 if you're in doubt if it's the most00:10:28.094 --> 00:10:29.652 up to date version, definitely.00:10:29.652 --> 00:10:30.276 You know,00:10:30.276 --> 00:10:31.836 verify that before you share00:10:31.836 --> 00:10:33.110 it with the client.00:10:33.110 --> 00:10:33.644 But anyway,00:10:33.644 --> 00:10:34.979 any questions about that guys.00:10:38.870 --> 00:10:40.508 One thing I wanted to point out00:10:40.508 --> 00:10:42.358 really fast on the SharePoint I just00:10:42.358 --> 00:10:44.002 to reiterate that 'cause I don't00:10:44.060 --> 00:10:46.344 know if everybody saw, but when you00:10:46.344 --> 00:10:49.320 first go to that there's kind of a.00:10:49.320 --> 00:10:52.083 You can't see it 'cause it's white on white,00:10:52.090 --> 00:10:53.938 but when you first go to00:10:53.938 --> 00:10:54.554 clarityventures.com sharepoint.com,00:10:54.560 --> 00:10:57.110 there's that little button just in00:10:57.110 --> 00:10:59.590 case anybody doesn't know that I00:10:59.590 --> 00:11:02.068 might not be the most intuitive thing.00:11:02.070 --> 00:11:04.414 Yeah, I don't know when that changed either.00:11:04.420 --> 00:11:06.190 That used to be black text.00:11:06.190 --> 00:11:08.534 I don't know why it's white text now,00:11:08.540 --> 00:11:10.598 but that that's a great call out.00:11:10.600 --> 00:11:13.540 Thanks for pointing that out, PJ.00:11:13.540 --> 00:11:15.889 So the link is in the header just to00:11:15.889 --> 00:11:18.409 the right of the clarity logo up there00:11:18.409 --> 00:11:20.984 and you won't be able to see it 'cause00:11:20.984 --> 00:11:23.450 the text is the same color as the background.00:11:23.450 --> 00:11:25.148 But yeah, to get into SharePoint00:11:25.148 --> 00:11:26.280 to really start searching,00:11:26.280 --> 00:11:28.170 you do have to click there like00:11:28.170 --> 00:11:30.240 PJ was saying and you'll see your.00:11:30.240 --> 00:11:31.938 You know it'll change from a00:11:31.938 --> 00:11:33.070 cursor to a pointer.00:11:33.070 --> 00:11:35.044 I mean an arrow to a pointer,00:11:35.050 --> 00:11:35.614 but yeah,00:11:35.614 --> 00:11:37.024 that's a good call out.00:11:39.060 --> 00:11:40.460 So alright, let's let's run00:11:40.460 --> 00:11:41.860 back over to our checklist.00:11:41.860 --> 00:11:43.540 Then guys on a new clean.00:11:43.540 --> 00:11:46.361 Oh, if you don't mind PJ and00:11:46.361 --> 00:11:48.380 thanks again for driving.00:11:48.380 --> 00:11:52.720 Yeah, no problem. OK, great.00:11:52.720 --> 00:11:55.499 So you know, once you do have00:11:55.499 --> 00:11:57.748 the hosting out of the way.00:11:57.750 --> 00:12:01.243 Then there's there's a lot of little00:12:01.243 --> 00:12:04.249 things that have to be in place.00:12:04.250 --> 00:12:07.148 First, before a site is ready00:12:07.148 --> 00:12:08.597 for public consumption,00:12:08.600 --> 00:12:10.968 assuming well number one.00:12:10.968 --> 00:12:13.928 Obviously the client needs to00:12:13.928 --> 00:12:16.986 sign off on the Golive first.00:12:16.990 --> 00:12:19.302 And there is a also in nucla know00:12:19.302 --> 00:12:21.959 if you want to keep this up and00:12:21.959 --> 00:12:24.149 open another tab with new clean00:12:24.149 --> 00:12:26.495 open we've we've already got some00:12:26.495 --> 00:12:28.330 like email templates in here.00:12:28.330 --> 00:12:30.780 This is like a pre launch acknowledgement00:12:30.846 --> 00:12:32.880 so take up the acknowledgement part00:12:32.880 --> 00:12:34.623 just pre launch sample connect00:12:34.623 --> 00:12:36.585 prelaunch letter and it looks like00:12:36.585 --> 00:12:40.420 we've got one for DNN and one for Seth.00:12:40.420 --> 00:12:43.066 As you can see in here,00:12:43.070 --> 00:12:45.280 by replying that you approve,00:12:45.280 --> 00:12:48.272 you are indicating that you have tested an00:12:48.272 --> 00:12:51.029 reviewed your your development integration.00:12:51.030 --> 00:12:55.454 So then that's you know specific for connect.00:12:55.460 --> 00:12:57.674 But that's just to see why a thing and00:12:57.674 --> 00:12:59.808 also gives us that confirmation that,00:12:59.810 --> 00:13:01.472 yeah, the client truly is ready00:13:01.472 --> 00:13:03.289 to go live with this thing.00:13:03.290 --> 00:13:05.342 But there's still a prelaunch checklist00:13:05.342 --> 00:13:07.742 of things that have to be in order00:13:07.742 --> 00:13:10.248 and have to be gone through to make you know,00:13:10.250 --> 00:13:11.700 make sure the sites ready.00:13:11.700 --> 00:13:14.135 So let's jump back over00:13:14.135 --> 00:13:16.083 to the launch checklist.00:13:16.090 --> 00:13:19.038 So moving on down.00:13:19.040 --> 00:13:20.135 As a PM,00:13:20.135 --> 00:13:23.220 when a site's getting ready to go live,00:13:23.220 --> 00:13:25.595 it's time to start thinking00:13:25.595 --> 00:13:27.495 about post launch support.00:13:27.500 --> 00:13:28.580 And historically,00:13:28.580 --> 00:13:33.400 I think we've done a poor to mediocre job.00:13:33.400 --> 00:13:34.621 At including myself,00:13:34.621 --> 00:13:37.063 I'm talking about me too here.00:13:37.070 --> 00:13:39.562 We've done it for to mediocre job00:13:39.562 --> 00:13:41.635 with setting the expectations for00:13:41.635 --> 00:13:44.413 service level agreement an an like.00:13:44.420 --> 00:13:46.856 What's going to happen post launch?00:13:46.860 --> 00:13:49.716 Obviously it's not clarity Zemo to say,00:13:49.720 --> 00:13:51.760 here's your website by Anan.00:13:51.760 --> 00:13:54.208 That just wouldn't be cool anyway.00:13:54.210 --> 00:13:55.026 I mean,00:13:55.026 --> 00:13:57.066 they're definitely going to need00:13:57.066 --> 00:13:59.510 supports and you gotta you gotta,00:13:59.510 --> 00:14:00.382 kind of.00:14:00.382 --> 00:14:02.126 Get there's an SL,00:14:02.130 --> 00:14:03.660 a document that was put together00:14:03.660 --> 00:14:05.541 as well and we should probably put00:14:05.541 --> 00:14:09.000 the link to that in here too, but.00:14:09.000 --> 00:14:10.818 In SharePoint you could probably search00:14:10.818 --> 00:14:12.920 for SLA or service level agreement,00:14:12.920 --> 00:14:15.062 and there's a really good document in00:14:15.062 --> 00:14:17.409 there that goes over the pricing and00:14:17.409 --> 00:14:19.455 the different types of response times,00:14:19.460 --> 00:14:19.790 but.00:14:19.790 --> 00:14:22.760 But it that would be time for the kind00:14:22.844 --> 00:14:25.686 of start letting the client know hey,00:14:25.690 --> 00:14:27.958 we're gonna have to have this conversation.00:14:27.960 --> 00:14:29.252 Here's some different options00:14:29.252 --> 00:14:30.544 to be thinking about,00:14:30.550 --> 00:14:32.944 so that when we do have that call it00:14:32.944 --> 00:14:35.410 can help guide your decision making.00:14:37.560 --> 00:14:41.596 Misty well that clarity S delayed maintenance00:14:41.596 --> 00:14:43.729 agreement that says far more ATI.00:14:43.730 --> 00:14:45.926 Either one of those are current.00:14:48.060 --> 00:14:52.015 I don't believe anything other than the.00:14:52.020 --> 00:14:55.089 Yeah, the title page has their name in it.00:14:55.090 --> 00:14:57.218 Everything else is just00:14:57.218 --> 00:14:59.346 very generic Slas stuff.00:14:59.350 --> 00:15:01.460 So you could take this.00:15:01.460 --> 00:15:03.707 And change the word Lyle to whatever00:15:03.707 --> 00:15:05.790 your project is and and you know.00:15:05.790 --> 00:15:07.070 Make sure that there's.00:15:07.070 --> 00:15:09.372 I don't think there's any others like00:15:09.372 --> 00:15:11.292 you know company names or titles00:15:11.292 --> 00:15:13.409 or anything inside the body of the00:15:13.409 --> 00:15:15.053 document that we need to change,00:15:15.060 --> 00:15:16.600 just mainly that top part.00:15:16.600 --> 00:15:18.742 But that does go over like all00:15:18.742 --> 00:15:20.309 the different options they have,00:15:20.310 --> 00:15:23.400 so if they've got a they've got a site that,00:15:23.400 --> 00:15:25.864 for example, cannot have any downtime at all.00:15:25.870 --> 00:15:27.470 They're probably going to want00:15:27.470 --> 00:15:29.888 to have a Sev 1S LA with us,00:15:29.890 --> 00:15:32.474 which they're going to have to pay a00:15:32.474 --> 00:15:35.206 monthly fee to have that level of service.00:15:35.210 --> 00:15:37.316 Because that means that 24/7 we're00:15:37.316 --> 00:15:39.726 gonna we're gonna jump to get there00:15:39.726 --> 00:15:41.610 and immediately work to get their00:15:41.610 --> 00:15:43.955 site back up at their site goes down.00:15:43.960 --> 00:15:47.520 Or if they have a set 1 issue on their site,00:15:47.520 --> 00:15:49.140 maybe their sites not down,00:15:49.140 --> 00:15:50.508 but a function breaks.00:15:50.508 --> 00:15:52.560 That is the most important feature00:15:52.628 --> 00:15:53.348 on the site.00:15:53.350 --> 00:15:55.852 I mean we we that if they have the00:15:55.852 --> 00:15:58.093 proper agreement with us will drop00:15:58.093 --> 00:16:00.808 everything and jump in there and fix it.00:16:00.810 --> 00:16:03.394 But I mean if they don't now again,00:16:03.400 --> 00:16:05.080 we have been historically kind00:16:05.080 --> 00:16:06.424 of poor at this.00:16:06.430 --> 00:16:07.210 And myself included,00:16:07.210 --> 00:16:09.596 but the we need to get better at this00:16:09.596 --> 00:16:11.381 this this is it really helps with00:16:11.381 --> 00:16:13.459 setting expectations too with the clients,00:16:13.460 --> 00:16:15.580 so they don't just think oh I'm just00:16:15.580 --> 00:16:17.948 going to get all this support for free.00:16:17.950 --> 00:16:19.768 I mean the business can't perform00:16:19.768 --> 00:16:21.507 magic like they're going to have00:16:21.507 --> 00:16:22.447 to pay for support.00:16:22.450 --> 00:16:24.698 We're not going to take advantage of them,00:16:24.700 --> 00:16:26.681 but I mean there are certain things00:16:26.681 --> 00:16:28.630 that they're going to need support for,00:16:28.630 --> 00:16:30.622 so the SL a piece is kind of00:16:30.622 --> 00:16:32.941 important as a PM to make sure that00:16:32.941 --> 00:16:34.467 we start communicating on that00:16:34.467 --> 00:16:35.937 as well prior to launch.00:16:35.940 --> 00:16:37.878 Because once you do launch it.00:16:37.880 --> 00:16:39.480 Ideally you're gonna want to00:16:39.480 --> 00:16:41.619 press them for a decision on that.00:16:41.620 --> 00:16:44.204 Any questions there and I didn't know Chris00:16:44.204 --> 00:16:46.617 if you've got anything to add to that,00:16:46.620 --> 00:16:49.374 otherwise I'll move on to some00:16:49.374 --> 00:16:51.730 other topics around go live.00:16:51.730 --> 00:16:52.936 Thank you OK,00:16:52.936 --> 00:16:55.348 once you so basically it's just00:16:55.348 --> 00:16:57.693 giving them all this information00:16:57.693 --> 00:17:00.477 in in preparation for having those00:17:00.563 --> 00:17:03.428 conversations with them after launch.00:17:03.430 --> 00:17:05.896 DNS access requests from the client00:17:05.896 --> 00:17:08.354 team IP change validation that stuffs00:17:08.354 --> 00:17:10.580 all kind of technical in nature,00:17:10.580 --> 00:17:13.401 but that would be the idea there00:17:13.401 --> 00:17:15.740 is is that we need to.00:17:15.740 --> 00:17:18.980 Basically we need to know who's going to00:17:18.980 --> 00:17:22.085 have control of the DNS tables like where,00:17:22.090 --> 00:17:23.678 where certain domain names00:17:23.678 --> 00:17:25.252 are pointing towards, right?00:17:25.252 --> 00:17:27.926 If that's the client then at go00:17:27.926 --> 00:17:31.519 live at the time of go live when00:17:31.519 --> 00:17:33.347 we're actually switching over.00:17:33.350 --> 00:17:35.426 To what the what?00:17:35.426 --> 00:17:39.040 The live URL is going to be.00:17:39.040 --> 00:17:41.144 You have to do that in with DNS.00:17:41.150 --> 00:17:43.254 So if we have access to that great,00:17:43.260 --> 00:17:47.157 we can do it and and then we're live.00:17:47.160 --> 00:17:50.400 Yes, only one of the things about the00:17:50.400 --> 00:17:53.330 process of the golive is if you can00:17:53.330 --> 00:17:56.289 get the SLA and the hosting going.00:17:56.290 --> 00:17:58.605 Now, especially for I know00:17:58.605 --> 00:18:00.920 there are several projects that00:18:01.003 --> 00:18:03.319 are trying to go live before.00:18:03.320 --> 00:18:05.595 July on July 1st before the June,00:18:05.600 --> 00:18:07.556 let's go ahead and get him.00:18:07.560 --> 00:18:08.514 The SLA agreement.00:18:08.514 --> 00:18:11.140 Let's go ahead and get him the host.00:18:11.140 --> 00:18:13.540 Get them the hosting requirements.00:18:13.540 --> 00:18:15.000 And if you haven't already,00:18:15.000 --> 00:18:17.040 we want to also give them the E00:18:17.040 --> 00:18:18.616 commerce checklist if their site00:18:18.616 --> 00:18:19.960 has some commerce functionality.00:18:19.960 --> 00:18:22.110 These are all things that.00:18:22.110 --> 00:18:24.486 You can do while we're in this call,00:18:24.490 --> 00:18:25.985 you can gather those documents00:18:25.985 --> 00:18:28.120 and get them ready to go ahead00:18:28.120 --> 00:18:29.560 and send to those clients,00:18:29.560 --> 00:18:31.348 even if they've already received them.00:18:31.350 --> 00:18:33.132 It's great as we're getting ready00:18:33.132 --> 00:18:35.519 to go live to go ahead and prep,00:18:35.520 --> 00:18:38.193 then get to a point where we're saying look,00:18:38.200 --> 00:18:40.202 this is just a reminder it doesn't00:18:40.202 --> 00:18:42.334 hurt to double check that you know00:18:42.334 --> 00:18:44.152 you guys have gone through this,00:18:44.160 --> 00:18:46.365 that we've gone through it with you00:18:46.365 --> 00:18:48.302 and we're making sure we're kind00:18:48.302 --> 00:18:50.156 of crossing T's and dotting eyes00:18:50.156 --> 00:18:52.350 on all of these different topics.00:18:52.350 --> 00:18:54.150 If you would like your welcome00:18:54.150 --> 00:18:55.888 to do a review, you know,00:18:55.888 --> 00:18:58.040 put a draft 6bc954e6-a811-4e3e-99b8-e110de4bc3a4 00:18:58.105 --> 00:19:00.505 review with myself or one of the other00:19:00.505 --> 00:19:03.074 leaders on the team so you can get00:19:03.074 --> 00:19:05.250 some feedback before sending in the actual,00:19:05.250 --> 00:19:05.850 no doubt.00:19:05.850 --> 00:19:07.350 But if you gather the00:19:07.350 --> 00:19:08.850 documents and get him ready,00:19:08.850 --> 00:19:10.789 it makes it pretty easy to go00:19:10.789 --> 00:19:12.450 ahead and send those along,00:19:12.450 --> 00:19:14.160 and then you can just draft00:19:14.160 --> 00:19:16.350 a 26414c08-5603-4075-8308-7c1ef89d9f60 00:19:16.350 --> 00:19:18.582 I wanna say that Compania and SSB for00:19:18.582 --> 00:19:21.150 sure are good projects that we need this,00:19:21.150 --> 00:19:24.078 but there are several others as well so.00:19:24.080 --> 00:19:26.152 One of the other big things that00:19:26.152 --> 00:19:28.460 you'll see in the actual checklist,00:19:28.460 --> 00:19:29.471 the e-commerce checklist,00:19:29.471 --> 00:19:31.830 which really is helpful to look at,00:19:31.830 --> 00:19:33.986 or any project you can see several00:19:33.986 --> 00:19:36.209 things that are kind of development,00:19:36.210 --> 00:19:38.226 typically for non e-commerce glad processes,00:19:38.230 --> 00:19:40.252 but one of them that you'll00:19:40.252 --> 00:19:41.600 see relates to DNS,00:19:41.600 --> 00:19:43.575 SSL certificate and basically steps00:19:43.575 --> 00:19:45.893 that might take awhile before they00:19:45.893 --> 00:19:47.567 go like one of the challenges00:19:47.567 --> 00:19:49.019 is not just like hey,00:19:49.020 --> 00:19:52.143 I think we're going to get you know we're00:19:52.143 --> 00:19:55.127 just gonna get all of our code working.00:19:55.130 --> 00:19:56.595 And then we're just going00:19:56.595 --> 00:19:57.767 to testing Ted alot.00:19:57.770 --> 00:19:58.276 So yeah,00:19:58.276 --> 00:20:00.300 it's not like you're gonna get into a00:20:00.363 --> 00:20:02.457 situation where they're just gonna go.00:20:02.460 --> 00:20:04.980 You know all the code is working and then00:20:04.980 --> 00:20:07.438 you just press a button and your life.00:20:07.440 --> 00:20:09.484 There are a lot of tactical things.00:20:09.490 --> 00:20:11.206 Logistical things that we have to00:20:11.206 --> 00:20:12.350 actually complete that includes00:20:12.400 --> 00:20:13.588 getting an SSL certificate,00:20:13.590 --> 00:20:15.252 which depending on what type they00:20:15.252 --> 00:20:17.109 want it might take several days,00:20:17.110 --> 00:20:18.278 even several weeks depending00:20:18.278 --> 00:20:19.446 on the business model,00:20:19.450 --> 00:20:20.950 making sure that their payment00:20:20.950 --> 00:20:23.260 processor is set up a lot of times,00:20:23.260 --> 00:20:25.227 plans like oh, you need it just00:20:25.227 --> 00:20:27.520 to set up a payment processor.00:20:27.520 --> 00:20:30.026 An like testing it in production mode,00:20:30.030 --> 00:20:32.184 so we may already have payment00:20:32.184 --> 00:20:33.620 processor and testing credentials,00:20:33.620 --> 00:20:35.954 but have you tested it in00:20:35.954 --> 00:20:37.902 production mode and usually don't00:20:37.902 --> 00:20:40.086 do a lot of testing on that,00:20:40.090 --> 00:20:42.898 but it's a good idea to test in00:20:42.898 --> 00:20:45.325 production mode before we go live at00:20:45.325 --> 00:20:48.570 some point and the list goes on and so00:20:48.570 --> 00:20:50.856 like another one of those categories00:20:50.860 --> 00:20:52.942 is making sure that the client00:20:52.942 --> 00:20:55.496 owns their domain and that we have00:20:55.496 --> 00:20:57.680 access to change the registrar info,00:20:57.680 --> 00:20:58.874 specifically the actual.00:20:58.874 --> 00:21:00.864 Domain name record for the00:21:00.864 --> 00:21:02.580 A records for the site.00:21:02.580 --> 00:21:04.000 Typically now if you're00:21:04.000 --> 00:21:05.420 not familiar with this,00:21:05.420 --> 00:21:08.236 all you need to know is that whenever00:21:08.236 --> 00:21:11.096 you go to a website in a browser,00:21:11.100 --> 00:21:13.788 the browser is actually resolving the00:21:13.788 --> 00:21:16.664 website that you're typing into an IP00:21:16.664 --> 00:21:19.016 address that the site is pointing at.00:21:19.020 --> 00:21:20.752 And whenever somebody takes00:21:20.752 --> 00:21:22.484 ownership of the domain,00:21:22.490 --> 00:21:23.792 they're actually registering00:21:23.792 --> 00:21:25.528 it with a registrar,00:21:25.530 --> 00:21:28.372 and the registrar's have to go through00:21:28.372 --> 00:21:30.740 certification and provide certain services.00:21:30.740 --> 00:21:32.870 One of those services that00:21:32.870 --> 00:21:35.000 they provide is they actually00:21:35.082 --> 00:21:37.518 provide name server information.00:21:37.520 --> 00:21:41.118 And most of them also provide domain00:21:41.118 --> 00:21:44.856 name servers where you can specify what00:21:44.856 --> 00:21:48.000 server your domain should point to.00:21:48.000 --> 00:21:49.560 It's all very complicated sounding,00:21:49.560 --> 00:21:51.032 but it's really simple.00:21:51.032 --> 00:21:53.240 It's like an address for somebody00:21:53.311 --> 00:21:55.432 you know and it literally is just00:21:55.432 --> 00:21:57.363 an IP address which is unique00:21:57.363 --> 00:21:59.259 and it points to the unique.00:21:59.260 --> 00:22:01.703 Physical set of hardware that's going to00:22:01.703 --> 00:22:04.249 be hosting this particular application.00:22:04.250 --> 00:22:04.912 And again,00:22:04.912 --> 00:22:06.567 without getting into the details,00:22:06.570 --> 00:22:08.544 they have to be able to change00:22:08.544 --> 00:22:11.074 that or give us access so they can00:22:11.074 --> 00:22:13.126 change it or somehow affect that00:22:13.126 --> 00:22:15.370 change through a contractor or a00:22:15.370 --> 00:22:17.162 third party service provider etc.00:22:17.162 --> 00:22:19.148 And what I can tell you,00:22:19.150 --> 00:22:20.848 and I think then you'll agree00:22:20.848 --> 00:22:23.244 these are the kind of things that00:22:23.244 --> 00:22:24.848 really frustrate clients whenever00:22:24.848 --> 00:22:26.759 we're getting ready to go live,00:22:26.760 --> 00:22:28.692 and they realize that their timeline00:22:28.692 --> 00:22:30.752 is blown because of something like00:22:30.752 --> 00:22:32.888 this because they're like you guys00:22:32.888 --> 00:22:34.700 are supposed to be the experts.00:22:36.920 --> 00:22:39.587 For pretty much everyone on the call,00:22:39.590 --> 00:22:41.500 you might be thinking, well,00:22:41.500 --> 00:22:43.410 other people in clarity are00:22:43.410 --> 00:22:45.320 supposed to be the experts.00:22:45.320 --> 00:22:47.230 I'm not the expert yet,00:22:47.230 --> 00:22:48.758 I just got started,00:22:48.758 --> 00:22:50.668 so we're trying to explain.00:22:50.670 --> 00:22:52.580 These are things that are00:22:52.580 --> 00:22:55.446 coming up so you know, we wanna.00:22:55.446 --> 00:22:59.270 We wanna help make sure you understand them.00:22:59.270 --> 00:23:00.179 And more importantly,00:23:00.179 --> 00:23:02.723 we want to make sure that you have00:23:02.723 --> 00:23:04.508 support so that you understand.00:23:04.510 --> 00:23:06.726 You have the whole team at your disposal.00:23:06.730 --> 00:23:08.898 Your job would be to kind of understand00:23:08.898 --> 00:23:10.940 that this is important and it is00:23:10.940 --> 00:23:12.696 urgent timeline wise for some of00:23:12.696 --> 00:23:14.256 these projects that are about to00:23:14.256 --> 00:23:16.570 go live and in fact we need to go00:23:16.570 --> 00:23:18.181 ahead and start meeting with the00:23:18.181 --> 00:23:20.043 client and I always like to talk00:23:20.043 --> 00:23:21.957 about this idea of parallel paths,00:23:21.960 --> 00:23:23.622 so this should be a parallel00:23:23.622 --> 00:23:24.730 path with everything else.00:23:24.730 --> 00:23:26.180 See the wonderful thing about00:23:26.180 --> 00:23:27.630 being the project managers and00:23:27.681 --> 00:23:28.886 get to spin plates right?00:23:28.890 --> 00:23:31.329 So you go spend one plate and then you00:23:31.329 --> 00:23:33.882 go spin the next one and then you go00:23:33.882 --> 00:23:36.487 spin the next one is just never ending.00:23:36.490 --> 00:23:37.414 Signing is awesome.00:23:37.414 --> 00:23:38.954 It's a lot of money.00:23:38.960 --> 00:23:41.172 But so this is a plate that00:23:41.172 --> 00:23:43.290 we need to get spinning.00:23:43.290 --> 00:23:45.770 I just want to add one thing that00:23:45.770 --> 00:23:48.708 so he mentioned a record in there,00:23:48.710 --> 00:23:51.617 which is I just wanted to let you guys00:23:51.617 --> 00:23:54.447 know that stamp that just stands for00:23:54.447 --> 00:23:57.727 address record and all that is is it's it's.00:23:57.730 --> 00:24:00.271 It's the actual record in a public00:24:00.271 --> 00:24:02.429 namespace that resolves that IP address.00:24:02.430 --> 00:24:04.230 So human beings don't remember00:24:04.230 --> 00:24:05.670 strings of numbers well,00:24:05.670 --> 00:24:07.833 so a human friendly name is a00:24:07.833 --> 00:24:10.119 domain and this that's why this00:24:10.119 --> 00:24:12.264 was actually developed is because.00:24:12.270 --> 00:24:14.522 Computers do not communicate.00:24:14.522 --> 00:24:17.337 By domain name they actually00:24:17.337 --> 00:24:19.108 communicate by IP address.00:24:19.110 --> 00:24:23.058 So before TCP communication can take place.00:24:23.060 --> 00:24:25.022 This system has to be able00:24:25.022 --> 00:24:26.770 to take the domain name,00:24:26.770 --> 00:24:28.786 resolve that to an IP address,00:24:28.790 --> 00:24:31.450 and then establish the connection.00:24:31.450 --> 00:24:32.266 Does that make sense?00:24:32.266 --> 00:24:34.052 I just want to add a little bit00:24:34.052 --> 00:24:35.570 of clarification on that to kind00:24:35.570 --> 00:24:36.949 of maybe help crystallize that00:24:36.949 --> 00:24:38.860 concept a little bit for you guys,00:24:38.860 --> 00:24:40.336 because yes, it is very important,00:24:40.340 --> 00:24:41.822 and as the parallel path like00:24:41.822 --> 00:24:42.563 Chris was saying,00:24:42.570 --> 00:24:43.805 this is something I typically00:24:43.805 --> 00:24:45.357 try to have worked out while00:24:45.357 --> 00:24:46.977 development is going on or even00:24:46.977 --> 00:24:48.694 during discovery if I have one of00:24:48.694 --> 00:24:49.972 the technical guys on the call,00:24:49.980 --> 00:24:51.636 that's probably going to be one00:24:51.636 --> 00:24:53.205 of the questions that I will00:24:53.205 --> 00:24:54.417 ask them as so for that.00:24:54.420 --> 00:24:55.992 You know when you when you're00:24:55.992 --> 00:24:57.552 asking them what the domain name00:24:57.552 --> 00:24:59.360 of the new site is going to be.00:24:59.360 --> 00:25:00.836 If that in some cases they00:25:00.836 --> 00:25:01.574 won't already know,00:25:01.580 --> 00:25:03.358 but if they do already know what00:25:03.358 --> 00:25:05.179 they want the domain name to be.00:25:05.180 --> 00:25:07.468 You want to you want to find out00:25:07.468 --> 00:25:09.900 who has access to that registrar.00:25:09.900 --> 00:25:11.248 Is that a contractor?00:25:11.248 --> 00:25:13.270 A one of the guys there?00:25:13.270 --> 00:25:15.349 Is that something that you know we00:25:15.349 --> 00:25:17.403 have to go to another department00:25:17.403 --> 00:25:19.944 there to get done across over the00:25:20.019 --> 00:25:21.358 seas? Because you're an00:25:21.358 --> 00:25:22.030 international company,00:25:22.030 --> 00:25:24.389 you know if you start early though,00:25:24.390 --> 00:25:26.208 it can prevent that piece from00:25:26.208 --> 00:25:28.100 causing a delay on launching.00:25:28.100 --> 00:25:30.116 'cause that is an important piece.00:25:30.120 --> 00:25:33.370 You kind of have to have in line along with00:25:33.451 --> 00:25:36.627 making sure you are covering like the SSL.00:25:36.630 --> 00:25:38.300 Sir, two and getting the00:25:38.300 --> 00:25:39.636 right certification for them.00:25:39.640 --> 00:25:41.638 Depending on the type of project.00:25:41.640 --> 00:25:44.112 So for example, like if you have a00:25:44.112 --> 00:25:45.497 transactional website where you're00:25:45.497 --> 00:25:47.982 taking payments that they typically you know,00:25:47.990 --> 00:25:50.654 don't want you to have like a let's encrypt00:25:50.654 --> 00:25:52.996 cert that expires every three months.00:25:53.000 --> 00:25:54.630 Typically you know they want00:25:54.630 --> 00:25:56.670 you to go with like sect,00:25:56.670 --> 00:25:58.994 ego and have like a three year00:25:58.994 --> 00:26:01.347 SSL cert type of type of thing.00:26:01.350 --> 00:26:02.140 So anyway,00:26:02.140 --> 00:26:04.115 parallel paths is great because00:26:04.115 --> 00:26:06.779 you can you can be doing these00:26:06.779 --> 00:26:09.180 things with the client as the PM.00:26:09.180 --> 00:26:11.225 Wow, the development team is00:26:11.225 --> 00:26:13.694 building out their project so you00:26:13.694 --> 00:26:16.158 get all those things in line and00:26:16.158 --> 00:26:18.280 start rolling into a soft launch.00:26:18.280 --> 00:26:20.877 It can definitely make things a lot00:26:20.877 --> 00:26:23.957 easier and also like any of the providers.00:26:23.960 --> 00:26:25.860 So what is a provider?00:26:25.860 --> 00:26:27.372 Payment provider? Shipping providers?00:26:27.372 --> 00:26:28.128 Tax providers?00:26:28.130 --> 00:26:28.538 Any?00:26:28.538 --> 00:26:30.986 Any providers where we're making calls00:26:30.986 --> 00:26:33.820 to external third party APIs in order to,00:26:33.820 --> 00:26:35.056 like, you know,00:26:35.056 --> 00:26:37.528 determine the taxes or get a00:26:37.528 --> 00:26:39.729 shipping rate quote or to send?00:26:39.730 --> 00:26:41.392 Payment details through a gateway over00:26:41.392 --> 00:26:43.440 the wire to their merchant services,00:26:43.440 --> 00:26:46.113 that sort of thing you we want to make00:26:46.113 --> 00:26:48.684 sure that we've got all that in line.00:26:48.690 --> 00:26:50.922 So what I what I mean by in line00:26:50.922 --> 00:26:53.287 is let me back up a little bit00:26:53.287 --> 00:26:55.374 so this whole time you've been00:26:55.374 --> 00:26:57.648 working on these dev sites dev,00:26:57.650 --> 00:26:59.190 staging and on local and00:26:59.190 --> 00:27:00.422 like for testing purposes.00:27:00.430 --> 00:27:02.534 Most of the time we will have been00:27:02.534 --> 00:27:04.758 using like sandbox or test credentials.00:27:04.760 --> 00:27:06.395 Most payment most providers will00:27:06.395 --> 00:27:08.030 have test credentials that can00:27:08.083 --> 00:27:09.533 be used for development purposes00:27:09.533 --> 00:27:10.983 just to make sure that.00:27:10.990 --> 00:27:11.646 You know,00:27:11.646 --> 00:27:13.614 like like a dummy payment provider00:27:13.614 --> 00:27:15.759 where you just you just put in00:27:15.759 --> 00:27:17.822 like 42424242 and any date in the00:27:17.822 --> 00:27:19.532 future and and it will simulate00:27:19.532 --> 00:27:21.150 making a payment and it creates00:27:21.150 --> 00:27:22.710 a transaction but no money is00:27:22.760 --> 00:27:24.059 actually exchanging hands.00:27:24.060 --> 00:27:25.580 That's where Chris was saying.00:27:25.580 --> 00:27:28.028 Like you want to go into like testing00:27:28.028 --> 00:27:30.449 with the live in live mode as well.00:27:30.450 --> 00:27:32.834 So when and this is where the whole00:27:32.834 --> 00:27:35.308 concept of like a soft launch comes in,00:27:35.310 --> 00:27:36.830 I really like soft launches,00:27:36.830 --> 00:27:38.918 which is the idea of getting the whole00:27:38.918 --> 00:27:40.589 getting the entire application set00:27:40.589 --> 00:27:42.414 up in its production environment.00:27:42.420 --> 00:27:44.492 But not flipping the switch on the00:27:44.492 --> 00:27:46.750 domain name to bring it live until00:27:46.750 --> 00:27:48.706 you've gone through and done these00:27:48.774 --> 00:27:50.919 final validation checks and those00:27:50.919 --> 00:27:53.064 validation checks would include doing00:27:53.070 --> 00:27:55.910 a live payment with an actual credit card.00:27:55.910 --> 00:27:58.395 Not I mean not going crazy with.00:27:58.400 --> 00:28:01.586 I mean it can be a low dollar amount,00:28:01.590 --> 00:28:03.756 but just making sure that that00:28:03.756 --> 00:28:05.636 payment gets processed and is00:28:05.636 --> 00:28:07.128 getting the appropriate responses00:28:07.128 --> 00:28:08.993 back for our system to00:28:09.063 --> 00:28:10.822 do its job. Same with shipping00:28:10.822 --> 00:28:12.984 rate quotes and taxes. Now those,00:28:12.984 --> 00:28:14.844 typically there's the shipping and.00:28:14.850 --> 00:28:16.780 Taxes, stuff you're not exchanging00:28:16.780 --> 00:28:17.938 credit card information,00:28:17.940 --> 00:28:20.250 so it's not as applicable there,00:28:20.250 --> 00:28:22.180 but with the payment piece.00:28:22.180 --> 00:28:25.654 Yeah, test mode in live mode is a thing,00:28:25.660 --> 00:28:28.846 and we do want to actually test live mode00:28:28.846 --> 00:28:32.697 two once we get it into the production00:28:32.697 --> 00:28:34.646 environment before actually flipping00:28:34.646 --> 00:28:39.270 the switch on the DNS. Let's see.00:28:39.270 --> 00:28:41.574 Some other things that you're going00:28:41.574 --> 00:28:44.597 to want to bring up prior to launch,00:28:44.600 --> 00:28:46.682 and then again after launch is00:28:46.682 --> 00:28:48.800 going into like server hardening,00:28:48.800 --> 00:28:49.560 security optimization.00:28:49.560 --> 00:28:50.700 Things like that.00:28:50.700 --> 00:28:52.986 Like before, the site actually is,00:28:52.990 --> 00:28:54.570 is online and live.00:28:54.570 --> 00:28:56.940 You don't want to the moment00:28:57.025 --> 00:28:59.328 you bring a site live and it's00:28:59.328 --> 00:29:02.129 on on the in the public domain,00:29:02.130 --> 00:29:06.146 you guys would not believe the number of.00:29:06.150 --> 00:29:08.520 Attempts to.00:29:08.520 --> 00:29:10.650 Break that machine and hack into00:29:10.650 --> 00:29:12.899 that machine and maybe put ransomware00:29:12.899 --> 00:29:15.173 or something like that on there.00:29:15.180 --> 00:29:17.770 It happens like so many within a00:29:17.770 --> 00:29:19.989 couple minutes of it being live.00:29:19.990 --> 00:29:22.150 I guarantee there will be either00:29:22.150 --> 00:29:24.060 a botnet or a hack.00:29:24.060 --> 00:29:26.256 An actual hacker himself in there00:29:26.256 --> 00:29:28.499 trying to get into that site,00:29:28.500 --> 00:29:30.594 so security making sure that the00:29:30.594 --> 00:29:32.448 site is secured before switching00:29:32.448 --> 00:29:34.788 over the DNS is really important.00:29:34.790 --> 00:29:37.526 So with that for the devs there and00:29:37.526 --> 00:29:40.038 for whoever is doing the deployment.00:29:40.040 --> 00:29:42.338 That the technical side of things00:29:42.338 --> 00:29:43.487 we actually have.00:29:43.490 --> 00:29:45.620 A server hardening checklist for00:29:45.620 --> 00:29:48.504 each of our platforms that we go00:29:48.504 --> 00:29:50.538 through an an implement to make00:29:50.538 --> 00:29:53.135 sure that that the server is locked00:29:53.135 --> 00:29:55.746 down and then in addition to that00:29:55.746 --> 00:29:57.823 part of that checklist, includes.00:29:57.823 --> 00:30:01.624 Going in and changing any dev passwords,00:30:01.630 --> 00:30:03.130 cleansing any test data.00:30:03.130 --> 00:30:05.380 Out of the database getting and00:30:05.448 --> 00:30:07.416 going in and making sure that00:30:07.416 --> 00:30:10.110 like any users that we have like a00:30:10.110 --> 00:30:12.078 password policy in place and we're00:30:12.080 --> 00:30:13.910 just not using like weak passwords,00:30:13.910 --> 00:30:15.110 that's a big thing.00:30:15.110 --> 00:30:17.583 And that kind of leads me into my00:30:17.583 --> 00:30:19.983 other point that I started to hit on,00:30:19.990 --> 00:30:22.717 but I realized was kind of a separate topic,00:30:22.720 --> 00:30:24.550 but still is a part of.00:30:24.550 --> 00:30:26.368 This is around the data too.00:30:26.370 --> 00:30:26.978 I mean,00:30:26.978 --> 00:30:29.106 it doesn't necessarily make a site insecure,00:30:29.110 --> 00:30:31.894 but you also want to make sure that00:30:31.894 --> 00:30:34.677 it's optimized in terms of its data as well.00:30:34.680 --> 00:30:36.912 And it's ready to start receiving00:30:36.912 --> 00:30:38.400 actual live production data.00:30:38.400 --> 00:30:40.647 So if you have an integration going00:30:40.647 --> 00:30:43.256 on that that may mean that you're00:30:43.256 --> 00:30:45.620 switching over from the client sandbox00:30:45.696 --> 00:30:48.440 ERP environment to their actual live ERP,00:30:48.440 --> 00:30:51.163 and then you want to validate that00:30:51.163 --> 00:30:53.089 it's actually pulling in live00:30:53.089 --> 00:30:55.135 customer data an in this within00:30:55.135 --> 00:30:57.000 the scope of your project.00:30:57.000 --> 00:30:58.032 Of course,00:30:58.032 --> 00:30:59.580 I mean that.00:30:59.580 --> 00:31:01.045 If you're syncing sales orders00:31:01.045 --> 00:31:02.217 and you're syncing inventory,00:31:02.220 --> 00:31:03.865 you know you want to test those00:31:03.865 --> 00:31:05.732 things and it outside of the00:31:05.732 --> 00:31:07.200 sandbox environment before launch.00:31:07.200 --> 00:31:08.880 The last thing you want to00:31:08.880 --> 00:31:10.420 do is bring in well.00:31:10.420 --> 00:31:13.630 You kind of talk about like.00:31:13.630 --> 00:31:15.448 How to what extent you can00:31:15.448 --> 00:31:16.660 count on the development00:31:16.723 --> 00:31:18.091 team members to be00:31:18.091 --> 00:31:19.459 responsible for doing that?00:31:19.460 --> 00:31:22.295 I know it depends on the different00:31:22.295 --> 00:31:25.076 personalities and kind of how they treat it.00:31:25.080 --> 00:31:26.180 Yeah, what's your experience?00:31:26.180 --> 00:31:27.648 Been there? My experience has00:31:27.648 --> 00:31:29.484 been that it really does require00:31:29.484 --> 00:31:31.677 2 to a high degree of just a lot.00:31:31.680 --> 00:31:34.430 You do have to press on them to do this,00:31:34.430 --> 00:31:35.810 'cause they're not going to.00:31:35.810 --> 00:31:38.258 Most of the devs won't remember.00:31:38.260 --> 00:31:39.176 To to do this?00:31:39.176 --> 00:31:40.909 This is a detail that you guys00:31:40.909 --> 00:31:42.679 really need to remember as PMS.00:31:42.680 --> 00:31:44.577 Obviously you don't have to perform the00:31:44.577 --> 00:31:46.318 task of cleaning out the test data,00:31:46.320 --> 00:31:48.064 but you need to make sure we at00:31:48.064 --> 00:31:49.700 least have a ticket assigned an00:31:49.700 --> 00:31:51.416 that the importance of that ticket00:31:51.468 --> 00:31:53.076 is made known to the developer.00:31:53.080 --> 00:31:53.600 I mean,00:31:53.600 --> 00:31:55.680 that's just something that has to be done.00:31:55.680 --> 00:31:57.366 My experience has been that if00:31:57.366 --> 00:31:59.060 you don't tell them to do it,00:31:59.060 --> 00:32:00.638 they won't do it and they00:32:00.638 --> 00:32:01.920 won't remember to do it.00:32:01.920 --> 00:32:02.436 It's there,00:32:02.436 --> 00:32:03.984 you know they were worrying about00:32:03.984 --> 00:32:05.309 development and in the software00:32:05.309 --> 00:32:06.579 getting done and working and00:32:06.579 --> 00:32:07.640 then completing the tickets,00:32:07.640 --> 00:32:09.266 we need to be worrying about.00:32:09.270 --> 00:32:10.680 When those tickets are complete,00:32:10.680 --> 00:32:12.605 do we have all these little high00:32:12.605 --> 00:32:14.596 level pieces in place for the site00:32:14.596 --> 00:32:16.600 to operate smoothly as an end user?00:32:16.600 --> 00:32:18.652 Am I going to be able to go in00:32:18.652 --> 00:32:20.929 and do the things that This site00:32:20.929 --> 00:32:22.520 is been developed to do?00:32:22.520 --> 00:32:24.776 So yeah, that definitely is something as PM.00:32:24.780 --> 00:32:26.474 You guys need to press on as00:32:26.474 --> 00:32:28.159 that also been your experience.00:32:28.160 --> 00:32:29.288 You are absolutely OK.00:32:29.288 --> 00:32:33.298 Alright, I was like I mean just making sure.00:32:33.300 --> 00:32:35.340 Years later, working on the project,00:32:35.340 --> 00:32:36.411 but generally speaking.00:32:36.411 --> 00:32:38.196 There's kind of like this00:32:38.196 --> 00:32:40.450 endorphin head that you get through00:32:40.450 --> 00:32:41.926 development work and development00:32:41.926 --> 00:32:43.950 team members kind of leave it that.00:32:43.950 --> 00:32:46.713 It's kind of like I don't know for me.00:32:46.720 --> 00:32:48.490 Sometimes I do honey do's around00:32:48.490 --> 00:32:50.669 the house on the weekend and like00:32:50.669 --> 00:32:52.860 once I get the first honeydew done,00:32:52.860 --> 00:32:54.390 I forget about the last.00:32:54.390 --> 00:32:54.998 You know,00:32:54.998 --> 00:32:56.518 there are three more that00:32:56.518 --> 00:32:58.079 are left on the list,00:32:58.080 --> 00:33:01.027 but I'm just so happy because Jessica00:33:01.027 --> 00:33:03.620 surprised that I didn't anything.00:33:03.620 --> 00:33:05.630 Feedback.00:33:05.630 --> 00:33:09.130 It sounds like it's so great, honey.00:33:09.130 --> 00:33:10.620 433 more things to do,00:33:10.620 --> 00:33:12.100 and that's how developers are.00:33:12.100 --> 00:33:13.942 It's like they're just like so00:33:13.942 --> 00:33:16.067 glad that they got the site to00:33:16.067 --> 00:33:17.735 where it's about to go live,00:33:17.740 --> 00:33:18.649 and they're not.00:33:18.649 --> 00:33:20.467 They don't still have the mental00:33:20.467 --> 00:33:22.188 energy that makes sense to kind00:33:22.188 --> 00:33:23.980 of think about those next things.00:33:23.980 --> 00:33:26.227 That's really the role of the PM00:33:26.227 --> 00:33:28.758 is to kind of be looking ahead.00:33:28.760 --> 00:33:30.770 And thinking ahead and kind of00:33:30.770 --> 00:33:32.514 pressing and it almost being00:33:32.514 --> 00:33:33.878 a little bit cynical.00:33:33.880 --> 00:33:36.336 I mean you don't need to share that00:33:36.336 --> 00:33:38.650 cynicism with the team members directly.00:33:38.650 --> 00:33:40.940 You can be cynical privately, I agree.00:33:40.940 --> 00:33:41.530 Yeah, absolutely.00:33:41.530 --> 00:33:44.158 And I also say that that's probably one00:33:44.158 --> 00:33:46.148 of the most critical characteristics,00:33:46.150 --> 00:33:46.504 right?00:33:46.504 --> 00:33:48.628 I mean, isn't that the whole00:33:48.628 --> 00:33:50.578 trust but verify thing it is?00:33:50.580 --> 00:33:51.628 Yep, so.00:33:51.628 --> 00:33:53.200 And it's really.00:33:53.200 --> 00:33:55.450 It's really a key thing because00:33:55.450 --> 00:33:56.950 your satisfaction in this00:33:57.019 --> 00:33:59.059 role will dramatically improve.00:33:59.060 --> 00:34:01.160 If you can understand that00:34:01.160 --> 00:34:02.420 development team members,00:34:02.420 --> 00:34:05.340 they just by the nature of the role00:34:05.340 --> 00:34:08.431 that they had there really laser00:34:08.431 --> 00:34:10.703 focused on something microscopic.00:34:10.710 --> 00:34:12.505 And whenever they're telling you00:34:12.505 --> 00:34:14.950 that it's working or is all done,00:34:14.950 --> 00:34:17.056 or anything like that, you know.00:34:17.060 --> 00:34:17.768 Generally speaking,00:34:17.768 --> 00:34:19.538 that's true of very specific,00:34:19.540 --> 00:34:22.004 focused you know pathway through the system,00:34:22.010 --> 00:34:24.292 but they almost never thinking about the00:34:24.292 --> 00:34:26.828 big picture and almost never taking into00:34:26.828 --> 00:34:29.066 account all of the different scenarios.00:34:29.070 --> 00:34:29.744 And again,00:34:29.744 --> 00:34:32.950 you know this is kind of a beautiful thing,00:34:32.950 --> 00:34:35.470 because if you're talking with the client00:34:35.470 --> 00:34:37.540 and explaining these things up front,00:34:37.540 --> 00:34:38.824 you can start now.00:34:38.824 --> 00:34:40.750 You can start massage ING this00:34:40.823 --> 00:34:42.527 into the conversation and.00:34:42.530 --> 00:34:44.468 Letting them know you know these00:34:44.468 --> 00:34:46.995 are things that are going to come up00:34:46.995 --> 00:34:49.000 and then whenever they do come up,00:34:49.000 --> 00:34:51.121 it's like you're the hero instead of00:34:51.121 --> 00:34:53.296 you making you know, sharing bad news.00:34:53.296 --> 00:34:55.108 It's kind of like a default00:34:55.108 --> 00:34:56.389 assumption and it's amazing.00:34:56.390 --> 00:34:58.232 It's a major kind of fallacy00:34:58.232 --> 00:34:59.153 of thought unfortunately.00:34:59.160 --> 00:35:01.316 But like if we don't say anything,00:35:01.320 --> 00:35:03.822 the client just gonna assume that00:35:03.822 --> 00:35:06.539 everything is going to go perfectly.00:35:06.540 --> 00:35:08.583 And so if you do say things and you00:35:08.583 --> 00:35:10.672 do kind of set the table and show00:35:10.672 --> 00:35:12.880 how many you know placemats are out,00:35:12.880 --> 00:35:13.936 they're gonna realize, oh,00:35:13.936 --> 00:35:15.520 they're going to be more guests.00:35:15.520 --> 00:35:17.098 It's not just you and me,00:35:17.100 --> 00:35:19.130 you know it's going to be security00:35:19.130 --> 00:35:20.939 and performance and SCO or going to00:35:20.939 --> 00:35:22.910 be joining us for this go live event.00:35:22.910 --> 00:35:24.488 But if you don't do that,00:35:24.490 --> 00:35:26.866 then they they kind of are like oh man,00:35:26.870 --> 00:35:29.147 I thought it was gonna be you and me00:35:29.147 --> 00:35:30.985 hanging out but have to deal with00:35:30.985 --> 00:35:32.938 all this other fun stuff. Dang it.00:35:32.938 --> 00:35:34.742 So yeah. Anyway, back over to you.00:35:34.742 --> 00:35:36.830 No no that's great and that actually.00:35:36.830 --> 00:35:39.278 Is a great segue in and to one of00:35:39.278 --> 00:35:41.785 the so I'll I'll touch real quick00:35:41.785 --> 00:35:43.225 on the pen testing,00:35:43.230 --> 00:35:45.750 but then I want to go into how the00:35:45.750 --> 00:35:47.845 SCO persona comes to the table00:35:47.845 --> 00:35:49.950 as well to come play now.00:35:49.950 --> 00:35:51.810 Clarity would make the recommendation00:35:51.810 --> 00:35:54.244 of a security pen test that may00:35:54.244 --> 00:35:56.029 or may not be in the budget.00:35:56.030 --> 00:35:58.340 It may have been budgeted in the00:35:58.340 --> 00:36:00.190 initial proposal that may not have,00:36:00.190 --> 00:36:00.590 nonetheless,00:36:00.590 --> 00:36:04.580 whether it we have the budget for it or not.00:36:04.580 --> 00:36:07.836 We are not doing our due diligence unless00:36:07.836 --> 00:36:10.840 we recommend that the site be pen tested.00:36:10.840 --> 00:36:12.448 OK, there's a lot of third00:36:12.448 --> 00:36:13.520 party applications out there,00:36:13.520 --> 00:36:15.396 like Kuala SIS and gosh, I can't.00:36:15.396 --> 00:36:16.468 There's several of them.00:36:16.470 --> 00:36:18.048 I can't think of the names00:36:18.048 --> 00:36:19.680 off the top of my head,00:36:19.680 --> 00:36:21.030 but nonetheless just know that00:36:21.030 --> 00:36:22.630 if the client agrees to say,00:36:22.630 --> 00:36:23.392 Oh yeah, yeah,00:36:23.392 --> 00:36:24.916 we need to pentest then then00:36:24.916 --> 00:36:26.628 it turns into just, you know,00:36:26.628 --> 00:36:28.152 checking the budget if we have00:36:28.152 --> 00:36:29.329 it in the budget,00:36:29.330 --> 00:36:30.310 great get it done.00:36:30.310 --> 00:36:32.099 If we don't then you know give00:36:32.099 --> 00:36:33.891 him and kind of an estimate from00:36:33.891 --> 00:36:35.337 Chris or myself for whomever00:36:35.337 --> 00:36:37.367 from our side would be doing it.00:36:37.370 --> 00:36:39.514 Or they may have it team members there.00:36:39.520 --> 00:36:42.304 I mean, a lot of cases, some of these big.00:36:42.304 --> 00:36:43.784 Businesses that hire clarity to00:36:43.784 --> 00:36:45.358 consult and build their project.00:36:45.360 --> 00:36:47.355 They may have a department there that's00:36:47.355 --> 00:36:49.390 fully capable of pentesting their site,00:36:49.390 --> 00:36:51.820 which has been the case with many banks and00:36:51.820 --> 00:36:54.038 larger corporations that I've worked with,00:36:54.040 --> 00:36:56.488 in which case they may run a security00:36:56.488 --> 00:36:59.310 scan and come back with a report and say,00:36:59.310 --> 00:37:00.860 yeah, we found these issues.00:37:00.860 --> 00:37:02.720 We want the critical ones fixed.00:37:02.720 --> 00:37:04.905 Don't worry about these medium00:37:04.905 --> 00:37:06.653 and low priority issues.00:37:06.660 --> 00:37:07.452 That's right,00:37:07.452 --> 00:37:10.620 and then just to chime in on that,00:37:10.620 --> 00:37:13.356 we have a couple of documents that are00:37:13.356 --> 00:37:15.700 similar to the hosting requirements00:37:15.700 --> 00:37:18.880 documents that basically go over security00:37:18.880 --> 00:37:21.508 hardening as well as end testing tools.00:37:21.510 --> 00:37:22.590 That are automated,00:37:22.590 --> 00:37:26.070 so we have a list of kind of recommended00:37:26.070 --> 00:37:29.150 tools that they can use to reference00:37:29.150 --> 00:37:32.388 and kind of getting overview an again.00:37:32.390 --> 00:37:35.306 The thing that I would ask for you to00:37:35.306 --> 00:37:37.841 take away if your eyes are glossing00:37:37.841 --> 00:37:41.037 over at all and you're like this much.00:37:41.040 --> 00:37:42.560 Just know that you.00:37:42.560 --> 00:37:45.929 You now know that they're all these things,00:37:45.930 --> 00:37:46.185 right?00:37:46.185 --> 00:37:48.480 And you know where to find a list of00:37:48.548 --> 00:37:50.936 them were asking to take responsibility00:37:50.936 --> 00:37:53.228 for coordinating and making sure that00:37:53.228 --> 00:37:55.447 the client and the experts at clarity,00:37:55.450 --> 00:37:57.085 which overtime you must become00:37:57.085 --> 00:37:58.393 an expert in many,00:37:58.400 --> 00:38:00.368 if not all of these topics.00:38:00.370 --> 00:38:01.360 But for now,00:38:01.360 --> 00:38:04.300 the other team members that you can live in.00:38:04.300 --> 00:38:06.420 Do you go ahead and get involved and00:38:06.420 --> 00:38:08.279 we start having these conversations00:38:08.279 --> 00:38:09.545 with the client.00:38:12.230 --> 00:38:14.687 Absolutely and no. You guys have support.00:38:14.690 --> 00:38:17.498 I mean, this is. I can't reiterate enough.00:38:17.500 --> 00:38:19.250 This is a team effort.00:38:19.250 --> 00:38:22.310 The the level of degree at which we are00:38:22.310 --> 00:38:24.803 developing applications and B to BE commerce00:38:24.803 --> 00:38:28.030 sites and all the other projects that we do,00:38:28.030 --> 00:38:28.730 integrations included.00:38:28.730 --> 00:38:32.148 There are no small feat. It takes a team.00:38:32.148 --> 00:38:35.589 To to succeed at these things, and so you00:38:35.589 --> 00:38:38.590 above all know you mean you have resources.00:38:38.590 --> 00:38:41.089 The deal is just like Chris said.00:38:41.090 --> 00:38:44.354 Now you know there are all these things00:38:44.354 --> 00:38:47.919 that have to be checked off before launch.00:38:47.920 --> 00:38:50.195 Until you get really comfortable with it.00:38:50.200 --> 00:38:52.496 I mean you have a checklist and you00:38:52.496 --> 00:38:54.750 have several senior team members myself,00:38:54.750 --> 00:38:56.375 Chris, and several others that00:38:56.375 --> 00:38:58.000 have had experience with this.00:38:58.000 --> 00:38:59.620 That can certainly help please.00:38:59.620 --> 00:39:02.545 I like bring me on to calls like Christmas,00:39:02.550 --> 00:39:05.198 saying early on and then like bring us00:39:05.198 --> 00:39:07.972 into calls we were happy to jump on and00:39:07.972 --> 00:39:10.605 and consult as the experts and until you00:39:10.605 --> 00:39:13.275 get to that degree where you feel like,00:39:13.275 --> 00:39:15.550 yeah I can give that expert advice.00:39:15.550 --> 00:39:17.300 I feel confident giving that00:39:17.300 --> 00:39:18.700 advice Chris does too.00:39:18.700 --> 00:39:19.495 Kevin, several others.00:39:19.495 --> 00:39:21.350 Just feel free to schedule us in00:39:21.406 --> 00:39:23.023 with your clients when it comes to00:39:23.023 --> 00:39:25.101 that point so that we can really00:39:25.101 --> 00:39:26.429 provide that expert recommendations.00:39:26.430 --> 00:39:27.032 So really,00:39:27.032 --> 00:39:29.139 it's just knowing that these things are00:39:29.139 --> 00:39:31.199 here and rallying the right resources is00:39:31.199 --> 00:39:33.596 what I would say at the end of the day.00:39:35.690 --> 00:39:39.850 Here's just an example of.00:39:39.850 --> 00:39:41.450 This is a DNN.00:39:41.450 --> 00:39:42.650 Tuning hardening guide.00:39:42.650 --> 00:39:43.990 We've got one for Seth,00:39:43.990 --> 00:39:46.134 and then I know like I've seen it,00:39:46.140 --> 00:39:48.300 I couldn't remember the name of the document,00:39:48.300 --> 00:39:50.550 Chris, but there was one that.00:39:50.550 --> 00:39:51.960 That literally had a list of00:39:51.960 --> 00:39:52.665 several different pentest00:39:52.665 --> 00:39:53.839 tools and things that we use,00:39:53.840 --> 00:39:56.216 and then you then you have like a.00:39:56.220 --> 00:39:58.978 Like a 40 or 50 item checklist00:39:58.978 --> 00:40:00.160 specifically for that,00:40:00.160 --> 00:40:04.094 I remember seeing that at one point.00:40:04.100 --> 00:40:05.724 So I mean, we've got the tools00:40:05.724 --> 00:40:07.622 guys and it's just a matter of00:40:07.622 --> 00:40:10.400 engaging the right team members, so.00:40:10.400 --> 00:40:11.500 And if you're curious,00:40:11.500 --> 00:40:13.709 just just for you know your own sake,00:40:13.710 --> 00:40:15.790 you just want to go in and kind00:40:15.790 --> 00:40:17.846 of look at some of this stuff.00:40:17.850 --> 00:40:19.310 I mean, there's some interesting00:40:19.310 --> 00:40:21.588 things in here as far as like what00:40:21.588 --> 00:40:23.366 we actually do to harden a server.00:40:23.370 --> 00:40:25.026 There's actually quite a bit involved.00:40:25.030 --> 00:40:26.119 This is about.00:40:26.119 --> 00:40:29.270 It usually takes me about an hour or two,00:40:29.270 --> 00:40:30.830 sometimes longer to you know.00:40:30.830 --> 00:40:33.318 Just make sure we get all this done.00:40:33.320 --> 00:40:34.568 Otherwise you're leaving a00:40:34.568 --> 00:40:35.816 system vulnerable to attack,00:40:35.820 --> 00:40:37.004 which is not good.00:40:37.004 --> 00:40:39.250 So then going into my next point,00:40:39.250 --> 00:40:40.996 'cause I know it's 436 an00:40:40.996 --> 00:40:42.680 there's still a few things.00:40:42.680 --> 00:40:45.176 I mean there's so much to unpack here,00:40:45.180 --> 00:40:48.260 but I'm trying to get the high points.00:40:48.260 --> 00:40:49.685 Efesios is also.00:40:49.685 --> 00:40:50.160 Obviously,00:40:50.160 --> 00:40:52.535 most marketing departments like anyone00:40:52.535 --> 00:40:55.554 just like if SCO is not important to them,00:40:55.560 --> 00:40:58.080 then why are you building a website you00:40:58.080 --> 00:41:00.790 don't want to bring people to your website?00:41:00.790 --> 00:41:02.420 OK, well that's silly anyway.00:41:02.420 --> 00:41:03.320 So with SCO,00:41:03.320 --> 00:41:06.020 like you may be doing a redesign project,00:41:06.020 --> 00:41:08.468 one of the things to think about there00:41:08.468 --> 00:41:10.916 that I check in is 301 redirects.00:41:10.920 --> 00:41:13.863 So let me talk a little bit about why,00:41:13.870 --> 00:41:16.159 why 301 redirects and why that's important.00:41:16.160 --> 00:41:18.086 So let's say you're doing a00:41:18.086 --> 00:41:19.750 redesign of an existing site,00:41:19.750 --> 00:41:21.856 so they've already got the domain.00:41:21.860 --> 00:41:24.569 And their old sites up and live and go00:41:24.569 --> 00:41:27.040 live event is actually going to be.00:41:27.040 --> 00:41:29.656 Pointing that domain at the new site once,00:41:29.660 --> 00:41:30.312 that's time.00:41:30.312 --> 00:41:34.150 Once it's time to go live, right?00:41:34.150 --> 00:41:37.377 What's gonna happen to all of those?00:41:37.380 --> 00:41:39.940 All of that indexing that Google is done00:41:39.940 --> 00:41:42.579 now for those of you that don't know,00:41:42.580 --> 00:41:44.205 Google actually has an indexing00:41:44.205 --> 00:41:45.180 budget for everyone.00:41:45.180 --> 00:41:47.190 They will only crawl so much00:41:47.190 --> 00:41:49.523 of your site and index so much00:41:49.523 --> 00:41:51.359 of your site at a time.00:41:51.360 --> 00:41:52.980 It takes Google forever to00:41:52.980 --> 00:41:54.276 index an entire site,00:41:54.280 --> 00:41:56.164 and they're kind of picky about00:41:56.164 --> 00:41:58.508 some of the pages that they index.00:41:58.510 --> 00:42:00.958 They won't index the page if it gets00:42:00.958 --> 00:42:03.380 a certain score when the page loads,00:42:03.380 --> 00:42:05.330 and it's just another important topic,00:42:05.330 --> 00:42:07.930 so I'm kind of digressing a little bit.00:42:07.930 --> 00:42:10.818 But anyway, my point is with the 301.00:42:10.820 --> 00:42:12.712 Redirects is they've gained00:42:12.712 --> 00:42:15.077 all of this SEO value.00:42:15.080 --> 00:42:16.300 With their current site,00:42:16.300 --> 00:42:18.130 wouldn't you want to preserve that?00:42:18.130 --> 00:42:19.045 Yeah, you do.00:42:19.045 --> 00:42:21.180 You want to preserve that for sure.00:42:21.180 --> 00:42:23.760 You lose all of that value in all of that00:42:23.830 --> 00:42:26.670 time that has been spent getting those pages.00:42:26.670 --> 00:42:28.200 Those routes to your site,00:42:28.200 --> 00:42:30.030 indexed and searchable on the web.00:42:30.030 --> 00:42:32.865 You don't want to lose that value.00:42:32.870 --> 00:42:35.970 So what we do and we have, you know,00:42:35.970 --> 00:42:38.530 we kind of have to put this in00:42:38.616 --> 00:42:40.938 in the clients hands as well.00:42:40.940 --> 00:42:43.684 I mean, it's kind of on them a00:42:43.684 --> 00:42:46.208 little bit little bit on us too,00:42:46.210 --> 00:42:48.667 depending on the budget in the project.00:42:48.670 --> 00:42:50.854 But the idea being that before we00:42:50.854 --> 00:42:53.083 flip the switch and bring the site00:42:53.083 --> 00:42:55.451 live and we need to implement 301 00:42:55.451 --> 00:42:57.786 redirects which are permanent redirects,00:42:57.790 --> 00:42:59.194 there's a 302 redirect.00:42:59.194 --> 00:43:00.598 That's a temporary redirect,00:43:00.600 --> 00:43:02.220 but 301 is permanent.00:43:02.220 --> 00:43:03.435 Anan whenever Google.00:43:03.440 --> 00:43:05.596 Whenever you set these 301 redirects up,00:43:05.600 --> 00:43:07.120 Google will see that those00:43:07.120 --> 00:43:08.980 links don't go to a 404,00:43:08.980 --> 00:43:10.660 which would be what would the00:43:10.660 --> 00:43:12.849 problem would be is that you bring00:43:12.849 --> 00:43:14.529 the site live without redirects,00:43:14.530 --> 00:43:17.293 those old routes would now go to a 404.00:43:17.300 --> 00:43:18.840 So Google's throwing up search00:43:18.840 --> 00:43:20.380 results that don't lead anywhere,00:43:20.380 --> 00:43:21.920 and Google doesn't like that,00:43:21.920 --> 00:43:23.460 so they'll pull your index00:43:23.460 --> 00:43:25.000 down real fast if they.00:43:25.000 --> 00:43:26.848 If there's a bunch of four,00:43:26.850 --> 00:43:28.692 oh fours that are getting hit00:43:28.692 --> 00:43:30.300 the 301 redirects, prevent that,00:43:30.300 --> 00:43:32.680 and Google knows that that is a00:43:32.680 --> 00:43:34.570 permanent redirect to a new route.00:43:34.570 --> 00:43:37.034 And it lets you keep the same that00:43:37.034 --> 00:43:39.120 SCO value that you had before.00:43:39.120 --> 00:43:40.089 So, for example,00:43:40.089 --> 00:43:42.027 you may have a resources link00:43:42.027 --> 00:43:44.502 from your old site that goes to a00:43:44.502 --> 00:43:46.599 resource page with lots of documents.00:43:46.600 --> 00:43:48.550 And now we've got this revised,00:43:48.550 --> 00:43:49.230 refactored, revised,00:43:49.230 --> 00:43:49.570 new,00:43:49.570 --> 00:43:52.449 and modern one that we're going live with an.00:43:52.450 --> 00:43:54.400 It's probably the exact same thing,00:43:54.400 --> 00:43:56.339 but maybe they wanted to do the00:43:56.339 --> 00:43:57.970 routing a bit differently.00:43:57.970 --> 00:44:00.245 You just do a 301 redirect inside00:44:00.245 --> 00:44:01.220 the new site,00:44:01.220 --> 00:44:03.516 so that if anyone tries to hit00:44:03.516 --> 00:44:04.920 that server with that.00:44:04.920 --> 00:44:07.152 Route it will redirect it to the new00:44:07.152 --> 00:44:09.329 page and that preserves the value.00:44:09.330 --> 00:44:11.577 Does anyone have any questions about that00:44:11.577 --> 00:44:14.360 I I don't know if that makes 100% sense.00:44:14.360 --> 00:44:16.160 It sounds like it does coming00:44:16.160 --> 00:44:17.520 out of my mouth,00:44:17.520 --> 00:44:19.504 but I just want to make sure if00:44:19.504 --> 00:44:21.618 there's any clarification needed there.00:44:24.800 --> 00:44:26.128 Biggest the biggest thing.00:44:26.128 --> 00:44:28.972 A lot of these topics is there like00:44:28.972 --> 00:44:31.318 entire sessions in and of themselves.00:44:31.320 --> 00:44:33.856 Yeah, a lot of them are probably more00:44:33.856 --> 00:44:36.019 technical than you'll necessarily need,00:44:36.020 --> 00:44:38.477 so I would just encourage you that00:44:38.477 --> 00:44:41.114 if you are interested in any of00:44:41.114 --> 00:44:43.785 these topics to let Ben and myself00:44:43.785 --> 00:44:46.529 know and and even just let us know00:44:46.529 --> 00:44:47.966 as another training discussion.00:44:47.966 --> 00:44:50.574 But again, just emphasis on the00:44:50.574 --> 00:44:52.929 fact that you have performance.00:44:52.930 --> 00:44:54.434 Security you have SCO,00:44:54.434 --> 00:44:56.690 you have just general testing and00:44:56.757 --> 00:44:59.037 making sure everything is working.00:44:59.040 --> 00:45:01.686 And it's a it's a lot of things coming00:45:01.686 --> 00:45:04.239 together at once and then if you don't mind,00:45:04.240 --> 00:45:06.384 will you actually feel free to kind of00:45:06.384 --> 00:45:08.578 summarize any other 09aecb55-ae43-47c0-a0d7-1bf6171025e9 00:45:08.580 --> 00:45:10.284 But we actually walk us through00:45:10.284 --> 00:45:12.035 some of the examples that you00:45:12.035 --> 00:45:13.981 went through and kind of what the00:45:13.981 --> 00:45:15.798 timeline was like and what occurred.00:45:15.800 --> 00:45:18.474 Walk us through what happened on Biofarm.00:45:18.480 --> 00:45:20.140 And walking through what happened00:45:20.140 --> 00:45:22.825 on GFS and just like any of the00:45:22.825 --> 00:45:24.745 projects that you think are good00:45:24.745 --> 00:45:26.896 projects on Becker and maybe kind of00:45:26.896 --> 00:45:30.072 explain like you got on to Becker and.00:45:30.072 --> 00:45:32.900 Yes, like OK.00:45:32.900 --> 00:45:34.340 This is my first project and00:45:34.340 --> 00:45:35.780 we're taking it alive and well.00:45:38.830 --> 00:45:40.846 Yeah, well, I think Farm might00:45:40.846 --> 00:45:42.849 actually be a really good one.00:45:42.850 --> 00:45:45.865 'cause it was kind of more recent last year.00:45:45.870 --> 00:45:48.246 It's still pretty fresh on my mind and00:45:48.246 --> 00:45:51.025 that was kind of an interesting one in that00:45:51.025 --> 00:45:53.565 I thought the launch the actual launch00:45:53.565 --> 00:45:55.911 itself finally went went really well.00:45:55.920 --> 00:45:57.930 But you remember with these projects,00:45:57.930 --> 00:46:01.314 like what do you guys think in terms00:46:01.314 --> 00:46:03.660 of development like what is the?00:46:03.660 --> 00:46:06.484 What? What is one of the areas that00:46:06.484 --> 00:46:09.039 that usually is the most problematic?00:46:09.040 --> 00:46:11.260 That's going to literally hinge on00:46:11.260 --> 00:46:14.028 whether a project is successful or not.00:46:14.030 --> 00:46:16.970 Anyone want to take a stab at00:46:16.970 --> 00:46:19.769 what aspect of the project is?00:46:19.770 --> 00:46:21.378 Is that important that it could00:46:21.378 --> 00:46:22.450 derail the entire thing?00:46:22.450 --> 00:46:24.853 If it's if there's a lot of problems there?00:46:27.110 --> 00:46:31.240 I'm biased, but I would say discovery.00:46:31.240 --> 00:46:33.178 OK, OK well I mean so.00:46:33.180 --> 00:46:34.790 But in discovery what is?00:46:34.790 --> 00:46:36.536 What is one of the things00:46:36.536 --> 00:46:38.130 that we spend the majority00:46:38.130 --> 00:46:40.278 of the time on figuring out?00:46:42.460 --> 00:46:46.109 Ask outs in architecture. Alright,00:46:46.109 --> 00:46:48.800 close does anyone else want to take a stab?00:46:51.140 --> 00:46:53.830 China engage you guys is.00:46:53.830 --> 00:46:55.958 Critical thinking skills here for a second.00:46:55.960 --> 00:46:58.552 So what the question is what it what let00:46:58.552 --> 00:47:01.126 me try to phrase it a different way.00:47:03.710 --> 00:47:06.614 What is one of the biggest00:47:06.614 --> 00:47:09.520 problem areas in a project?00:47:09.520 --> 00:47:13.948 That if it isn't right and you go live.00:47:13.950 --> 00:47:16.198 You're going to have all kinds of issues.00:47:16.200 --> 00:47:18.448 I'm going to just spit it out guys.00:47:18.450 --> 00:47:20.130 It's data. Working software, state well.00:47:20.130 --> 00:47:21.780 Working software isn't going to00:47:21.780 --> 00:47:24.370 happen if the data is all messed up.00:47:24.370 --> 00:47:26.236 So that's that's one of the00:47:26.236 --> 00:47:27.851 areas that actually causes more00:47:27.851 --> 00:47:29.386 projects to bleed out then.00:47:29.390 --> 00:47:30.960 Not like where clients they00:47:30.960 --> 00:47:32.530 want it to go live.00:47:32.530 --> 00:47:34.728 They're going to keep paying those invoices,00:47:34.730 --> 00:47:36.928 but a lot of times they're like.00:47:36.930 --> 00:47:38.808 Well, what is the problem here?00:47:38.810 --> 00:47:39.398 Like and?00:47:39.398 --> 00:47:41.456 The reason I'm starting out like this00:47:41.456 --> 00:47:43.745 is because I want to talk about some00:47:43.745 --> 00:47:45.716 of the things specific examples I00:47:45.716 --> 00:47:47.870 ran into bringing Lyle Farms website00:47:47.870 --> 00:47:50.114 live so we were building an invoice00:47:50.114 --> 00:47:51.999 platform that where they are users.00:47:52.000 --> 00:47:55.114 It's a portal that they could go in and.00:47:55.120 --> 00:47:56.720 And pay their outstanding invoices00:47:56.720 --> 00:47:58.652 that they have on like net00:47:58.652 --> 00:48:00.290 terms so they might have some.00:48:00.290 --> 00:48:02.730 Net 30 and 45 invoices in there and00:48:02.730 --> 00:48:04.837 they that this is just a portal00:48:04.837 --> 00:48:07.278 where they can go in and pay those.00:48:07.280 --> 00:48:09.452 The problem with this project was00:48:09.452 --> 00:48:11.603 like we had everything in place00:48:11.603 --> 00:48:13.815 but we spent almost an entire year.00:48:13.820 --> 00:48:16.408 Just on the data.00:48:16.410 --> 00:48:18.762 And part of the issue was that I00:48:18.762 --> 00:48:20.526 couldn't convince I wasn't, I guess,00:48:20.526 --> 00:48:22.284 and I've gotten better at this.00:48:22.290 --> 00:48:24.936 I wasn't at the time I was really green,00:48:24.940 --> 00:48:26.410 and I wasn't convincing enough.00:48:26.410 --> 00:48:28.102 I don't think it wasn't really00:48:28.102 --> 00:48:30.189 proving it to them well enough to00:48:30.189 --> 00:48:32.282 until towards the end of the project,00:48:32.290 --> 00:48:34.138 but I kept telling them that00:48:34.138 --> 00:48:35.809 that's where the hang up is.00:48:35.810 --> 00:48:36.990 The data is inconsistent,00:48:36.990 --> 00:48:38.676 for example, in the state fields00:48:38.676 --> 00:48:40.810 chef is looking for a two letter,00:48:40.810 --> 00:48:42.426 a brief state abbreviation.00:48:42.426 --> 00:48:42.830 Right,00:48:42.830 --> 00:48:44.190 some fields in there would00:48:44.190 --> 00:48:45.550 be the full state name.00:48:45.550 --> 00:48:46.910 Some fields wouldn't even be,00:48:46.910 --> 00:48:49.086 it just be some random letters like BA.00:48:49.090 --> 00:48:50.716 That's not a state you know.00:48:50.720 --> 00:48:52.470 So those are some of the challenges00:48:52.470 --> 00:48:54.429 I ran into and then trying to00:48:54.429 --> 00:48:56.157 like get the client to understand.00:48:56.160 --> 00:48:57.786 These are where the delays are.00:48:57.790 --> 00:48:58.878 We've got everything developed.00:48:58.878 --> 00:49:00.238 We want it there like,00:49:00.240 --> 00:49:01.866 well, we need to go live.00:49:01.870 --> 00:49:04.318 We need to go live and I'm like no.00:49:04.320 --> 00:49:05.946 If we go live right now,00:49:05.950 --> 00:49:07.588 none of your data is going00:49:07.588 --> 00:49:09.220 to be consistent on the web.00:49:09.220 --> 00:49:10.870 Your users are going to log00:49:10.870 --> 00:49:12.869 in and they're going to try to00:49:12.869 --> 00:49:14.264 make payments on this portal.00:49:14.270 --> 00:49:16.870 An it's it's not going to work right?00:49:16.870 --> 00:49:18.495 There's going to be invoices00:49:18.495 --> 00:49:19.470 showing wrong amounts.00:49:19.470 --> 00:49:20.770 Payments aren't going to00:49:20.770 --> 00:49:21.745 be applied correctly.00:49:21.750 --> 00:49:23.046 Statuses aren't going to00:49:23.046 --> 00:49:24.018 be updated appropriately.00:49:24.020 --> 00:49:26.295 I mean, it's just a bad idea.00:49:26.300 --> 00:49:28.900 So they went with it for a while.00:49:28.900 --> 00:49:30.818 We were going back and forth trying00:49:30.818 --> 00:49:32.701 to fix the data specifically with00:49:32.701 --> 00:49:35.032 a third party that they had hired00:49:35.101 --> 00:49:36.886 a company called Velocio that00:49:36.886 --> 00:49:38.314 managed their their ERP.00:49:38.320 --> 00:49:38.702 Finally,00:49:38.702 --> 00:49:40.230 with like working directly00:49:40.230 --> 00:49:42.140 with Rob after several months00:49:42.199 --> 00:49:44.208 towards the end of the project we00:49:44.208 --> 00:49:45.959 were getting to a place where.00:49:45.960 --> 00:49:48.263 The data was starting to be looking00:49:48.263 --> 00:49:50.748 really good 'cause he had put a bunch of00:49:50.748 --> 00:49:53.073 filters in on his place so that and on00:49:53.073 --> 00:49:55.398 his end so that before the data got to00:49:55.398 --> 00:49:57.480 us it would already have been cleansed.00:49:57.480 --> 00:49:58.656 OK, scrubbed and cleanse.00:49:58.656 --> 00:50:00.126 So it's we're getting clean00:50:00.126 --> 00:50:01.128 data now and then.00:50:01.130 --> 00:50:02.374 I'm like, OK, great,00:50:02.374 --> 00:50:04.240 but by this time I've got00:50:04.317 --> 00:50:06.077 an escalation on my hands.00:50:06.080 --> 00:50:08.006 Because the clients thinking this is00:50:08.006 --> 00:50:10.171 all clarity's fault and we should have00:50:10.171 --> 00:50:12.082 been live months ago and I'm sitting00:50:12.142 --> 00:50:14.174 here asking them to pay us more money.00:50:14.180 --> 00:50:16.168 And they're not want to do it.00:50:16.170 --> 00:50:18.788 Right, what a spot to be in,00:50:18.790 --> 00:50:21.774 so fortunately enough on a call with myself,00:50:21.780 --> 00:50:23.296 the technical folks Robin,00:50:23.296 --> 00:50:25.191 one of the other developers00:50:25.191 --> 00:50:27.017 and the higher ups there.00:50:27.020 --> 00:50:29.972 The C title folks that were not real00:50:29.972 --> 00:50:32.261 technical but are just obviously wanting00:50:32.261 --> 00:50:35.010 this to go live and not understanding00:50:35.010 --> 00:50:38.237 that the problems lie in their data.00:50:38.240 --> 00:50:38.688 Folks.00:50:38.688 --> 00:50:41.376 Clarity is not responsible for a00:50:41.376 --> 00:50:44.556 clients data if they want to pay us00:50:44.556 --> 00:50:47.290 to scrub and cleanse it and fix it,00:50:47.290 --> 00:50:47.890 we can,00:50:47.890 --> 00:50:49.990 but I mean they've gotta pay us00:50:49.990 --> 00:50:51.903 for that's not our responsibility00:50:51.903 --> 00:50:54.597 and I was finally able to prove00:50:54.597 --> 00:50:56.795 to her name was VDI was finally00:50:56.795 --> 00:50:58.765 able to prove d'ovide that.00:50:58.765 --> 00:51:02.303 This entire time the data issues have been00:51:02.303 --> 00:51:05.800 on their end and it happened in a call with.00:51:05.800 --> 00:51:07.786 Their contractor admitting that yeah yeah,00:51:07.790 --> 00:51:09.114 these are all problems.00:51:09.114 --> 00:51:10.769 This is on our end.00:51:10.770 --> 00:51:12.420 This is on our end.00:51:12.420 --> 00:51:14.730 So towards the end they just left00:51:14.730 --> 00:51:17.091 the there was like I think 60 00:51:17.091 --> 00:51:19.029 out of like 2000 invoices that00:51:19.107 --> 00:51:21.354 still had some bad data in them.00:51:21.360 --> 00:51:24.670 It was all I was like balls in your court.00:51:24.670 --> 00:51:27.318 You guys want to launch let's do it.00:51:27.320 --> 00:51:28.970 I've I've thrown I've we've00:51:28.970 --> 00:51:29.960 documented the risk.00:51:29.960 --> 00:51:30.998 Clarity is covered.00:51:30.998 --> 00:51:33.420 We've covered our but on it let's00:51:33.494 --> 00:51:35.950 let's go and so we launched and it00:51:35.950 --> 00:51:37.695 was actually pretty successful too00:51:37.695 --> 00:51:40.441 because I did a very soft launch with00:51:40.441 --> 00:51:42.338 them where we got the server all00:51:42.338 --> 00:51:44.832 set up and then the final phases of00:51:44.832 --> 00:51:47.250 testing that were done was all done00:51:47.250 --> 00:51:49.070 in the production environment to00:51:49.070 --> 00:51:51.027 validate that everything would work.00:51:51.027 --> 00:51:53.890 I wouldn't let them flip the switch00:51:53.961 --> 00:51:56.278 until I knew that the site would00:51:56.278 --> 00:51:58.670 work and maybe a little bit to00:51:58.670 --> 00:52:00.656 my detriment in the sense that.00:52:00.660 --> 00:52:02.884 I didn't do a very good job explaining00:52:02.884 --> 00:52:05.090 or getting them to realize that I'm00:52:05.090 --> 00:52:06.680 sitting here working with them,00:52:06.680 --> 00:52:08.486 trying to fix their data issues,00:52:08.490 --> 00:52:10.597 and that's part of why this is00:52:10.597 --> 00:52:11.500 taking so long,00:52:11.500 --> 00:52:13.126 and I'm asking for more money00:52:13.126 --> 00:52:14.810 because this is time consuming.00:52:14.810 --> 00:52:16.514 Obviously I've got to sit here00:52:16.514 --> 00:52:18.120 and find all these issues.00:52:18.120 --> 00:52:19.818 I've gotta have Brendan go in00:52:19.818 --> 00:52:21.430 and find all these issues,00:52:21.430 --> 00:52:22.930 and we have to communicate,00:52:22.930 --> 00:52:24.650 coordinate back and forth with00:52:24.650 --> 00:52:26.928 Rob to get this resolved and you00:52:26.928 --> 00:52:28.880 know at the end the site did go00:52:28.947 --> 00:52:30.037 live. VD ended up.00:52:30.037 --> 00:52:32.221 I don't know if she got fired or00:52:32.221 --> 00:52:34.377 ended up moving on to somewhere else,00:52:34.380 --> 00:52:36.588 but they basically did a whole regime change,00:52:36.590 --> 00:52:37.970 but that's beside the point.00:52:37.970 --> 00:52:40.094 My point is, I was just trying to get00:52:40.094 --> 00:52:42.048 into some that one example with farm00:52:42.048 --> 00:52:44.728 of like just some of the things that I00:52:44.728 --> 00:52:46.562 went through surrounding the data and.00:52:46.562 --> 00:52:48.434 And that's also really good point00:52:48.434 --> 00:52:50.970 that I'm not seeing on this checklist.00:52:50.970 --> 00:52:53.940 I don't think.00:52:53.940 --> 00:52:56.208 And hopefully this is our address00:52:56.208 --> 00:52:58.512 during development we have to validate00:52:58.512 --> 00:53:00.684 that we're working with good data.00:53:00.690 --> 00:53:03.690 Probably wouldn't patch past much much of QA.00:53:03.690 --> 00:53:06.315 If it's you know, egregiously dirty data,00:53:06.320 --> 00:53:08.190 but that's a big one.00:53:08.190 --> 00:53:09.354 Guys like projects.00:53:09.354 --> 00:53:11.682 Success can hinge on failure with00:53:11.682 --> 00:53:13.814 that not liking literally that's00:53:13.814 --> 00:53:16.332 that is the whingeing point, right?00:53:16.332 --> 00:53:18.924 There is like if we can00:53:18.924 --> 00:53:21.400 if their data is bad and.00:53:21.400 --> 00:53:23.496 They don't want to pay to fix it,00:53:23.500 --> 00:53:25.604 and they don't want to fix it themselves.00:53:25.610 --> 00:53:27.706 I mean that we can't work with that.00:53:27.710 --> 00:53:29.544 That's a tough one to work with,00:53:29.550 --> 00:53:31.654 but if they're willing to do it themselves,00:53:31.660 --> 00:53:34.018 or they're willing to pay clarity to fix it,00:53:34.020 --> 00:53:35.340 well that's a different scenario.00:53:35.340 --> 00:53:36.655 That's not going to block00:53:36.655 --> 00:53:37.707 us from moving forward,00:53:37.710 --> 00:53:39.708 but there could also be other00:53:39.708 --> 00:53:41.040 circumstances with data that.00:53:41.040 --> 00:53:43.266 Could could just end up being.00:53:43.270 --> 00:53:43.746 I mean,00:53:43.746 --> 00:53:46.131 you may end up having to find work arounds00:53:46.131 --> 00:53:48.657 for different different solutions with devs,00:53:48.660 --> 00:53:50.240 not from a technical standpoint,00:53:50.240 --> 00:53:52.148 but from the big picture standpoint.00:53:52.150 --> 00:53:54.740 So that was with farm.00:53:54.740 --> 00:53:55.047 Now,00:53:55.047 --> 00:53:56.889 I didn't actually bring GFS live,00:53:56.890 --> 00:53:59.510 but I got GFS after the fact and I was00:53:59.586 --> 00:54:02.418 Privy to some of the issues around there.00:54:02.420 --> 00:54:03.218 There go live.00:54:03.218 --> 00:54:05.426 It was kind of a long time coming00:54:05.426 --> 00:54:07.610 to if there there was a lot of00:54:07.610 --> 00:54:09.479 data exchanging with an integration00:54:09.479 --> 00:54:11.007 that was set up.00:54:11.010 --> 00:54:12.445 Some pretty complex integrations with00:54:12.445 --> 00:54:14.390 Dynamics AX and they sell chemicals.00:54:14.390 --> 00:54:16.539 For those of you that don't know.00:54:16.540 --> 00:54:19.788 So they have some really interesting like.00:54:19.790 --> 00:54:21.085 The way their product variants00:54:21.085 --> 00:54:22.790 are setup is kind of custom,00:54:22.790 --> 00:54:25.139 so we had to do a lot of customization00:54:25.139 --> 00:54:26.803 there before launch and it and00:54:26.803 --> 00:54:28.799 it was just taking a long time.00:54:28.800 --> 00:54:30.378 The owner of the company Steel00:54:30.378 --> 00:54:32.079 and our main point of contact,00:54:32.080 --> 00:54:33.956 Don well Don was getting a lot00:54:33.956 --> 00:54:35.665 of pressure from the owner to00:54:35.665 --> 00:54:37.345 launch and they just they weren't00:54:37.345 --> 00:54:39.165 in a good place at that time.00:54:39.170 --> 00:54:40.724 They felt like they were spending00:54:40.724 --> 00:54:42.669 a lot of money on the verge00:54:42.669 --> 00:54:43.809 of a serious escalation.00:54:43.810 --> 00:54:44.620 Kevin came in,00:54:44.620 --> 00:54:47.090 worked out a deal with them that we would.00:54:47.090 --> 00:54:48.994 I think we were working at like00:54:48.994 --> 00:54:50.780 80% rate for awhile until we.00:54:50.780 --> 00:54:52.412 We launched and then a little00:54:52.412 --> 00:54:54.111 bit afterwards on some of the00:54:54.111 --> 00:54:55.496 change request items that they00:54:55.496 --> 00:54:56.910 were wanting to have done.00:54:56.910 --> 00:54:58.842 So I came in with the change00:54:58.842 --> 00:55:00.542 request items like I came in00:55:00.542 --> 00:55:02.162 right after launch and we were00:55:02.162 --> 00:55:04.080 still we were adding doing a00:55:04.080 --> 00:55:05.665 lot of feature enhancements but00:55:05.670 --> 00:55:08.250 my guess is that with GFS it was a lot00:55:08.318 --> 00:55:10.883 of the same thing as with farm in terms00:55:10.883 --> 00:55:13.152 of just dealing with the data that's00:55:13.152 --> 00:55:16.815 going to be a big one on these self00:55:16.815 --> 00:55:18.723 projects where there's integrations.00:55:18.730 --> 00:55:21.670 So just some things to look for.00:55:21.670 --> 00:55:23.847 And I think the biggest thing that's00:55:23.847 --> 00:55:26.823 common here is that you get pressure from00:55:26.823 --> 00:55:28.803 executives and leadership on timeline.00:55:28.810 --> 00:55:31.370 And how do you push back on that?00:55:31.370 --> 00:55:31.793 Affectively.00:55:31.793 --> 00:55:35.177 And what when did you start pushing back?00:55:35.180 --> 00:55:36.874 Was it when you first got started00:55:36.874 --> 00:55:38.904 or was it when you actually started00:55:38.904 --> 00:55:40.464 to see things go poorly?00:55:40.470 --> 00:55:42.126 Yes, it was rushed. That's true.00:55:42.130 --> 00:55:43.520 Yeah, that's a good point.00:55:43.520 --> 00:55:46.058 So when I first started, I never pushed back.00:55:46.058 --> 00:55:49.080 I was I was came from I was a sales guy.00:55:49.080 --> 00:55:51.304 I mean I come from a technical background,00:55:51.310 --> 00:55:53.294 but at the time I was a general00:55:53.294 --> 00:55:54.920 manager of a furniture store,00:55:54.920 --> 00:55:57.144 so I was like a yes guy man,00:55:57.150 --> 00:55:59.230 I want to say yes to everybody you00:55:59.230 --> 00:56:01.590 know I didn't do a lot of pushback.00:56:01.590 --> 00:56:03.536 I also didn't have a lot of00:56:03.536 --> 00:56:05.569 experience to do a lot of pushback.00:56:05.570 --> 00:56:08.936 So I'd say I I started like saying pushing00:56:08.936 --> 00:56:12.020 back on timeline issues and saying no,00:56:12.020 --> 00:56:13.204 that's unrealistic,00:56:13.204 --> 00:56:14.980 and here's why.00:56:14.980 --> 00:56:15.400 Really,00:56:15.400 --> 00:56:18.760 God within about a year of me being00:56:18.760 --> 00:56:22.538 in in this role because that's when I00:56:22.538 --> 00:56:26.039 finally had seen enough problems occur.00:56:26.040 --> 00:56:28.254 And I knew what the cause00:56:28.254 --> 00:56:30.040 of those problems were so.00:56:30.040 --> 00:56:32.040 When I saw on then I started seeing00:56:32.040 --> 00:56:33.827 like with some other projects where00:56:33.827 --> 00:56:36.170 those were and I'm being very general,00:56:36.170 --> 00:56:38.214 but I'm I'm doing that on purpose.00:56:38.220 --> 00:56:40.590 If when I saw a problem come up I would00:56:40.653 --> 00:56:43.110 I would say or I'm sorry when I see00:56:43.110 --> 00:56:44.860 something that would potentially cause00:56:44.860 --> 00:56:47.856 a problem because I'd seen it in the past,00:56:47.856 --> 00:56:48.440 I could.00:56:48.440 --> 00:56:50.536 You know I would call it out and00:56:50.536 --> 00:56:52.810 then and then you start to see like00:56:52.810 --> 00:56:55.149 it all kinds kind of comes together.00:56:55.150 --> 00:56:58.006 Once you get the whole concept down.00:56:58.010 --> 00:56:59.780 Anne Anne, remember this morning with00:56:59.780 --> 00:57:02.140 Jeff and I know you got other folks,00:57:02.140 --> 00:57:03.910 but it was PJ and Jeff.00:57:03.910 --> 00:57:04.798 We were in.00:57:04.798 --> 00:57:05.390 We were.00:57:05.390 --> 00:57:07.638 We spent quite a bit of time just00:57:07.638 --> 00:57:09.390 running through some different scenarios00:57:09.390 --> 00:57:11.646 on the triple constraints and how.00:57:11.650 --> 00:57:13.430 It is tough without experience,00:57:13.430 --> 00:57:16.202 but if you get the concept down00:57:16.202 --> 00:57:18.888 it will allow you to identify.00:57:18.890 --> 00:57:20.927 Where these risks that come up like00:57:20.927 --> 00:57:23.070 you know they're adding to scope or00:57:23.070 --> 00:57:24.882 they're they're trying to rush you.00:57:24.890 --> 00:57:27.375 Rush the timeline and and so that's00:57:27.375 --> 00:57:29.099 that's affecting quality and scope.00:57:29.100 --> 00:57:32.397 It all kind of runs along that00:57:32.397 --> 00:57:34.759 that same line I think.00:57:34.760 --> 00:57:36.200 And it was good actually.00:57:36.200 --> 00:57:38.216 The SAT improved my clients at improved.00:57:38.220 --> 00:57:40.516 I had good sat at the time too,00:57:40.520 --> 00:57:41.955 because I mean if something00:57:41.955 --> 00:57:43.103 needs to get done,00:57:43.110 --> 00:57:45.140 I would bust my and bend over00:57:45.140 --> 00:57:46.570 backwards and get it done.00:57:46.570 --> 00:57:48.292 Whatever it took at the sacrifice00:57:48.292 --> 00:57:50.062 of my own stress and mental00:57:50.062 --> 00:57:51.457 well being at the time,00:57:51.460 --> 00:57:53.652 honestly. But it I got it done and00:57:53.652 --> 00:57:55.780 it like it forged me into this.00:57:55.780 --> 00:57:56.884 Freaking like iron sword.00:57:56.884 --> 00:57:58.904 Now that at like with that experience00:57:58.904 --> 00:58:00.722 I can identify those things and00:58:00.722 --> 00:58:02.697 that's kind of where my point was.00:58:02.700 --> 00:58:04.416 With the triple constraints is it's.00:58:04.420 --> 00:58:06.569 It's getting these concepts down so it's.00:58:06.570 --> 00:58:07.986 Not just like, oh,00:58:07.986 --> 00:58:10.689 I've seen this specific issue caused by this,00:58:10.690 --> 00:58:12.760 so now I know the causality00:58:12.760 --> 00:58:14.799 and I can call it out.00:58:14.800 --> 00:58:17.336 You've got to be able to kind of00:58:17.336 --> 00:58:19.570 predict what the impact of certain00:58:19.570 --> 00:58:22.349 changes in the project as things go on.00:58:22.350 --> 00:58:24.700 It is going to be and so and that will00:58:24.765 --> 00:58:27.490 happen organically overtime with experience,00:58:27.490 --> 00:58:29.548 but just kind of knowing that00:58:29.548 --> 00:58:30.920 changes will impact timeline.00:58:30.920 --> 00:58:32.665 Getting that you'll have these00:58:32.665 --> 00:58:34.410 higher sea levels pushing down00:58:34.468 --> 00:58:36.068 on your contact on timeline,00:58:36.070 --> 00:58:37.795 and they don't necessarily understand00:58:37.795 --> 00:58:40.330 all of the nuances and details that.00:58:40.330 --> 00:58:41.296 Are going on,00:58:41.296 --> 00:58:43.228 they just want the thing live.00:58:43.230 --> 00:58:46.218 They're the ones signing the check.00:58:46.220 --> 00:58:49.010 But that's when like if you set the right00:58:49.010 --> 00:58:50.503 expectations when something comes up00:58:50.503 --> 00:58:53.169 that you know is going to impact timeline,00:58:53.170 --> 00:58:56.014 or at least has a risk to impact timeline.00:58:56.020 --> 00:58:57.555 If you document memorialized that00:58:57.555 --> 00:58:59.809 and call it out to the client,00:58:59.810 --> 00:59:01.390 the person you're working with,00:59:01.390 --> 00:59:02.606 your point of contact.00:59:02.606 --> 00:59:04.821 I mean it's their job to really00:59:04.821 --> 00:59:06.436 push that up the chain.00:59:06.440 --> 00:59:08.659 And if you deal with that appropriately,00:59:08.660 --> 00:59:10.865 I'll give really good example right now.00:59:10.870 --> 00:59:12.658 Is Didg Chris digital directions so00:59:12.658 --> 00:59:14.978 that one Karen is so besides herself,00:59:14.980 --> 00:59:16.870 happy with where we're at?00:59:16.870 --> 00:59:19.382 To the point where like we didn't make00:59:19.382 --> 00:59:21.922 this for weeks thing that was we were00:59:21.922 --> 00:59:24.359 going to hit that in the 1st place.00:59:24.360 --> 00:59:26.257 But we did give it our best00:59:26.257 --> 00:59:28.216 effort and we're almost done with00:59:28.216 --> 00:59:29.660 this first date example,00:59:29.660 --> 00:59:32.156 will you tell you tell me what happened?00:59:32.160 --> 00:59:32.784 What happened?00:59:32.784 --> 00:59:34.342 Yeah, absolutely yeah. And this.00:59:34.342 --> 00:59:35.586 This one is amazing.00:59:35.590 --> 00:59:37.378 'cause right now like the kind00:59:37.378 --> 00:59:39.649 of report that I have with Karen,00:59:39.650 --> 00:59:41.670 the person that were directly00:59:41.670 --> 00:59:43.690 working with over digital directions00:59:43.752 --> 00:59:45.588 is such that like we're working00:59:45.588 --> 00:59:47.669 together as a team to keep Bart.00:59:47.670 --> 00:59:49.488 So sheated, if that makes sense,00:59:49.490 --> 00:59:51.240 like So what happened with this one00:59:51.240 --> 00:59:53.189 was there was apparently some really00:59:53.189 --> 00:59:54.944 aggressive yeah Bartz, their CEO.00:59:54.944 --> 00:59:56.454 There was some really aggressive00:59:56.454 --> 00:59:57.058 timelines expectations.00:59:57.060 --> 00:59:58.998 Apparently that I wasn't even made00:59:58.998 --> 01:00:00.920 aware of until it had escalated01:00:00.920 --> 01:00:03.160 all the way up the chain and me01:00:03.224 --> 01:00:05.268 and Chris Redeker on a call with01:00:05.268 --> 01:00:07.068 Bart and Karen talking about it.01:00:07.068 --> 01:00:08.904 There was some date they had01:00:08.904 --> 01:00:10.399 in mind of April 1st,01:00:10.400 --> 01:00:11.915 which I think we started01:00:11.915 --> 01:00:13.430 Discovery early to mid March.01:00:13.430 --> 01:00:16.148 I would if I knew that was the case.01:00:16.150 --> 01:00:17.665 I would have called that01:00:17.665 --> 01:00:19.180 out immediately as a risk.01:00:19.180 --> 01:00:21.070 I Oh no, there's no way.01:00:21.070 --> 01:00:23.135 When I gave him the actual timeline,01:00:23.140 --> 01:00:24.615 it created an instant escalation01:00:24.615 --> 01:00:26.972 with Bart like Oh no, wait a minute.01:00:26.972 --> 01:00:29.330 We're supposed to be done by April 1st.01:00:29.330 --> 01:00:31.100 We didn't get started until March.01:00:31.100 --> 01:00:33.476 I mean, there's a lot of reasons for01:00:33.476 --> 01:00:35.819 that that I'm not going to get into,01:00:35.820 --> 01:00:38.132 but to lend credence to what we were01:00:38.132 --> 01:00:39.655 talking about and what Christmas01:00:39.655 --> 01:00:41.720 point was is with the push back.01:00:41.720 --> 01:00:43.916 Part of it was I just I just politely01:00:43.916 --> 01:00:45.889 and professionally pushed back in a01:00:45.889 --> 01:00:48.203 way to Karen where she's like, yeah,01:00:48.203 --> 01:00:50.467 I I she understood because of the way01:00:50.467 --> 01:00:53.387 I explained it to her and I set the01:00:53.387 --> 01:00:55.420 expectations very clearly and she knew.01:00:55.420 --> 01:00:57.415 That she was the the gap creator01:00:57.415 --> 01:00:59.265 there she was actually the one01:00:59.265 --> 01:01:01.435 that knew that date and had never01:01:01.499 --> 01:01:03.974 communicated it to me an and so she had.01:01:03.980 --> 01:01:06.630 It was like, you know, I apologize for that.01:01:06.630 --> 01:01:08.700 That that was my mistake and and,01:01:08.700 --> 01:01:10.446 and this is not always going01:01:10.446 --> 01:01:11.940 to work out this way.01:01:11.940 --> 01:01:14.131 We were just fortunate that that our01:01:14.131 --> 01:01:15.780 personalities mesh really well to wear.01:01:15.780 --> 01:01:17.691 Like just today we had a conversation01:01:17.691 --> 01:01:19.608 and I'm like asking her success.01:01:19.610 --> 01:01:21.675 Bart seen this yet and she's like,01:01:21.680 --> 01:01:23.724 Oh no, he'll have a heart attack01:01:23.724 --> 01:01:26.037 if he sees it before it's done.01:01:26.040 --> 01:01:27.816 I'm like OK so I mean,01:01:27.820 --> 01:01:29.948 but like I'm asking her like well how01:01:29.948 --> 01:01:32.258 are you feeling about where we're at?01:01:32.260 --> 01:01:34.122 An in our next steps and and01:01:34.122 --> 01:01:35.510 what we have planned?01:01:35.510 --> 01:01:36.970 'cause now we're giving them01:01:36.970 --> 01:01:38.770 a tentative date of the 18th.01:01:38.770 --> 01:01:40.835 And that's including the final pieces too.01:01:40.840 --> 01:01:41.432 I mean,01:01:41.432 --> 01:01:43.800 we've got the majority of the work done,01:01:43.800 --> 01:01:45.280 but anyway, she's just ecstatic.01:01:45.280 --> 01:01:46.165 She's like, yeah,01:01:46.165 --> 01:01:47.935 I know you guys are great.01:01:47.940 --> 01:01:49.964 I can't even believe how how well this01:01:49.964 --> 01:01:51.748 has been whipped together and there01:01:51.748 --> 01:01:54.292 hasn't been a single breath of any type01:01:54.292 --> 01:01:56.230 of escalation coming down the pipeline.01:01:56.230 --> 01:01:57.530 And I really honest,01:01:57.530 --> 01:01:58.830 I attribute that to.01:01:58.830 --> 01:02:01.266 Setting the proper expectations up front01:02:01.266 --> 01:02:04.209 and then pushing back really transparent.01:02:04.210 --> 01:02:06.450 Yes, absolutely not holding back.01:02:06.450 --> 01:02:07.344 That's right,01:02:07.344 --> 01:02:09.579 Strahle stressed about a timeline.01:02:09.580 --> 01:02:13.052 Say something that is the time to raise01:02:13.052 --> 01:02:17.460 it and just to close this out and thanks01:02:17.460 --> 01:02:21.487 again for everyone for listening and kind of.01:02:21.490 --> 01:02:22.654 Allowing this to percolate,01:02:22.654 --> 01:02:24.400 I really think it will help.01:02:24.400 --> 01:02:26.423 I would put myself out there and01:02:26.423 --> 01:02:28.766 then I think you would do the same,01:02:28.770 --> 01:02:29.152 Kevin.01:02:29.152 --> 01:02:33.180 And and down the list of the team of more01:02:33.180 --> 01:02:36.673 senior Floridians on the PM team please,01:02:36.680 --> 01:02:39.641 as you guys have some of these01:02:39.641 --> 01:02:41.230 urgent projects coming up,01:02:41.230 --> 01:02:41.621 please,01:02:41.621 --> 01:02:44.358 please enlist us like if you have01:02:44.358 --> 01:02:47.362 any doubt and I'm I'm actually like01:02:47.362 --> 01:02:49.507 proactively bringing it up at,01:02:49.510 --> 01:02:50.268 you know,01:02:50.268 --> 01:02:52.542 within this training and trying to01:02:52.542 --> 01:02:54.801 get you thinking about it because01:02:54.801 --> 01:02:57.687 I would ask you to take ownership01:02:57.687 --> 01:03:00.367 and responsibility for coordinating.01:03:00.370 --> 01:03:02.617 But just know that you have support.01:03:02.620 --> 01:03:04.540 We're here to support, you know,01:03:04.540 --> 01:03:06.394 make sure things go smoothly and01:03:06.394 --> 01:03:08.719 we're here to help tactically on it,01:03:08.720 --> 01:03:10.960 so you can just be like man.01:03:10.960 --> 01:03:13.488 I I need a line person block so01:03:13.488 --> 01:03:15.778 we don't keep getting sacked.01:03:15.780 --> 01:03:19.566 Put me in coach. I put Kevin in.01:03:19.566 --> 01:03:21.136 That's what we're here for,01:03:21.140 --> 01:03:23.541 and you'll learn and you'll see you01:03:23.541 --> 01:03:25.849 know what we're doing is as we go.01:03:25.850 --> 01:03:27.915 So sound good and my final statement01:03:27.915 --> 01:03:30.669 is going to be that I learned a lot01:03:30.669 --> 01:03:32.605 of my pushback techniques from getting01:03:32.605 --> 01:03:34.943 on those calls with Chris and Kevin.01:03:34.950 --> 01:03:37.148 And in my first year at clarity,01:03:37.150 --> 01:03:39.643 and I picked up on what they were doing01:03:39.643 --> 01:03:42.192 an with practice, I got better at,01:03:42.192 --> 01:03:44.100 and I was very uncomfortable pushing01:03:44.160 --> 01:03:47.980 back at first. But I'm not now.01:03:47.980 --> 01:03:48.814 Anyway, I'm done.01:03:48.814 --> 01:03:50.414 We're going to Jeff. Hey Chris,01:03:50.414 --> 01:03:53.035 I meant to ask you if we have to pull01:03:53.035 --> 01:03:55.507 you into a meeting someone mentioned to me,01:03:55.510 --> 01:03:57.558 like when I first days here and I01:03:57.558 --> 01:03:59.980 kind of forgot, but what do we like?01:03:59.980 --> 01:04:02.268 Call you if we it was like are01:04:02.268 --> 01:04:03.598 likely like I want to.01:04:03.600 --> 01:04:04.395 Yeah if anyone.01:04:04.395 --> 01:04:06.596 Yeah if anyone ever asks like point blank01:04:06.596 --> 01:04:08.908 if they're like it's Krista CEO or whatever.01:04:08.910 --> 01:04:11.134 I mean, feel free to tell him that,01:04:11.140 --> 01:04:12.530 but sometimes it's a little01:04:12.530 --> 01:04:13.364 intimidating and I'm.01:04:13.370 --> 01:04:15.323 I mean I don't mind ever being01:04:15.323 --> 01:04:16.160 called the CEO.01:04:16.160 --> 01:04:17.828 I mean, it's kind of cool,01:04:17.830 --> 01:04:21.390 but Sometimes people are like oh oh oh,01:04:21.390 --> 01:04:23.260 OK, we do something wrong.01:04:23.260 --> 01:04:25.060 Or you know we're thinking01:04:25.060 --> 01:04:27.370 that just makes it feel weird.01:04:27.370 --> 01:04:29.926 See, but you can refer to me as one01:04:29.926 --> 01:04:32.609 of the senior technical resources,01:04:32.610 --> 01:04:34.848 or you know something like that.01:04:34.850 --> 01:04:37.058 Chris is one of our senior01:04:37.058 --> 01:04:38.970 technical members of the team.01:04:38.970 --> 01:04:40.835 You know anything like that01:04:40.835 --> 01:04:41.954 senior technical engineer,01:04:41.960 --> 01:04:43.910 etc.01:04:43.910 --> 01:04:44.464 Awesome possum,01:04:44.464 --> 01:04:46.126 and if it doesn't go perfectly,01:04:46.130 --> 01:04:47.798 that is totally cool because then01:04:47.798 --> 01:04:49.866 we can just joke around with the01:04:49.866 --> 01:04:51.666 client about it and all laugh01:04:51.666 --> 01:04:53.488 together and I will turn it into01:04:53.488 --> 01:04:55.460 something funny or I will say puns,01:04:55.460 --> 01:04:57.110 and then they'll forget that01:04:57.110 --> 01:04:59.139 we even messed up the title.01:04:59.140 --> 01:04:59.560 So.01:05:01.720 --> 01:05:02.756 Yeah, great and uh,01:05:02.756 --> 01:05:04.051 I was hoping somebody would01:05:04.051 --> 01:05:05.629 say something but no nothing.01:05:05.630 --> 01:05:07.025 So I was speaking actually01:05:07.025 --> 01:05:08.420 was talking but I was.01:05:08.420 --> 01:05:10.338 I was saying that the development team01:05:10.338 --> 01:05:12.317 members they start heckling Me right away.01:05:12.320 --> 01:05:14.000 I think it's so funny man,01:05:14.000 --> 01:05:16.072 because I'll always be like I don't01:05:16.072 --> 01:05:17.620 ever introduce you as the CEO.01:05:17.620 --> 01:05:19.015 If someone asked me directly01:05:19.015 --> 01:05:20.410 I would tell him that.01:05:20.410 --> 01:05:22.722 But for those exact same reasons I feel01:05:22.722 --> 01:05:24.899 like it can be a little intimidating01:05:24.899 --> 01:05:27.411 and they may not open up to you in01:05:27.411 --> 01:05:29.620 the way that we need him to or at01:05:29.620 --> 01:05:31.673 the time or whatever, but I'll just.01:05:31.673 --> 01:05:33.766 Like he's one of our, you know,01:05:33.766 --> 01:05:35.106 managing partners or lead technical01:05:35.106 --> 01:05:36.290 resources with the company.01:05:36.290 --> 01:05:38.250 I mean, none of that's a lie.01:05:38.250 --> 01:05:40.196 I mean, it's all the same thing.01:05:40.200 --> 01:05:41.844 I think that's how you introduce01:05:41.844 --> 01:05:43.549 yourself a lot of the times.01:05:43.550 --> 01:05:44.662 If I remember right?01:05:44.662 --> 01:05:46.278 Yeah, yeah, I do.01:05:46.278 --> 01:05:48.463 'cause I just. I mean I,01:05:48.463 --> 01:05:51.649 I don't know if it's bad or not for people,01:05:51.650 --> 01:05:54.130 but it just feel like sometimes they're like,01:05:54.130 --> 01:05:55.370 oh, you're the CEO.01:05:55.370 --> 01:05:56.610 You don't know anything.01:05:56.610 --> 01:05:58.160 Or oh, you're the CEO.01:05:58.160 --> 01:06:00.253 I don't wanna talk to you now01:06:00.253 --> 01:06:02.500 so I don't know why that is.01:06:02.500 --> 01:06:04.050 But does it make sense?01:06:04.050 --> 01:06:04.980 Yeah, I agree.01:06:04.980 --> 01:06:05.600 I agree.01:06:05.600 --> 01:06:06.840 I think words matter,01:06:06.840 --> 01:06:08.390 an especially being in sales.01:06:08.390 --> 01:06:11.360 I can tell you that the word choices that you01:06:11.434 --> 01:06:14.278 guys use with titles or just in general it.01:06:14.280 --> 01:06:14.900 I mean,01:06:14.900 --> 01:06:15.830 it all matters.01:06:15.830 --> 01:06:17.070 Words matter for sure.