WEBVTT 1 00:00:00.000 --> 00:00:02.640 All right, cool. 2 00:00:02.640 --> 00:00:05.080 We're back with another team training. 3 00:00:05.080 --> 00:00:07.680 We're working on our team here on the call 4 00:00:07.680 --> 00:00:09.920 and we're going to be walking through 5 00:00:09.920 --> 00:00:13.720 just like a retrospective of a particular project we did. 6 00:00:13.720 --> 00:00:15.600 I'm gonna show you the whole process 7 00:00:15.600 --> 00:00:17.440 of how we framed something, 8 00:00:17.440 --> 00:00:18.940 kind of what the client gave us initially, 9 00:00:18.940 --> 00:00:21.000 how we framed it, breadboarded it, 10 00:00:21.000 --> 00:00:23.780 made a task grid, and then kind of show you the end product. 11 00:00:23.780 --> 00:00:27.300 This is a ongoing project that is still got 12 00:00:27.300 --> 00:00:29.620 maybe 40% left to do, 13 00:00:29.620 --> 00:00:31.180 but we've actually delivered the prototype. 14 00:00:31.180 --> 00:00:34.360 We've delivered the first draft of everything to the client. 15 00:00:34.360 --> 00:00:36.920 And now they're just in the process this week and next 16 00:00:36.920 --> 00:00:39.440 of reviewing and giving feedback and fixing some bugs. 17 00:00:39.440 --> 00:00:42.320 So we have a really good pace on the project. 18 00:00:42.320 --> 00:00:44.400 I think like we framed it really well. 19 00:00:44.400 --> 00:00:46.480 And I just thought it would be good to do a top to bottom, 20 00:00:46.480 --> 00:00:48.280 like kind of look through all those steps 21 00:00:48.280 --> 00:00:50.660 of how a real project took place. 22 00:00:50.660 --> 00:00:52.260 And this was a four week project. 23 00:00:52.260 --> 00:00:54.680 So it's a decent size project, 24 00:00:54.680 --> 00:00:57.060 a little bit bigger than we're normally used to. 25 00:00:57.060 --> 00:00:59.540 So let's jump in. 26 00:01:00.360 --> 00:01:03.520 I may also share with Janata here as well, 27 00:01:03.520 --> 00:01:06.000 who's the lead developer on this project. 28 00:01:06.000 --> 00:01:08.080 And let's go through it. 29 00:01:08.080 --> 00:01:10.600 So I'm gonna share my screen here. 30 00:01:10.600 --> 00:01:15.600 And we had, this will be kind of our little agenda 31 00:01:15.660 --> 00:01:16.920 for today. 32 00:01:16.920 --> 00:01:18.760 This is for one of our clients, 33 00:01:18.760 --> 00:01:22.440 building out a SaaS product for electricians. 34 00:01:22.440 --> 00:01:24.280 And so I'm just gonna walk you through 35 00:01:24.280 --> 00:01:25.880 the actual Figma board. 36 00:01:25.880 --> 00:01:29.160 So you can kind of see how this went down. 37 00:01:29.820 --> 00:01:32.420 Now, this is a client that actually gave us 38 00:01:32.420 --> 00:01:37.060 a 20 or 30 page PDF when we started working with them 39 00:01:37.060 --> 00:01:38.140 on everything they wanted. 40 00:01:38.140 --> 00:01:40.300 They had actually sat down in a document 41 00:01:40.300 --> 00:01:43.620 and built the entire project in a document, 42 00:01:43.620 --> 00:01:45.460 which doesn't normally happen. 43 00:01:45.460 --> 00:01:49.180 So when it came to this kind of project page 44 00:01:49.180 --> 00:01:50.100 is what they were calling it, 45 00:01:50.100 --> 00:01:54.660 they wanted this one page where they could see, 46 00:01:54.660 --> 00:01:56.260 a little bit about the project, 47 00:01:56.260 --> 00:01:59.040 like they have things where they have estimates, 48 00:01:59.880 --> 00:02:02.220 they have rooms, invoices, expenses, 49 00:02:02.220 --> 00:02:04.300 and orders all related to a project. 50 00:02:04.300 --> 00:02:06.300 And they wanna kind of see everything in one place. 51 00:02:06.300 --> 00:02:07.700 And so the last few months, 52 00:02:07.700 --> 00:02:11.460 we've been building out things like an estimate tool. 53 00:02:11.460 --> 00:02:13.140 So they have a whole estimate tool 54 00:02:13.140 --> 00:02:15.500 and you'd go to page with a list of estimates 55 00:02:15.500 --> 00:02:17.460 and all the estimates would be there for all projects. 56 00:02:17.460 --> 00:02:18.940 Then we had a room functionality 57 00:02:18.940 --> 00:02:20.100 and you'd go to the rooms tab 58 00:02:20.100 --> 00:02:21.500 and then there'd be a lot of, 59 00:02:21.500 --> 00:02:23.540 place to edit the rooms. 60 00:02:23.540 --> 00:02:25.780 And so now they kind of wanted to re, 61 00:02:25.780 --> 00:02:27.180 kind of, this is sort of the final step 62 00:02:27.180 --> 00:02:28.760 where they wanted to look at it 63 00:02:28.760 --> 00:02:30.960 from the perspective of a single project, 64 00:02:30.960 --> 00:02:33.240 show me everything that's going on with this one project. 65 00:02:33.240 --> 00:02:37.320 And it's kind of tying the entire app together that way. 66 00:02:37.320 --> 00:02:40.040 So the way that it went down is we had this 67 00:02:40.040 --> 00:02:43.560 and we had some initial little existing structure 68 00:02:43.560 --> 00:02:44.400 of how it works. 69 00:02:44.400 --> 00:02:47.040 So you can see we had tabs for each of these things, 70 00:02:47.040 --> 00:02:50.560 you know, inventory, products, estimates, 71 00:02:50.560 --> 00:02:52.680 and you could go to those tabs 72 00:02:52.680 --> 00:02:55.940 and look at specific table of the content there. 73 00:02:57.280 --> 00:02:58.680 So we made some notes here 74 00:02:58.680 --> 00:03:02.680 and then Gennato went in and built this pretty great 75 00:03:02.680 --> 00:03:04.840 first version of a breadboard. 76 00:03:04.840 --> 00:03:09.200 And so we arrived at our first shaping session 77 00:03:09.200 --> 00:03:12.540 with the client or just with Gennato and myself, 78 00:03:12.540 --> 00:03:16.400 and we opened this and my first comment was, 79 00:03:16.400 --> 00:03:20.440 okay, this is great, like where is the framed document? 80 00:03:20.440 --> 00:03:23.880 And so Gennato, I'm not throwing him under the bus, 81 00:03:23.880 --> 00:03:24.800 he did a phenomenal job. 82 00:03:24.800 --> 00:03:27.920 He's like, oh yeah, I just went right into the breadboard. 83 00:03:27.920 --> 00:03:29.860 So this is, I'm just showing you guys like the real, 84 00:03:29.860 --> 00:03:31.900 real talk of like how this went down. 85 00:03:31.900 --> 00:03:35.940 Cause I would say this is an extremely successful project, 86 00:03:35.940 --> 00:03:39.180 but we still like kind of getting our process dialed in. 87 00:03:39.180 --> 00:03:42.540 And it's pretty exciting cause it feels so clear 88 00:03:42.540 --> 00:03:44.020 to just jump right into it 89 00:03:44.020 --> 00:03:45.580 and to jump into like the breadboarding. 90 00:03:45.580 --> 00:03:47.540 And so we've got all of this down here. 91 00:03:47.540 --> 00:03:49.220 So we kind of put a pause on that 92 00:03:49.220 --> 00:03:51.620 and then him and I spent like a whole session 93 00:03:51.620 --> 00:03:56.580 and we kind of came up with this problem outcome appetite. 94 00:03:56.580 --> 00:03:59.280 And you'll see, I'll delete this just for a second here 95 00:03:59.280 --> 00:04:00.280 to actually read it. 96 00:04:01.880 --> 00:04:03.440 This is sort of how we sketched it out. 97 00:04:03.440 --> 00:04:06.000 And so, this is some of the problems. 98 00:04:06.000 --> 00:04:07.680 There's just one view. 99 00:04:07.680 --> 00:04:11.640 They wanted, they needed one view for all the project data. 100 00:04:11.640 --> 00:04:14.320 Product data is scattered across different areas of the app. 101 00:04:14.320 --> 00:04:18.240 And then they want to basically have modules 102 00:04:18.240 --> 00:04:20.120 so they can show this. 103 00:04:20.120 --> 00:04:24.940 So this was a very, like, I would say give this like a D 104 00:04:24.940 --> 00:04:29.100 or like a maybe a 70, you know, ish score. 105 00:04:29.100 --> 00:04:31.780 70% like, well, maybe not. 106 00:04:31.780 --> 00:04:36.460 Let me say this is more like a three or four out of 10 score 107 00:04:36.460 --> 00:04:39.540 of like finished framed projects. 108 00:04:39.540 --> 00:04:44.260 So we sat, this took probably an hour, hour and a half. 109 00:04:44.260 --> 00:04:46.740 And we knew it was going to be four weeks was the appetite 110 00:04:46.740 --> 00:04:48.660 and things we said we weren't doing as a mobile app 111 00:04:48.660 --> 00:04:51.720 which we had talked about with the client 112 00:04:51.720 --> 00:04:53.480 and then specifically mentioned we weren't doing. 113 00:04:53.480 --> 00:04:55.760 So this is a great thing that keeps coming up. 114 00:04:55.760 --> 00:04:58.560 We tend to talk about a lot of things with the client 115 00:04:58.560 --> 00:05:00.720 and then what's helpful with the not doing. 116 00:05:00.000 --> 00:05:03.600 is to show them what we're doing above in the outcome, 117 00:05:03.600 --> 00:05:05.740 but then go and, if we talked about it, 118 00:05:05.740 --> 00:05:07.500 we typically put it on the not doing list 119 00:05:07.500 --> 00:05:10.740 so they're super clear that we're not doing this thing. 120 00:05:10.740 --> 00:05:12.260 Because sometimes it gets lost, 121 00:05:12.260 --> 00:05:15.880 and we've had conversations about a certain thing, 122 00:05:15.880 --> 00:05:18.420 and it's kind of putting all the bad news up front. 123 00:05:18.420 --> 00:05:20.900 So this tends to be very helpful, 124 00:05:20.900 --> 00:05:22.920 because while we were talking about this, 125 00:05:22.920 --> 00:05:25.060 they also mentioned how they have people in the field, 126 00:05:25.060 --> 00:05:26.540 and they want to have a mobile app, 127 00:05:26.540 --> 00:05:29.620 and we just want to be really clear with, 128 00:05:29.820 --> 00:05:31.140 especially when you're working with clients, 129 00:05:31.140 --> 00:05:32.620 or anyone for that matter, 130 00:05:32.620 --> 00:05:34.780 that they don't have this impression that like, 131 00:05:34.780 --> 00:05:36.420 oh, well, we talked about mobile apps, 132 00:05:36.420 --> 00:05:38.460 and now that's just included. 133 00:05:38.460 --> 00:05:40.660 Because we have to be really, really concrete, 134 00:05:40.660 --> 00:05:43.220 and not have anything vague in here 135 00:05:43.220 --> 00:05:44.540 when we said four weeks. 136 00:05:44.540 --> 00:05:46.600 So in a previous video, 137 00:05:46.600 --> 00:05:50.220 I showed you guys the Claude skill of framing. 138 00:05:50.220 --> 00:05:52.460 So you can go back and watch that other one. 139 00:05:52.460 --> 00:05:54.320 So we took all of this, 140 00:05:54.320 --> 00:05:57.660 and we brought it to the repository, 141 00:05:57.660 --> 00:05:59.940 and went back and forth, 142 00:05:59.940 --> 00:06:01.420 and it asked a lot of different questions, 143 00:06:01.420 --> 00:06:03.180 and this is kind of how we ended up 144 00:06:04.100 --> 00:06:07.220 with a much, much better frame. 145 00:06:07.220 --> 00:06:09.220 So this is actually a screenshot from our dashboard, 146 00:06:09.220 --> 00:06:10.780 so I'm gonna flip back here, 147 00:06:10.780 --> 00:06:13.540 and kind of show you, sorry, the, over here. 148 00:06:14.660 --> 00:06:16.940 So we got much more clear about it, 149 00:06:16.940 --> 00:06:20.140 and we have, the way that it comes out here 150 00:06:20.140 --> 00:06:23.940 is working really nicely in our dashboard here, 151 00:06:23.940 --> 00:06:26.500 so we have a good formatting there, 152 00:06:26.500 --> 00:06:28.740 and then, so we said project management 153 00:06:28.740 --> 00:06:30.580 cannot see what's happening with a project. 154 00:06:30.580 --> 00:06:32.300 All project-related data exists in the app, 155 00:06:32.300 --> 00:06:34.520 but it's organized by the type of data, 156 00:06:34.520 --> 00:06:36.540 rather than by the project. 157 00:06:36.540 --> 00:06:38.100 To understand the status of a single project, 158 00:06:38.100 --> 00:06:40.440 users must go to six different dashboards, 159 00:06:40.440 --> 00:06:42.300 mentally filter each screen, 160 00:06:42.300 --> 00:06:44.940 cross-reference information across tabs of memory, 161 00:06:44.940 --> 00:06:46.980 and repeat this process multiple times a day, 162 00:06:46.980 --> 00:06:50.120 because everything they're doing for their jobs 163 00:06:50.120 --> 00:06:52.300 is related to projects. 164 00:06:52.300 --> 00:06:54.660 Data that should drive decisions 165 00:06:55.220 --> 00:06:57.700 sits unused, budget variances go unnoticed, 166 00:06:57.700 --> 00:06:59.100 tasks slip through the cracks, 167 00:06:59.100 --> 00:07:01.360 teams waste a lot of time hunting instead of managing. 168 00:07:01.360 --> 00:07:03.740 So of course, it's kind of summarizing this, 169 00:07:03.740 --> 00:07:07.500 but this clarity came because there's probably 170 00:07:07.500 --> 00:07:11.380 three or four hours worth of me and Jonato's time 171 00:07:11.380 --> 00:07:14.140 drawing squares and rectangles in this, 172 00:07:14.140 --> 00:07:15.420 and then playing with the code, 173 00:07:15.420 --> 00:07:17.340 and then looking back and forth, 174 00:07:17.340 --> 00:07:21.140 and it had to, we had to build this mental structure 175 00:07:21.140 --> 00:07:23.380 in our brains of how this project 176 00:07:23.380 --> 00:07:25.380 was gonna actually come about. 177 00:07:25.380 --> 00:07:28.820 And this, to me, what it really came down to 178 00:07:28.820 --> 00:07:30.780 was we've been working on this project 179 00:07:30.780 --> 00:07:33.140 for almost a year with them, 180 00:07:33.140 --> 00:07:35.020 and this was sort of the cherry on top. 181 00:07:35.020 --> 00:07:36.280 Like this was actually like, 182 00:07:36.280 --> 00:07:37.940 we sort of repositioned this whole project 183 00:07:37.940 --> 00:07:39.380 as a much bigger deal. 184 00:07:39.380 --> 00:07:41.220 It wasn't like, oh, and here's another project. 185 00:07:41.220 --> 00:07:43.740 We're just gonna make a dashboard for projects. 186 00:07:43.740 --> 00:07:46.260 It actually kind of positioned it in our minds 187 00:07:46.260 --> 00:07:48.060 as like, hey, you have to do this. 188 00:07:48.060 --> 00:07:49.980 This is like, this is the missing piece 189 00:07:49.980 --> 00:07:52.180 that's gonna bring all the other pieces together. 190 00:07:52.180 --> 00:07:55.020 And it really, just from like a, 191 00:07:55.020 --> 00:07:57.100 helping cast a vision for the client as well, 192 00:07:57.100 --> 00:07:59.260 it changed how we presented it to the clients 193 00:07:59.260 --> 00:08:02.620 because we had sort of mentally built this frame 194 00:08:02.620 --> 00:08:06.600 in our minds of how important this project actually was. 195 00:08:07.940 --> 00:08:12.940 And then what was great is when we handed this frame 196 00:08:12.980 --> 00:08:17.140 to the Cloud Skill and we reviewed it against the code, 197 00:08:17.140 --> 00:08:18.900 it asked us lots and lots of questions, 198 00:08:18.900 --> 00:08:22.140 and then we went in a few different iterations 199 00:08:22.980 --> 00:08:25.300 to this, and then we actually sat 200 00:08:25.300 --> 00:08:27.740 and kind of reworded a few things just to be extra clear. 201 00:08:27.740 --> 00:08:30.500 So it's just this, like it comes out 202 00:08:30.500 --> 00:08:33.299 and looks so simple and clear. 203 00:08:33.299 --> 00:08:35.700 And even when I started talking about this project 204 00:08:35.700 --> 00:08:36.820 at the beginning of this video, 205 00:08:36.820 --> 00:08:39.140 like you probably didn't know exactly what it was, 206 00:08:39.140 --> 00:08:41.340 but now when you start to read this finished frame, 207 00:08:41.340 --> 00:08:43.460 it's probably like, oh yeah, no, that's exactly it. 208 00:08:43.460 --> 00:08:46.460 So it feels so much more concrete. 209 00:08:47.380 --> 00:08:48.680 And so here's some of the outcome statements. 210 00:08:48.680 --> 00:08:50.060 We just said, you know, we wanna be able to see 211 00:08:50.060 --> 00:08:52.500 the health of a project quickly, you know, 212 00:08:52.500 --> 00:08:54.580 under 30 seconds, you could glance at a dashboard 213 00:08:54.580 --> 00:08:56.020 and kind of see, are we on track? 214 00:08:56.020 --> 00:08:58.260 Are we over or behind schedule? 215 00:08:59.420 --> 00:09:01.460 Budget status is visible. 216 00:09:01.460 --> 00:09:03.720 Task progress is visible. 217 00:09:03.720 --> 00:09:05.580 Critical information is not hidden. 218 00:09:05.580 --> 00:09:07.740 This was something we talked over and over about 219 00:09:07.740 --> 00:09:11.720 because little things get a life in projects. 220 00:09:11.720 --> 00:09:14.080 I'll go all the way back here. 221 00:09:14.080 --> 00:09:18.820 This little mock-up that the project manager 222 00:09:19.220 --> 00:09:23.940 on the client side designed in Excel to show how it works. 223 00:09:23.940 --> 00:09:26.020 And everything that they wanted was in tabs. 224 00:09:26.020 --> 00:09:29.420 And they kept using this word tabs everywhere. 225 00:09:29.420 --> 00:09:30.780 And they would say, you know, 226 00:09:30.780 --> 00:09:32.600 they mentioned it in their requirements doc, 227 00:09:32.600 --> 00:09:34.540 they had the mock-up with tabs, 228 00:09:34.540 --> 00:09:37.340 and we just built it kind of with a tab idea 229 00:09:37.340 --> 00:09:39.060 in the first initial plan. 230 00:09:39.060 --> 00:09:43.160 We had, you know, estimates and room tab, like, you know, 231 00:09:44.000 --> 00:09:47.720 and then we had, let's see, what other tabs did we have? 232 00:09:48.000 --> 00:09:50.120 You get the idea, inventory, order, tab. 233 00:09:50.120 --> 00:09:52.440 So we just threw this word tab in everywhere, 234 00:09:52.440 --> 00:09:54.280 and it kind of got a life. 235 00:09:54.280 --> 00:09:57.360 And that's kind of scary when you're building out 236 00:09:57.360 --> 00:10:00.040 the frame of a project because we did not. 237 00:10:00.000 --> 00:10:01.600 use the word tabs anywhere. 238 00:10:01.600 --> 00:10:05.240 Because once we got into it, the more we got into it, 239 00:10:05.240 --> 00:10:07.400 we're like, you're going to have something 240 00:10:07.400 --> 00:10:10.160 on the third tab on the fourth row down 241 00:10:10.160 --> 00:10:11.760 that's pretty important, and you're not 242 00:10:11.760 --> 00:10:15.520 going to see it because it's buried three clicks away 243 00:10:15.520 --> 00:10:16.840 to get to that. 244 00:10:16.840 --> 00:10:17.880 And we just assumed. 245 00:10:17.880 --> 00:10:20.020 But it took us four or five hours 246 00:10:20.020 --> 00:10:22.040 of being into just the framing and the shaping 247 00:10:22.040 --> 00:10:24.560 to finally pull that piece out of it. 248 00:10:24.560 --> 00:10:27.920 And you can see here we actually put tabs in our initial frame. 249 00:10:27.920 --> 00:10:30.560 And it's just one word, but it all of a sudden 250 00:10:30.560 --> 00:10:33.600 create this little mental model of, no, they asked for tabs. 251 00:10:33.600 --> 00:10:35.960 Obviously, we have to build tabs. 252 00:10:35.960 --> 00:10:40.920 And so it took us getting into it to really push the, 253 00:10:40.920 --> 00:10:43.800 to get clear on it that, hey, one of the big deals 254 00:10:43.800 --> 00:10:45.600 here is we're trying to make this one page 255 00:10:45.600 --> 00:10:47.240 so you don't miss things. 256 00:10:47.240 --> 00:10:49.720 And if we basically go back to tabs, 257 00:10:49.720 --> 00:10:53.200 ironically, we're kind of back to a similar problem 258 00:10:53.200 --> 00:10:58.400 as before, where we had all these tabs. 259 00:10:58.400 --> 00:11:01.960 We had tabs to get to these different things that 260 00:11:01.960 --> 00:11:03.480 were related to the project. 261 00:11:03.480 --> 00:11:05.920 And we've sort of moved those tabs from a vertical list 262 00:11:05.920 --> 00:11:09.560 to a horizontal list and filtered them by the project. 263 00:11:09.560 --> 00:11:11.600 So it is a very logical. 264 00:11:11.600 --> 00:11:12.800 It's one way to do it. 265 00:11:12.800 --> 00:11:15.760 It's just not the best way to do it. 266 00:11:15.760 --> 00:11:17.920 And so when we really pressed into it, 267 00:11:17.920 --> 00:11:19.800 it was all about this visibility thing 268 00:11:19.800 --> 00:11:21.920 and project health being scannable 269 00:11:21.920 --> 00:11:25.680 and having all the data in kind of one location. 270 00:11:25.680 --> 00:11:27.600 And we used this to present this to the client. 271 00:11:27.600 --> 00:11:29.920 And once they kind of saw it, they got a vision for it. 272 00:11:29.920 --> 00:11:34.720 And we never went back on the tab idea again. 273 00:11:34.720 --> 00:11:38.720 Again, look how long the out-of-bounds list is. 274 00:11:38.720 --> 00:11:41.240 These all got surfaced by the Cloud Skill 275 00:11:41.240 --> 00:11:45.120 after our conversation with it and looking at the code. 276 00:11:45.120 --> 00:11:46.800 We wanted to be really clear about, hey, 277 00:11:46.800 --> 00:11:50.200 this is really just a view to get to other places of the app. 278 00:11:50.200 --> 00:11:54.160 We're not going to have the full experience of building out 279 00:11:54.160 --> 00:11:57.600 an estimate in this little project dashboard thing. 280 00:11:57.600 --> 00:11:59.520 You're going to basically, hey, I want to make a new estimate. 281 00:11:59.520 --> 00:12:01.440 You're going to go to the estimate section 282 00:12:01.440 --> 00:12:03.400 now and reuse existing pages. 283 00:12:03.400 --> 00:12:05.280 So we got really clear so the clients knew 284 00:12:05.280 --> 00:12:09.080 exactly what we were going after. 285 00:12:09.080 --> 00:12:14.800 One of the other things we said, there's 286 00:12:14.800 --> 00:12:16.600 a list of projects that happen. 287 00:12:16.600 --> 00:12:19.800 And I'm actually just going to jump into it here. 288 00:12:19.800 --> 00:12:21.320 So I kind of sneak peek there. 289 00:12:21.320 --> 00:12:24.040 There's a list of projects here where it just 290 00:12:24.040 --> 00:12:25.800 lists out all the projects. 291 00:12:25.800 --> 00:12:30.360 And that is something we just said, hey, 292 00:12:30.360 --> 00:12:32.160 we're going to leave that as is. 293 00:12:32.160 --> 00:12:33.240 The list is still there. 294 00:12:33.240 --> 00:12:34.740 But once you click into the project, 295 00:12:34.740 --> 00:12:36.800 that's when this new view takes over. 296 00:12:36.800 --> 00:12:41.160 So we were able to talk through each of these bullet points. 297 00:12:41.160 --> 00:12:42.760 And this is a bit of an exercise. 298 00:12:42.760 --> 00:12:44.840 We do talk through each of these with the client 299 00:12:44.840 --> 00:12:46.440 to explain that they really understand 300 00:12:46.440 --> 00:12:47.800 what they're not getting. 301 00:12:47.800 --> 00:12:49.640 Because so often, they're going to be like, 302 00:12:49.640 --> 00:12:52.480 oh, but we really wanted notifications in there. 303 00:12:52.480 --> 00:12:54.800 Or we wanted this other thing. 304 00:12:54.800 --> 00:12:56.680 And then potentially, that affects 305 00:12:56.680 --> 00:12:57.760 what we can and can't do. 306 00:12:57.760 --> 00:13:01.880 So this is good to just write it out, be extremely clear. 307 00:13:01.880 --> 00:13:03.880 And there was some discussion about whether they 308 00:13:03.880 --> 00:13:04.880 could upload documents. 309 00:13:04.880 --> 00:13:07.920 I think we did end up allowing them to do this at the end. 310 00:13:07.920 --> 00:13:09.720 And there was one thing in here. 311 00:13:09.720 --> 00:13:12.240 I don't think we actually mentioned it. 312 00:13:12.240 --> 00:13:14.560 But we were pretty clear that we would come up 313 00:13:14.560 --> 00:13:16.920 with this view of the dashboard. 314 00:13:16.920 --> 00:13:18.800 And that would be the view. 315 00:13:18.800 --> 00:13:20.160 It's not customizable. 316 00:13:20.160 --> 00:13:21.120 You can't save things. 317 00:13:21.120 --> 00:13:22.880 That was one thing that came up. 318 00:13:22.880 --> 00:13:25.640 I don't know if we actually wrote it out here specifically. 319 00:13:25.640 --> 00:13:27.640 But it was something we definitely 320 00:13:27.640 --> 00:13:29.200 told them verbally on some calls. 321 00:13:29.200 --> 00:13:32.400 It's totally out of scope. 322 00:13:32.400 --> 00:13:35.360 So we went through that. 323 00:13:35.360 --> 00:13:36.900 And then the way that our system works 324 00:13:36.900 --> 00:13:38.400 is this project gets approved. 325 00:13:38.400 --> 00:13:40.240 And then the frame actually gets locked down 326 00:13:40.240 --> 00:13:42.440 so we can't edit it anymore. 327 00:13:42.440 --> 00:13:45.360 Then Janata built out a whole task grid. 328 00:13:45.360 --> 00:13:47.680 So we had a bunch of different things here. 329 00:13:47.680 --> 00:13:50.360 I know we broke the rule a little bit because we 330 00:13:50.360 --> 00:13:51.560 have a few more than nine. 331 00:13:51.560 --> 00:13:53.320 But this is sort of the different sections. 332 00:13:53.320 --> 00:13:56.560 Each component has its own little list of things to do. 333 00:13:56.560 --> 00:13:59.360 And we had some extra stuff. 334 00:13:59.360 --> 00:14:01.160 We actually had time to go in and make 335 00:14:01.160 --> 00:14:04.640 this customizable drag and drop functionality. 336 00:14:04.640 --> 00:14:07.720 And so the way that the project goes, 337 00:14:07.720 --> 00:14:09.240 if I can kind of go back to my list 338 00:14:09.240 --> 00:14:11.440 here, make sure I don't miss anything. 339 00:14:11.440 --> 00:14:13.040 We went through this initial board. 340 00:14:13.040 --> 00:14:13.600 We framed it. 341 00:14:13.600 --> 00:14:14.840 We then did the here. 342 00:14:14.840 --> 00:14:20.400 This was with the Cloud Skill that happened here. 343 00:14:20.400 --> 00:14:23.080 Then we did the task grid and jumped into it. 344 00:14:23.080 --> 00:14:27.760 And this all happened within maybe a span of a week 345 00:14:27.760 --> 00:14:30.200 to 10 days in January. 346 00:14:30.200 --> 00:14:32.800 And then we were able to kick off and actually start 347 00:14:32.800 --> 00:14:34.600 kind of beginning of February. 348 00:14:34.600 --> 00:14:37.440 And looking at the actual time list here, 349 00:14:37.440 --> 00:14:39.560 you can see that's kind of what happened. 350 00:14:39.560 --> 00:14:42.080 We had a start date of the 3rd of February. 351 00:14:42.080 --> 00:14:44.000 And the first block of hours started 352 00:14:44.000 --> 00:14:45.760 coming in around here. 353 00:14:45.760 --> 00:14:47.920 And there's a bunch of pre-work that got done. 354 00:14:47.920 --> 00:14:50.080 I don't know if we really tracked it to this project 355 00:14:50.080 --> 00:14:51.400 or not. 356 00:14:51.400 --> 00:14:54.840 But that all sort of happened on the other side of this. 357 00:14:54.840 --> 00:14:58.520 So we kind of had sign-off right from the beginning of it. 358 00:14:58.520 --> 00:15:01.240 And you can see we have our little log. 359 00:15:00.000 --> 00:15:05.680 here so you can see it got approved on the third was sort of our first date where he said yes this 360 00:15:05.680 --> 00:15:15.120 is this is confirmed. So we went through the project here we did do a little mock-up in v0 361 00:15:16.080 --> 00:15:22.400 oops in v0 here this was helpful to show the client when they saw this they kind of got the 362 00:15:22.400 --> 00:15:29.680 vision for it this idea of like having sections and I think this says six six version six I think 363 00:15:29.680 --> 00:15:36.880 there was more like 10 or 15 of these versions but once we kind of had the idea for how this 364 00:15:36.880 --> 00:15:42.400 was going to work we had like these little sections that would be laid out in sort of 365 00:15:42.400 --> 00:15:49.520 like a grid or like a what's it called like not a mosaic but like the the um a bento box 366 00:15:49.520 --> 00:15:54.720 a layout these are like popular um we showed this to them and then we could show like how 367 00:15:54.720 --> 00:15:59.440 we could isolate numbers and see like charts and all this stuff they got very excited about it 368 00:15:59.440 --> 00:16:06.000 and this was very useful to submit alongside the frame to get that approval it got them really 369 00:16:06.000 --> 00:16:11.600 excited about the project and then where we landed was I'll jump into this test project here 370 00:16:12.800 --> 00:16:20.160 is something like this and we have all the you know different numbers at the top 371 00:16:20.160 --> 00:16:25.520 we have a number of different sections here and when you go into an estimate for example it pulls 372 00:16:25.520 --> 00:16:31.360 up these little cards and they can kind of get to more detailed information from inside here so 373 00:16:31.360 --> 00:16:35.840 if you go to estimates and they hit new estimate they can fill out a few things and then they get 374 00:16:35.840 --> 00:16:41.840 kicked into the new estimate flow which was already existing in the app and so forth they have an 375 00:16:41.840 --> 00:16:47.760 activity you can see like what things have been done this is like a whole little list of things 376 00:16:47.760 --> 00:16:51.760 this was actually I think out of scope but we once we were in here which is something that 377 00:16:52.640 --> 00:16:57.520 Junauda made and it's super cool because you can see like what happened with the project yesterday 378 00:16:57.520 --> 00:17:02.880 what's happening today a little summary of everything and the clients absolutely love that 379 00:17:04.400 --> 00:17:09.760 seeing each room so like this this project has like a bathroom bathroom two bedroom one bedroom 380 00:17:09.760 --> 00:17:14.720 two and you can click into a room here and see what's going on you know with this hypothetical 381 00:17:14.720 --> 00:17:21.119 little project here so pretty cool and the clients love this and then of course we because we're sort 382 00:17:21.119 --> 00:17:26.240 of like ahead of schedule let me just look at this so we're kind of sitting here on the 19th is 383 00:17:26.240 --> 00:17:32.960 when we're recording this we've really delivered most of the functionality and we still have like 384 00:17:32.960 --> 00:17:38.960 a solid week or two to go so even with that we were able to build out this little cool functionality 385 00:17:38.960 --> 00:17:45.440 where you can hit the edit button and you can actually move these blocks around and then save 386 00:17:45.440 --> 00:17:51.680 your you know your new view for that users of kind of how you want to see a project so that was 387 00:17:51.680 --> 00:17:58.000 that was just an incredible cool feature there that just made it like a even better for them 388 00:17:58.000 --> 00:18:04.560 so we showed it the client here in the timeline we showed them on the 16th I believe or the 17th I 389 00:18:04.560 --> 00:18:08.880 think is the Tuesday demoed it they actually reviewed it for two days and they just sent us 390 00:18:08.880 --> 00:18:16.480 like a whole list of like items that they noticed either were bugs or things that are being presented 391 00:18:16.480 --> 00:18:22.720 as a bug but they're kind of like a small feature we know what those look like and again with the 392 00:18:22.720 --> 00:18:27.520 margin we have two full weeks to go and make this look really great one thing that we've just been 393 00:18:27.520 --> 00:18:34.560 fighting for like because this is a four-week project we 100 have to be done with this thing 394 00:18:34.560 --> 00:18:40.080 on the 20th this means they've gone through like two or three rounds of fixes on it what we don't 395 00:18:40.080 --> 00:18:45.360 want to do is we kind of deliver this first version in the to the client like the last few days they 396 00:18:45.360 --> 00:18:49.200 have a day or two to look at it and then really what happens is we end up with this like massive 397 00:18:49.200 --> 00:18:54.400 list of reactive work in March for this this project and now we're kind of cleaning up March 398 00:18:55.120 --> 00:19:00.960 for stuff that should have happened you know in February and so these are you know that we want 399 00:19:00.960 --> 00:19:05.760 to kind of tighten up and we're doing a lot of things to make sure that this was a very clear 400 00:19:05.760 --> 00:19:12.800 project right up front and I think we cut back a ton of cost with this because we massively simplified 401 00:19:12.800 --> 00:19:16.560 the output here where we just said let's do everything on one screen and we didn't have all 402 00:19:16.560 --> 00:19:20.880 these tabs to worry about and we can have these little modals that pop up it we just kind of made 403 00:19:20.880 --> 00:19:25.360 everything smaller because we didn't have to like design as much for these little modals versus 404 00:19:25.360 --> 00:19:30.560 an entire tab that would take up the entire screen so little little changes but actually 405 00:19:30.560 --> 00:19:38.240 made like a huge difference to the project here so yeah very very cool let me see if I had anything 406 00:19:38.240 --> 00:19:44.320 else yeah we said we delivered and we're just wrapping up the bug fixes here so any questions 407 00:19:44.320 --> 00:19:49.920 comments from the team I'd love to like if you guys have questions Lu Chen or Chris or Janata 408 00:19:49.920 --> 00:19:54.320 if you want to comment on anything you were obviously involved heavily let's like do a 409 00:19:54.320 --> 00:19:59.760 little bit of discussion about this or the process and get from there 410 00:20:00.000 --> 00:20:12.720 Yeah, sure. I just adding my two cents to the conversation. I believe like we have been 411 00:20:12.720 --> 00:20:21.400 discussing this, this idea a lot of having on one side that a preview where we do the 412 00:20:21.400 --> 00:20:28.120 framing, we do the shaping and a lot of this is the human side of the work and basically 413 00:20:28.120 --> 00:20:35.120 to better understand the customer and how to present this in a better way for them. 414 00:20:35.120 --> 00:20:43.760 And I think this process, we are getting better at it each day. But yeah, this is actually 415 00:20:43.760 --> 00:20:51.300 what I'm looking now, Bruce. He has the FigJam open, I think he will share this screen. But 416 00:20:51.300 --> 00:20:56.600 I think we are getting, yeah, exactly this one, like we are getting better each day at 417 00:20:56.600 --> 00:21:08.020 the first part so that the second part becomes the more, I want to use the word like the 418 00:21:08.020 --> 00:21:14.460 more delightful as possible. Because I think working with AI can be very frustrating in 419 00:21:14.460 --> 00:21:20.100 the sense of like, sometimes if you are hitting your head against the wall, like, why don't 420 00:21:20.100 --> 00:21:25.740 you do what I want and stuff like that, we can really easily enter into this mode. But 421 00:21:25.880 --> 00:21:33.960 I think the whole first part really helps in terms of breaking it down for the agentic 422 00:21:33.960 --> 00:21:41.040 workflow. And especially for this project, and I think this project had one very interesting 423 00:21:41.040 --> 00:21:50.640 characteristic, that we had many components, and none of them were related. So basically, 424 00:21:50.700 --> 00:21:58.180 the bulk of the work was done in parallel, meaning I broke the project down into small 425 00:21:58.180 --> 00:22:03.260 components, meaning the estimates component, the orders components, and each component 426 00:22:03.260 --> 00:22:11.640 had its own .MD plan for me to implement. But when I triggered the implementation, I 427 00:22:11.640 --> 00:22:18.860 triggered for all plans simultaneously, meaning that all agents were working on the feature 428 00:22:18.880 --> 00:22:25.920 like I had one agent for each component work on the feature simultaneously. And since the 429 00:22:25.920 --> 00:22:34.440 features were not interceding with each other, all of the agents ran smoothly. So I could 430 00:22:34.440 --> 00:22:39.920 test by the end of the process. Of course, this was not like perfect. And a lot of agents 431 00:22:39.920 --> 00:22:46.880 got stuck in some points. But this talks a lot about this changing this view, where we 432 00:22:46.880 --> 00:22:54.380 are not exactly maintaining the code directly, but we maintain the agents that maintain the 433 00:22:54.380 --> 00:23:03.580 code. And we need these agents to be as well directed, and also have access as the tools 434 00:23:03.580 --> 00:23:12.060 they need. So one example, if you allow one agent to be able to open your Chrome, screenshot 435 00:23:12.120 --> 00:23:19.440 the page it's doing and go back to the to the workboard, let's say, we increase our 436 00:23:19.440 --> 00:23:26.840 chances of by the end of the work of this agent, that you have built a interface that 437 00:23:26.840 --> 00:23:33.320 is nice, because we added the capacity for these agents to screenshot its own work and 438 00:23:33.320 --> 00:23:40.680 look at it and evaluate. So I think there's a lot of progress to be made in the sense 439 00:23:40.680 --> 00:23:47.660 of thinking, how do I make this agent as capable as possible? But also, how do I implement 440 00:23:47.660 --> 00:23:54.620 as much guardrails as possible? So this agent works like a train, it's working on this, 441 00:23:54.620 --> 00:24:00.060 it's a locomotive, like it's we have the trails, and it's working on the right trails. And 442 00:24:00.060 --> 00:24:06.980 our function as a developer now is to more or less to maintain the trails and maintain 443 00:24:07.040 --> 00:24:15.800 the train, keep it running, and keep it flowing smoothly. And especially, don't let it run 444 00:24:15.800 --> 00:24:21.000 over the city. So you don't want for because this is a very specific train that can also 445 00:24:21.000 --> 00:24:26.560 make some form of decision making and build itself. So you don't want this to happen like 446 00:24:26.560 --> 00:24:31.480 you don't want it to, you don't want an agent working on top of the other and stuff like 447 00:24:31.500 --> 00:24:38.860 that. So yeah, I think more or less, this is a comprehensive view of like, what was the flow of 448 00:24:38.860 --> 00:24:39.460 development? 449 00:24:40.380 --> 00:24:44.700 That's good. I think. And also, I mean, technically, there's some things you can get 450 00:24:44.700 --> 00:24:50.740 into. Like, we've used Git, like work trees as well, to be in the same branch and then have 451 00:24:50.740 --> 00:24:55.340 like, each agent has its own tree, essentially, and then you kind of bring it all back 452 00:24:55.340 --> 00:25:00.060 together. There's there's some we can get into that. There's some cool things there. 453 00:25:00.000 --> 00:25:05.460 I also, I mean, what's also worth saying in this retrospective thing is that, 454 00:25:05.800 --> 00:25:10.740 um, looking at the frame here and looking at kind of the finished, uh, product, 455 00:25:10.740 --> 00:25:15.720 even, um, this was like, this type of view was obviously like this type of 456 00:25:15.720 --> 00:25:18.540 project made for, for agentic coding. 457 00:25:19.980 --> 00:25:24.760 There's a very, uh, other than this whole, like, you know, the reordering, 458 00:25:24.760 --> 00:25:28.740 there's some customization there, but these it's referencing concepts 459 00:25:28.840 --> 00:25:30.080 that are already in the code. 460 00:25:30.220 --> 00:25:34.700 Um, and so it can go and reference how product, you know, looks how like 461 00:25:34.700 --> 00:25:37.940 order stats, you know, these are things that you can go and everybody 462 00:25:37.940 --> 00:25:39.640 has concepts for this in the app. 463 00:25:40.120 --> 00:25:43.300 Um, so it is a great example of how we could use it. 464 00:25:43.600 --> 00:25:47.280 Obviously we have, I have other projects, uh, working on with, with Greg and 465 00:25:47.280 --> 00:25:51.160 other people this week that are just, just so complicated and there's so much 466 00:25:51.160 --> 00:25:54.100 new content and there's so much new concepts that you have to put together. 467 00:25:54.100 --> 00:25:56.000 But this is a good example. 468 00:25:56.000 --> 00:25:58.340 So I just, I just want to mention that not to say like, Oh, well, no 469 00:25:58.340 --> 00:25:59.720 wonder we're ahead of schedule. 470 00:25:59.720 --> 00:26:01.880 And it's so easy because this is an easy project. 471 00:26:02.240 --> 00:26:07.840 Um, it kind of became easy after a lot of like thinking and, you know, 472 00:26:07.960 --> 00:26:11.400 diving into it and putting a lot of thought into the finished product. 473 00:26:11.720 --> 00:26:14.800 Um, first, just like jumping in and having Claude sort of 474 00:26:14.800 --> 00:26:16.040 put the structure together. 475 00:26:16.400 --> 00:26:19.040 Uh, it was easy for Claude, like I said, to execute on these 476 00:26:19.080 --> 00:26:23.800 individual components and tasks for the, yeah, for the frame, like this thing, 477 00:26:23.800 --> 00:26:29.020 any, anything we, Alex, maybe on the process of the project, um, I think 478 00:26:29.300 --> 00:26:32.940 like the agentic pieces is good. 479 00:26:32.940 --> 00:26:37.100 And we basically breaking up like each slice to kind of run it simultaneously. 480 00:26:37.540 --> 00:26:42.500 Um, and I've kind of like treated, even if you don't run, so if you're 481 00:26:42.500 --> 00:26:46.880 like, Oh wow, running multiple parallel, uh, agents all at once sounds 482 00:26:46.880 --> 00:26:51.700 intimidating, um, if you kind of break things up by like the slices, if you 483 00:26:51.700 --> 00:26:56.240 take each one of these and kind of run that to me as like a work session, like 484 00:26:56.240 --> 00:26:59.980 I can, you can pretty much rip through an entire slice in one, two or three 485 00:26:59.980 --> 00:27:03.960 hours session and just kind of work through that it goes very, very quickly. 486 00:27:04.320 --> 00:27:08.400 Um, So where, you know, this is a technically a four week project, but 487 00:27:08.720 --> 00:27:12.240 it's, uh, it's a number of, you know, sort of deep work sessions to get, get 488 00:27:12.240 --> 00:27:14.320 each one done and some of them will go very, very quickly. 489 00:27:14.760 --> 00:27:19.440 Um, and this is a great case because you kind of have this one container of a. 490 00:27:19.860 --> 00:27:20.300 Component. 491 00:27:20.300 --> 00:27:23.820 And then you had lots of different types of components that were all very 492 00:27:24.140 --> 00:27:26.820 easily able to reference the code itself. 493 00:27:26.980 --> 00:27:30.420 So that kind of makes good sense to have like multiple running at the same time. 494 00:27:30.840 --> 00:27:34.860 Um, I have done like two or three running at the same time. 495 00:27:35.140 --> 00:27:38.700 If you work on different parts of the app, because a lot of the time, if you 496 00:27:38.700 --> 00:27:42.100 guys have found that you're doing this coding, you just sit and waiting for 497 00:27:42.100 --> 00:27:46.420 like two or three minutes to like it to crank through a bunch of stuff and you 498 00:27:46.420 --> 00:27:49.000 get bored, so you start clicking through the app and you're like, Oh, 499 00:27:49.000 --> 00:27:50.700 why is this bug still happening? 500 00:27:50.700 --> 00:27:53.760 And so you've got to go on like another rabbit trail, at least when 501 00:27:53.760 --> 00:27:55.000 I'm working on the dashboard. 502 00:27:55.060 --> 00:27:57.820 Um, I, that's constantly how I do it. 503 00:27:57.820 --> 00:28:01.780 So I ended up like making a few like, but smaller tasks kind of around 504 00:28:01.780 --> 00:28:03.160 while the main task is working. 505 00:28:04.600 --> 00:28:06.800 Or the other thing you can do is put it in plan mode. 506 00:28:06.800 --> 00:28:11.440 So you could have two or three plan mode on, uh, running together. 507 00:28:11.440 --> 00:28:14.580 So you're like planning different things altogether and then it's 508 00:28:14.580 --> 00:28:16.560 building the, the execution plan. 509 00:28:16.860 --> 00:28:19.160 And then you just kind of like execute, execute, execute. 510 00:28:19.520 --> 00:28:23.120 Um, if you want to be safe, you can like execute, like build 511 00:28:23.120 --> 00:28:24.640 all the plans at the same time. 512 00:28:25.120 --> 00:28:28.160 And then kind of just build the first one, get it done, commit 513 00:28:28.160 --> 00:28:29.640 that code, build a second commit. 514 00:28:29.640 --> 00:28:32.600 So you kind of like queue them all up and then just like fire away. 515 00:28:33.080 --> 00:28:35.620 Um, you can get, you can get a lot of work done very quickly. 516 00:28:35.620 --> 00:28:39.560 So it's, I'm just, I'm giving you sort of like some, some baby steps to get 517 00:28:39.560 --> 00:28:44.360 it to maybe what Jonathan was saying, if that sounds insane, but, um, there we go. 518 00:28:44.460 --> 00:28:48.660 I think, yeah, the other thing with this is, um, like, um, this 519 00:28:48.660 --> 00:28:51.740 is fresh cause I, we, I was shaping and doing all this process again 520 00:28:51.740 --> 00:28:54.420 with, with Greg, uh, earlier this week. 521 00:28:54.500 --> 00:28:58.660 And so, um, one thing is that we've also, I told him yesterday. 522 00:28:58.660 --> 00:29:03.920 It's like, I don't think anyone here is doing any of this process solo. 523 00:29:04.400 --> 00:29:07.860 Um, so like the framing, you know, we're getting stuff from the client. 524 00:29:07.860 --> 00:29:08.540 We're framing stuff. 525 00:29:08.540 --> 00:29:14.540 We're coming back doing like an internal team, um, uh, you know, review, then 526 00:29:14.540 --> 00:29:17.840 we're going to kind of like a second phase at the, as at the breadboard. 527 00:29:17.840 --> 00:29:19.860 Then we do another thing and we stick it through Claude and we're 528 00:29:19.860 --> 00:29:21.380 kind of doing it all together. 529 00:29:21.380 --> 00:29:24.940 And I think, um, I heard, I think it was Jason Freed made a great comment 530 00:29:24.980 --> 00:29:29.180 is like the reason you need a second person is because you need someone 531 00:29:29.180 --> 00:29:33.060 to kind of like pull on the thought process and kind of argue with you a 532 00:29:33.060 --> 00:29:36.300 little bit, because that's the one thing like AI is not going to really do. 533 00:29:36.300 --> 00:29:37.740 They're going to be like, you're absolutely right. 534 00:29:37.740 --> 00:29:38.740 Like you're phenomenal. 535 00:29:38.740 --> 00:29:41.740 Like just, it's going to keep just telling you that you're doing a great job. 536 00:29:42.100 --> 00:29:47.820 Whereas as humans, we kind of keep this context window of like, um, you know, 537 00:29:47.820 --> 00:29:52.020 and in one, just one with Greg, like Janata spent way more time in the Xdeck 538 00:29:52.020 --> 00:29:55.900 code, uh, Greg has spent more time in this other project and I was kind of 539 00:29:55.900 --> 00:29:59.260 coming in just to help put the system together, so there was like these 540 00:29:59.260 --> 00:30:00.020 little nuances. 541 00:30:00.000 --> 00:30:05.040 that you know about once you're kind of familiar with the code itself, that when you start to 542 00:30:05.840 --> 00:30:11.760 frame it or think of how this new thing's going to fit in, you just don't have that context. 543 00:30:11.760 --> 00:30:19.920 So there's a good tug of war going on between two different thoughts. And then you throw AI 544 00:30:19.920 --> 00:30:24.160 in there to basically just make sure we're keeping to the process is really great. So those little 545 00:30:24.160 --> 00:30:31.440 framing skills would be great. I think we're going to make a new shape up task grid skill as well 546 00:30:31.440 --> 00:30:37.120 that can take that. Maybe it can use the Innovo dashboard API and just load them into the project 547 00:30:37.120 --> 00:30:42.240 for us would be great. And then read them out of there when they're ready. That'd be really easy. 548 00:30:43.040 --> 00:30:49.040 To help keep us on task with this, when you go into a new project, this one's a little bit 549 00:30:49.040 --> 00:30:58.400 done after the fact, but there'll be a short list of things in a slice called admin and strategy. 550 00:30:58.400 --> 00:31:02.720 So just random things that we need to do here. We need to email the client and we need to get 551 00:31:02.720 --> 00:31:07.600 approval from the budget and we need to make sure we build the task grid. This is just like help keep 552 00:31:07.600 --> 00:31:12.720 us a little checklist on kind of the rest of the project. So you'll see this little slice show up 553 00:31:12.720 --> 00:31:18.320 on all new projects. If a project was made before last week, it doesn't have it, but you can easily 554 00:31:18.320 --> 00:31:23.760 make one. But now when we start a new project, there'll be this little admin strategy slice 555 00:31:23.760 --> 00:31:29.440 that gets added automatically. I don't think it follows exactly this, but it's 556 00:31:29.440 --> 00:31:35.280 something similar to this where we will make sure all the things are connected, 557 00:31:35.280 --> 00:31:40.800 the framing doc is set, we build up a task grid, actually get approval on the budget, 558 00:31:40.800 --> 00:31:44.720 things like that. Just little hit list. If we think of something like, oh, I got to email the client 559 00:31:44.720 --> 00:31:48.320 and ask them that question and you want to track it somewhere, this is a great little spot to keep 560 00:31:48.320 --> 00:31:53.120 it there. Or I need to remember to actually send a video review of where we're at in this process. 561 00:31:53.920 --> 00:31:59.520 That's also super helpful. So that'll be in there. And we'll continue to change that checklist 562 00:31:59.520 --> 00:32:06.640 as we go through it. I will say also on the feedback of this task grid from a client standpoint, 563 00:32:06.640 --> 00:32:12.800 this is a, it looks like there's a lot going on. This is about the easiest way I've ever seen in 564 00:32:12.800 --> 00:32:19.280 the last 16 years of doing development projects to show a client what's going on. Because you can 565 00:32:19.280 --> 00:32:24.960 see like major sections of the project being completed. And with a little bit of percentage 566 00:32:24.960 --> 00:32:30.240 up here, just anyone could look at this and kind of look at the big headlines and kind of skim it 567 00:32:30.240 --> 00:32:35.440 and kind of get a sense of where we're at. I just haven't seen like any other Kanban board or 568 00:32:35.440 --> 00:32:41.440 anything else match this. So this would be something to just make sure we're keeping up with 569 00:32:41.440 --> 00:32:48.480 at the end of each session. For my workflow, I have this up and VS Code and I just constantly 570 00:32:48.480 --> 00:32:54.160 toggling between them. And as I think of tasks, I'm adding them, I'm marking them complete, and I 571 00:32:54.160 --> 00:33:01.040 keep it kind of updated live. So as soon as we get the MCP working from Claude, then you can just 572 00:33:01.040 --> 00:33:06.080 have it update the tasks for you. But just don't throw these all in the task and then go off and 573 00:33:06.080 --> 00:33:10.240 do the project and come back. Because there's a reason there's like rewrite stuff down. Because we 574 00:33:10.240 --> 00:33:17.200 just assume that we're not going to remember things. Same thing, you know, I'm just built like 575 00:33:17.200 --> 00:33:22.560 trying to steal all the best practices and some good habits I learned getting my pilot's license. 576 00:33:22.560 --> 00:33:27.520 Is that no one, even if you've been flying for like two decades, you still have your little checklist. 577 00:33:27.520 --> 00:33:32.720 Because people just forget stuff. And the best, the way to make sure you're absolutely perfect 578 00:33:32.720 --> 00:33:35.920 every time and don't miss things, is just to assume that you're not going to remember these 579 00:33:36.000 --> 00:33:41.760 things and keep them all in your head. So it's a great way to do that. So any other questions, 580 00:33:41.760 --> 00:33:45.680 thoughts? I know we'll wrap up in a minute here. That's good stuff. 581 00:33:48.000 --> 00:33:55.600 Yeah, outstanding work. Yeah, awesome. Well done. Well done. Sweet. I think a couple 582 00:33:55.600 --> 00:34:02.240 takeaways for us was just like, for the team, like keeping, getting, trying to get to like 583 00:34:02.240 --> 00:34:07.760 something that we can demo or put in the client's hands around the 50 to 60% mark, 584 00:34:07.760 --> 00:34:13.440 70% mark of the budget. Much easier, I know, when there's like a four-week budget than if you've 585 00:34:13.440 --> 00:34:16.560 got like a one-week project and you're two days in, you're trying to show the client something 586 00:34:16.560 --> 00:34:22.000 that I know that's hard. But at least keeping like the updates flowing, at least letting them 587 00:34:22.000 --> 00:34:28.800 see stuff early on. One great trick we did with this project was actually prototype the front end 588 00:34:28.800 --> 00:34:33.120 and get them to see it before we hooked up the back end. Of course, those types of little tricks 589 00:34:33.120 --> 00:34:37.840 are great. They can see it in their app. They can see how all things connect. And then we spend 590 00:34:37.840 --> 00:34:43.520 another step just like making stuff functional because we don't want to go too far down. So just 591 00:34:43.520 --> 00:34:48.800 those regular quick updates is very helpful. It gives clients peace of mind because we're in it 592 00:34:48.800 --> 00:34:52.719 and we're seeing everything happen so fast, we get excited. So capture some of that excitement, 593 00:34:52.719 --> 00:34:55.920 like send it on over to the client. Like if you got a little cool screenshot to show, 594 00:34:55.920 --> 00:34:59.680 that's always great. You can drop it in Notion or drop it in Slack, whatever. 595 00:35:00.000 --> 00:35:03.640 and those go a long way. 596 00:35:03.640 --> 00:35:05.960 It just keeps the excitement level up and the focus 597 00:35:05.960 --> 00:35:07.740 and as you're making progress, 598 00:35:07.740 --> 00:35:11.320 there's always probably something you could show for that. 599 00:35:11.320 --> 00:35:12.900 So all good stuff. 600 00:35:14.000 --> 00:35:16.240 And we'll figure out a good, 601 00:35:17.160 --> 00:35:19.880 there's a couple other trainings we wanna do in the future. 602 00:35:19.880 --> 00:35:23.920 One was maybe a longer, maybe an hour or two session 603 00:35:23.920 --> 00:35:26.640 where we do go from zero to one 604 00:35:26.640 --> 00:35:30.180 of setting up an entire new project, 605 00:35:31.480 --> 00:35:33.000 just starting something from scratch. 606 00:35:33.000 --> 00:35:35.520 So if you wanted to go do a side project, 607 00:35:35.520 --> 00:35:38.560 how would you go from a concept to quickly shaping something 608 00:35:38.560 --> 00:35:40.640 up to get it deployed? 609 00:35:40.640 --> 00:35:42.980 Where do you host it? 610 00:35:42.980 --> 00:35:44.880 How do you set up Stripe to get billing? 611 00:35:44.880 --> 00:35:47.900 There's something you can do in an hour or two 612 00:35:47.900 --> 00:35:50.320 to just get the bones of something up 613 00:35:50.320 --> 00:35:53.840 and then you can go and fill out marketing 614 00:35:53.840 --> 00:35:55.120 and you can fill out all the features 615 00:35:55.120 --> 00:35:55.960 and all the other stuff. 616 00:35:56.280 --> 00:35:57.960 So there's kind of like getting the framework 617 00:35:57.960 --> 00:35:58.800 of something up. 618 00:35:58.800 --> 00:36:01.320 I think we can help out with that 619 00:36:01.320 --> 00:36:03.920 in like a one to two hour live build session 620 00:36:03.920 --> 00:36:05.640 and maybe if you guys have projects, 621 00:36:05.640 --> 00:36:08.480 we can do those alongside us and kind of keep, 622 00:36:08.480 --> 00:36:11.660 do kind of a real time build of something. 623 00:36:11.660 --> 00:36:14.820 And then I've been sort of watching a lot 624 00:36:14.820 --> 00:36:18.560 of what Janata is doing and we'll kind of show some things 625 00:36:18.560 --> 00:36:21.680 on the process side and then we've got some cool tools 626 00:36:21.680 --> 00:36:24.120 potentially coming to where you guys could 627 00:36:24.120 --> 00:36:26.760 maybe use some really cool tech stuff 628 00:36:26.760 --> 00:36:28.960 that he's been building somewhere 629 00:36:28.960 --> 00:36:31.040 between all these other projects he's doing. 630 00:36:31.040 --> 00:36:32.560 I don't know when he had time for that, 631 00:36:32.560 --> 00:36:36.360 but so good stuff, yeah. 632 00:36:39.440 --> 00:36:40.760 Awesome guys, I'm gonna end the stream 633 00:36:40.760 --> 00:36:42.760 and we can chat for a few minutes if you want.