Meeting Title: Default Project Ticket Updates Sync Date: 2026-04-22 Meeting participants: Advait Nandakumar Menon, Demilade Agboola, Brylle Girang, Greg Stoutenburg
WEBVTT
1 00:01:39.540 ⇒ 00:01:40.570 Brylle Girang: Hello!
2 00:01:43.470 ⇒ 00:01:44.849 Advait Nandakumar Menon: Hello, hey guys.
3 00:01:54.290 ⇒ 00:01:55.439 Brylle Girang: How’s it going?
4 00:01:57.110 ⇒ 00:01:59.420 Advait Nandakumar Menon: Going good. How about you?
5 00:02:01.230 ⇒ 00:02:03.589 Brylle Girang: Great. Amazing. How are you, Demi?
6 00:02:09.090 ⇒ 00:02:10.970 Demilade Agboola: I’m doing alright, how’s everyone doing?
7 00:02:13.970 ⇒ 00:02:14.900 Brylle Girang: Amazing.
8 00:02:15.390 ⇒ 00:02:16.810 Brylle Girang: an ecstatic.
9 00:02:16.980 ⇒ 00:02:21.070 Brylle Girang: Does it look like… Looked like it.
10 00:02:22.410 ⇒ 00:02:30.599 Brylle Girang: I am looking at, like, the linear board right now. I guess we need to wait for Greg, but I want to… I wanted to take a look at this.
11 00:02:41.830 ⇒ 00:02:45.120 Brylle Girang: Okay, from one glance, I think,
12 00:02:47.000 ⇒ 00:02:52.060 Brylle Girang: Modeling metrics, definition, post-feedback iteration, okay.
13 00:02:52.060 ⇒ 00:02:57.199 Greg Stoutenburg: I should have gotten logged in, and B would just be getting it done. B delivers.
14 00:02:57.890 ⇒ 00:03:08.619 Brylle Girang: No, I was just looking at this, but this is mostly going to be Debbie and Abby. But I wanted to check here. There are… so the main reason why I’m going to
15 00:03:08.770 ⇒ 00:03:09.520 Brylle Girang: Like…
16 00:03:10.340 ⇒ 00:03:16.029 Brylle Girang: pinpoint at some things here is because this is going to be, like, shown to the client, and I want to make sure that we
17 00:03:16.140 ⇒ 00:03:25.640 Brylle Girang: keep this out of the way and not let them ask questions. So there are stuff here in red, but I don’t think that this is accurate.
18 00:03:25.930 ⇒ 00:03:34.490 Brylle Girang: For example, for the customer success dashboard, we’re done with 2, 3, 4, 5, 1 is red. This shouldn’t be like this, right? This should be completed.
19 00:03:34.490 ⇒ 00:03:46.500 Greg Stoutenburg: Can you help me understand what to do here? So, some of the places where we’ve got a milestone that shows red is a situation where we delivered the dash to spec.
20 00:03:46.700 ⇒ 00:04:01.540 Greg Stoutenburg: And then they gave us feedback and made a request, and the feedback… and the request can’t be executed because of, like, we need access to a system, and the CEO hasn’t given it to us, and we’ve been begging for a month. Like, that kind of thing.
21 00:04:01.540 ⇒ 00:04:13.150 Greg Stoutenburg: So, I don’t know what to do with that for status. I don’t know if that means I should just cancel the ticket, I don’t know… I don’t know what to do. What do we do in that kind of situation? Because linear will show it as blocked or delayed, when really, like.
22 00:04:13.670 ⇒ 00:04:17.479 Greg Stoutenburg: We know the status, but we don’t want to be relying on our memory, we want to be relying on linear.
23 00:04:17.810 ⇒ 00:04:34.130 Brylle Girang: Yeah, yeah, that makes sense. So, let’s just… I’m just going to try to look at the customer success dashboard here. This one is in red, so that means there’s something that we were not able to, like, deliver for the… for this specific dashboard that was blocked by them.
24 00:04:34.370 ⇒ 00:04:37.109 Brylle Girang: I think the best way… sorry, Advait…
25 00:04:37.110 ⇒ 00:04:45.579 Advait Nandakumar Menon: Yeah, for this ticket, I’m working on this right now. Demi has already modeled it, so I’m adding it to the dashboard right now, so maybe this shouldn’t be here.
26 00:04:46.750 ⇒ 00:04:48.720 Greg Stoutenburg: Maybe just mark it as in progress.
27 00:04:49.640 ⇒ 00:04:50.290 Advait Nandakumar Menon: Yeah.
28 00:04:50.440 ⇒ 00:04:51.870 Greg Stoutenburg: If that’s.
29 00:04:51.870 ⇒ 00:04:52.669 Brylle Girang: Yeah, yeah, yeah.
30 00:04:53.210 ⇒ 00:05:03.550 Brylle Girang: this should be in progress, then. So, Avegan, can you… I’m not going to do it, I just want to make sure that we… we practice, like, that muscle memory. Can you make this in progress?
31 00:05:03.980 ⇒ 00:05:04.580 Advait Nandakumar Menon: Sure.
32 00:05:04.580 ⇒ 00:05:05.349 Brylle Girang: Okay, and then…
33 00:05:05.350 ⇒ 00:05:06.110 Greg Stoutenburg: agree.
34 00:05:06.780 ⇒ 00:05:13.680 Brylle Girang: It would be amazing if you could, like, leave a more specific comment here, that this is what… this is what we’re doing, etc. And again.
35 00:05:13.820 ⇒ 00:05:28.869 Brylle Girang: reiterating that the client has access to this linear board, and we want to make sure that the board answers all of their questions, and they’re not going to, like, send it via Slack, and then there’s going to be a lengthy discussion. Sounds good?
36 00:05:29.720 ⇒ 00:05:30.320 Advait Nandakumar Menon: Yep.
37 00:05:30.710 ⇒ 00:05:31.240 Brylle Girang: Okay.
38 00:05:31.650 ⇒ 00:05:49.790 Greg Stoutenburg: Because, yeah, they will be, so I walked Caitlin through this yesterday, and said, the milestones are accurate insofar as, like, these are the dates when we did these things, that’s pretty accurate, but I clarified to her, if you actually click through and look at the issues, you’ll find cases where
39 00:05:49.790 ⇒ 00:05:58.869 Greg Stoutenburg: I did things like, I know that we actually did do this, but I just invented an issue and then marked it done so that you’d see the milestone was completed. So, like, I said, if we need another day.
40 00:05:58.870 ⇒ 00:06:01.460 Greg Stoutenburg: to get this up to date. So that’s where we’re at right now.
41 00:06:01.690 ⇒ 00:06:03.800 Brylle Girang: Okay, and what was their feedback, Greg?
42 00:06:04.090 ⇒ 00:06:11.359 Greg Stoutenburg: She was happy with it. She was happy to see this. Yeah, and… and so, for me, this was… the narrative that I’m pushing is.
43 00:06:11.730 ⇒ 00:06:13.789 Greg Stoutenburg: We are on time.
44 00:06:13.790 ⇒ 00:06:36.229 Greg Stoutenburg: But we need to improve communication and visibility, and so this is an exercise in that. And then the second thing is cases where we’re delayed. The reason why we’re delayed isn’t because we just didn’t get something done on time, it’s because we received feedback after QA with them, where they made a bunch of net new asks, and we didn’t clearly enough, and I say, you know, I personally didn’t clearly enough.
45 00:06:36.260 ⇒ 00:06:41.579 Greg Stoutenburg: Say, this is a net new ask, this is going to take us 4 days,
46 00:06:41.650 ⇒ 00:06:58.390 Greg Stoutenburg: you know, given the allocations for hours we have in this team, this is gonna take us an extra 4 days. So you pick, either your next dashboard is hereby delayed by 4 days, or we revisit this later, after we do the initial pass of whatever’s next, and put that in front of them.
47 00:06:58.390 ⇒ 00:07:03.560 Greg Stoutenburg: I did finally do that on something, a particular request, like, a week ago.
48 00:07:03.810 ⇒ 00:07:16.269 Greg Stoutenburg: And that was well received. But I think, you know, not having… not having had that as a more, consistent approach, has helped bring about this sort of challenge.
49 00:07:17.310 ⇒ 00:07:19.729 Brylle Girang: Okay, okay, that makes sense.
50 00:07:19.850 ⇒ 00:07:21.960 Brylle Girang: With that in mind, I think…
51 00:07:22.180 ⇒ 00:07:34.579 Brylle Girang: I’m just going to, like, think about how we can better visualize it here. Like, after post-feedback iteration, I’m imagining there should be milestones saying that, hey, this is a new ass.
52 00:07:34.780 ⇒ 00:07:38.640 Brylle Girang: Was completed here, here’s the new target date, etc, etc.
53 00:07:38.990 ⇒ 00:07:39.710 Brylle Girang: So…
54 00:07:39.710 ⇒ 00:07:47.289 Greg Stoutenburg: Yeah. I mean, I think, yeah, so the milestones that are in each dashboard make perfect sense. It’s like…
55 00:07:47.500 ⇒ 00:07:53.649 Greg Stoutenburg: It’s like… modeling and spec finished. Version 1 built.
56 00:07:54.090 ⇒ 00:07:57.700 Greg Stoutenburg: Internal QA complete. Review with client.
57 00:07:58.420 ⇒ 00:08:06.490 Greg Stoutenburg: execute on client feedback, and then, like, final sign-off. Like, those stages make perfect sense. And so, I think we just have to…
58 00:08:06.490 ⇒ 00:08:19.419 Greg Stoutenburg: what I… what I want this team to do is… we’ve got a ton of tickets out there already, we just have to assign them to the right milestones, so that… so that we, you know, basically so that this board is accurate. And anything that needs to be marked as done, just, you know, mark it as done.
59 00:08:20.800 ⇒ 00:08:21.330 Brylle Girang: Yeah.
60 00:08:21.820 ⇒ 00:08:24.669 Brylle Girang: Okay, any thoughts there, Demi and Advay?
61 00:08:25.320 ⇒ 00:08:27.030 Brylle Girang: Or is everything clear?
62 00:08:28.870 ⇒ 00:08:31.440 Advait Nandakumar Menon: Oh, so, it’s clear, so I have been…
63 00:08:31.550 ⇒ 00:08:41.879 Advait Nandakumar Menon: Trying to work up a routine to routinely update the tickets. I’ve been doing that, so I think the next thing is just adding it to the right milestone, so yeah, that’s…
64 00:08:42.309 ⇒ 00:08:43.990 Advait Nandakumar Menon: Something to keep in mind.
65 00:08:43.990 ⇒ 00:08:48.569 Greg Stoutenburg: B, can you show how to do that? In case, just for the sake of the team?
66 00:08:48.770 ⇒ 00:08:53.560 Greg Stoutenburg: Yeah. So just, like, find an issue and just put it in a milestone for us.
67 00:08:54.280 ⇒ 00:08:59.620 Brylle Girang: Yeah, for example, I’m working on, like, this issue. You can see that there’s no project.
68 00:08:59.840 ⇒ 00:09:00.590 Brylle Girang: I would…
69 00:09:01.660 ⇒ 00:09:07.370 Brylle Girang: like, assign this to a project, or maybe assign this to a milestone instead? I’m not sure why it’s not loading.
70 00:09:09.650 ⇒ 00:09:10.530 Brylle Girang: That’s weird.
71 00:09:10.530 ⇒ 00:09:12.369 Greg Stoutenburg: Maybe you have to put it in a project first.
72 00:09:15.780 ⇒ 00:09:18.690 Brylle Girang: First step, assign it to project, then set a milestone.
73 00:09:18.690 ⇒ 00:09:20.059 Greg Stoutenburg: There we go.
74 00:09:20.060 ⇒ 00:09:20.590 Brylle Girang: fifth.
75 00:09:21.000 ⇒ 00:09:35.030 Brylle Girang: If I’m… if we’re going to, like, do it manually, that’s going to be that, but, you know, use open code. Like, list down all the… all the issues that are assigned to me, which doesn’t have milestones, assign it to these milestones, etc. That should be a lot faster.
76 00:09:35.990 ⇒ 00:09:36.480 Advait Nandakumar Menon: Okay.
77 00:09:38.950 ⇒ 00:09:40.330 Greg Stoutenburg: Yep, that’ll work.
78 00:09:41.470 ⇒ 00:09:43.980 Demilade Agboola: Also, I just wanted to say that,
79 00:09:44.400 ⇒ 00:09:58.680 Demilade Agboola: some of the work done on this project don’t necessarily have tickets, because, like, sometimes some things are, like, Advait will give me, like, some context on something he’s blocked on, on a ticket, and I will just, like, rip through it and say, like, okay, Advait, you can… I’ll do it now.
80 00:09:59.330 ⇒ 00:10:05.660 Demilade Agboola: That doesn’t involve tickets, but yeah, I’m just… just wanted to point that out as well.
81 00:10:06.060 ⇒ 00:10:06.900 Greg Stoutenburg: Yeah.
82 00:10:06.900 ⇒ 00:10:17.460 Brylle Girang: I think that opportunity here… so… and how is this, like, work being handed off? Is, like, Advait, are you messaging Demi directly and then asking him for things? Is that it?
83 00:10:18.610 ⇒ 00:10:35.470 Advait Nandakumar Menon: Yeah, maybe direct DMs, or, like, direct messages, or just in the channel, I might ask a few things, and he sometimes just models it then and there. Sometimes we create a ticket, or it’s already part of an existing ticket, so… yeah.
84 00:10:36.070 ⇒ 00:10:36.720 Brylle Girang: Okay.
85 00:10:36.860 ⇒ 00:10:37.620 Brylle Girang: Well…
86 00:10:39.160 ⇒ 00:10:48.509 Brylle Girang: I guess, based on your judgment, but what I would say, and what I would argue, is that every time that there’s work that needs to be done, there needs to be a linear ticket created.
87 00:10:48.550 ⇒ 00:11:00.709 Brylle Girang: accordingly, and it should be easy, like, you can still do the same, but an additional step would be, like, tagging linear in the channel, or in your message, and then just say, create a ticket, this should be under default.
88 00:11:00.910 ⇒ 00:11:07.360 Brylle Girang: I think one line shouldn’t be that much of a work, and making sure that it’s properly documented.
89 00:11:08.290 ⇒ 00:11:08.890 Advait Nandakumar Menon: Nope.
90 00:11:08.890 ⇒ 00:11:14.629 Greg Stoutenburg: Hey, hey B, just, given the workflow that the team has been using so far, especially because, like.
91 00:11:14.840 ⇒ 00:11:28.550 Greg Stoutenburg: Demi and Abbey have just been cranking out dashboards. I mean, like, it’s, like, it’s a lot, and there has been a lot of communication around it. Is there a way that we could do something like… or, like, do we have a cursor skill that could do something like, if they use…
92 00:11:28.550 ⇒ 00:11:35.349 Greg Stoutenburg: if they just… if they use certain words in their communication. For example, if they say something explicit, like, you know, if Advait says.
93 00:11:35.350 ⇒ 00:11:41.990 Greg Stoutenburg: Hey, Demi, for the Customer Product Activity Dashboard, have you connected, you know, data source, or something like that?
94 00:11:42.020 ⇒ 00:11:48.159 Greg Stoutenburg: And then, you know, as long as, like, the language we’re using is clear enough, can we do something, like, at the end of the day.
95 00:11:49.090 ⇒ 00:12:01.489 Greg Stoutenburg: you know, AI runs through a bunch of Slack channels that are for default, and proposes, hey, here are linear updates. Yes, you know, here are linear updates I propose, click yes or click no.
96 00:12:01.810 ⇒ 00:12:04.549 Greg Stoutenburg: And then it updates the tickets, like, can we do something like that?
97 00:12:04.890 ⇒ 00:12:21.589 Brylle Girang: Yeah, actually, the current EPA audit skill should already solve that. Part of the step there is making sure that the Slack channels are scanned, and then if there are updates that would relate to a project or a ticket, it should propose you that specific updates.
98 00:12:21.620 ⇒ 00:12:29.559 Brylle Girang: The question here would be who’s going to run it, and who’s going to own that. Is that going to be, like, Demi as the SL, or you, Greg, as the CSO?
99 00:12:29.770 ⇒ 00:12:31.450 Greg Stoutenburg: I think,
100 00:12:32.510 ⇒ 00:12:41.639 Greg Stoutenburg: Yeah, I… I kind of think it makes more sense for Demi to do it, given the level of detail and interaction with the…
101 00:12:41.830 ⇒ 00:12:45.450 Greg Stoutenburg: individual tickets in the dashboard, for the dashboards.
102 00:12:45.770 ⇒ 00:12:46.920 Greg Stoutenburg: What do you think, Demi?
103 00:12:48.160 ⇒ 00:12:51.379 Demilade Agboola: I mean, I could definitely do it,
104 00:12:52.830 ⇒ 00:12:54.950 Demilade Agboola: I will say, though, that, like.
105 00:12:55.400 ⇒ 00:13:01.330 Demilade Agboola: in terms of how I work, sometimes my priority ends up being, like, the actual
106 00:13:02.000 ⇒ 00:13:21.649 Demilade Agboola: modeling. Yeah. That kind of, like, makes me, like, not focus on other things that come up during the day. That being said, part of what the focus is, you know, over the last couple of weeks has been trying to get Mustafa to do more modeling, so I’m trying to, like, push him, like, into more tasks around that, and get him to, like, do it.
107 00:13:21.960 ⇒ 00:13:22.420 Greg Stoutenburg: Yeah.
108 00:13:22.420 ⇒ 00:13:26.290 Demilade Agboola: That should free me up a bit to handle some of these around them.
109 00:13:26.290 ⇒ 00:13:42.319 Greg Stoutenburg: Well, yeah, I mean, what if we did something like… be, like, I mean, what if I created another cursor automation and, and just have it run EP Audit every day at 6 Eastern Time, and, and check the default Slack channels?
110 00:13:42.390 ⇒ 00:13:52.280 Greg Stoutenburg: and propose a bunch of tickets to update, and then, you know, services in Slack, in client default, and then Demi can just click, you know, yes or no on the proposals. Can we do something like that?
111 00:13:52.760 ⇒ 00:13:58.260 Brylle Girang: Yeah, I mean, try it. I think it will work, and if it doesn’t, then let’s try it again. Let’s try another step.
112 00:13:58.450 ⇒ 00:14:00.410 Greg Stoutenburg: Yeah. What do you think about that idea, Demi?
113 00:14:02.710 ⇒ 00:14:06.669 Demilade Agboola: Yeah, I think that’ll be fine. Do we have automation set up?
114 00:14:07.600 ⇒ 00:14:15.790 Greg Stoutenburg: I mean, the thing that runs every day that identifies stale tickets, that’s an automation that I set up, but I could set up an automation for the EP audit
115 00:14:15.930 ⇒ 00:14:23.080 Greg Stoutenburg: And then, you know, if you can help reinforce the discipline on the team of making sure that those milestones are assigned, then…
116 00:14:23.700 ⇒ 00:14:24.700 Greg Stoutenburg: Yeah, that would cut it.
117 00:14:25.480 ⇒ 00:14:26.780 Demilade Agboola: Alright, sounds good then.
118 00:14:27.070 ⇒ 00:14:29.219 Greg Stoutenburg: Cool, alright, we’ll do that, we’ll try that.
119 00:14:29.970 ⇒ 00:14:31.629 Greg Stoutenburg: We’ll try that for a few days, see what we think.
120 00:14:34.740 ⇒ 00:14:36.520 Greg Stoutenburg: Okay,
121 00:14:37.350 ⇒ 00:14:44.359 Greg Stoutenburg: In the meantime, what will it take to get all these tickets updated for the dashboarding projects?
122 00:14:45.000 ⇒ 00:14:45.960 Greg Stoutenburg: No.
123 00:14:46.090 ⇒ 00:14:53.230 Greg Stoutenburg: Does it have to be a manual task, or is it something that we can, you know, be… is there a way that we can just, like, cover this in a single sweep?
124 00:14:54.100 ⇒ 00:14:57.870 Brylle Girang: Yeah, I think this can be covered in a single sweep.
125 00:14:58.040 ⇒ 00:15:16.210 Brylle Girang: again, around the AP audit skill. It’s going to be… it’s going to work really well here. If it doesn’t work, you know, update the skill. If something’s not working for… for the client default specifically, we can update the skill. But I would say there’s no need to, like, go through each ticket and update those.
126 00:15:16.390 ⇒ 00:15:25.119 Brylle Girang: Make open code or cursor, whatever you’re using, give you a summary, the skills that are not updated, update them all at once, etc.
127 00:15:25.620 ⇒ 00:15:29.459 Greg Stoutenburg: Yeah, okay, I’m, I’m gonna do it right now.
128 00:15:33.750 ⇒ 00:15:34.659 Greg Stoutenburg: I think.
129 00:15:38.460 ⇒ 00:15:41.759 Demilade Agboola: On OpenCore, do we have certain models that are disabled?
130 00:15:44.030 ⇒ 00:15:46.180 Brylle Girang: Yes.
131 00:15:46.360 ⇒ 00:15:51.600 Brylle Girang: Actually… so, are you, like, receiving an error that, hey, model’s not available?
132 00:15:52.690 ⇒ 00:16:02.459 Brylle Girang: Okay, thanks for pointing that out. I’m going to create an announcement about that, but yes, there are certain models that are disabled. It’s on me that I was not able to make that clear earlier. But thanks, Debbie.
133 00:16:04.440 ⇒ 00:16:23.459 Brylle Girang: Okay, and then, what else do we need help, Greg? I know that there’s going to be, like, a meeting tomorrow with default. I think we need help when it comes to… we need to focus on making sure that all action items from that is properly documented and clear if they are not new, or updates to new dashboards.
134 00:16:23.770 ⇒ 00:16:26.529 Brylle Girang: Yeah. I might not join that call, I will.
135 00:16:26.530 ⇒ 00:16:26.930 Greg Stoutenburg: will be…
136 00:16:27.170 ⇒ 00:16:28.389 Brylle Girang: Boarding it in.
137 00:16:28.390 ⇒ 00:16:33.030 Greg Stoutenburg: No, what I wanted your help for is what we’ve just been talking about, so…
138 00:16:33.210 ⇒ 00:16:35.350 Greg Stoutenburg: With linear in good shape.
139 00:16:35.360 ⇒ 00:16:55.100 Greg Stoutenburg: I feel fine running, you know, doing the things that we’ve been doing for the last 6 weeks to create the weekly deck, and we can go in with confidence on the work that, you know, exactly what our progress is. And I can show the linear board, go, hey, we updated all those things per your request, here’s where these things are at,
140 00:16:55.500 ⇒ 00:17:01.419 Greg Stoutenburg: And then… and just have the discussion there, and feel like we’re back in the driver’s seat, rather than being dragged around.
141 00:17:02.650 ⇒ 00:17:03.030 Brylle Girang: Okay.
142 00:17:03.030 ⇒ 00:17:08.550 Greg Stoutenburg: So I don’t think… Yeah, so I don’t think I need help on any of that.
143 00:17:09.890 ⇒ 00:17:13.250 Greg Stoutenburg: Yeah, Demi Radvate, anything?
144 00:17:13.930 ⇒ 00:17:15.009 Greg Stoutenburg: That you can think of?
145 00:17:15.339 ⇒ 00:17:16.610 Greg Stoutenburg: We need B’s help?
146 00:17:17.069 ⇒ 00:17:19.590 Greg Stoutenburg: Otherwise, we can just wrap up and get back to work.
147 00:17:20.950 ⇒ 00:17:30.040 Advait Nandakumar Menon: I’m just trying to update one of these tickets, which I think Nandika and, For Monday.
148 00:17:30.180 ⇒ 00:17:45.510 Advait Nandakumar Menon: her name, but yeah, they were providing updates about the BDR dashboard right now in the client’s channel, and Utam just created two tickets for me, or one ticket. I’m just trying to assign a milestone for it. I’m trying to understand which milestone I should.
149 00:17:46.040 ⇒ 00:17:46.390 Greg Stoutenburg: Okay.
150 00:17:46.390 ⇒ 00:17:47.240 Advait Nandakumar Menon: in front of…
151 00:17:47.390 ⇒ 00:17:49.080 Greg Stoutenburg: Can you share your screen so we can look at it?
152 00:17:49.470 ⇒ 00:17:50.110 Advait Nandakumar Menon: Yep.
153 00:18:05.770 ⇒ 00:18:10.430 Greg Stoutenburg: This is one of the things that, utom commented, right?
154 00:18:10.430 ⇒ 00:18:11.050 Advait Nandakumar Menon: Yep.
155 00:18:11.300 ⇒ 00:18:15.859 Greg Stoutenburg: Okay, so for this one, I would mark this as internal review and testing.
156 00:18:17.920 ⇒ 00:18:27.509 Advait Nandakumar Menon: the one Uttam created after we got feedback from them is… I’m talking about, not the feedback he gave before. Like, I’m not talking about the internal QA we were doing.
157 00:18:29.450 ⇒ 00:18:34.650 Greg Stoutenburg: Well, we haven’t showed this to the client yet, so it can’t be… stage…
158 00:18:34.990 ⇒ 00:18:37.850 Greg Stoutenburg: It can’t be Stage 5 feedback.
159 00:18:39.360 ⇒ 00:18:48.300 Demilade Agboola: We have, like, we’ve done it in the default, like, data team channel, so that’s, like, Nautica’s feedback.
160 00:18:48.720 ⇒ 00:18:49.690 Advait Nandakumar Menon: Yeah, yeah.
161 00:18:49.790 ⇒ 00:18:50.430 Demilade Agboola: So it’s…
162 00:18:50.430 ⇒ 00:18:53.139 Greg Stoutenburg: Oh, I’m so… oh, I’m so sorry, Nandica said this.
163 00:18:53.140 ⇒ 00:18:53.980 Advait Nandakumar Menon: Yeah, yeah.
164 00:18:53.980 ⇒ 00:18:56.789 Greg Stoutenburg: Okay, then I would put that… I’d put that at, 5.
165 00:18:57.410 ⇒ 00:18:58.020 Advait Nandakumar Menon: Okay.
166 00:18:58.020 ⇒ 00:19:01.230 Greg Stoutenburg: And we’re just in a kind of funny position right now that,
167 00:19:01.510 ⇒ 00:19:17.529 Greg Stoutenburg: it’s shared, but we haven’t reviewed it. So, yeah, I would put this as one of those things. Basically, if the client asked for it after we made the dashboard, then I think it belongs in post-feedback iteration milestone, regardless of which dashboard we’re working on. I think, conceptually, that’s where we want that to go.
168 00:19:18.100 ⇒ 00:19:19.450 Advait Nandakumar Menon: Okay, I’m going.
169 00:19:20.640 ⇒ 00:19:22.230 Greg Stoutenburg: Do you agree, Demi? Does that sound right?
170 00:19:23.400 ⇒ 00:19:32.839 Demilade Agboola: Yeah, definitely. I think being able to market this way makes it clear, like, how fast we’re able to go through the initial phase, and what’s taking so long. Yeah, yeah.
171 00:19:32.840 ⇒ 00:19:51.869 Greg Stoutenburg: Yeah, and actually, I think this milestone view has already started to pay off, because yesterday, I was able to call out, I said, you know, even though we need to come in and update some of these things more, you’ll see consistently the biggest gap in the timeline is always between we showed you the dashboard, and we delivered on all the things that you asked for. And she was able to see that and be like.
172 00:19:52.150 ⇒ 00:19:53.150 Greg Stoutenburg: That’s helpful.
173 00:19:53.440 ⇒ 00:19:55.040 Demilade Agboola: Yeah, yeah, yeah, definitely.
174 00:19:55.560 ⇒ 00:20:14.049 Demilade Agboola: I think, I think it’s one of those things where, people really don’t understand, like, going from 0 to 80 is the, fast part. That 80% takes a lot of time, because you’re really going into the weeds of everything, and that can easily start to compile.
175 00:20:14.250 ⇒ 00:20:32.669 Greg Stoutenburg: Yeah, no, and that’s good, and I think that that’s helpful because, you know, when we need to go to bat for more hours as well, just for them to understand the significance of their asks and, you know, how much time it’s taking the team to deliver on those things because they’re difficult, I think is good for us as well, and not just their visibility.
176 00:20:34.430 ⇒ 00:20:40.300 Greg Stoutenburg: Alright, I’m gonna eat something in this 10 minutes that I have before the next hour and a half back-to-back, so…
177 00:20:41.470 ⇒ 00:20:42.900 Greg Stoutenburg: See ya. Thanks, guys.
178 00:20:42.900 ⇒ 00:20:43.480 Advait Nandakumar Menon: dealers.
179 00:20:43.480 ⇒ 00:20:44.600 Greg Stoutenburg: Alright, bye.
180 00:20:44.600 ⇒ 00:20:45.280 Advait Nandakumar Menon: Bye-bye.