WEBVTT 1 00:00:00.000 --> 00:00:15.000 Last, maybe our last one for the year last live stream. We're gonna do a part two of how we have been framing up this project for this internal dashboard. So I'm gonna leave it on here. We may bring some team members on me bring the show there. 2 00:00:16.400 --> 00:00:23.720 And last week we just opened up, you can go watch the first part. If you're interested in this, but we just started with a totally blank canvas. 3 00:00:24.280 --> 00:00:33.840 We mentioned that we had a team retreat here in Franklin and we did a whole kind of mock up of ideas of different things that would help our team be a little bit more efficient. 4 00:00:34.160 --> 00:00:43.240 So it happened by just putting the ideas doing some brainstorming. Everybody kind of wrote down stickies and then we just each person presented their ideas. 5 00:00:43.600 --> 00:00:47.920 Then we captured all those ideas and we kind of organized them in some stickies here just to kind of see 6 00:00:48.200 --> 00:00:56.720 it doesn't mean that every single sticky now has to go into a backlog or any of that. It just was like, hey, generally, there's this sense that we need this one view. So one of the 7 00:00:57.360 --> 00:01:05.920 things that arose was this idea to have a new view that gives team members and clients and admin clarity on billing and schedule. So 8 00:01:06.560 --> 00:01:14.400 I think this is very much a similar view with like different filters on it, potentially. And so last week we kind of framed up 9 00:01:15.040 --> 00:01:21.360 some context here. I won't going to read all of this, since you can go back and watch how we got to this point in the other video. 10 00:01:22.760 --> 00:01:30.040 And we've kind of talked through the problem here and then kind of what we want the outcome. So I'll just kind of focus on the outcome here is we want to 11 00:01:30.640 --> 00:01:43.360 be able to move budget around and have just visibility on what's expected on basically for schedule and billing for clients. We have this view, which took a little screenshot down here for quick reference. 12 00:01:44.400 --> 00:01:51.440 Where we will take a client and then we will have, you know, each column has kind of like 13 00:01:52.120 --> 00:02:02.320 you know the month and then what projects are happening in the month and then what weeks each size project is and what's the status, what's the payment status. There's a lot of information here and Notion doesn't really 14 00:02:03.040 --> 00:02:09.199 give us a nice way to display this is pretty limited as far as how this works and it can still be a little bit overwhelming to clients. 15 00:02:09.759 --> 00:02:13.640 Because we're still talking in weeks where maybe they want to see dollar amounts or 16 00:02:14.640 --> 00:02:27.040 you know, maybe they want to see, you know, we kind of total up here that there's five weeks for that month. So anyway, this is just the kind of the limitations here. And one of the big things that we sort of framed up in a part two here and I may take 17 00:02:28.280 --> 00:02:38.280 this and we're just going to just like you would in, you know, Git, in a Git repository, we're going to fork this and I'm just going to draw a little line and this will be our 18 00:02:39.200 --> 00:02:46.520 official, this will be December 23 session. So we're just going to kind of keep the, we're not going to delete that, we're going to keep it open there. 19 00:02:47.080 --> 00:02:54.760 But one of the big problems that we identified more than anything as we got into a second session was this idea of 20 00:02:55.720 --> 00:03:06.400 there's really, since we're using Notion, so one of the top things here that's relevant. This is a bunch of, I'm just going to put the most important stuff at the top, but most important thing is we 21 00:03:07.000 --> 00:03:12.000 we heavily like rely on Notion for all like projects and tasks. 22 00:03:13.960 --> 00:03:15.080 And I'll say task management. 23 00:03:17.600 --> 00:03:21.240 And so because of that, one of the problems that arises, like we have very limited 24 00:03:21.240 --> 00:03:33.600 control over what users can see, let's say like what projects, you know, and what what access they have, essentially, what 25 00:03:35.640 --> 00:03:37.840 we'll say maybe capabilities, I don't know, okay. 26 00:03:37.880 --> 00:03:47.320 They have to modify. So like if we share, one of the problems right now is we have one massive database called projects and they're all organized with filters by client. 27 00:03:47.640 --> 00:03:54.480 And so in order to share a list of projects with a client, we actually have to share the entire projects database with a client. 28 00:03:55.240 --> 00:04:01.840 So technically, they have access to every single project. If we wanted them in Notion to see this kind of really, you know, 29 00:04:02.720 --> 00:04:11.160 So technically, they have access to every single project. If we wanted them in Notion to see this kind of recreation of this view down here, they'd have to have every single 30 00:04:11.640 --> 00:04:17.160 and they could basically go to any single project of any kind. And they can, we can put them in a read only mode, but then they can only read 31 00:04:17.680 --> 00:04:29.640 their own stuff. They can't interact and stuff. So it's not, it's not ideal. So what we thought would be sort of the, this idea is this view idea was really the most important thing here 32 00:04:30.080 --> 00:04:43.080 is that we just wanted a way for them to view the same data. Same thing that's in Notion, just view it in a different way, but it gives us control over knowing that this is a client or this is a team member that's looking at it. This may be an admin that's looking at it. 33 00:04:43.360 --> 00:04:54.600 And we can hide and show different things on the screen. So that, that created a lot of clarity, how we got there. And this is, we did a session between last Tuesday and this session. So this is actually technically our third session. 34 00:04:54.600 --> 00:05:00.520 And I'll just show you guys this. We actually just started, we started doing a breadboard, but then we went to the next session. 35 00:05:00.000 --> 00:05:03.420 We sort of zoomed out a little bit and we said, okay, how does this work? 36 00:05:03.420 --> 00:05:07.880 We had this idea of like clients doing a multi-month retainer. 37 00:05:08.400 --> 00:05:11.320 So they agree like, Hey, we want to do three weeks per month at this rate. 38 00:05:11.920 --> 00:05:13.080 So they'll have an idea. 39 00:05:13.160 --> 00:05:13.840 They'll give it to us. 40 00:05:13.840 --> 00:05:15.000 We'll frame and shape it. 41 00:05:16.200 --> 00:05:17.960 They confirm that we're using the weeks. 42 00:05:18.000 --> 00:05:21.480 And then we, on the first of the month, they purchased those weeks. 43 00:05:21.480 --> 00:05:25.160 We do work, review, kind of go back and forth as they give feedback. 44 00:05:25.480 --> 00:05:30.160 And then once we finish it, we like release funds to the, to the team for that. 45 00:05:30.160 --> 00:05:34.080 So that's kind of our little, that's sort of how it is to now. 46 00:05:34.080 --> 00:05:36.640 And we even thought of like how we could clean this up a little bit. 47 00:05:36.920 --> 00:05:42.260 So we sort of zoomed out quite a bit because we also didn't want to start 48 00:05:42.260 --> 00:05:47.880 building software for something that is actually a process problem. 49 00:05:47.880 --> 00:05:51.920 So this also happens as well because we are also, I'm the client in this case 50 00:05:51.920 --> 00:05:53.480 and our team, it really is the client. 51 00:05:53.480 --> 00:05:55.480 In this case, we're doing it for ourselves. 52 00:05:55.920 --> 00:05:59.240 We have the control of also fixing the process. 53 00:05:59.240 --> 00:06:03.120 And so this can be a little bit of a painful problem when you, when you're 54 00:06:03.120 --> 00:06:08.560 working with other clients is they need to be open to also sometimes, sometimes 55 00:06:08.560 --> 00:06:14.240 the process itself is not good and you can't really fix a bad process with software. 56 00:06:14.320 --> 00:06:17.480 So if you have a pretty good process and you just want to remove some of the 57 00:06:17.480 --> 00:06:20.800 friction, that's a good time to like bring software into the mix. 58 00:06:21.200 --> 00:06:25.640 And so what we did here is we just, just made sure that our process was simple enough. 59 00:06:25.640 --> 00:06:29.360 And so we did come up with kind of a nicer idea where clients would have an idea. 60 00:06:29.840 --> 00:06:32.520 They could frame and shape, we'll frame and shape it. 61 00:06:32.560 --> 00:06:34.160 We'll propose it to them. 62 00:06:34.600 --> 00:06:36.880 And this could, doesn't have to happen on the, like it happened 63 00:06:36.880 --> 00:06:38.000 anytime during the month. 64 00:06:38.000 --> 00:06:38.880 They can confirm it. 65 00:06:39.440 --> 00:06:41.040 We do the work, we review it. 66 00:06:41.160 --> 00:06:44.800 And we thought of having some like master approve button where we actually mark 67 00:06:44.800 --> 00:06:47.120 the work as completed, at least in Notion. 68 00:06:47.800 --> 00:06:50.120 And then we'd kind of release and that whole project would be done. 69 00:06:50.120 --> 00:06:54.200 So we just, this isn't really super relevant to this, but it does help us give 70 00:06:54.200 --> 00:06:56.720 context of actually just looking at it. 71 00:06:56.720 --> 00:07:02.200 Cause until we got into this, we had never even put these blocks on a board at all. 72 00:07:02.480 --> 00:07:04.240 And these are just something that was in my head. 73 00:07:04.520 --> 00:07:07.600 Maybe it was in Lucian's head, maybe it was in Macy's, but it wasn't clear. 74 00:07:07.640 --> 00:07:12.000 And so by me having to draw it and everybody seeing it, you know, it kind of 75 00:07:12.000 --> 00:07:15.240 helped us move the things around and said, okay, we kind of have it working this way. 76 00:07:15.240 --> 00:07:17.760 We probably should simplify it a little bit to do it this way. 77 00:07:18.440 --> 00:07:22.040 And then we actually got into some of the breadboarding stuff here where we said, 78 00:07:22.080 --> 00:07:25.840 well, we started looking at even like, how does the shaping take place? 79 00:07:25.840 --> 00:07:29.680 Like we meet with the client, we book the shaping calls. 80 00:07:29.680 --> 00:07:32.480 We do actually like a, this is sort of the initial, like, Hey, we want a 81 00:07:32.480 --> 00:07:33.840 project that does this and this. 82 00:07:34.200 --> 00:07:38.880 Then we get into a 90 minute shaping session where we look at, you know, kind 83 00:07:38.880 --> 00:07:41.920 of all these different pieces that we're sort of doing with you guys now frame it. 84 00:07:41.920 --> 00:07:42.800 We give an appetite. 85 00:07:42.880 --> 00:07:47.080 We typically do a second shaping session, if it's internal or with the client. 86 00:07:47.280 --> 00:07:48.800 And then we actually asked them to approve it. 87 00:07:48.840 --> 00:07:51.960 And then we sort of book it and off we go with that. 88 00:07:51.960 --> 00:07:54.920 So that's sort of the process, how a new project comes in the door. 89 00:07:55.360 --> 00:07:58.720 And so this is important because this is what's happening sort of at this phase. 90 00:07:59.120 --> 00:08:02.640 And we needed a screen where all this could take place. 91 00:08:02.640 --> 00:08:04.960 So this is sort of what's happening on the process side. 92 00:08:05.360 --> 00:08:09.200 And maybe we'll just add some definitions here since I wasn't very clear. 93 00:08:09.640 --> 00:08:15.720 So then we, we said, maybe we would have, let's see here. 94 00:08:16.320 --> 00:08:17.520 Future, this is some of the future. 95 00:08:17.520 --> 00:08:20.280 So we, then we started mapping out, did I do a client one? 96 00:08:21.400 --> 00:08:26.440 Yeah, I think this was the, this actually should say client, I think. 97 00:08:26.440 --> 00:08:26.840 Sorry. 98 00:08:27.920 --> 00:08:33.400 So we, we said you would have some sort of navigation. 99 00:08:33.440 --> 00:08:34.799 You would look at the dashboard. 100 00:08:35.840 --> 00:08:38.320 We could kind of see like a chart of like weeks and stuff. 101 00:08:38.320 --> 00:08:41.880 And then we would have these totals and some, something to show 102 00:08:41.880 --> 00:08:44.080 like the different weeks. 103 00:08:44.080 --> 00:08:47.000 So one of the, so we kind of got this far into it. 104 00:08:47.120 --> 00:08:51.240 We even try to like map out just, this would be sort of like our fat marker sketch. 105 00:08:51.240 --> 00:08:52.120 It's not a UI. 106 00:08:52.120 --> 00:08:53.480 It's not even really a wireframe. 107 00:08:53.480 --> 00:08:56.880 It was just trying to like, I had an idea down here. 108 00:08:56.880 --> 00:08:59.800 And so I scribbled it out really quick with some of the texts just 109 00:08:59.800 --> 00:09:01.120 to kind of illustrate what it is. 110 00:09:01.480 --> 00:09:04.040 It's kind of another version of what we, what we had here. 111 00:09:04.800 --> 00:09:09.680 And we also looked at like just these little diagrams here to show like, Hey, 112 00:09:09.680 --> 00:09:10.800 what was actually happening? 113 00:09:10.800 --> 00:09:13.880 Like we had clients paying in the first, sometimes projects ran 114 00:09:13.880 --> 00:09:17.880 into December and then we'd have to like approve and wrap it up in December, 115 00:09:17.880 --> 00:09:19.360 but they actually paid for it in November. 116 00:09:19.440 --> 00:09:22.840 So this is just very complicated. 117 00:09:23.120 --> 00:09:25.360 And so we wanted to figure out how we could simplify it. 118 00:09:25.360 --> 00:09:28.440 So anyway, these are just some of our scribbles and I just put this 119 00:09:28.440 --> 00:09:30.080 line, we can reference it if we need to. 120 00:09:30.080 --> 00:09:33.880 There's nothing in here that's going to be like officially published 121 00:09:33.920 --> 00:09:36.120 anywhere in our SOPs or anything like that. 122 00:09:36.120 --> 00:09:40.560 It's just us getting our, like what's in our brain down on paper. 123 00:09:40.560 --> 00:09:41.520 So we could talk about it. 124 00:09:42.000 --> 00:09:46.880 And then one thing we like to do, just to get in a process is we like 125 00:09:46.880 --> 00:09:48.880 to think of the Hill chart here. 126 00:09:49.120 --> 00:09:53.320 And we have some sort of like magic moment here where we want to get to clarity. 127 00:09:53.720 --> 00:10:00.000 And what's happening down in here is we have things like we're doing. 128 00:10:00.000 --> 00:10:03.720 The framing stuff, we're doing this breadboarding, 129 00:10:03.720 --> 00:10:06.000 which we haven't really even got into the breadboarding 130 00:10:06.000 --> 00:10:06.880 specifically. 131 00:10:06.880 --> 00:10:12.040 We also do some quick prototyping is happening here. 132 00:10:12.040 --> 00:10:16.480 And all of this is happening before we've 133 00:10:16.480 --> 00:10:17.920 kind of hit this middle part. 134 00:10:17.920 --> 00:10:21.480 So that's why we spent, now this will be our third hour 135 00:10:21.480 --> 00:10:23.040 going through this. 136 00:10:23.040 --> 00:10:24.920 So from a time standpoint, we're probably 137 00:10:24.920 --> 00:10:28.400 like 20%, 30% of our hours for this project 138 00:10:28.640 --> 00:10:31.440 have been used up so far. 139 00:10:31.440 --> 00:10:32.480 And that's OK. 140 00:10:32.480 --> 00:10:34.800 We're happy to spend up to half of the hours 141 00:10:34.800 --> 00:10:35.760 just on this first half. 142 00:10:35.760 --> 00:10:39.560 Because once we get this really crispy point of where 143 00:10:39.560 --> 00:10:42.480 it's super concrete, and we know exactly what we got to go do, 144 00:10:42.480 --> 00:10:43.920 then we just map out the steps. 145 00:10:43.920 --> 00:10:45.040 And we just go execute. 146 00:10:45.040 --> 00:10:47.160 And we use AI, of course, down this side 147 00:10:47.160 --> 00:10:57.920 to do a lot of we'll call it agentic coding. 148 00:10:57.920 --> 00:11:01.840 And we test it, and we get the clients. 149 00:11:01.840 --> 00:11:03.680 But typically what happens is people 150 00:11:03.680 --> 00:11:05.640 jump too soon into the coding. 151 00:11:05.640 --> 00:11:08.160 And so it's not crispy yet. 152 00:11:08.160 --> 00:11:10.200 It's not ironed out. 153 00:11:10.200 --> 00:11:11.760 Lucian and Macy were very patient. 154 00:11:11.760 --> 00:11:13.560 Because as soon as this is one of the first projects 155 00:11:13.560 --> 00:11:15.360 we're doing, so we're trying to get a lot of clarity 156 00:11:15.360 --> 00:11:16.160 on a lot of things. 157 00:11:16.160 --> 00:11:19.760 So it really forced us to whittle down 158 00:11:19.760 --> 00:11:23.040 what we're not doing in this project. 159 00:11:23.040 --> 00:11:24.960 And so let me come over here. 160 00:11:24.960 --> 00:11:26.720 So one of the things I did was a prototype. 161 00:11:26.720 --> 00:11:29.120 So we actually went over to our dashboard. 162 00:11:29.120 --> 00:11:32.040 We have our website. 163 00:11:32.040 --> 00:11:36.680 And what's cool about our little Next.js website, 164 00:11:36.680 --> 00:11:39.200 we have a way to actually sign in. 165 00:11:39.200 --> 00:11:41.680 So we don't have a separate app. 166 00:11:41.680 --> 00:11:43.760 It's just one single app that's our website. 167 00:11:43.760 --> 00:11:46.240 And then you can flip over to a dashboard. 168 00:11:46.240 --> 00:11:47.640 And so then there's a client role, 169 00:11:47.640 --> 00:11:50.440 there's a team member role, and there's a admin role. 170 00:11:50.440 --> 00:11:52.440 And so right now, I've just broken them up 171 00:11:52.440 --> 00:11:55.280 by team, client, and admin here. 172 00:11:55.360 --> 00:11:58.680 And so if I go to the client dashboard, 173 00:11:58.680 --> 00:12:01.000 I went ahead and just prototyped this out. 174 00:12:01.000 --> 00:12:03.440 And when I say prototype quickly, 175 00:12:03.440 --> 00:12:07.480 this took me an hour, maybe two hours. 176 00:12:07.480 --> 00:12:09.320 It was not a lot of time. 177 00:12:09.320 --> 00:12:13.000 And I only did this maybe after we had gotten 178 00:12:13.000 --> 00:12:14.080 some of the clarity here. 179 00:12:14.080 --> 00:12:16.360 So I did a quick prototype, knowing 180 00:12:16.360 --> 00:12:17.920 that we may throw this away. 181 00:12:17.920 --> 00:12:19.760 And the one thing I wanted to figure out 182 00:12:19.760 --> 00:12:23.360 was I didn't really get this idea of the control piece. 183 00:12:23.360 --> 00:12:24.760 Because what we wanted to do is we 184 00:12:25.080 --> 00:12:27.120 wanted clients to be able to come in here 185 00:12:27.120 --> 00:12:29.840 and pick up a card and drop it, let's say, 186 00:12:29.840 --> 00:12:32.120 into a different phase, where they mark something 187 00:12:32.120 --> 00:12:33.720 as completed. 188 00:12:33.720 --> 00:12:37.400 We wanted for them to quickly see a much prettier UI, 189 00:12:37.400 --> 00:12:39.320 like they could see the budget from this standpoint. 190 00:12:39.320 --> 00:12:40.480 They can see that they're on schedule. 191 00:12:40.480 --> 00:12:44.840 So on schedule, on budget, little green, green. 192 00:12:44.840 --> 00:12:46.840 And we can see the total weeks here. 193 00:12:46.840 --> 00:12:49.520 And we can see that we have five weeks in progress. 194 00:12:49.520 --> 00:12:52.080 And maybe they can switch it from like a status view 195 00:12:52.080 --> 00:12:54.480 to like a month view if they wanted. 196 00:12:54.480 --> 00:12:57.640 And so that's possible too. 197 00:12:57.640 --> 00:13:00.840 And so this is kind of like where we got to. 198 00:13:00.840 --> 00:13:02.480 And the other thing we typically do a lot 199 00:13:02.480 --> 00:13:06.600 is we have this inbox status, where just a ton of stuff, 200 00:13:06.600 --> 00:13:09.400 like there's 12 weeks worth of things in here. 201 00:13:09.400 --> 00:13:11.440 And we don't like to show it, because it normally 202 00:13:11.440 --> 00:13:12.440 clutters it up. 203 00:13:12.440 --> 00:13:13.840 And then, of course, we have this completed, 204 00:13:13.840 --> 00:13:16.240 which is everything we've ever completed for this client. 205 00:13:16.240 --> 00:13:18.160 So there's just a lot in here too. 206 00:13:18.160 --> 00:13:19.760 So what we thought would be nice, 207 00:13:19.760 --> 00:13:22.920 and I kind of stole some inspiration, 208 00:13:22.920 --> 00:13:27.520 we'll say, from the Fizzy app. 209 00:13:27.520 --> 00:13:30.880 So they have this column that kind of opens and closes. 210 00:13:30.880 --> 00:13:32.760 So a really cool UI. 211 00:13:32.760 --> 00:13:36.240 And we just borrowed that concept for this. 212 00:13:36.240 --> 00:13:37.800 And same thing on completed. 213 00:13:37.800 --> 00:13:41.520 We can pop it open, check stuff, and pull it closed again. 214 00:13:41.520 --> 00:13:44.640 And so that way, things are a little bit more clear. 215 00:13:44.640 --> 00:13:46.320 And of course, we could click into this 216 00:13:46.320 --> 00:13:47.680 and maybe go to a detail page. 217 00:13:47.680 --> 00:13:49.400 We already have some pages in here 218 00:13:49.400 --> 00:13:52.520 that show you details about the project. 219 00:13:52.600 --> 00:13:54.880 And from here, we can, of course, go into Notion 220 00:13:54.880 --> 00:13:57.840 and jump deep into this project of how we're actually 221 00:13:57.840 --> 00:13:58.800 tracking it and stuff. 222 00:13:58.800 --> 00:14:03.520 So again, this is just a quick prototype of this. 223 00:14:03.520 --> 00:14:08.040 And what we did was I just got it started, 224 00:14:08.040 --> 00:14:10.640 and then I showed Luchin and how it works in our team. 225 00:14:10.640 --> 00:14:13.720 And if you're working on our team, this is how it will go. 226 00:14:13.720 --> 00:14:16.440 But we have a single Notion project 227 00:14:16.440 --> 00:14:17.960 with all the information. 228 00:14:17.960 --> 00:14:21.720 And you can link to things like the breadboard, 229 00:14:21.760 --> 00:14:23.840 and you can link to the task grid. 230 00:14:23.840 --> 00:14:26.360 And then we've got things like comments here. 231 00:14:26.360 --> 00:14:32.160 So all that happened was we met last Tuesday. 232 00:14:32.160 --> 00:14:35.080 We, I think it was maybe Tuesday or Wednesday, 233 00:14:35.080 --> 00:14:40.960 Macy and Luchin and I had a few clarity bullet points here. 234 00:14:40.960 --> 00:14:43.960 And then the next day, I just went in and by myself, 235 00:14:43.960 --> 00:14:45.400 I just built a little prototype. 236 00:14:45.400 --> 00:14:48.160 And it doesn't even look that pretty when I made the video 237 00:14:48.160 --> 00:14:49.200 and made a quick preview. 238 00:14:49.200 --> 00:14:50.720 And then Luchin and I went back and forth. 239 00:14:50.720 --> 00:14:51.800 And we started to get some clarity. 240 00:14:51.800 --> 00:14:53.880 So I just wanted to show you that there's 241 00:14:53.880 --> 00:14:57.240 a lot of asynchronous conversation happening here. 242 00:14:57.240 --> 00:15:00.840 And this is something I think. 243 00:15:00.000 --> 00:15:04.400 Lucien and I have been working together for the longest of anyone on the team. 244 00:15:04.760 --> 00:15:08.640 And it's, we're kind of starting to get to the point where we can have good, 245 00:15:08.720 --> 00:15:14.620 uh, uh, like transfer of knowledge and thought back and forth without having 246 00:15:14.620 --> 00:15:16.400 to be on a, like talking face to face. 247 00:15:16.800 --> 00:15:20.580 I love hanging out face to face or in person, but this is great because I could 248 00:15:20.580 --> 00:15:23.920 put my thoughts and when he had a moment, he would be able to re watch the video, 249 00:15:24.160 --> 00:15:27.240 look through the, the, where I was and then give his thoughts that, you know, 250 00:15:27.720 --> 00:15:30.160 um, he was having, so this is good. 251 00:15:30.160 --> 00:15:32.800 So we, this is sort of the, the real, just wanted to show you guys what it's 252 00:15:32.800 --> 00:15:37.840 like, how we work, um, you know, on a real project, because we've did a bit 253 00:15:37.840 --> 00:15:41.640 of coding to get it to this point, but I also just prototyped it in a way that I 254 00:15:41.640 --> 00:15:46.520 could delete this whole module, um, because we haven't really nailed anything down. 255 00:15:46.520 --> 00:15:51.180 I just wanted to see how hard is it to actually, um, build this and get it, get 256 00:15:51.180 --> 00:15:54.820 kind of a UI together to where, and it was, it was me building the UI that I 257 00:15:54.820 --> 00:15:57.740 realized, oh, I get to have full control over what the client's seeing. 258 00:15:57.740 --> 00:15:59.340 And that's actually what we've been missing. 259 00:15:59.780 --> 00:16:00.820 Um, was this sort of. 260 00:16:01.260 --> 00:16:03.860 Controlled view where they don't have to be invited to notion. 261 00:16:03.860 --> 00:16:07.700 They don't have to be invited to a bunch of weird database, like task 262 00:16:07.700 --> 00:16:09.260 databases and project databases. 263 00:16:09.260 --> 00:16:11.500 And that's invited to our whole client database. 264 00:16:11.900 --> 00:16:15.500 Um, I could just make this one view that's reading the API. 265 00:16:15.820 --> 00:16:19.140 And, um, we were able to do a simple little test year where if I drag it 266 00:16:19.140 --> 00:16:23.420 and drop this into shaping, um, and I open this up here in, in notion, you 267 00:16:23.420 --> 00:16:25.220 can see it's just shifted to shaping. 268 00:16:25.540 --> 00:16:30.500 If I come back, of course, um, here and I move it back to in progress and it 269 00:16:30.500 --> 00:16:34.460 immediately like jumps to in progress and notion, so little prototype and a 270 00:16:34.460 --> 00:16:38.820 little proof of concept to show that like, it actually could feel very much 271 00:16:38.820 --> 00:16:43.820 in sync with what our team's seeing and notion, but it's like a much cleaner 272 00:16:43.860 --> 00:16:45.860 view of it and that's where we got a lot of clarity. 273 00:16:45.860 --> 00:16:47.360 So that was a very long update. 274 00:16:47.360 --> 00:16:51.500 I don't know, Lucian, if you want to share some thoughts on this or so, or 275 00:16:51.500 --> 00:16:55.900 where we got to so far, and then we'll dive into some specifics of what to decide next. 276 00:16:57.140 --> 00:16:58.620 Yeah, you pretty much covered the main points. 277 00:16:58.620 --> 00:17:00.380 I would just add that like framing. 278 00:17:00.380 --> 00:17:04.540 It's like, you can never be like too clear on the framing. 279 00:17:04.819 --> 00:17:08.760 So like even we did the prototype and we came back like, ah, this clarifies the 280 00:17:08.760 --> 00:17:12.660 framing and that was probably where the, the biggest like gold happened. 281 00:17:15.859 --> 00:17:17.060 Yeah, I agree. 282 00:17:17.300 --> 00:17:22.220 Um, and we may come back here and it's not so much maybe about the budget anymore. 283 00:17:22.220 --> 00:17:28.380 I would, I would actually say it's, we can put that in a not doing, but, um, we 284 00:17:28.380 --> 00:17:36.860 just really want like, um, a single like view for, for clients, um, to see all 285 00:17:36.860 --> 00:17:42.740 like, um, projects, um, their status, maybe they're like, um, their schedule 286 00:17:43.100 --> 00:17:47.540 and, um, total appetite or something, something like that, just like a high 287 00:17:47.540 --> 00:17:51.060 level overview for the client and something that honestly, like this could 288 00:17:51.060 --> 00:17:54.300 be pretty enough where I could screenshot this and drop it in Slack. 289 00:17:54.340 --> 00:17:57.260 You know, like I could just screenshot this, drop it in Slack. 290 00:17:57.420 --> 00:18:00.540 They can glance at it and be like, okay, so we went over here. 291 00:18:00.740 --> 00:18:01.760 These are on schedule though. 292 00:18:01.760 --> 00:18:02.100 Great. 293 00:18:02.340 --> 00:18:03.140 All, all good. 294 00:18:03.660 --> 00:18:06.380 Um, and we may have like a few in review. 295 00:18:06.740 --> 00:18:10.020 And one of the things we really want to, uh, that we identified here. 296 00:18:10.300 --> 00:18:14.140 When we breadboarded it was when we go into review, we need the clients to 297 00:18:14.140 --> 00:18:18.900 really be involved with getting things out of review and into the completed 298 00:18:18.900 --> 00:18:24.060 status because things can sit, um, as you guys all know on the team, I think 299 00:18:24.060 --> 00:18:25.340 sit and review for a while. 300 00:18:25.340 --> 00:18:29.180 And sometimes, um, we had stuff that wasn't even, um, closed. 301 00:18:29.700 --> 00:18:35.300 And, uh, another thing that we, um, we ran into, I think it was over here. 302 00:18:35.820 --> 00:18:41.340 And if I, uh, went into notion, we actually just built this one board, 303 00:18:41.820 --> 00:18:46.100 which we hadn't been using for a while, but this was every project organized 304 00:18:46.100 --> 00:18:49.220 by status, um, across all clients. 305 00:18:49.340 --> 00:18:52.500 And so we actually quickly found stuff that was in review. 306 00:18:52.500 --> 00:18:55.180 That was maybe like six months old when we did this. 307 00:18:55.660 --> 00:19:00.900 And, um, and, uh, it was, it was kind of, it just, you took the, and we didn't 308 00:19:00.900 --> 00:19:02.020 even, we didn't even build anything. 309 00:19:02.020 --> 00:19:02.840 We didn't write any code. 310 00:19:03.400 --> 00:19:06.760 Once we got the clarity of like, oh, there's this view that's kind of missing. 311 00:19:07.040 --> 00:19:10.240 We're like, oh, we can actually make that view in, in notion in five minutes. 312 00:19:10.280 --> 00:19:13.920 And so we were able to quickly create that and kind of got pretty similar there. 313 00:19:13.920 --> 00:19:15.440 You can see the status of the hours. 314 00:19:15.760 --> 00:19:17.600 You can see the, um, billing. 315 00:19:17.660 --> 00:19:21.400 It doesn't quite show you the date if we're on schedule or not, but, um, 316 00:19:21.400 --> 00:19:22.440 it's a good, good part of that. 317 00:19:22.440 --> 00:19:25.400 I don't know, Greg, if you were wanting to add something popped on. 318 00:19:25.680 --> 00:19:25.880 Okay. 319 00:19:25.880 --> 00:19:26.240 You're good. 320 00:19:26.680 --> 00:19:30.920 Um, I wanted to add something about like, you know, you said that, uh, you 321 00:19:30.920 --> 00:19:34.160 know, software doesn't fix like a bad process, like going through this. 322 00:19:34.560 --> 00:19:37.440 We also got the clarity of like the end review. 323 00:19:37.440 --> 00:19:38.960 It's like, it was a bit fuzzy. 324 00:19:38.960 --> 00:19:40.520 Like what is in review? 325 00:19:40.920 --> 00:19:46.560 Is it like kind of code review by a peer or, and we've, we figured it's better 326 00:19:46.560 --> 00:19:50.880 that like, we are all like done and like shipped and like the client is looking at 327 00:19:50.880 --> 00:19:55.440 it, that's what's in review, like until like you're done and you're giving it in 328 00:19:55.440 --> 00:19:57.800 the hands of the client to say like, is this good enough? 329 00:19:57.800 --> 00:19:59.600 Like, are we done with this? 330 00:20:00.000 --> 00:20:01.920 then it's still in progress up to that point. 331 00:20:01.960 --> 00:20:03.600 Yeah, definitely. 332 00:20:03.600 --> 00:20:09.120 And I think one, so I think what we were missing, and it's, it's so simple, like 333 00:20:09.120 --> 00:20:12.140 once you draw it out and we kind of like, Oh yeah, these, these, these different 334 00:20:12.140 --> 00:20:16.920 spots, there's kind of two things where like people have to take action has to 335 00:20:16.920 --> 00:20:20.700 take place where we need the clients to actually come in here and approve it. 336 00:20:20.700 --> 00:20:28.280 And that's actually a pretty big blocker for, for Macy and me when we're, when 337 00:20:28.280 --> 00:20:31.960 we're making sure, like, was this actually approved because there's, sometimes 338 00:20:31.960 --> 00:20:33.280 they, we get a verbal, yes. 339 00:20:33.300 --> 00:20:34.840 Sometimes it's a reply in an email. 340 00:20:35.060 --> 00:20:37.400 Sometimes we get an emoji on a Slack thread. 341 00:20:37.400 --> 00:20:41.200 Like it's pretty it's not very concrete for the clients to do that. 342 00:20:41.200 --> 00:20:46.020 So we came up with this process, which again, is maybe part of more like we 343 00:20:46.020 --> 00:20:49.520 would call like the monster project, which is maybe a few projects strung 344 00:20:49.520 --> 00:20:55.360 together, but we talked, this came out in the team discussion and I'm not going 345 00:20:55.360 --> 00:20:58.000 to specific you know, stickies here. 346 00:20:58.000 --> 00:21:01.040 I just remember it was, it was so, it came up so many times with the team 347 00:21:01.040 --> 00:21:02.320 that it's just top of mind. 348 00:21:02.320 --> 00:21:02.560 Right. 349 00:21:02.560 --> 00:21:04.520 So I didn't have to really think about it. 350 00:21:05.020 --> 00:21:08.360 It just came up a lot when we were talking about it, but maybe having 351 00:21:08.360 --> 00:21:12.700 something where we send something to a client and it says, Hey, like there's 352 00:21:12.700 --> 00:21:16.700 a, yes, I approve this or like, no, I want other changes and they hit yes. 353 00:21:16.700 --> 00:21:21.680 And it's kind of like their signature on the project to say, we've now approved 354 00:21:21.680 --> 00:21:25.280 this and then everything else, just the work can begin and we can kick it off. 355 00:21:25.280 --> 00:21:28.280 And then the same thing happens at the other end, kind of like these two 356 00:21:28.280 --> 00:21:33.280 bookends of the project, because it was a little bit vague, it wasn't super clear. 357 00:21:33.640 --> 00:21:39.440 And since we deal in the currency of like clarity and crispiness on all our projects, 358 00:21:39.440 --> 00:21:43.400 like we should definitely have a process that's just super clear for clients and 359 00:21:43.400 --> 00:21:48.160 the team to know exactly, you know, when things are ready to be worked on and so 360 00:21:48.160 --> 00:21:48.400 forth. 361 00:21:48.400 --> 00:21:51.120 So this, so that was good. 362 00:21:51.120 --> 00:21:53.880 Cause yeah, we didn't have a good, and this all came because we had this column 363 00:21:53.880 --> 00:21:56.760 called interview that wasn't, we didn't know what it was for. 364 00:21:57.240 --> 00:22:01.240 But when we said, Oh, the clients need to move it out of, they're the only ones that 365 00:22:01.240 --> 00:22:03.840 can move it out of interview to complete it. 366 00:22:03.840 --> 00:22:06.760 We, I think we, I don't know if we said that somewhere, but I remember there was 367 00:22:06.760 --> 00:22:10.240 this like clarity moment where like, Oh, we're not allowed to move it out of 368 00:22:10.240 --> 00:22:10.800 interview. 369 00:22:10.840 --> 00:22:13.800 Like, unless we're on a call with a client and they say yes, then we'll move 370 00:22:13.800 --> 00:22:14.480 it together. 371 00:22:14.720 --> 00:22:18.880 And then we'll still leave a comment and be like such and such client approved 372 00:22:18.880 --> 00:22:19.240 this. 373 00:22:19.680 --> 00:22:22.240 That's how we should get things out of interview. 374 00:22:22.520 --> 00:22:26.560 And then it also creates like a nice hard stop and we don't have this tail because a 375 00:22:26.560 --> 00:22:30.920 lot of times things can sit in review and then two weeks later a bug pops up and we 376 00:22:30.920 --> 00:22:33.640 kind of reopen the whole thing and it's sort of never ending. 377 00:22:34.000 --> 00:22:40.160 So anyway, that, that was just yeah, how we got some clarity there. 378 00:22:40.560 --> 00:22:44.280 But I think, I think this is getting more simple. 379 00:22:44.280 --> 00:22:45.720 I don't know if we want to just quickly clean this up. 380 00:22:45.720 --> 00:22:49.440 If you have any thoughts, Lucian or Ira, anyone want to jump in as well? 381 00:22:49.880 --> 00:22:54.280 Yeah, maybe it's in the details a bit, but I got really nice, like clarity here 382 00:22:54.280 --> 00:22:57.720 about the process, you know, where I was saying about like in review should be 383 00:22:57.720 --> 00:23:03.120 just when the client is looking at, um, there's like a process thing that it's 384 00:23:03.120 --> 00:23:05.400 like not clear when it's done. 385 00:23:05.400 --> 00:23:11.960 What we can do is like have a, you know, just like notion automation that you have 386 00:23:11.960 --> 00:23:18.560 to like create, um, what do we call, um, we saw this like Ryan video, he's doing 387 00:23:18.560 --> 00:23:22.600 like case study and like they, they have a deliverable thing, like a document that 388 00:23:22.600 --> 00:23:25.840 like shows like, Oh, this is how you use the new feature. 389 00:23:25.840 --> 00:23:30.120 And like, just like kind of the summary of like what was built or like a video 390 00:23:30.120 --> 00:23:33.760 demo or something like that, like a deliverable and you have to like have 391 00:23:33.760 --> 00:23:37.200 that to create like an in review to, to change status in review. 392 00:23:37.840 --> 00:23:42.080 So that could be like a good, you know, process and it would be like pretty 393 00:23:42.080 --> 00:23:46.440 simple to just like, um, do some software that enforces this, you know? 394 00:23:47.440 --> 00:23:48.480 Yeah, that's great. 395 00:23:49.640 --> 00:23:54.000 Um, so one thing I'll leave here is like the views are, we'd like to create 396 00:23:54.000 --> 00:23:55.720 are technically impossible in notion. 397 00:23:55.760 --> 00:23:57.880 I think it's one that you said there, it's kind of similar to this one. 398 00:23:57.880 --> 00:23:59.120 I could probably clear these up. 399 00:23:59.760 --> 00:24:05.040 Um, so I, and I think this one's very much, and I'm what I'm shaped. 400 00:24:05.760 --> 00:24:10.960 So in, in, uh, the shape up, they have a great little diagram, which I don't 401 00:24:10.960 --> 00:24:15.160 have time to like find, but we have this like random blob of a project. 402 00:24:15.160 --> 00:24:19.000 And so we've kind of started to carve out like sections of what the, I mean, they 403 00:24:19.000 --> 00:24:20.760 call these kind of the vertical slices. 404 00:24:21.160 --> 00:24:25.360 So one of these, one of these things is the actual client view here. 405 00:24:25.880 --> 00:24:29.720 Um, and the other one may be like a team member view. 406 00:24:29.720 --> 00:24:31.200 The other one may be like security. 407 00:24:31.200 --> 00:24:35.280 So what we were going to focus on is we can actually get this all solved for the 408 00:24:35.280 --> 00:24:39.920 client and publish it and start using it as a company and then go back and like 409 00:24:39.920 --> 00:24:42.800 solve a different problem, which is like, how did the team members see this? 410 00:24:42.800 --> 00:24:44.080 So how did the admin see this? 411 00:24:44.440 --> 00:24:48.000 Because we can, you know, this could turn into like a, you know, one, a two week 412 00:24:48.000 --> 00:24:50.200 project versus being maybe a six week project. 413 00:24:50.680 --> 00:24:56.080 Um, so because I'm always like, I'm very much in the mode of like, get something 414 00:24:56.080 --> 00:24:59.760 small, that's really, really useful, ship it and let us start. 415 00:25:00.000 --> 00:25:05.120 using it. And then we'll go and figure out the next thing. So I would say anything that's 416 00:25:07.840 --> 00:25:12.240 not related to the client piece, I would almost take those things out initially, 417 00:25:12.240 --> 00:25:16.880 just because then at least we're all looking at this client view and the clients can see 418 00:25:16.880 --> 00:25:23.200 what's going on. Because I guarantee it, we look at a board like this every single day, 419 00:25:23.200 --> 00:25:27.200 maybe pull it up with clients, but they're not looking at this and they're not looking at it 420 00:25:27.200 --> 00:25:33.200 the same way. This means a lot to us, probably doesn't mean a lot to clients because they're 421 00:25:33.200 --> 00:25:38.960 just not using it every single day. And so it looks kind of unfamiliar and it looks confusing. 422 00:25:38.960 --> 00:25:44.880 So we want to just simplify that. So what's nice about having the blocks like here, 423 00:25:45.680 --> 00:25:48.560 while you guys were talking, I just dragged a couple of these things that they're not doing. 424 00:25:48.560 --> 00:25:53.280 So it's very clear, not only am I deleting it, but I'm specifically saying nothing to do with 425 00:25:54.080 --> 00:25:59.040 clients. So is there anything else we want to tweak on this? 426 00:25:59.040 --> 00:26:02.800 Anyone on the problem or outcome? And then we'll move on. 427 00:26:06.320 --> 00:26:10.880 Not doing project changes, like the last item in the outcome. 428 00:26:12.880 --> 00:26:14.240 Oh, this one? 429 00:26:14.960 --> 00:26:15.200 Yeah. 430 00:26:15.920 --> 00:26:16.880 Yeah, we can take this out. 431 00:26:17.840 --> 00:26:20.160 I mean, this project could just be like client view, 432 00:26:20.880 --> 00:26:24.720 and then we have like a shipped, an actual thing, and then we can look at the next thing. 433 00:26:24.720 --> 00:26:29.680 Yeah. And part of this is like, this is like more on the process side. 434 00:26:34.320 --> 00:26:39.360 And projects will require admins to, so, and this may be good because maybe this like 435 00:26:39.360 --> 00:26:42.880 approval process is actually part of it is because we don't, 436 00:26:43.360 --> 00:26:46.880 because we said this is where they can see stuff, but I think maybe there's also like a, 437 00:26:48.160 --> 00:26:52.720 now that we kind of sliced it differently, we sliced it to like team to the clients only. 438 00:26:53.440 --> 00:27:02.640 We could say like, a like tool or just like a, we'll say a way for clients to 439 00:27:04.800 --> 00:27:10.960 approve projects before work. And I don't know if it's approved. What did we said? 440 00:27:11.360 --> 00:27:16.720 We came up with a really good word for it. Approve. And then like. 441 00:27:18.960 --> 00:27:19.760 Approve and fund. 442 00:27:21.040 --> 00:27:22.240 Yeah. Something like that. 443 00:27:24.240 --> 00:27:27.760 Even if you say fund, now it's like, does that mean we have to have like this hooked into Stripe? 444 00:27:27.760 --> 00:27:33.520 Does it mean like, it just opens up like approve projects before work? 445 00:27:33.600 --> 00:27:42.960 And kind of a move to completed after interview. This is not written well, but maybe it's 446 00:27:42.960 --> 00:27:47.920 a little wordy, but I'd rather be. So maybe there's a way for them to approve it in this 447 00:27:47.920 --> 00:27:52.480 phase. Cause we, this could be a button. So so many times these, like this whole outcome, 448 00:27:53.200 --> 00:27:57.520 I think I drew it somewhere over here. It could literally just be a button that says like, 449 00:27:57.520 --> 00:28:01.680 they hit approve pops up. It says like, are you sure you hit? Yes. And then it's like approved. 450 00:28:02.160 --> 00:28:08.640 Um, cause we couldn't really, there's not like a great mechanism to do this in notion. Yes. You 451 00:28:08.640 --> 00:28:12.480 could make like a check box that says client approved. Yes or no. And they could check it, 452 00:28:12.480 --> 00:28:16.560 but like then anyone else can uncheck it. So it's just kind of, it's not a very like 453 00:28:17.600 --> 00:28:23.280 definite thing where we could have a button when they push this, it like updates the status to 454 00:28:23.280 --> 00:28:28.320 dev ready. It makes a comment in the notion project that says such and such user approved 455 00:28:28.320 --> 00:28:32.960 on this date for this thing at two weeks. And we has a kind of that log in the comments on the 456 00:28:32.960 --> 00:28:37.280 notion. So that could just be a button. So I don't think, I think that's very much in scope. 457 00:28:37.280 --> 00:28:43.120 Um, it's probably two hours of work to add that. Um, and that could be kind of get us this outcome 458 00:28:43.120 --> 00:28:49.680 we're looking for. Um, and then maybe it's the same thing once the project is, so we really have 459 00:28:49.680 --> 00:28:54.320 like a kind of, we're confusing it even I'm in confused because we have these two points of like, 460 00:28:55.200 --> 00:28:58.320 Oh, maybe it's confirmed and approved. Maybe those are the two. 461 00:28:58.320 --> 00:29:02.080 Yeah. You just have to watch out like, cause it opens the edge case that they 462 00:29:02.080 --> 00:29:07.360 approve, but they didn't pay. And then the dev gets like the, the dev ready status. 463 00:29:09.120 --> 00:29:14.160 Sure. So, so that's good. Cause you brought that up and then I immediately want to like 464 00:29:14.160 --> 00:29:19.520 swap that away. Um, so let's just like, that's good. Cause, cause there seems like there's 465 00:29:19.520 --> 00:29:30.880 something vague there. So we'll say like, um, uh, no, um, like we'll say like, uh, payment, uh, 466 00:29:32.000 --> 00:29:40.640 processing included project. Um, we'll just be like, uh, admins will keep close watch. We don't 467 00:29:40.640 --> 00:29:47.760 have a hundred projects happening in a week. Cause we're tracking. It's like, uh, you track 468 00:29:47.760 --> 00:29:54.800 like payments away from view. It could be like, if it's linked to a payment and it was approved, 469 00:29:54.800 --> 00:29:59.520 then it's okay. So just like, I think it's fine if they approved it here and they hit the button 470 00:30:00.000 --> 00:30:02.000 Like, it felt a little more formal. 471 00:30:02.000 --> 00:30:03.800 We don't even do that now. 472 00:30:03.800 --> 00:30:07.120 And then we have to deal with the movement of money 473 00:30:07.120 --> 00:30:08.400 afterwards. 474 00:30:08.400 --> 00:30:10.560 That's probably fine. 475 00:30:10.560 --> 00:30:12.920 If they hit yes and they approved it, 476 00:30:12.920 --> 00:30:15.520 and we basically have a log where they're like, no, 477 00:30:15.520 --> 00:30:17.960 you requested this work on this date, 478 00:30:17.960 --> 00:30:19.420 we're never going to get into issue 479 00:30:19.420 --> 00:30:22.520 where we could even do the work, even if they haven't paid. 480 00:30:22.520 --> 00:30:25.720 We still have the log of them formally approving 481 00:30:25.720 --> 00:30:28.520 the work to be done. 482 00:30:28.520 --> 00:30:30.880 But yes, I think down the road, it'd be super cool 483 00:30:30.880 --> 00:30:33.800 if it just pulls a Stripe transaction. 484 00:30:33.800 --> 00:30:35.800 It's one little movement, 100%. 485 00:30:35.800 --> 00:30:39.000 But just for the sake of getting this one launched, 486 00:30:39.000 --> 00:30:40.440 because it runs into other problems 487 00:30:40.440 --> 00:30:45.240 where not all clients pay us through Stripe, for example. 488 00:30:45.240 --> 00:30:48.000 And maybe it needs to generate a Mercury wire 489 00:30:48.000 --> 00:30:50.640 request versus Stripe. 490 00:30:50.640 --> 00:30:53.640 So yes, maybe that's another project. 491 00:30:53.640 --> 00:30:56.320 But I'll just say, don't worry about the processing right now. 492 00:31:00.080 --> 00:31:03.520 Yeah, current, future projects. 493 00:31:03.520 --> 00:31:07.080 Knowing which projects are paid for, that's fine. 494 00:31:07.080 --> 00:31:09.440 And then I don't even have to worry about this. 495 00:31:17.320 --> 00:31:19.760 Yeah, I think this is fine. 496 00:31:19.760 --> 00:31:22.200 This probably feels small enough now. 497 00:31:22.200 --> 00:31:24.200 And then I think the appetite's pretty simple. 498 00:31:24.200 --> 00:31:27.560 I would probably put two weeks on this, which for us 499 00:31:27.560 --> 00:31:32.840 would be 50 hours, roughly, in normal language. 500 00:31:32.840 --> 00:31:34.880 I think that's definitely doable. 501 00:31:34.880 --> 00:31:36.800 It's probably a one-week project, honestly. 502 00:31:36.800 --> 00:31:41.200 But part of the outcome of this is us also 503 00:31:41.200 --> 00:31:43.280 doing it together as a team. 504 00:31:43.280 --> 00:31:45.200 So we probably are doubling up the time 505 00:31:45.200 --> 00:31:47.800 just talking about it with all of us on the call. 506 00:31:47.800 --> 00:31:50.120 We're probably way over our budget with nine of us 507 00:31:50.120 --> 00:31:53.840 on this call. 508 00:31:53.840 --> 00:31:56.160 OK, anything else you guys want to add? 509 00:31:56.160 --> 00:31:57.560 And then I think we're good. 510 00:31:57.560 --> 00:32:01.240 We'll take 10 minutes and kind of breadboard a few things. 511 00:32:01.240 --> 00:32:03.200 But anything else you guys want to add here? 512 00:32:09.240 --> 00:32:11.720 For you guys, Ira, Janata, Lucian, 513 00:32:11.720 --> 00:32:14.200 you guys are typically in with clients. 514 00:32:14.200 --> 00:32:17.560 Like, this is what I'm seeing from my standpoint, which 515 00:32:17.560 --> 00:32:20.600 may be a little bit different than yours. 516 00:32:20.600 --> 00:32:24.000 Are these problems that you think the clients have 517 00:32:24.000 --> 00:32:28.120 or that you have at times, does this 518 00:32:28.120 --> 00:32:33.120 add any benefit for you to see a view like this? 519 00:32:33.120 --> 00:32:37.280 I mean, we're in Notion, so it's not probably very useful. 520 00:32:37.280 --> 00:32:40.200 But we also didn't want to assume that everybody 521 00:32:40.200 --> 00:32:43.480 was using a view like, I think we actually came up 522 00:32:43.480 --> 00:32:47.800 with like a My Dashboard team dashboard. 523 00:32:47.800 --> 00:32:51.000 Yeah, we did create this little sample dashboard 524 00:32:51.000 --> 00:32:54.240 so you could click on what all the team was doing, 525 00:32:54.240 --> 00:32:59.160 my projects, what's in review, and so forth. 526 00:32:59.160 --> 00:33:01.320 Because the one thing I love about Notion 527 00:33:01.320 --> 00:33:02.640 is it's highly customizable. 528 00:33:02.640 --> 00:33:04.080 And I also hate that about Notion 529 00:33:04.080 --> 00:33:07.080 because I can have one view that looks amazing for Bruce. 530 00:33:07.080 --> 00:33:08.720 And Lucian could have his own view that 531 00:33:08.720 --> 00:33:09.760 looks amazing for Lucian. 532 00:33:09.760 --> 00:33:12.800 And then like, Ira and Janata don't use that or see it 533 00:33:12.800 --> 00:33:15.960 because you have to sit there and make it yourself. 534 00:33:15.960 --> 00:33:18.520 Like, you have to build your own view of this stuff. 535 00:33:18.520 --> 00:33:22.640 So I don't know if this is helpful. 536 00:33:22.640 --> 00:33:31.040 Yeah, I think I'm using something similar. 537 00:33:31.040 --> 00:33:37.080 But I think the most important part of having this, 538 00:33:37.080 --> 00:33:40.920 I think we really nailed down the part of what really matters 539 00:33:40.920 --> 00:33:45.200 is to have this view accessible for the customer. 540 00:33:45.200 --> 00:33:48.640 Because Notion is like really good to use and stuff 541 00:33:48.640 --> 00:33:50.040 and it's very flexible. 542 00:33:50.040 --> 00:33:55.040 But incredibly, like the sharing system, it's strange. 543 00:33:55.040 --> 00:34:00.240 And if you send to a customer, they have to like be logged in 544 00:34:00.240 --> 00:34:02.640 and not everyone uses Notion. 545 00:34:02.640 --> 00:34:06.800 So it creates a lot of friction with the customer. 546 00:34:06.800 --> 00:34:08.880 So for instance, like with Hackstack, 547 00:34:08.880 --> 00:34:12.000 they are a customer that we are running for a long time 548 00:34:12.000 --> 00:34:14.199 and they don't use Notion a lot. 549 00:34:14.199 --> 00:34:18.560 So I think if you have something that we can use as a basis 550 00:34:18.560 --> 00:34:24.960 to like have the customers to look to help customers 551 00:34:24.960 --> 00:34:27.800 to create the habit of like using this 552 00:34:27.800 --> 00:34:30.040 as the main point of reference, I 553 00:34:30.040 --> 00:34:33.120 think this is the key value, especially 554 00:34:33.120 --> 00:34:37.639 for this long term running project, where 555 00:34:37.679 --> 00:34:44.080 you can like have plan like one, two, or three months ahead. 556 00:34:44.080 --> 00:34:49.560 But we need to like to have this common view where everyone 557 00:34:49.560 --> 00:34:52.560 can look and see, hey, this is where we are going. 558 00:34:52.560 --> 00:34:55.400 We agreed that we are going to this direction 559 00:34:55.400 --> 00:34:57.880 and we agreed at this point in time. 560 00:34:57.880 --> 00:35:01.200 So I think my main. 561 00:35:00.000 --> 00:35:07.880 The main use for me for this specific view is to improve client communication. 562 00:35:07.880 --> 00:35:13.080 Like it's to have a point, a source of truth where we can always point customers 563 00:35:13.080 --> 00:35:19.240 back to, and we don't have to rely on them, like using Notion or like having to 564 00:35:19.240 --> 00:35:25.160 know how to use Notion because we can like, make it as easy or as complicated 565 00:35:25.160 --> 00:35:27.640 as you want, because we are like creating from scratch. 566 00:35:27.640 --> 00:35:35.880 So I think it's, it can easily, like sometimes if you think like it could 567 00:35:35.880 --> 00:35:42.920 like sound like an overkill, but if you use Notion and if you shared stuff 568 00:35:42.960 --> 00:35:48.000 with it, you'll know that that's not an overkill, like especially if the 569 00:35:48.000 --> 00:35:53.040 other end is not accustomed with Notion that like doesn't have the practices 570 00:35:53.040 --> 00:35:56.280 and doesn't use it a lot, it can create a lot of friction. 571 00:35:56.280 --> 00:36:02.640 And like, for instance, every month we need to share the new database with, 572 00:36:02.720 --> 00:36:07.840 or like we need to, to review the share, the access to chase if they're 573 00:36:07.840 --> 00:36:09.680 seeing the reactive stuff or not. 574 00:36:09.680 --> 00:36:15.720 I mean, like this kind of creates unnecessary friction and breaks like 575 00:36:15.720 --> 00:36:19.040 the, the possibility of creating a habit around it. 576 00:36:19.040 --> 00:36:24.960 So yeah, I think, sorry, really long handling around it, but, but I think 577 00:36:24.960 --> 00:36:30.800 it's, it's I think it's my, my way of seeing it's like having the source of 578 00:36:30.800 --> 00:36:33.440 truth and easy access for the customer. 579 00:36:34.280 --> 00:36:34.600 Okay. 580 00:36:35.040 --> 00:36:35.400 That's good. 581 00:36:35.440 --> 00:36:38.400 So I'll just, I think we're in a good spot. 582 00:36:38.440 --> 00:36:45.240 So I would, I started doing this last time. 583 00:36:45.480 --> 00:36:46.280 Let me just grab this. 584 00:36:46.280 --> 00:36:48.440 So we're going to kind of have like maybe two components. 585 00:36:49.120 --> 00:36:52.640 I think this by status is helpful because they can quickly see like 586 00:36:52.640 --> 00:36:53.920 everything moving to the right. 587 00:36:54.240 --> 00:36:58.720 But maybe from a billing standpoint, we do need it rearranged to the month 588 00:36:58.720 --> 00:37:02.400 view, which is kind of more like this, where it's got columns for each month. 589 00:37:03.080 --> 00:37:06.040 It might even be better to have like timeline view. 590 00:37:06.040 --> 00:37:08.240 Cause it's not always like a clean overlap. 591 00:37:09.040 --> 00:37:09.360 Hmm. 592 00:37:10.600 --> 00:37:10.760 Yeah. 593 00:37:10.760 --> 00:37:14.240 So maybe it's, I'll just say, yeah, let's just, yeah. 594 00:37:14.760 --> 00:37:15.200 Roots. 595 00:37:16.000 --> 00:37:26.160 Um, maybe by, by I'm going to give it a, a, a ugly name, like work dates or by, 596 00:37:26.920 --> 00:37:30.280 uh, maybe it's a project calendar or something. 597 00:37:30.320 --> 00:37:34.520 It could be a cam Kanban or I don't really care what, what it is. 598 00:37:34.520 --> 00:37:35.280 We'll figure that out. 599 00:37:35.640 --> 00:37:37.760 And I want to piggyback off of what Janata said. 600 00:37:37.760 --> 00:37:39.880 You asked about like, what, like pain points. 601 00:37:40.280 --> 00:37:43.040 And cause now we have like, you know, the monster projects and like 602 00:37:43.040 --> 00:37:46.560 kind of showing them the sequence of upcoming work and like reshuffling. 603 00:37:46.560 --> 00:37:51.680 That is like, this project has like huge potential to, to help 604 00:37:51.680 --> 00:37:53.280 the communications on that side. 605 00:37:53.960 --> 00:37:54.360 Sure. 606 00:37:55.040 --> 00:37:58.320 So I just want to, so this, I think is clear, the Kanban stuff 607 00:37:58.320 --> 00:38:00.600 like makes sense for me here. 608 00:38:01.160 --> 00:38:05.040 Um, since we, so we already didn't have like a immediate clarity on 609 00:38:05.040 --> 00:38:06.840 the, on, is it Kanban or is it timeline? 610 00:38:06.840 --> 00:38:10.000 I'm just going to put projects by dates and then we'll figure this out later. 611 00:38:10.600 --> 00:38:18.440 Um, and, uh, we could have like, um, uh, for the month would be helpful. 612 00:38:18.880 --> 00:38:23.320 We also want to see like the, um, and then what I would say is, uh, 613 00:38:23.360 --> 00:38:27.120 actually have like a component here called the, um, project card. 614 00:38:27.880 --> 00:38:33.640 And this would have like the title and you guys, we got like a total, 615 00:38:33.720 --> 00:38:39.400 or we'll say actual hours versus, um, total hours or something like that. 616 00:38:39.400 --> 00:38:43.880 We could also have even, I might contest this because on the client side, they 617 00:38:43.880 --> 00:38:45.840 don't even necessarily need to know. 618 00:38:45.840 --> 00:38:47.280 It's more like an internal metric. 619 00:38:47.280 --> 00:38:50.320 Like, were we clear enough on this project? 620 00:38:50.320 --> 00:38:53.960 If we weren't, then we end up spending more time than we should have. 621 00:38:54.360 --> 00:38:59.120 And on their side, they just know that they paid this much and like the dates 622 00:38:59.160 --> 00:39:04.600 that we like wanted to complete it by, you know, it's not even necessarily 623 00:39:04.600 --> 00:39:06.960 relevant to them, like how many hours we spent on it. 624 00:39:07.960 --> 00:39:14.280 I think, yes, but also, um, it does cause this, this actually told, this 625 00:39:14.280 --> 00:39:17.480 is actually the total appetite. 626 00:39:17.480 --> 00:39:18.880 Cause it does show movement. 627 00:39:19.080 --> 00:39:24.160 Um, it's just that we don't like stop billing clearly on the, uh, like this 628 00:39:24.160 --> 00:39:30.280 guy, like 38 hours out of, so I love showing this to clients, um, because I 629 00:39:30.280 --> 00:39:36.400 paid for 30 or like we, like they only paid for a week, but they got like 150% 630 00:39:36.560 --> 00:39:39.080 more, like 50% more than what they want. 631 00:39:39.400 --> 00:39:41.920 That's on us to fix, not, not on them. 632 00:39:42.480 --> 00:39:44.920 Um, and there was a bunch of like research and stuff happening on this. 633 00:39:44.920 --> 00:39:45.920 We know why that was there. 634 00:39:45.920 --> 00:39:50.320 Cause there's another bigger project coming, but this is nice because it 635 00:39:50.320 --> 00:39:53.320 does kind of show you, um, progress. 636 00:39:53.360 --> 00:39:56.920 Like if this is it just cause we want to make full transparency. 637 00:39:57.320 --> 00:39:59.840 So I think this is just a, like a, um. 638 00:40:00.000 --> 00:40:05.000 like a way to add clarity to the, 639 00:40:05.440 --> 00:40:08.200 like, or just shows them that work's being done 640 00:40:08.200 --> 00:40:11.080 because it's hard to know because they're not, 641 00:40:11.080 --> 00:40:13.040 most of the clients are not technical. 642 00:40:13.040 --> 00:40:15.540 They just know like, oh, ours have been invested, 643 00:40:16.760 --> 00:40:20.720 which is maybe pretty, yeah, I don't know. 644 00:40:20.720 --> 00:40:23.840 And this at the risk of throwing like a monkey wrench 645 00:40:23.840 --> 00:40:27.960 into this, which I love doing, but you know, 646 00:40:28.600 --> 00:40:33.320 potential process like question or, you know, blurriness is, 647 00:40:33.320 --> 00:40:35.920 because on this like project that's gone, 648 00:40:35.920 --> 00:40:38.840 we're over scalability upgrade. 649 00:40:38.840 --> 00:40:42.920 A bunch of that time was spent shaping the next project. 650 00:40:42.920 --> 00:40:45.440 And that's kind of like, like when we shape a project, 651 00:40:45.440 --> 00:40:47.520 should we be billing on that project, 652 00:40:47.520 --> 00:40:48.760 which hasn't been paid yet. 653 00:40:48.760 --> 00:40:52.080 So there's a bit of like, you know, circular. 654 00:40:52.080 --> 00:40:53.280 Yeah, yeah, yeah. 655 00:40:54.920 --> 00:40:56.400 That's true. 656 00:40:56.400 --> 00:40:59.320 I think those are more like definitely process things. 657 00:40:59.320 --> 00:41:02.280 And once we have the clarity for it as well, 658 00:41:02.280 --> 00:41:04.000 I think there was also in our process, 659 00:41:04.000 --> 00:41:09.000 there's probably like a little post project debrief for, 660 00:41:09.080 --> 00:41:10.940 even if it's just a few comments back and forth, 661 00:41:10.940 --> 00:41:13.440 but just to look at these numbers. 662 00:41:13.440 --> 00:41:16.900 And if we get this project card that feels very clear 663 00:41:16.900 --> 00:41:19.920 that anyone can look at this and kind of see what happened, 664 00:41:19.920 --> 00:41:21.740 it's like, oh, there's something to talk about that. 665 00:41:21.740 --> 00:41:23.040 Like, okay, it went over, 666 00:41:23.040 --> 00:41:24.440 did we just forget to change the dates? 667 00:41:25.200 --> 00:41:28.000 Do we massively underestimate this? 668 00:41:28.000 --> 00:41:31.480 This is a very unique project and I'm not worried about it, 669 00:41:31.480 --> 00:41:34.240 but it'd be good to like just talk that through 670 00:41:34.240 --> 00:41:38.280 to see, you know, did it actually need, 671 00:41:38.280 --> 00:41:41.680 and there's maybe other projects which are probably, 672 00:41:42.520 --> 00:41:45.840 actually, where is the, did we just finish the, 673 00:41:45.840 --> 00:41:48.860 where's the attachments one? 674 00:41:51.080 --> 00:41:51.920 Yeah, it's weird. 675 00:41:51.920 --> 00:41:53.100 Maybe it's a bug in your prototype 676 00:41:53.100 --> 00:41:54.980 or is it, I'm pretty sure it's in review. 677 00:41:54.980 --> 00:41:55.820 It's in review? 678 00:41:55.820 --> 00:41:56.640 Is it in review? 679 00:41:56.640 --> 00:41:59.740 It doesn't have the right client, maybe? 680 00:42:01.220 --> 00:42:02.580 I'm checking it out. 681 00:42:02.580 --> 00:42:03.420 Okay. 682 00:42:06.220 --> 00:42:07.060 I'll wait just a second. 683 00:42:07.060 --> 00:42:07.880 It has two clients. 684 00:42:10.340 --> 00:42:11.780 Just delete this one. 685 00:42:11.780 --> 00:42:14.220 Yeah, and it's in review, so it should be showing up. 686 00:42:14.220 --> 00:42:15.500 That's it, so yeah. 687 00:42:15.500 --> 00:42:17.140 Maybe it's in the tribe one then. 688 00:42:17.140 --> 00:42:19.140 Yeah, go ahead, Ira. 689 00:42:19.140 --> 00:42:21.180 Yeah, so I think it's, 690 00:42:21.180 --> 00:42:23.780 since this is for the, our clients, 691 00:42:23.780 --> 00:42:27.140 I think it's important to see like the, 692 00:42:27.140 --> 00:42:31.500 if we're going beyond like the agreed upon timeframe, 693 00:42:31.500 --> 00:42:34.020 but in terms of the progress bar, 694 00:42:34.020 --> 00:42:38.300 I feel like it would be better to have the progress 695 00:42:38.300 --> 00:42:41.740 maybe in terms of, so one thing I always use, 696 00:42:41.740 --> 00:42:44.060 I use the monster map or like the verticals. 697 00:42:44.060 --> 00:42:44.900 Right. 698 00:42:44.900 --> 00:42:46.420 Like, yeah, these are the points, 699 00:42:46.420 --> 00:42:49.820 and maybe that time bar is like, 700 00:42:49.820 --> 00:42:53.500 there's a chunk for each of these verticals. 701 00:42:53.500 --> 00:42:55.980 And so they can like click it and see, okay, 702 00:42:55.980 --> 00:42:57.380 well, you're working on, 703 00:42:57.380 --> 00:42:59.300 you've completed these two verticals and like that. 704 00:42:59.300 --> 00:43:03.540 I think that my concern with like letting it be based 705 00:43:03.540 --> 00:43:06.540 on time is I try to, when I can, 706 00:43:06.540 --> 00:43:10.540 I try to like implement it as quickly as I can, you know? 707 00:43:10.540 --> 00:43:13.900 And I don't wanna be in a situation where, 708 00:43:13.900 --> 00:43:16.220 because I'm trying to like do clever things 709 00:43:17.020 --> 00:43:19.340 and like get it done faster that it's like, 710 00:43:19.340 --> 00:43:20.940 oh, well you can actually work faster. 711 00:43:20.940 --> 00:43:22.980 So for your next project, we'll. 712 00:43:22.980 --> 00:43:23.820 Yeah, yeah. 713 00:43:23.820 --> 00:43:24.700 You know? 714 00:43:24.700 --> 00:43:25.540 Yeah. 715 00:43:25.540 --> 00:43:28.780 I think it's, yeah. 716 00:43:28.780 --> 00:43:29.620 Either way. 717 00:43:29.620 --> 00:43:32.260 And then also they always see a full, 718 00:43:33.300 --> 00:43:36.460 they'll also, they'll always see like a full 100% 719 00:43:36.460 --> 00:43:40.140 like thing, which as I'm like tackling the verticals, 720 00:43:40.140 --> 00:43:42.260 that bar will always hit 100%, 721 00:43:42.260 --> 00:43:43.620 where if it's based on time, 722 00:43:43.620 --> 00:43:46.020 it could potentially not 100%. 723 00:43:46.980 --> 00:43:47.820 Okay. 724 00:43:47.820 --> 00:43:48.660 Yeah. 725 00:43:53.660 --> 00:43:54.660 You guys happy? 726 00:43:55.820 --> 00:43:56.660 Yeah. 727 00:44:01.420 --> 00:44:04.140 So conditional, if that's there, 728 00:44:04.140 --> 00:44:06.140 if not, we just wanna see, 729 00:44:06.140 --> 00:44:07.340 we still wanna see the app. 730 00:44:07.340 --> 00:44:09.460 Like we still need them to see that this is, 731 00:44:09.460 --> 00:44:12.460 what's the appetite maybe somewhere? 732 00:44:13.420 --> 00:44:16.260 Cause this would tell you that it's two weeks. 733 00:44:16.260 --> 00:44:20.900 And so that, and it's really the first couple hours. 734 00:44:20.900 --> 00:44:22.220 So we can do that for now. 735 00:44:23.740 --> 00:44:25.780 We can have that little conditional. 736 00:44:25.780 --> 00:44:27.860 I'm okay with that for now. 737 00:44:27.860 --> 00:44:30.540 Cause, and this is exactly what we can't do in Notion. 738 00:44:30.540 --> 00:44:33.620 So this is one like line of code 739 00:44:33.620 --> 00:44:36.260 wrapping that one little component. 740 00:44:36.260 --> 00:44:38.140 It's a great, great example where we could actually 741 00:44:38.140 --> 00:44:40.300 super quick to change that. 742 00:44:40.300 --> 00:44:42.060 And maybe they do wanna see it down the road. 743 00:44:42.580 --> 00:44:44.740 And we enable it or not. 744 00:44:44.740 --> 00:44:45.620 Sorry, I said end team. 745 00:44:45.620 --> 00:44:47.140 This is where admin here. 746 00:44:47.140 --> 00:44:49.340 We just have two different roles right now. 747 00:44:51.820 --> 00:44:56.020 And I think that's Chinada's dog. 748 00:44:57.540 --> 00:45:00.100 My dog under my desk is gonna start barking at him. 749 00:45:00.000 --> 00:45:02.180 That's good. 750 00:45:02.180 --> 00:45:03.940 So we can kind of breadboard this out. 751 00:45:03.940 --> 00:45:05.600 We're going to kind of wrap this up in like two minutes 752 00:45:05.600 --> 00:45:07.300 because I got to jump to the next thing. 753 00:45:07.300 --> 00:45:11.540 But this is just a great example. 754 00:45:11.540 --> 00:45:14.740 It kind of felt pretty cool when you guys all looked at this 755 00:45:14.740 --> 00:45:15.700 and were like, this is awesome. 756 00:45:15.700 --> 00:45:16.540 Let's ship it. 757 00:45:16.540 --> 00:45:19.540 We could probably send this to a client today. 758 00:45:19.540 --> 00:45:22.220 And then we get into this discussion about this bar. 759 00:45:22.220 --> 00:45:25.380 And all of a sudden, we're not clear anymore about this bar. 760 00:45:25.380 --> 00:45:27.340 So that's good. 761 00:45:27.340 --> 00:45:30.500 And I think what we'd do is probably have the same project 762 00:45:30.500 --> 00:45:31.720 card if we can. 763 00:45:31.720 --> 00:45:34.040 I don't know why we would need a different component. 764 00:45:34.040 --> 00:45:35.620 But what's nice about this is we start 765 00:45:35.620 --> 00:45:38.520 to see that there's one project card component. 766 00:45:38.520 --> 00:45:41.520 And then we can maybe arrange them in two different views, 767 00:45:41.520 --> 00:45:43.240 whatever those views might be. 768 00:45:43.240 --> 00:45:44.160 Maybe it's a timeline. 769 00:45:44.160 --> 00:45:47.380 Maybe it's a calendar. 770 00:45:47.380 --> 00:45:51.080 I suspect it's going to be a little bit of both 771 00:45:51.080 --> 00:45:53.320 because I think the timeline view is pretty nice. 772 00:45:53.320 --> 00:45:55.000 We actually looked at this. 773 00:45:55.000 --> 00:45:56.920 Do you remember who you built it for, Lucien? 774 00:45:56.980 --> 00:45:58.700 Was it Kavimars? 775 00:45:58.700 --> 00:46:01.260 Oh, yeah, timeline. 776 00:46:01.260 --> 00:46:03.780 So we started to do this kind of view. 777 00:46:03.780 --> 00:46:05.260 Again, this is a great example where 778 00:46:05.260 --> 00:46:06.700 you have to use a bunch of filters 779 00:46:06.700 --> 00:46:08.140 to get this to not look insane. 780 00:46:10.660 --> 00:46:12.820 And I think it looks better if you look at quarter 781 00:46:12.820 --> 00:46:15.500 because it kind of zooms out a hair. 782 00:46:15.500 --> 00:46:16.180 Exactly. 783 00:46:16.180 --> 00:46:17.340 And there's limitations. 784 00:46:17.340 --> 00:46:21.740 You can't filter by start date or end date or stuff like that. 785 00:46:21.740 --> 00:46:23.900 Yes, it's just all projects right now, 786 00:46:23.900 --> 00:46:25.100 and then including completed. 787 00:46:25.120 --> 00:46:28.720 So this list is pretty long. 788 00:46:28.720 --> 00:46:30.720 And if you hide completed, it's hard to see. 789 00:46:30.720 --> 00:46:32.120 You kind of want completed but only 790 00:46:32.120 --> 00:46:34.120 completed within the last 90 days or something. 791 00:46:34.120 --> 00:46:36.440 You don't want it from two years ago. 792 00:46:36.440 --> 00:46:38.480 But anyway, something like this potentially 793 00:46:38.480 --> 00:46:44.080 could be good because you can kind of see this timeline. 794 00:46:44.080 --> 00:46:45.520 So we'll play with that. 795 00:46:45.520 --> 00:46:47.640 I'm not going to worry too much about it. 796 00:46:47.640 --> 00:46:51.620 What I did start to do as well, we call it the task grid. 797 00:46:51.640 --> 00:46:55.360 This is a tool Ryan built, which we really like, 798 00:46:55.360 --> 00:46:57.760 which is just this grid of nine things. 799 00:46:57.760 --> 00:47:01.520 And so I'm going to go ahead and delete this. 800 00:47:01.520 --> 00:47:03.480 Can you delete stuff? 801 00:47:03.480 --> 00:47:06.040 Oh, you can't. 802 00:47:06.040 --> 00:47:08.200 I'll let him know about that. 803 00:47:08.200 --> 00:47:10.680 So we're actually not going to do any of these things 804 00:47:10.680 --> 00:47:13.480 for this project. 805 00:47:13.480 --> 00:47:16.800 And I said by month here. 806 00:47:16.800 --> 00:47:18.380 There's some security stuff right now. 807 00:47:18.380 --> 00:47:21.000 We have to make sure that this client, if they signed in, 808 00:47:21.740 --> 00:47:24.900 we know which client they're supposed to be associated with. 809 00:47:24.900 --> 00:47:26.140 I can do that. 810 00:47:26.140 --> 00:47:27.820 And then I've got this view by status. 811 00:47:27.820 --> 00:47:32.620 And maybe I'll make this as the project part. 812 00:47:32.620 --> 00:47:34.900 The approve button, so they have to log in. 813 00:47:34.900 --> 00:47:36.580 We can't not let them log in. 814 00:47:40.420 --> 00:47:41.020 So there's two. 815 00:47:41.020 --> 00:47:42.020 There's confirm process. 816 00:47:46.060 --> 00:47:49.620 And so I wouldn't go typically in our heads to this. 817 00:47:49.640 --> 00:47:52.320 But this is better to know that just to make that clarity, 818 00:47:52.320 --> 00:47:53.800 there's a thing here. 819 00:47:53.800 --> 00:47:56.320 We need to put some tasks into this bucket. 820 00:47:56.320 --> 00:48:00.240 What's not in here is, yeah, if you're a client, 821 00:48:00.240 --> 00:48:07.400 then we would have something like if in the whatever it's 822 00:48:07.400 --> 00:48:13.320 like shaping status and client logged in, 823 00:48:13.320 --> 00:48:16.280 then we would show some sort of confirm project button. 824 00:48:19.620 --> 00:48:29.800 So and then this will just go to a whole flow basically 825 00:48:29.800 --> 00:48:32.320 of like confirm project. 826 00:48:32.320 --> 00:48:33.480 I don't know what's in here. 827 00:48:33.480 --> 00:48:34.760 But there's something in here. 828 00:48:34.760 --> 00:48:40.600 And I assume there's a big confirm button, right? 829 00:48:40.600 --> 00:48:42.520 This can be very quick and smooth. 830 00:48:42.520 --> 00:48:43.480 And then that's it. 831 00:48:43.480 --> 00:48:44.900 There's nothing really after that. 832 00:48:44.900 --> 00:48:47.640 It just kind of loops you back to the view. 833 00:48:47.660 --> 00:48:51.980 I think it includes a notion comment. 834 00:48:51.980 --> 00:48:52.780 Yes. 835 00:48:52.780 --> 00:48:54.540 And that would be illustrated here 836 00:48:54.540 --> 00:48:59.140 with like a little gray thing. 837 00:49:07.060 --> 00:49:08.660 I've got to use these words correctly. 838 00:49:08.660 --> 00:49:14.260 Confirmed project on like y date. 839 00:49:14.260 --> 00:49:16.580 There's my cue. 840 00:49:17.440 --> 00:49:17.960 Cool. 841 00:49:17.960 --> 00:49:20.320 So we'll have something like this happens. 842 00:49:20.320 --> 00:49:20.840 I don't know. 843 00:49:20.840 --> 00:49:21.520 We probably have some other things 844 00:49:21.520 --> 00:49:22.840 we want to do in the database. 845 00:49:22.840 --> 00:49:24.640 And it updates the status, obviously. 846 00:49:27.800 --> 00:49:31.040 We'll like update notion status, et cetera. 847 00:49:31.040 --> 00:49:32.800 So you guys get the idea. 848 00:49:32.800 --> 00:49:34.680 But just breaking this into a little piece, 849 00:49:34.680 --> 00:49:37.360 we can kind of see what's going to happen in the database. 850 00:49:37.360 --> 00:49:39.040 So now I could very, very quickly add 851 00:49:39.040 --> 00:49:43.520 like this needs to send comment to notion. 852 00:49:43.540 --> 00:49:48.460 This needs to change status in notion and a few other things. 853 00:49:48.460 --> 00:49:50.500 So I can keep going on this. 854 00:49:50.500 --> 00:49:51.740 But you guys get the idea. 855 00:49:51.740 --> 00:49:53.540 I'll keep wrapping it up later today. 856 00:49:53.540 --> 00:49:58.980 And then following our process, I will make a quick video 857 00:49:58.980 --> 00:50:01.020 and share like. 858 00:50:00.000 --> 00:50:01.480 the final breadboard here. 859 00:50:01.480 --> 00:50:02.440 And you guys can follow. 860 00:50:02.440 --> 00:50:05.640 Anyone on the team here can follow the project here. 861 00:50:05.640 --> 00:50:07.400 It's called New. 862 00:50:07.400 --> 00:50:08.880 And I'll keep posting, and you guys 863 00:50:08.880 --> 00:50:11.400 can see the whole history of the conversations here. 864 00:50:11.400 --> 00:50:13.920 So I'll put a new video later today, some links there. 865 00:50:13.920 --> 00:50:16.120 But you guys can all comment and weigh in on it 866 00:50:16.120 --> 00:50:18.320 if you have thoughts. 867 00:50:18.320 --> 00:50:21.800 But I think it's definitely getting really, really clear 868 00:50:21.800 --> 00:50:23.280 of what we're building. 869 00:50:23.280 --> 00:50:24.920 And once that's done, we'll obviously 870 00:50:24.920 --> 00:50:27.000 go and add maybe the team member stuff next. 871 00:50:27.000 --> 00:50:29.360 But cool. 872 00:50:29.640 --> 00:50:30.520 Awesome, guys. 873 00:50:30.520 --> 00:50:31.480 That's awesome. 874 00:50:31.480 --> 00:50:32.200 Closing thoughts? 875 00:50:35.640 --> 00:50:37.280 You're like 50% shaped, right? 876 00:50:37.280 --> 00:50:37.780 Yeah. 877 00:50:37.780 --> 00:50:38.280 Yeah. 878 00:50:38.280 --> 00:50:39.400 We always do. 879 00:50:39.400 --> 00:50:40.200 No, this is good. 880 00:50:40.200 --> 00:50:42.280 Because we always, at the end of it, just be like, 881 00:50:42.280 --> 00:50:43.040 where are we at? 882 00:50:43.040 --> 00:50:44.760 And it's always like, oh, this is awesome. 883 00:50:44.760 --> 00:50:45.600 We're at 90%. 884 00:50:45.600 --> 00:50:47.000 And if you really think about it, 885 00:50:47.000 --> 00:50:49.160 you're like, we're probably like 60. 886 00:50:49.160 --> 00:50:49.960 Lucian says 50. 887 00:50:49.960 --> 00:50:51.920 I'd say 60. 888 00:50:51.920 --> 00:50:53.720 Because we're just used to like, this 889 00:50:53.720 --> 00:50:56.760 feels so much more clear than maybe other projects we've done. 890 00:50:56.800 --> 00:51:00.480 But every time we get something really, really clear, 891 00:51:00.480 --> 00:51:02.760 and we're like, oh, this is the 80-90, now we're like, 892 00:51:02.760 --> 00:51:05.480 OK, that's actually what 80-90%, 100% feels like, 893 00:51:05.480 --> 00:51:07.520 there's just this like, we've kind of ruled out 894 00:51:07.520 --> 00:51:10.080 all the edge cases. 895 00:51:10.080 --> 00:51:11.440 We've answered all the questions. 896 00:51:11.440 --> 00:51:14.000 Now Ryan says you get to this point where you're like, OK, 897 00:51:14.000 --> 00:51:15.680 could you just stop talking about it? 898 00:51:15.680 --> 00:51:16.560 Just let me go build it. 899 00:51:16.560 --> 00:51:17.600 I'm ready to go build it. 900 00:51:17.600 --> 00:51:18.720 Let me start coding. 901 00:51:18.720 --> 00:51:20.040 I know exactly what to go do. 902 00:51:20.040 --> 00:51:22.360 And then you kind of know you've hit it. 903 00:51:22.360 --> 00:51:23.000 We're close. 904 00:51:23.000 --> 00:51:24.560 I think we're close to that. 905 00:51:24.600 --> 00:51:27.280 So awesome, guys. 906 00:51:27.280 --> 00:51:30.720 Well, I hope everybody has a good Christmas. 907 00:51:30.720 --> 00:51:34.680 And I think we'll probably skip next week. 908 00:51:34.680 --> 00:51:37.680 But we'll catch up with you guys soon.