WEBVTT NOTE This file was generated by Descript 00:01:53.753 --> 00:01:54.263 CJ: we're live. 00:01:54.353 --> 00:01:54.843 Whenever you're ready. 00:01:55.613 --> 00:01:58.073 Duke: I was about to tell this awful story about how these spiders jumped 00:01:58.073 --> 00:01:59.063 me while I was walking my dog. 00:01:59.063 --> 00:02:01.503 I walked through one of those, early morning nets, you know, 00:02:01.503 --> 00:02:03.633 where they go, like they go like four or five feet across. 00:02:04.298 --> 00:02:04.518 CJ: Yep. 00:02:05.028 --> 00:02:06.708 Duke: I was like, what the heck? 00:02:06.708 --> 00:02:08.178 And I like got the web outta my face. 00:02:08.178 --> 00:02:08.928 I'm like, that's gross. 00:02:08.928 --> 00:02:11.388 And I looked down there, it was just like four or five, and I'm just like, 00:02:11.388 --> 00:02:13.488 just crawling all over my tummy. 00:02:13.488 --> 00:02:22.608 I'm just like, ah, five 30 in the morning and I'm flailing my arms 00:02:22.608 --> 00:02:23.658 and screaming in the middle of the. 00:02:27.093 --> 00:02:29.763 CJ: Only one way out of this I must light myself on fire. 00:02:31.338 --> 00:02:31.878 Duke: Yes. 00:02:32.658 --> 00:02:35.328 It's sad, but it's the only way to be sure. 00:02:41.118 --> 00:02:41.298 Okay. 00:02:41.303 --> 00:02:42.198 We're leaving that one in. 00:02:42.438 --> 00:02:43.878 What else are we talking about today? 00:02:45.918 --> 00:02:46.308 CJ: All right. 00:02:46.308 --> 00:02:49.518 Today, duke, , we're gonna do a requirements gathering, , episode. 00:02:49.818 --> 00:02:51.678 , you are thinking about building a new app. 00:02:51.875 --> 00:02:52.345 Duke: I am. 00:02:52.708 --> 00:02:52.928 And. 00:02:53.258 --> 00:02:58.058 The app is about a coaching program that I do, and so I'm 00:02:58.058 --> 00:02:59.678 just gonna shamelessly pitch. 00:02:59.901 --> 00:03:03.211 , I've been, in a lot of conversations with a lot of people who have gone 00:03:03.211 --> 00:03:07.231 through a lot of bootcamps and I am sick and tired of how many people 00:03:07.236 --> 00:03:08.341 are falling through the cracks. 00:03:09.091 --> 00:03:11.251 Great people out there, great skills. 00:03:11.581 --> 00:03:13.501 They just haven't got enough practical experience. 00:03:13.501 --> 00:03:17.191 So I've designed my own custom training program. 00:03:18.226 --> 00:03:20.476 Um, custom, no. 00:03:20.476 --> 00:03:21.076 Wait, no. 00:03:21.076 --> 00:03:23.056 I configured a training program, right. 00:03:26.116 --> 00:03:27.436 Customization bad. 00:03:27.436 --> 00:03:28.276 Configured good, 00:03:28.591 --> 00:03:28.981 CJ: Nice 00:03:30.866 --> 00:03:32.606 , Duke: I've made this new training program. 00:03:32.656 --> 00:03:34.006 My trial run was three people. 00:03:34.006 --> 00:03:38.676 They were all hired before it ended, and I'm now in my, second session. 00:03:39.321 --> 00:03:41.061 We're not even halfway yet, so nobody's been hired. 00:03:41.311 --> 00:03:44.261 , but we've got 15 people and I wanna , keep scaling from there. 00:03:44.261 --> 00:03:48.281 And so if you're tired of the status quo, if you wanna go to a place that's 00:03:48.281 --> 00:03:52.181 gonna teach you the concepts deep and then give you legit work that 00:03:52.181 --> 00:03:56.091 you can cut your teeth on, , reach out to me at Rob at the Duke Digital 00:03:56.391 --> 00:03:58.965 and, , see if you can join cohort three. 00:03:58.965 --> 00:04:01.725 Unfortunately, this is North America only, but uh, I'd. 00:04:03.130 --> 00:04:03.790 CJ: Nice. 00:04:04.390 --> 00:04:05.200 All right, duke. 00:04:05.200 --> 00:04:08.440 Unlike a lot of people right, who complain about the status quo, complain 00:04:08.440 --> 00:04:12.110 about, , problems that, that exist and you complained about it then 00:04:12.110 --> 00:04:13.250 when, and did something about it. 00:04:13.430 --> 00:04:14.240 So that's pretty cool. 00:04:15.095 --> 00:04:16.145 Duke: I appreciate that, brother. 00:04:16.670 --> 00:04:17.000 CJ: Yeah. 00:04:17.180 --> 00:04:17.450 Yeah. 00:04:17.590 --> 00:04:19.355 Duke: we hadn't talked about it together for like a hundred 00:04:19.415 --> 00:04:20.435 something times though, so. 00:04:21.050 --> 00:04:22.010 CJ: well, I know, right? 00:04:22.010 --> 00:04:22.820 But that's my point. 00:04:22.820 --> 00:04:25.610 We did talk about it a hundred some times and boom, now you're doing it. 00:04:25.895 --> 00:04:29.610 And really, , excited for all the people you've helped get gigs and 00:04:29.610 --> 00:04:32.520 people you will be helping getting gigs because I think this is important. 00:04:32.940 --> 00:04:33.780 , Obviously, right. 00:04:34.200 --> 00:04:37.090 I'm affiliated with the ServiceNow rise up initiative, right? 00:04:37.090 --> 00:04:41.760 There's pushing like a similar thing, ? Just to get more people, into this field, 00:04:41.970 --> 00:04:45.770 getting them skilled up in ways like you are doing right that will make them 00:04:45.770 --> 00:04:47.450 good ServiceNow resources in the future. 00:04:47.780 --> 00:04:48.080 So, 00:04:48.410 --> 00:04:50.060 , Duke: I definitely don't wanna take anything from rise up. 00:04:50.060 --> 00:04:54.130 And I, I'd like to say that I'm aligned from the outside, like same goal, 00:04:54.310 --> 00:04:56.500 but just a way different strategy. 00:04:56.560 --> 00:04:58.900 And I happen to believe that my strategy's better and I'm 00:04:58.900 --> 00:04:59.830 not gonna apologize about that. 00:05:01.780 --> 00:05:03.160 CJ: And you should, right. 00:05:03.160 --> 00:05:06.520 Like what's the point in doing it if you don't think you're doing it the best? 00:05:08.502 --> 00:05:11.172 I think the goals are, are very much aligned at the end of the day. 00:05:11.172 --> 00:05:13.812 Both systems are trying to get more people into the ecosystem. 00:05:14.292 --> 00:05:14.622 Duke: Okay, 00:05:15.162 --> 00:05:15.372 CJ: Yeah. 00:05:15.612 --> 00:05:21.082 Duke: let me, let me just be right up front that, building a new system sucks. 00:05:21.182 --> 00:05:21.902 , it just sucks. 00:05:22.022 --> 00:05:26.912 I'm doing a ton of stuff that's just seat of my pants, and so 00:05:26.972 --> 00:05:29.192 like, you're roleplaying the requirements gather, right? 00:05:29.432 --> 00:05:29.732 CJ: Yeah. 00:05:29.762 --> 00:05:30.602 Yeah, absolutely. 00:05:30.652 --> 00:05:34.292 , I personally love seat of the pants, ? , that's where a lot 00:05:34.297 --> 00:05:35.672 of the creativity comes from. 00:05:35.822 --> 00:05:39.512 But now that you've been doing this, , a cohort and a half I anticipate that 00:05:39.522 --> 00:05:42.647 you've, , kinda out some of the bugs and you're now looking to formalize 00:05:42.652 --> 00:05:43.637 a little bit of what you're doing. 00:05:44.432 --> 00:05:48.482 Duke: Yeah, there's a lot of information I want to capture, right? 00:05:49.142 --> 00:05:52.712 And it helps me, it helps me decisions, it helps me keep on top of stuff. 00:05:52.712 --> 00:05:54.572 It makes me, it helps me do more intelligent. 00:05:55.037 --> 00:05:56.177 , use of my time. 00:05:56.597 --> 00:06:02.587 And so I find , there's a lot of details that I forget and there's a lot of details 00:06:02.592 --> 00:06:07.990 that I spend time looking for in email, and I've created two or three different. 00:06:08.410 --> 00:06:10.120 Excel sheets to help with that. 00:06:10.120 --> 00:06:13.510 But I, I'll tell you, I'm dealing a ton with attachments as well. 00:06:14.140 --> 00:06:17.700 , and , I never realized how bad searching through email is until I 00:06:17.700 --> 00:06:19.230 started searching for attachments. 00:06:19.800 --> 00:06:20.400 CJ: Yeah. 00:06:20.537 --> 00:06:21.017 Duke: whoa. 00:06:21.487 --> 00:06:21.787 Anyway, 00:06:21.932 --> 00:06:24.572 CJ: And if you're not using something like Google, then it's, 00:06:24.812 --> 00:06:26.102 and then the search is even worse. 00:06:26.402 --> 00:06:26.752 Duke: Right. 00:06:27.092 --> 00:06:28.382 So where do you wanna start, man? 00:06:28.787 --> 00:06:30.497 CJ: I mean, we've already started actually. 00:06:30.497 --> 00:06:33.767 See, that's the great thing, that's the great thing about doing 00:06:33.767 --> 00:06:37.547 , requirements gathering, which is my f preferred style anyway, right? 00:06:37.547 --> 00:06:40.727 Is that now I know you've got information that you need to capture, that you're 00:06:40.727 --> 00:06:44.097 dealing with a lot of attachments and that you've tried to do this, , several 00:06:44.097 --> 00:06:47.204 times already through both email and Excel spreadsheets, we've got 00:06:47.204 --> 00:06:50.804 a solid base on things that you've tried to do and a solid base on, at 00:06:50.804 --> 00:06:53.654 least at the beginning of a solid base on what you're trying to accomplish. 00:06:53.654 --> 00:06:56.414 So when you say info that you're trying to capture, , let's go 00:06:56.414 --> 00:06:58.464 ahead , and categorize that, right? 00:06:58.514 --> 00:07:00.524 what are you trying, what are you trying to store? 00:07:00.824 --> 00:07:01.814 How are you going to use it? 00:07:02.240 --> 00:07:02.510 Duke: Okay. 00:07:02.510 --> 00:07:04.340 Well maybe we start at the beginning, right? 00:07:04.460 --> 00:07:05.000 And 00:07:05.170 --> 00:07:06.940 CJ: Oh, man, we're, we're already at the beginning. 00:07:06.940 --> 00:07:07.450 We're starting in 00:07:07.460 --> 00:07:09.410 Duke: No, but I mean, the beginning of my process. 00:07:09.410 --> 00:07:14.447 So , planning a cohort, Because the one thing my competition has over 00:07:14.447 --> 00:07:18.437 me is they already have established businesses around it, right? 00:07:18.677 --> 00:07:21.887 And they have, they have full-time staff that can deal with the 00:07:21.887 --> 00:07:24.317 administrative logistics, right? 00:07:24.647 --> 00:07:28.487 And so it's hard for me to just say it starts at this date. 00:07:28.487 --> 00:07:29.837 It runs these times. 00:07:29.837 --> 00:07:32.537 And if you don't like it, It's not for you. 00:07:33.197 --> 00:07:37.492 Um, so when I first started out, I'm like, I have to get a critical mass of interest 00:07:37.785 --> 00:07:44.559 and then make the start date and the, coaching times reasonably aligned, right? 00:07:45.429 --> 00:07:50.284 And so I was putting feelers out and saying , who's interested, and so , think 00:07:50.284 --> 00:07:52.114 about this as your sales pipeline. 00:07:52.294 --> 00:07:53.164 I don't even have that. 00:07:53.674 --> 00:07:56.160 And so that information's all stuck in LinkedIn. 00:07:56.165 --> 00:07:58.590 It's stuck in email, it's stuck in wherever. 00:07:58.815 --> 00:08:01.515 CJ: Oh, I get you. 00:08:01.575 --> 00:08:03.225 You don't have a top of a funnel, 00:08:03.360 --> 00:08:04.980 Duke: yeah, I don't have who's in the pipe? 00:08:05.505 --> 00:08:06.045 CJ: right? 00:08:06.660 --> 00:08:08.805 Duke: And we do have conversations along the way. 00:08:08.805 --> 00:08:10.485 Some people just decide it's not for them. 00:08:10.665 --> 00:08:11.055 Right. 00:08:11.415 --> 00:08:12.345 Most of them decide. 00:08:12.345 --> 00:08:12.585 Yeah. 00:08:12.590 --> 00:08:12.775 Yeah. 00:08:13.305 --> 00:08:14.805 But I don't have anything to track that. 00:08:14.810 --> 00:08:19.737 So of course I pull out Excel and , it's just name email. 00:08:20.167 --> 00:08:23.437 Where did they confirm Via, so 00:08:23.512 --> 00:08:24.592 CJ: email source. 00:08:24.872 --> 00:08:25.162 Yeah. 00:08:25.237 --> 00:08:28.597 Duke: source, it was, was it LinkedIn, email, like whatever. 00:08:29.317 --> 00:08:32.017 . Then I have an acid test interest. 00:08:32.477 --> 00:08:32.767 CJ: Okay. 00:08:33.307 --> 00:08:36.127 Duke: Like some people are like, Hmm, maybe we should talk about that. 00:08:36.127 --> 00:08:41.617 So , I won't give it an acid test of true, but somebody, I have like a legit phone 00:08:41.617 --> 00:08:45.937 call about it and they just say, okay, , I gotta talk to my spouse or whatever. 00:08:46.027 --> 00:08:49.597 I put those as like a, as a more warm, it's like a, a like a lead 00:08:49.597 --> 00:08:50.687 warmth, I guess you could say. 00:08:50.992 --> 00:08:51.232 CJ: Yeah. 00:08:51.232 --> 00:08:51.412 Yeah. 00:08:51.442 --> 00:08:52.462 Qualifying ease. 00:08:52.462 --> 00:08:52.702 Yeah, 00:08:52.927 --> 00:08:53.407 Duke: Yeah. 00:08:54.007 --> 00:08:54.397 Okay. 00:08:54.397 --> 00:08:58.532 Then I track if they'd been through another program in which program. 00:08:59.822 --> 00:09:05.762 So I've got like next Gen M T B F or either of those, that's not those. 00:09:07.772 --> 00:09:12.314 , I get a lot of interest outside in North America, so I also track if 00:09:12.314 --> 00:09:14.354 you're non N A M R, where are you? 00:09:16.169 --> 00:09:16.289 CJ: As 00:09:16.434 --> 00:09:21.444 Duke: Like think there's a few people in the UK that I might let into the next one. 00:09:21.564 --> 00:09:25.074 CJ: Yeah, but it's probably a lot harder like with a, an pack given 00:09:25.074 --> 00:09:26.444 the way , the time zones align. 00:09:27.209 --> 00:09:27.499 Okay. 00:09:28.229 --> 00:09:34.919 Duke: And then I have some check boxes for if they object is the objection, 00:09:35.249 --> 00:09:41.013 financial timeline or something else, like they already have a job or something. 00:09:41.513 --> 00:09:41.973 CJ: Got it. 00:09:42.183 --> 00:09:44.163 So objection and then Objection, reason. 00:09:44.763 --> 00:09:45.123 Duke: Yeah. 00:09:45.423 --> 00:09:47.193 , I imagine it being like a choice. 00:09:47.540 --> 00:09:48.440 Objection, reason. 00:09:48.765 --> 00:09:49.505 CJ: Oh, okay. 00:09:49.505 --> 00:09:49.925 Got it. 00:09:49.985 --> 00:09:50.225 Yeah. 00:09:50.225 --> 00:09:51.485 Like just a, a selection. 00:09:51.485 --> 00:09:51.785 Okay. 00:09:51.860 --> 00:09:52.760 Duke: yeah, so it's none. 00:09:52.760 --> 00:09:53.450 If it is none. 00:09:53.450 --> 00:09:54.860 And it is something, if it is something. 00:09:55.535 --> 00:09:55.895 CJ: Right. 00:09:56.465 --> 00:09:56.895 Makes sense. 00:09:57.220 --> 00:10:00.250 Duke: So then it's just like all the logistics of, did I 00:10:00.250 --> 00:10:01.390 actually send them an invite? 00:10:01.900 --> 00:10:08.083 , and when I give them the invite, I send them like a contract, via, um, 00:10:08.623 --> 00:10:09.613 CJ: Oh, DocuSign. 00:10:09.913 --> 00:10:10.093 Duke: Mm-hmm. 00:10:10.323 --> 00:10:14.083 So I send everybody, so I get keep track is of , who's, , submitted a contract, 00:10:14.473 --> 00:10:14.803 CJ: Right. 00:10:15.043 --> 00:10:18.793 Did you invite them at the, and did you send a contract and have they Yeah. 00:10:18.793 --> 00:10:19.813 Have they signed it now? 00:10:19.993 --> 00:10:21.373 Is any of this, oh, I'm sorry. 00:10:21.373 --> 00:10:21.763 Keep going. 00:10:21.997 --> 00:10:23.077 Duke: Is any of this what. 00:10:23.497 --> 00:10:26.197 CJ: I was gonna ask, uh, is any of this automated at this point? 00:10:26.197 --> 00:10:26.767 Oh, is this all you? 00:10:27.037 --> 00:10:28.627 Uh, manually by ticking 00:10:28.687 --> 00:10:29.287 Duke: It's all me. 00:10:29.287 --> 00:10:36.937 Like, whenever I, whenever like, um, when I, uh, DocuSign will send me an 00:10:36.937 --> 00:10:40.777 email back saying like, this contract's been signed, which it is dumb. 00:10:40.782 --> 00:10:43.387 It says this contract has been signed, but nowhere in there 00:10:43.387 --> 00:10:44.497 does it say who signed it. 00:10:44.647 --> 00:10:48.277 You literally gotta go back to the platform and like look to see 00:10:48.277 --> 00:10:50.797 which ones are signed and which is like a five step process. 00:10:50.802 --> 00:10:51.547 I hate it. 00:10:52.672 --> 00:10:53.062 CJ: Yeah. 00:10:53.167 --> 00:10:53.347 Duke: it. 00:10:53.752 --> 00:10:56.002 CJ: Yeah, no, that, that sounds pretty, pretty gruesome. 00:10:56.977 --> 00:10:58.087 Duke: But I do that. 00:10:58.477 --> 00:11:02.617 Then I ask them to submit like little tiny bios and I check to see if they did that. 00:11:02.857 --> 00:11:05.827 I asked 'em to send me their resume as it is right now. 00:11:06.397 --> 00:11:06.817 Right. 00:11:06.937 --> 00:11:09.337 So I asked 'em to send me that. 00:11:09.337 --> 00:11:10.357 It's like who's done it? 00:11:10.507 --> 00:11:12.287 But also where is the darn thing? 00:11:12.287 --> 00:11:16.307 'cause five weeks later I want to pull out an example of how to 00:11:16.312 --> 00:11:19.607 write something in a resume, or I'm doing somebody's resume review. 00:11:19.982 --> 00:11:20.852 Where is it? 00:11:21.092 --> 00:11:21.992 Is it an email? 00:11:21.992 --> 00:11:23.522 Did I put it in my resume folder? 00:11:23.877 --> 00:11:24.227 CJ: Right. 00:11:24.932 --> 00:11:29.997 Duke: So there's a lot of just pulling pieces of paper into, physical folders. 00:11:30.522 --> 00:11:31.032 CJ: Got it. 00:11:31.302 --> 00:11:35.897 , I mean, this is ground zero for what ServiceNow is good for, this is taking 00:11:35.897 --> 00:11:40.037 work that exists manually, offline and inside of Excel spreadsheets. 00:11:40.317 --> 00:11:41.637 and there's a process here, right? 00:11:41.637 --> 00:11:45.637 , there's a workflow, , and then taking that and translating it into digital. 00:11:45.952 --> 00:11:50.252 And making it move easier so that , you can gain back like, you know, 00:11:50.432 --> 00:11:52.172 80% of your time on this thing. 00:11:52.382 --> 00:11:52.802 Duke: Right. 00:11:53.432 --> 00:11:54.992 CJ: Alright, so, oh, keep going. 00:11:55.308 --> 00:11:57.618 Duke: well, I was just going to start into the next thing, but do you have quick 00:11:57.618 --> 00:11:59.478 questions about the pipeline process? 00:12:00.018 --> 00:12:02.478 CJ: Uh, no, I think I got the pipeline process down right? 00:12:02.478 --> 00:12:05.593 Like I got a bunch of information that you're collecting and then you've 00:12:05.593 --> 00:12:08.228 got some things that you're sending out , and that you're waiting on 00:12:08.233 --> 00:12:11.638 returns , for, and you wanna track the process of all on all of those things. 00:12:11.998 --> 00:12:12.988 That makes a lot of sense. 00:12:13.208 --> 00:12:17.238 , the question, and the next question I have is, , is this like a, is this a app that 00:12:17.243 --> 00:12:21.598 only , you use or is this, does it have a self , service portion of it as well? 00:12:22.343 --> 00:12:31.643 Duke: I think at the start it would just be handy to have a place where like user, 00:12:31.703 --> 00:12:37.973 like , the stuff I collect from people and all the different true falses was in 00:12:37.973 --> 00:12:40.463 somewhere where there were unique records 00:12:41.648 --> 00:12:43.898 CJ: So , like a checklist that you go through while you're 00:12:43.898 --> 00:12:44.798 having a call with someone. 00:12:44.888 --> 00:12:47.678 Duke: Yeah, it could be checklist or it could just be like, Hey, 00:12:47.725 --> 00:12:49.435 who's scheduled for cohort three? 00:12:49.435 --> 00:12:52.902 Who hasn't returned their, contract yet? 00:12:53.602 --> 00:12:53.942 CJ: Got it. 00:12:54.042 --> 00:12:57.222 Duke: So the, yeah, so maybe like some of these things aren't checklists, 00:12:57.222 --> 00:12:59.172 they're literal, like they're properties. 00:12:59.172 --> 00:12:59.232 I. 00:12:59.742 --> 00:13:00.072 CJ: Right. 00:13:00.262 --> 00:13:00.472 Okay. 00:13:00.472 --> 00:13:03.592 And is all this information gap doing that initial call or is it 00:13:03.772 --> 00:13:07.082 back and forth over email, or how do you typically get the info? 00:13:07.558 --> 00:13:09.178 Duke: that's a great question. 00:13:09.228 --> 00:13:14.298 It all just kind of manifests, like if they're, if they're, like, if 00:13:14.298 --> 00:13:16.458 we're talking on LinkedIn, like, Hey, I heard about your cohort. 00:13:16.488 --> 00:13:18.048 I'm like, so let's, oh, let's do a call. 00:13:18.246 --> 00:13:18.696 Right. 00:13:18.906 --> 00:13:22.323 So that might be interesting,, for the pipeline is calls that we've had. 00:13:22.446 --> 00:13:24.881 cause then I'd know, 'cause I've been in places where it was like, I 00:13:24.881 --> 00:13:27.461 was dealing with 50 people at once in a week and it's like, did we 00:13:27.461 --> 00:13:28.541 could call and talk on the phone? 00:13:28.541 --> 00:13:29.471 Yeah, we talked on the phone. 00:13:29.951 --> 00:13:33.041 So that might be an interesting thing to track is just contacts. 00:13:33.306 --> 00:13:33.756 CJ: Yeah. 00:13:33.816 --> 00:13:34.596 Yeah, absolutely. 00:13:34.686 --> 00:13:36.816 this is shaping up to be like a mini c r m. 00:13:36.996 --> 00:13:38.676 Duke: Yeah, it like a very mini one. 00:13:38.676 --> 00:13:41.706 I don't, I don't care for like full c r m functionality. 00:13:41.856 --> 00:13:45.216 It would if I scaled it as a business and I had like 10 of me, 00:13:45.786 --> 00:13:46.146 CJ: sure. 00:13:46.956 --> 00:13:51.786 Duke: it's just me and the real headache I have is just, , blah blah. 00:13:51.786 --> 00:13:54.326 Said that he, wanted to check back in two weeks. 00:13:56.246 --> 00:13:56.546 CJ: Okay. 00:13:57.146 --> 00:13:57.506 Right. 00:13:57.506 --> 00:14:00.386 So that I could, I definitely see that as a headache. 00:14:00.386 --> 00:14:02.246 Right, but is it the real headache? 00:14:02.246 --> 00:14:03.866 , because you're the client now, right? 00:14:03.871 --> 00:14:04.316 So I'm gonna, 00:14:04.321 --> 00:14:07.263 Duke: so many more, there's so many more like, did they get me their resume? 00:14:07.293 --> 00:14:10.508 No, , I got 15 people in cohort two, and , I have a check that says did they 00:14:10.508 --> 00:14:12.968 gimme the resume or not, but where is it? 00:14:13.028 --> 00:14:15.938 It's in my email somewhere and I'm still like searching 00:14:15.938 --> 00:14:17.318 through my email like a pleb. 00:14:18.263 --> 00:14:18.553 CJ: Yeah. 00:14:18.778 --> 00:14:20.333 Duke: to get to the, 'cause we're doing, we're just on the 00:14:20.333 --> 00:14:21.953 phase of resume reviews now. 00:14:22.173 --> 00:14:26.276 And so I'm plowing through, trying to find it in the email now, trying 00:14:26.276 --> 00:14:28.301 to get them into my, resume folder. 00:14:28.841 --> 00:14:31.781 And some of them are sending me like, oh, you know, I've learned 00:14:31.781 --> 00:14:33.521 so much and I finally get it. 00:14:33.521 --> 00:14:37.481 Now here's a second version of my resume before I get to my review. 00:14:37.481 --> 00:14:40.031 So it's like, now it's like, which of those resumes are authoritative? 00:14:40.241 --> 00:14:40.931 You see what I mean? 00:14:41.261 --> 00:14:44.381 When it's two days later and three of them have played, have done this to me. 00:14:44.381 --> 00:14:44.681 Right. 00:14:45.356 --> 00:14:45.596 CJ: Yep. 00:14:46.061 --> 00:14:50.231 Duke: It's just like, so, and it would make it so much easier. 00:14:50.231 --> 00:14:53.711 'cause right now I have Excel and email and they're separate. 00:14:54.266 --> 00:14:54.686 CJ: Right. 00:14:54.931 --> 00:14:58.561 Duke: But in ServiceNow you get like a user record and it has attachments. 00:14:59.026 --> 00:15:01.601 CJ: Yeah, and you can also have, related, , tables, right? 00:15:01.811 --> 00:15:04.661 That you can put off the user record so you can see if there's different versions 00:15:04.661 --> 00:15:06.791 of a resume and so on and so forth. 00:15:07.076 --> 00:15:07.366 Duke: Yeah. 00:15:08.006 --> 00:15:10.976 CJ: So , since I'm the consultant in this situation, I'll tell you, , what 00:15:10.976 --> 00:15:14.976 I tell a lot of my clients is that, the problems that you are identifying 00:15:14.976 --> 00:15:17.646 are different problem, right? 00:15:17.646 --> 00:15:20.796 And it's, so I think you're missing the bigger problem, right? 00:15:20.801 --> 00:15:24.691 And the bigger problem is, that this takes a lot of time for you to do. 00:15:25.141 --> 00:15:27.931 And even if we build the app in the way that you're asking for 00:15:27.931 --> 00:15:30.781 me to build it, you're still going to have to do all the work. 00:15:32.116 --> 00:15:36.706 So we aren't, we, what we're what we're doing is mean you are repository, but 00:15:36.706 --> 00:15:39.086 we're not giving you, , any time back. 00:15:39.266 --> 00:15:40.046 Does that make sense? 00:15:40.796 --> 00:15:46.246 Duke: Um, , I would ask you to consider that I spend a lot of time 00:15:46.366 --> 00:15:49.876 looking for like Joe Schmoe's resume, 00:15:50.401 --> 00:15:50.761 CJ: Sure. 00:15:51.031 --> 00:15:51.331 Okay. 00:15:51.391 --> 00:15:51.571 Yeah. 00:15:51.576 --> 00:15:55.631 So yeah, so we do give you some time back by, , putting everything in one place. 00:15:55.631 --> 00:15:56.231 Absolutely. 00:15:56.351 --> 00:15:56.741 Duke: Right. 00:15:57.101 --> 00:15:58.901 CJ: But you still have to put it there. 00:15:59.121 --> 00:15:59.901 Duke: Yeah, yeah. 00:16:00.081 --> 00:16:01.101 No, you're absolutely right. 00:16:01.106 --> 00:16:05.091 Like if we could say, send your resume to this email. 00:16:05.331 --> 00:16:09.711 We can figure out what their email address and use an inbound action or 00:16:09.711 --> 00:16:13.311 a flow designer to basically say, just look up the user with the same email 00:16:13.311 --> 00:16:15.111 address and attach this attachment there. 00:16:15.440 --> 00:16:16.010 CJ: Wait, I'm sorry. 00:16:16.010 --> 00:16:16.700 Say that again. 00:16:16.920 --> 00:16:20.070 Duke: Okay, so , they send their resume to my Gmail, right? 00:16:20.843 --> 00:16:23.423 Then I'm like, okay, let's download it and then I have to open service 00:16:23.423 --> 00:16:26.693 now, log in and then like find their user record and upload it. 00:16:26.753 --> 00:16:29.903 And that's where you're saying, oh Robert, you're not saving any time at all. 00:16:29.908 --> 00:16:30.323 You're right. 00:16:30.653 --> 00:16:33.623 But if we could get, if we could get them to just say, like, email 00:16:33.623 --> 00:16:35.850 my instance with your attachment. 00:16:35.970 --> 00:16:40.860 And so Joe Schmo emails my instance, and he's like, joe@schmo.com. 00:16:41.143 --> 00:16:43.753 Well, I already have his email address because he's in my funnel. 00:16:44.143 --> 00:16:44.623 CJ: Right? 00:16:44.818 --> 00:16:48.208 Duke: And then it just says, oh, joe@schmo.com sent this attachment. 00:16:48.208 --> 00:16:50.308 Take that attachment, attach it to his user record. 00:16:50.518 --> 00:16:51.958 So I, now I know he has his resume. 00:16:52.303 --> 00:16:52.873 CJ: Exactly. 00:16:52.903 --> 00:16:57.413 , now we're talking about taking, , the process that, is time consuming, right? 00:16:57.713 --> 00:17:01.103 , reducing the time that it takes, but also making it more efficient for you as well. 00:17:01.313 --> 00:17:03.083 I, you know, the, keep going. 00:17:03.083 --> 00:17:03.743 Let's go. 00:17:03.743 --> 00:17:05.093 Um, so let 00:17:05.258 --> 00:17:08.168 Duke: let me, let me lemme, because we're on a topic that. 00:17:08.513 --> 00:17:13.663 Is bigger than just resumes too, because my first session is a real 00:17:13.663 --> 00:17:15.433 deep dive on the why of ServiceNow, 00:17:16.153 --> 00:17:16.543 CJ: Right. 00:17:16.603 --> 00:17:19.573 Duke: You like, can I just pull my hair out for two seconds here? 00:17:19.633 --> 00:17:20.143 CJ: Go for it. 00:17:20.383 --> 00:17:26.773 Duke: it blows my mind how many people are coming out of bootcamps that cannot 00:17:26.773 --> 00:17:29.353 adequately describe what ServiceNow does. 00:17:30.448 --> 00:17:32.458 And what his value proposition is. 00:17:32.698 --> 00:17:37.408 I can't tell you how many times it's been like, uh, it's a ticketing tool for it. 00:17:39.368 --> 00:17:44.348 They haven't inherited any gravitas around like, why does everybody love it so much? 00:17:44.348 --> 00:17:45.458 If it's just that 00:17:46.568 --> 00:17:47.078 CJ: Yeah. 00:17:47.138 --> 00:17:47.505 Right. 00:17:47.505 --> 00:17:50.911 I was at the, ServiceNow Summit here in Chicago, just this week. 00:17:51.031 --> 00:17:55.341 And, , the guy who was presenting mentioned the ServiceNow, , has for 00:17:55.341 --> 00:17:57.411 a client 80% of the Fortune 500. 00:17:57.753 --> 00:18:00.093 They're not all just using it because it's a ticketing system. 00:18:00.138 --> 00:18:00.558 Duke: Right. 00:18:00.588 --> 00:18:05.088 And I'm just like, I wanna be clear for these learners, it's not their fault 00:18:05.553 --> 00:18:05.843 CJ: Yeah. 00:18:06.078 --> 00:18:09.138 Duke: just, but who's gonna go deep and just say like, listen, this is 00:18:09.138 --> 00:18:11.088 why ServiceNow is so miraculous. 00:18:11.328 --> 00:18:15.385 So anyways, I do that as session number one, the miracle of ServiceNow, 00:18:15.505 --> 00:18:19.480 not like, ServiceNow, the ticket tool, the miracle of ServiceNow. 00:18:20.140 --> 00:18:23.910 And then the first homework they get is I send them this thing called 00:18:23.910 --> 00:18:25.585 the, , solution ideation template, 00:18:26.155 --> 00:18:26.485 CJ: Yeah. 00:18:26.645 --> 00:18:28.235 Duke: Take all that stuff in your own life. 00:18:28.235 --> 00:18:30.455 Like all the jobs you had where you just like pulled your hair 00:18:30.455 --> 00:18:31.445 and said, this is bullshit. 00:18:31.445 --> 00:18:32.345 I can't stand this. 00:18:32.601 --> 00:18:34.821 And make a ServiceNow app out of it. 00:18:35.181 --> 00:18:38.915 But use some of the principles we discussed in the miracle 00:18:38.915 --> 00:18:40.145 of ServiceNow session. 00:18:40.306 --> 00:18:44.446 To tell me why this app belongs on ServiceNow, what value does 00:18:44.446 --> 00:18:46.516 ServiceNow bring to this situation? 00:18:46.775 --> 00:18:47.025 CJ: Right. 00:18:47.025 --> 00:18:51.135 Is it fair to say that then the solution ideation template to the bringing the app 00:18:51.135 --> 00:18:55.545 to life, um, is that like the homework for the Miracle Service Now session? 00:18:55.545 --> 00:18:58.845 Or is this, or is it a separate thing that has its own homework? 00:18:58.845 --> 00:18:58.905 I. 00:18:59.095 --> 00:19:00.445 Duke: it's an ongoing thing. 00:19:00.445 --> 00:19:03.405 So like well a lot of them don't get it in the first session, but as 00:19:03.405 --> 00:19:06.705 we go through session more and more sessions, then they're like, oh, okay. 00:19:06.705 --> 00:19:07.005 I get it. 00:19:07.010 --> 00:19:12.585 Like it's usually around after we talk about database structure and a e s that 00:19:13.065 --> 00:19:16.335 they finally get, oh, the reason I'm doing this thing, so I can write down 00:19:16.335 --> 00:19:20.085 the tables and the columns that I need, and the properties of those tables. 00:19:20.320 --> 00:19:20.680 CJ: Yeah. 00:19:21.245 --> 00:19:22.525 Duke: Uh, and what to do there. 00:19:22.525 --> 00:19:24.745 And that is currently a Word document. 00:19:24.788 --> 00:19:27.938 because it is a word processor thing, it's very heavily formatted. 00:19:27.938 --> 00:19:31.688 And so word I usually prefer, but it strikes me now that I don't necessarily 00:19:31.688 --> 00:19:33.348 need that , as an attachment. 00:19:33.348 --> 00:19:34.968 Like maybe a different record type. 00:19:35.081 --> 00:19:36.221 CJ: Yeah, possibly. 00:19:36.401 --> 00:19:39.281 Duke: here's all the solution ideation templates and who 00:19:39.281 --> 00:19:41.531 submitted them and link it back to. 00:19:41.876 --> 00:19:43.766 Users, you know what I mean? 00:19:43.766 --> 00:19:46.806 I'm sure that there's hooks for ways we can make that interesting. 00:19:46.806 --> 00:19:47.126 Later. 00:19:47.473 --> 00:19:48.283 CJ: Yeah, I agree. 00:19:48.333 --> 00:19:51.753 , and so , where we are here now in this process is that we started off 00:19:51.758 --> 00:19:55.163 talking about how we can get the work right, and then how we're gonna store 00:19:55.163 --> 00:19:56.603 the data that comprises the work. 00:19:56.608 --> 00:20:00.033 And now we're talking about, how you deliver the class. 00:20:00.033 --> 00:20:01.653 And this is a different set of work. 00:20:02.598 --> 00:20:04.158 And this is a different set of data. 00:20:04.368 --> 00:20:08.108 So are you looking for an app that is not just the intake, right, 00:20:08.108 --> 00:20:11.348 which is what we were talking about earlier, but now also the delivery 00:20:11.348 --> 00:20:13.118 or the execution of the coursework. 00:20:14.168 --> 00:20:18.691 Duke: Kind of so there's one thing I tell my cohort, is that I'm not 00:20:18.691 --> 00:20:20.281 gonna chase anybody at homework. 00:20:20.373 --> 00:20:24.453 nor am I gonna judge anybody at how much they have done. 00:20:25.083 --> 00:20:25.373 CJ: Okay. 00:20:25.773 --> 00:20:26.343 Duke: You know what I mean? 00:20:26.343 --> 00:20:28.623 Like every, there's all kinds of different stages of life. 00:20:28.623 --> 00:20:32.223 There's people that have full-time jobs while they're doing this. 00:20:32.350 --> 00:20:34.510 maybe they got sick parents, sick kids. 00:20:34.780 --> 00:20:37.800 Maybe they've got, , like we had a awful flood in our house. 00:20:37.800 --> 00:20:39.360 We had sewage pumped into our basement. 00:20:39.360 --> 00:20:41.010 So, , I myself am dealing with. 00:20:41.100 --> 00:20:42.180 All the drama of that. 00:20:42.180 --> 00:20:44.520 There's just too much drama in life for grownups, right? 00:20:44.940 --> 00:20:48.213 And so it's like if you don't, if you don't do this homework for 00:20:48.213 --> 00:20:50.290 whatever reason, no judgment from me. 00:20:50.521 --> 00:20:50.871 CJ: Right. 00:20:51.146 --> 00:20:54.110 Duke: So I know there's a rant there, but I don't want it to be some kind 00:20:54.110 --> 00:20:55.790 of like hard thing like pass fail. 00:20:55.970 --> 00:21:02.230 But , there are some things that I want to see, like I want to check in on. 00:21:02.235 --> 00:21:05.830 So we do a requirements gathering workshop where they ask me about my 00:21:05.830 --> 00:21:09.940 soaping business and they have to like design an app around it, kind 00:21:09.940 --> 00:21:11.470 of like what we're doing right now. 00:21:11.470 --> 00:21:17.393 and so after they build that app, we do all the other components of 00:21:17.393 --> 00:21:19.103 ServiceNow in the context of that app. 00:21:19.103 --> 00:21:21.823 So basically I want to get everybody across the finish line. 00:21:21.823 --> 00:21:26.083 So I'd love to have tasks where I could say, where it's like, 00:21:26.638 --> 00:21:30.358 It's associated to the user and I have some kind of status on it. 00:21:30.958 --> 00:21:32.308 CJ: Oh, so this is pretty cool. 00:21:32.458 --> 00:21:36.638 you're having the cohort essentially, , build individualized applications, but 00:21:36.638 --> 00:21:41.463 then , because the applications all follow the same sort of template and then 00:21:41.463 --> 00:21:45.243 talk to them with a frame of reference that relates to them, even though 00:21:45.248 --> 00:21:47.943 you're talking at a higher level that relates to everyone at the same time. 00:21:48.213 --> 00:21:48.753 Duke: That's right. 00:21:48.783 --> 00:21:51.333 We all build something big, but it's not like, you know. 00:21:52.353 --> 00:21:55.083 Five of us in a group or 10 of us in a group. 00:21:55.143 --> 00:21:57.693 We all air quotes worked together. 00:21:58.653 --> 00:22:01.593 No, it's just everybody works together on the requirements, but 00:22:02.493 --> 00:22:04.083 you build it on your own instance. 00:22:04.113 --> 00:22:06.303 Everybody has to go through the crucible of build. 00:22:06.791 --> 00:22:07.031 CJ: Yeah. 00:22:07.031 --> 00:22:07.751 I, I agree. 00:22:08.021 --> 00:22:08.231 Yeah. 00:22:08.296 --> 00:22:12.286 , Duke: and so , I'd like to be able to have a, whether it's a task or a 00:22:12.286 --> 00:22:18.616 checkbox, something that says they got to the end of this requirement. 00:22:19.411 --> 00:22:19.801 CJ: Okay. 00:22:20.311 --> 00:22:22.651 Duke: Using that term requirement softly. 00:22:23.041 --> 00:22:27.658 CJ: So is this a stage or state field that is driving this kinda 00:22:27.658 --> 00:22:30.478 like lifecycle of the course right. 00:22:30.478 --> 00:22:31.498 Per individual 00:22:32.125 --> 00:22:32.725 Duke: Yeah. 00:22:33.025 --> 00:22:35.575 I'm still trying to figure out what the task bit is. 00:22:35.580 --> 00:22:35.935 Right. 00:22:35.935 --> 00:22:38.095 I tell, I tell my this, my students this all the time, 00:22:38.145 --> 00:22:40.005 there has to be a tasky component 00:22:40.351 --> 00:22:40.641 CJ: Yeah. 00:22:40.841 --> 00:22:41.241 Fair enough. 00:22:41.711 --> 00:22:42.371 Duke: I think. 00:22:42.570 --> 00:22:44.880 where the more important pieces of homework are. 00:22:44.880 --> 00:22:45.240 Yes. 00:22:45.240 --> 00:22:48.530 They're simple tasks like Joe Schmo, please make sure you 00:22:48.530 --> 00:22:49.730 have the Soaping app done. 00:22:49.940 --> 00:22:52.190 Do whatever you can including call me 00:22:52.316 --> 00:22:53.096 to get it done. 00:22:53.336 --> 00:22:55.256 So that could be, that could definitely be a task. 00:22:55.466 --> 00:22:55.686 And 00:22:56.071 --> 00:22:56.361 CJ: yeah. 00:22:57.416 --> 00:23:00.586 Duke: then, who doesn't have the Soaping app done or who haven't I checked in with? 00:23:01.681 --> 00:23:01.891 CJ: So. 00:23:01.891 --> 00:23:03.751 Duke: now, that's all just in my brain. 00:23:04.138 --> 00:23:07.408 CJ: is this something that, you're tracking on your own or is 00:23:07.413 --> 00:23:12.208 this something that you want the individual to assist you in tracking? 00:23:12.641 --> 00:23:13.271 You know what I mean? 00:23:13.321 --> 00:23:17.441 What I'm asking essentially is, Are you asking the indi the 00:23:17.441 --> 00:23:21.821 individual and course, Hey, did you create the soap, the Soaping app? 00:23:21.821 --> 00:23:25.811 And if they say, yeah, you go in and you change the state from , beginner 00:23:25.811 --> 00:23:28.451 to Soaping app, app completed, right? 00:23:28.691 --> 00:23:29.951 Or is this a situation. 00:23:31.421 --> 00:23:34.811 Where , you want them to log into something like a portal. 00:23:34.928 --> 00:23:38.738 . And they upload their work and then the process of upload, uploading 00:23:38.738 --> 00:23:40.553 the work changes, their state. 00:23:40.703 --> 00:23:41.153 Moves it 00:23:41.393 --> 00:23:44.633 Duke: Maybe they can interact like, here's an expectation record and you can, 00:23:44.733 --> 00:23:45.023 CJ: Yeah. 00:23:45.623 --> 00:23:48.893 Duke: like an expectation record is gimme your V two resume. 00:23:49.043 --> 00:23:53.633 An expectation record might be validate that you've closed the Soaping app. 00:23:54.233 --> 00:23:54.443 CJ: Yeah. 00:23:54.443 --> 00:23:56.813 And then we, when you think about it, right from that perspective, 00:23:56.813 --> 00:24:00.323 this is just a series of catalog tasks to a certain degree, right? 00:24:00.323 --> 00:24:00.923 It's a process. 00:24:00.923 --> 00:24:02.693 There's a workflow behind it, right? 00:24:02.698 --> 00:24:05.093 And maybe catalog tasks is the wrong way to think about it. 00:24:05.093 --> 00:24:06.953 But you know, there is a. 00:24:07.663 --> 00:24:08.473 There's a task. 00:24:08.473 --> 00:24:12.223 That task, , is a, predecessor to another task, which is a predecessor 00:24:12.223 --> 00:24:15.343 to another task, so on and so forth, until they get to the finish line. 00:24:15.343 --> 00:24:17.443 And the finish line is the completion of the course. 00:24:17.753 --> 00:24:19.643 . And so when they look back, they can look back at all those 00:24:19.643 --> 00:24:20.923 tasks , that they completed. 00:24:21.103 --> 00:24:24.103 Some of them will have attachments, some of them not right. 00:24:24.103 --> 00:24:24.613 And. 00:24:25.138 --> 00:24:27.148 But they're driving this thing forward. 00:24:27.178 --> 00:24:30.028 And then you can look at the back end of it and see all the 00:24:30.028 --> 00:24:33.998 data that's been put in via the customer, , via each, , individual. 00:24:34.268 --> 00:24:36.398 But are you looking for something like that or are you looking 00:24:36.403 --> 00:24:39.428 for something where you know they've completed the thing? 00:24:39.428 --> 00:24:42.523 Then you check the box off and you just use it in that way and you 00:24:42.523 --> 00:24:44.323 create your own dashboard to monitor. 00:24:45.053 --> 00:24:45.263 Duke: Okay. 00:24:45.263 --> 00:24:51.263 So whether it's their like interaction with the record that self closes. 00:24:52.493 --> 00:24:55.646 I don't really care, but I do have a set of expectations. 00:24:55.826 --> 00:24:59.216 And , this is an interesting angle, not only that I have for them, but 00:24:59.216 --> 00:25:00.866 maybe they don't know for themselves. 00:25:01.316 --> 00:25:03.326 Like at the start, there's just a lot of moving parts. 00:25:03.326 --> 00:25:05.091 , Hey, listen, get me a resume. 00:25:05.091 --> 00:25:08.361 Hey listen, start working on these solution ideation templates. 00:25:08.701 --> 00:25:13.111 , when I teach them users, groups and roles, I teach them how to build a 00:25:13.111 --> 00:25:15.781 ServiceNow admin group on their instance. 00:25:16.336 --> 00:25:18.856 Put their own personal account in there. 00:25:18.916 --> 00:25:24.826 Granted the admin role, then make an account for me, copy the password and 00:25:24.831 --> 00:25:26.356 send me the instance and the password. 00:25:27.191 --> 00:25:27.481 CJ: Okay. 00:25:27.676 --> 00:25:28.936 Duke: Like that's an exercise. 00:25:28.936 --> 00:25:31.366 And it's one of the first exercises so that when they get 00:25:31.371 --> 00:25:34.126 to like flow designer and they're like, Hey, my flow doesn't work. 00:25:34.126 --> 00:25:36.076 I'm just like, let me just log into your system. 00:25:36.495 --> 00:25:36.945 CJ: Yeah, that makes 00:25:37.140 --> 00:25:39.180 Duke: See what I, so I'm just like going really, really 00:25:39.180 --> 00:25:40.470 deep on a lot of this stuff. 00:25:40.740 --> 00:25:44.700 But like you can imagine like none of them are in order, right? 00:25:44.700 --> 00:25:47.130 So it's not like a flow that says do this, then this and this. 00:25:47.130 --> 00:25:51.090 It's just like, here's all the things and then weekly here's more 00:25:51.090 --> 00:25:52.650 expectation, more expectations. 00:25:52.650 --> 00:25:55.530 So at least it's visible for them and us. 00:25:55.530 --> 00:25:57.120 So I'm definitely gonna change my answer. 00:25:57.120 --> 00:25:58.440 That's a portal. 00:25:58.658 --> 00:26:02.318 That is useful to me and them is definitely a useful thing. 00:26:02.963 --> 00:26:03.323 CJ: Okay. 00:26:03.403 --> 00:26:04.153 That makes sense. 00:26:04.318 --> 00:26:07.948 Duke: And shoot something else I just did last week. 00:26:07.948 --> 00:26:09.238 I'm like, here's my Calendly. 00:26:09.238 --> 00:26:10.888 Everybody book a time, 00:26:11.231 --> 00:26:11.501 CJ: Oh yeah. 00:26:11.501 --> 00:26:12.221 I love Calendly. 00:26:12.605 --> 00:26:14.525 Duke: oh, wouldn't a Calendly integration be so sweet? 00:26:14.825 --> 00:26:15.095 Hmm. 00:26:15.875 --> 00:26:17.165 CJ: Yeah, it would be, huh. 00:26:17.435 --> 00:26:18.155 That's a nice to have. 00:26:18.155 --> 00:26:19.065 We'll put that on a nice to, 00:26:19.145 --> 00:26:19.625 Duke: Yeah. 00:26:19.715 --> 00:26:21.065 But like a record producer, right? 00:26:21.065 --> 00:26:21.275 Like I. 00:26:21.745 --> 00:26:22.035 CJ: yeah. 00:26:22.250 --> 00:26:25.730 Duke: Here we are on the Robert Fedor ServiceNow Coaching cohort 00:26:25.730 --> 00:26:27.470 portal, book a time, right? 00:26:27.678 --> 00:26:28.448 CJ: Yeah, exactly. 00:26:28.623 --> 00:26:30.543 Duke: to Calendly and then that just does its thing. 00:26:30.800 --> 00:26:33.225 CJ: so I'm gonna try to tie some of this together, right, because we went 00:26:33.225 --> 00:26:36.855 in, two different directions, on two different, definitions of work and 00:26:36.860 --> 00:26:38.325 two different parts of this process. 00:26:38.535 --> 00:26:40.605 But there are, they are complimentary, right? 00:26:40.610 --> 00:26:44.625 So from where I'm sitting right now, you have an intake process, 00:26:44.775 --> 00:26:45.975 right, that you need to manage. 00:26:46.035 --> 00:26:49.131 That meant that the way that you're managing it now is, basically a wing 00:26:49.131 --> 00:26:51.385 and a prayer, somebody will e email 00:26:51.490 --> 00:26:52.715 Duke: highly manual. 00:26:53.035 --> 00:26:53.575 CJ: Yes. 00:26:53.631 --> 00:26:54.861 incredibly manual. 00:26:54.920 --> 00:26:56.865 not just like manual as in corporate. 00:26:56.870 --> 00:26:57.045 It. 00:26:57.165 --> 00:26:58.815 Somebody sent me an email manual. 00:26:58.935 --> 00:27:02.265 This is manual in, in that it might be a several different, 00:27:02.315 --> 00:27:03.685 intake, , sources for you, 00:27:03.685 --> 00:27:07.295 ? LinkedIn could be email, it could be, any source of things. 00:27:07.595 --> 00:27:09.665 Somebody could have stopped you on the street, right? 00:27:10.680 --> 00:27:14.930 Um, so, you know, with intake you got a highly manual process that you want to 00:27:14.930 --> 00:27:20.365 streamline the abil the way that you get, , information from your potential, cohort. 00:27:21.010 --> 00:27:21.310 Right. 00:27:21.413 --> 00:27:26.333 We've categorized that you need to really, , be able to, capture attachments 00:27:26.483 --> 00:27:30.143 and we've also, , captured , the fields that you're gonna use, right? 00:27:30.143 --> 00:27:32.633 And that you're gonna be used these field, a lot of these fields to track 00:27:32.633 --> 00:27:36.803 the progress or to validate whether or not a qualified, whether or not 00:27:36.983 --> 00:27:40.793 a potential cohort member will be someone that you actually interact 00:27:40.793 --> 00:27:42.893 with more to see if they're interested. 00:27:43.225 --> 00:27:46.705 we've also updated, now this is the thing well, where sometimes 00:27:46.705 --> 00:27:48.085 jumping around is helpful. 00:27:48.205 --> 00:27:51.775 We validated that you'd likely want this , to have some kind of po , portal 00:27:51.775 --> 00:27:56.505 component, So when we started collecting the information around the intake app, 00:27:56.628 --> 00:28:00.518 you were very much in the mind of, I just need somewhere to put this stuff. 00:28:01.011 --> 00:28:03.891 , if I just have somewhere to put it, then that's enough. 00:28:04.071 --> 00:28:07.881 But then when we started talking about the coursework and how your 00:28:07.881 --> 00:28:12.141 cohort interacts with you and how you interact with them and being able to, 00:28:12.191 --> 00:28:16.641 , communicate progress, , you say, well, actually a portal will be very valuable. 00:28:16.791 --> 00:28:17.031 Right? 00:28:17.031 --> 00:28:18.981 So then we backport the portal. 00:28:19.201 --> 00:28:20.311 To the intake app. 00:28:20.341 --> 00:28:20.671 Right. 00:28:20.671 --> 00:28:25.521 And we can use that here as, as probably , the way we want folks to interact with 00:28:25.521 --> 00:28:27.231 you during the intake process as well, 00:28:27.416 --> 00:28:29.396 Duke: let's break the fourth wall here for a second. 00:28:29.576 --> 00:28:34.056 Like, isn't it amazing that I had such a clear idea in my head, I just want 00:28:34.061 --> 00:28:37.476 this, but you just made yourself more consulting dollars because you convinced 00:28:37.476 --> 00:28:40.433 me that well, don't you also need this? 00:28:40.433 --> 00:28:42.713 Like, isn't this a big, wouldn't it also help. 00:28:43.568 --> 00:28:43.928 CJ: Yeah, 00:28:44.198 --> 00:28:46.748 Duke: you convinced me to increase the scope of the project because 00:28:46.748 --> 00:28:47.618 now I'm like, you know what? 00:28:47.668 --> 00:28:49.828 , why don't I make this self-service? 00:28:49.888 --> 00:28:50.968 , not self-service is the wrong word. 00:28:50.968 --> 00:28:54.698 Why don't I have a portal component that my cohort, uses? 00:28:54.973 --> 00:28:56.383 CJ: Absolutely right. 00:28:56.668 --> 00:28:58.268 Duke: for them now, like, mm-hmm. 00:28:59.153 --> 00:29:02.733 , CJ: and the, way that I did that was by listening to you, right? 00:29:02.823 --> 00:29:07.803 I listened to how you framed what the information that you gave back to me and I 00:29:07.803 --> 00:29:11.983 noticed that it wasn't gist, capturing the information and have it somewhere store 00:29:11.983 --> 00:29:15.373 It is also that you're a one man show. 00:29:15.868 --> 00:29:18.933 It's also that , you haven't formalized a lot of it, right? 00:29:18.933 --> 00:29:21.033 Like you're still in the process of shaking it out. 00:29:21.346 --> 00:29:24.736 It's also that a lot of the time for this, you need to spend on 00:29:24.736 --> 00:29:26.566 teaching and not on managing. 00:29:26.763 --> 00:29:30.143 And so based on all of these situations, all of those, , those 00:29:30.148 --> 00:29:32.663 situations that I was able to read into our conversation, right? 00:29:32.663 --> 00:29:34.016 I also noted that. 00:29:34.313 --> 00:29:37.433 a big requirement wasn't necessarily articulating, but was really 00:29:37.433 --> 00:29:39.323 present is time management, right? 00:29:39.443 --> 00:29:43.283 The ability to shrink the amount of time that you spend on managing this process 00:29:43.433 --> 00:29:47.533 so that you can expand the amount of time that you spend with your cohort, and then, 00:29:47.713 --> 00:29:51.283 you know, having a portal that folks can interact with allows you to push some 00:29:51.283 --> 00:29:55.423 of the work that you were doing off on them, which gives you some time back. 00:29:55.820 --> 00:29:58.250 So I, I got the purpose of the app here now. 00:29:58.250 --> 00:29:59.390 We know who's gonna use it. 00:29:59.390 --> 00:30:02.700 We know how they're gonna use it, ? We know the data that's gonna be created. 00:30:02.920 --> 00:30:05.230 , we don't yet know how you're going to consume it. 00:30:05.230 --> 00:30:07.665 So are you looking at , some kind of dashboard on your end? 00:30:07.935 --> 00:30:10.125 Are you looking to have some kind of scheduled reporting? 00:30:10.485 --> 00:30:11.775 , what are you looking at on this? 00:30:12.160 --> 00:30:16.460 Duke: Yeah, I, definitely have want a dashboard , or dashboards 00:30:16.520 --> 00:30:17.960 or a dashboard with tabs. 00:30:18.260 --> 00:30:18.560 CJ: Okay. 00:30:18.650 --> 00:30:20.330 Or workspace or, 00:30:20.975 --> 00:30:21.335 Duke: Yeah. 00:30:21.335 --> 00:30:23.855 , no, not a workspace, because I think a workspace is more like every day 00:30:23.855 --> 00:30:26.825 I'm gonna go here and see these things and here's why it's not an every day. 00:30:26.855 --> 00:30:31.385 'cause there's a dashboard I'll be using during the cohort planning, right? 00:30:31.390 --> 00:30:33.845 Because now I'm starting to advertise cohort three. 00:30:34.085 --> 00:30:37.655 Cough, cough, hit me up at Rob, at the duke, do digital, hit 00:30:37.655 --> 00:30:39.125 me up at rob@theduke.digital. 00:30:39.155 --> 00:30:40.325 Digital if you're interested. 00:30:40.535 --> 00:30:41.765 But I'm planning it, right? 00:30:41.765 --> 00:30:44.795 And so it's, it's basically like we can't start till everything's ready. 00:30:45.425 --> 00:30:47.195 Here's all the parts that still need ready. 00:30:47.285 --> 00:30:50.705 Like who hasn't put in contracts, do we have a critical mass yet of people 00:30:50.705 --> 00:30:52.295 who have definitively said yes? 00:30:52.710 --> 00:30:53.060 CJ: Right. 00:30:53.405 --> 00:30:54.665 Duke: so there's that kind of stuff. 00:30:54.665 --> 00:30:59.735 But then also during the cohort, there's that idea of expectations. 00:31:00.340 --> 00:31:01.810 Please get me your resume. 00:31:01.900 --> 00:31:06.240 Please get me your, , instance credentials for the account you made of me. 00:31:06.570 --> 00:31:10.410 Please get me your solution ideation template or templates. 00:31:10.750 --> 00:31:13.240 , please validate that you've finished the SOAP app. 00:31:13.610 --> 00:31:15.050 Submit a question to me. 00:31:15.550 --> 00:31:17.610 yeah, just like a lot of stuff that like. 00:31:18.310 --> 00:31:21.160 You can call them tasks, but they're just expectations now. 00:31:21.595 --> 00:31:22.225 , CJ: absolutely. 00:31:22.325 --> 00:31:25.435 , and because some of those things, , relate to each other and some, well, 00:31:25.440 --> 00:31:28.160 they all relate to each other as they're part of the, , execution of 00:31:28.160 --> 00:31:32.990 running the business, but some of them are more closely aligned than others. 00:31:33.200 --> 00:31:35.870 You want multiple dashboards or at least multiple , tabs, 00:31:36.345 --> 00:31:39.185 Duke: I'd, I'd be happy with just like some, like, you know, 00:31:39.185 --> 00:31:40.745 how I can master a list, right? 00:31:40.745 --> 00:31:44.255 But definitely a dashboard that's kind of like I. 00:31:44.255 --> 00:31:47.360 What are the, I think maybe just the types of things 00:31:47.945 --> 00:31:48.235 CJ: Yeah. 00:31:48.290 --> 00:31:50.950 Duke: how many people are, are left open. 00:31:50.950 --> 00:31:54.340 So we got fi, we got two people that haven't signed a contract yet. 00:31:54.640 --> 00:31:57.340 We have two people that haven't submitted resumes yet. 00:31:57.370 --> 00:31:59.470 We have five people that haven't submitted a solution. 00:31:59.475 --> 00:32:00.520 Ideation templates. 00:32:01.300 --> 00:32:03.700 CJ: Yeah, I mean, this is one of, the things that you preach, , around 00:32:03.700 --> 00:32:07.360 performance analytics, it's like, you know , what's the metric and which way is good, 00:32:07.705 --> 00:32:08.995 Duke: Yeah, yeah. 00:32:09.805 --> 00:32:13.645 I'll tell you, I mean we do have just, can I just take another two minutes 00:32:13.900 --> 00:32:14.500 CJ: yeah, go for it. 00:32:14.665 --> 00:32:17.270 Duke: 'cause one thing , I'm really wanting to get my arms around is 00:32:17.270 --> 00:32:21.530 a data-driven way to figure out who is comfortable with what. 00:32:22.490 --> 00:32:26.360 So like I'd love to be able to toss some kind of record somewhere that just says 00:32:26.720 --> 00:32:33.590 Bob is having trouble with flow designer Jane is still needs more help with. 00:32:33.648 --> 00:32:38.590 data structure, And then, then what I can do is by looking at the records of it, 00:32:38.650 --> 00:32:41.835 I can just say, there's five people that still need help with data structures. 00:32:41.835 --> 00:32:44.775 Let's just jump on a call and have an extra hour session on that. 00:32:44.865 --> 00:32:45.975 Just the people who are having trouble. 00:32:47.205 --> 00:32:47.535 CJ: Yeah. 00:32:47.565 --> 00:32:52.425 So you want an ability to log, um, um, cohort competency against a set of skills, 00:32:52.515 --> 00:32:52.905 Duke: Yeah. 00:32:52.905 --> 00:32:53.235 Yeah. 00:32:53.235 --> 00:32:57.335 It like skills fascinates me except for the skills are one dimensional, right? 00:32:57.340 --> 00:33:01.615 The skills table contains skills and only skills, but yeah, , I'm really curious 00:33:01.620 --> 00:33:03.655 about anything we can do that way as well. 00:33:04.420 --> 00:33:06.200 CJ: Yeah, , that's a really interesting requirement. 00:33:06.470 --> 00:33:07.790 , I think it's pretty cool, right? 00:33:07.870 --> 00:33:10.755 , I think you'd also gamify it, ? That might be something that'd be interesting to 00:33:10.755 --> 00:33:13.815 think about is how do you gamify, right? 00:33:13.815 --> 00:33:19.305 Like, you know, um, your, your cohort, um, mastering all of those skills, right? 00:33:19.515 --> 00:33:23.175 Duke: I would love a points board of some sort. 00:33:23.475 --> 00:33:23.895 CJ: Yeah. 00:33:24.205 --> 00:33:26.875 , Duke: I always joke about it in my classes, so somebody asks 00:33:26.875 --> 00:33:27.895 a really profound question. 00:33:27.895 --> 00:33:29.095 I'm like, you get the bonus point today. 00:33:29.605 --> 00:33:33.235 But I'd also love to track that and just say so and so got the most 00:33:33.235 --> 00:33:36.115 points and they get, I don't know, a discount on the whole cohort or 00:33:36.115 --> 00:33:38.215 something, or, you know what I mean? 00:33:38.215 --> 00:33:38.425 Or, 00:33:38.590 --> 00:33:38.950 CJ: Yeah. 00:33:39.010 --> 00:33:39.820 No, absolutely. 00:33:39.870 --> 00:33:43.170 . I think that's great, given folks, that, , in the moment accomplishment 00:33:43.320 --> 00:33:46.470 because the skills that they're taking that they're going to have here, 00:33:46.800 --> 00:33:50.460 they will accumulate over time and sometimes in small increments, right? 00:33:50.460 --> 00:33:55.730 So you don't always get that payoff , and dopamine like, but if you get some points, 00:33:55.735 --> 00:33:59.390 points are dopamine incarnate, so, yeah. 00:34:01.545 --> 00:34:04.675 We're gonna do some gamification around, some, , around skill mastery. 00:34:04.680 --> 00:34:05.895 , I really like this idea. 00:34:06.225 --> 00:34:09.885 I think this will be really, , in a cohort at the level of what you're doing, right? 00:34:09.935 --> 00:34:10.625 , it's a good spot. 00:34:10.665 --> 00:34:11.805 , let's see what else we got here. 00:34:11.805 --> 00:34:13.115 So I. 00:34:13.530 --> 00:34:14.370 We've got dashboards. 00:34:14.370 --> 00:34:16.640 We know we're gonna, one of those dashboards , should be 00:34:16.670 --> 00:34:19.040 some kind of, , points system. 00:34:19.350 --> 00:34:20.850 , we know the information. 00:34:20.850 --> 00:34:23.820 We know, okay, we know how we're doing this. 00:34:23.850 --> 00:34:25.620 , I know the purpose of it, you know. 00:34:26.355 --> 00:34:30.195 You know, Robert, I think I have probably enough here to get started. 00:34:30.525 --> 00:34:33.315 , I think there's gonna, there are some open items here that I think 00:34:33.315 --> 00:34:34.665 we're gonna have to it, right? 00:34:34.665 --> 00:34:39.480 And they largely, , revolve around the, , the course itself, right? 00:34:39.480 --> 00:34:42.060 Like, so you gave me a couple of items, , that you're delivering, ? Like 00:34:42.065 --> 00:34:45.150 the Americorp of ServiceNow, the Solution Ideation template, right? 00:34:45.330 --> 00:34:49.240 The Req Requirements Gathering Workshop, a k a and the SOAP building, , app. 00:34:49.250 --> 00:34:52.820 There's probably a few other things here that, that we're missing that need to be 00:34:53.130 --> 00:34:55.710 added to this, topic list of the course. 00:34:56.040 --> 00:35:01.050 ? But then you also want to have an easy way to add and remove and, and move 00:35:01.050 --> 00:35:02.990 around , the actual topics themselves. 00:35:03.040 --> 00:35:07.830 Duke: Well, I have an idea, since we are at 41 minutes, maybe we test far people 00:35:07.830 --> 00:35:10.350 have gotten into this episode, and, 00:35:10.500 --> 00:35:10.830 CJ: Okay. 00:35:11.070 --> 00:35:15.090 Duke: and we say like, well, let me say like, um, show me more. 00:35:15.540 --> 00:35:18.960 Put that down in the reply wherever you see this type down. 00:35:18.960 --> 00:35:19.860 Show me more. 00:35:20.043 --> 00:35:22.893 if you want us to do a full other episode on this and go deeper, 00:35:24.933 --> 00:35:25.413 CJ: I like it. 00:35:25.623 --> 00:35:25.833 Dude. 00:35:25.833 --> 00:35:27.033 This has been fun, right? 00:35:27.033 --> 00:35:27.723 Like, so 00:35:27.963 --> 00:35:30.183 Duke: I, I do like the requirement gathering stuff. 00:35:30.183 --> 00:35:31.563 It's one of my favorite parts of the job. 00:35:31.563 --> 00:35:31.833 So, 00:35:31.953 --> 00:35:32.763 CJ: Yeah. 00:35:32.768 --> 00:35:36.013 I it put me in a situation to actually gather requirements from somebody 00:35:36.013 --> 00:35:40.096 who knows a lot about service and that that's a right, like that's a 00:35:40.096 --> 00:35:41.746 situation that I'm hardly ever in. 00:35:42.226 --> 00:35:44.686 And when I'm in workshops, I'm normally trying to teach people 00:35:44.736 --> 00:35:47.956 , how to use ServiceNow and what, and , the functionality, but you 00:35:47.956 --> 00:35:49.486 know what the things are, right? 00:35:49.486 --> 00:35:50.806 It's , yeah, I can use the portal for that. 00:35:50.896 --> 00:35:53.236 We can probably do some task records against that. 00:35:53.506 --> 00:35:55.216 Maybe some KPIs, you know. 00:35:56.116 --> 00:35:56.566 Duke: Yep. 00:35:56.686 --> 00:35:59.266 And it's so nice being on the other side of it this time. 00:36:01.696 --> 00:36:02.056 All right. 00:36:02.056 --> 00:36:04.006 I think that's all we have time for today though, right? 00:36:04.306 --> 00:36:05.206 CJ: Yeah, I think so. 00:36:05.386 --> 00:36:05.896 All right, guys. 00:36:05.926 --> 00:36:07.186 Uh, let's tune in next time. 00:36:07.516 --> 00:36:07.936 Duke: All right. 00:36:07.996 --> 00:36:08.896 Still no outro 00:36:09.106 --> 00:36:09.966 CJ: Still no outro. 00:36:10.396 --> 00:36:10.516 Duke: all.