Meeting Title: US x BF Deprecation Cleanup Sync Date: 2025-06-27 Meeting participants: Zack Gibbs, Amber Lin, Uttam Kumaran
WEBVTT
1 00:02:16.570 ⇒ 00:02:17.560 Amber Lin: Hi Zach!
2 00:02:18.760 ⇒ 00:02:19.970 Zack Gibbs: Hello!
3 00:02:19.970 ⇒ 00:02:24.160 Amber Lin: Hi! We just came from my our company meeting, so Guten will be right here.
4 00:02:48.730 ⇒ 00:02:49.570 Uttam Kumaran: Hey!
5 00:02:51.580 ⇒ 00:02:53.009 Zack Gibbs: Hey? How’s it going.
6 00:02:53.010 ⇒ 00:02:54.130 Uttam Kumaran: Good! How are you?
7 00:02:56.170 ⇒ 00:02:57.380 Zack Gibbs: All right.
8 00:03:00.320 ⇒ 00:03:01.920 Uttam Kumaran: How’s the week back.
9 00:03:03.330 ⇒ 00:03:10.667 Zack Gibbs: Oh, it was me! It’s good! There’s there’s a we have just a lot of lot of irons in the fire kind of across the board.
10 00:03:11.120 ⇒ 00:03:15.794 Zack Gibbs: it’s like a lot of. There’s a lot of desire to get a bunch of stuff done this summer.
11 00:03:16.160 ⇒ 00:03:20.470 Zack Gibbs: and we just have limited limited resourcing to get it done. So.
12 00:03:20.470 ⇒ 00:03:21.020 Uttam Kumaran: Cool.
13 00:03:22.140 ⇒ 00:03:25.899 Uttam Kumaran: Okay, cool. So hopefully, I think today, just wanted to sort of
14 00:03:26.080 ⇒ 00:03:50.990 Uttam Kumaran: basically give you like an overview of like all progress so far. We made a I think we’re sort of at the finish on a lot of the deprecation Cleanup related work that we set out to do. That was pretty expansive. And then, yeah, basically just talk about a couple of options for the next few sprints. And then just see if there’s any changes we want to make. But yeah, maybe amber, I can let you lead. And then.
15 00:03:51.210 ⇒ 00:03:52.700 Uttam Kumaran: however, we want to take this.
16 00:03:57.390 ⇒ 00:04:18.140 Amber Lin: Okay, yeah. So I can give you a quick update on how we’re going and how we plan to move forward. It’s pretty much similar to the video I sent you, but as a high level overview. We are pretty much at the last step of deprecating the either for looker or for redshift.
17 00:04:18.140 ⇒ 00:04:35.929 Amber Lin: And after that it’s optimization work on making these structures more bulletproof for the future. But right now we’re at the last step of okay, making sure that everybody is informed of deprecation decisions and making sure that we don’t
18 00:04:36.330 ⇒ 00:04:38.150 Amber Lin: act without
19 00:04:40.600 ⇒ 00:04:58.050 Amber Lin: having stakeholders know what we’re doing. So that’s on the deprecation side for the refracturing of Dbt. Marts. So we are a cycle and a half away from finishing inventory, and after that we will. We will get started with revenue.
20 00:04:58.390 ⇒ 00:05:10.940 Amber Lin: And if you want more details on how many points are for each project, how fast we complete each sprint, and how we allocate points, each
21 00:05:11.435 ⇒ 00:05:16.910 Amber Lin: each cycle to each person. I can definitely write that up for you as reference.
22 00:05:18.319 ⇒ 00:05:25.809 Zack Gibbs: Yeah, I mean, I don’t think I need a write up right up here, but I so let me just let me just share.
23 00:05:27.230 ⇒ 00:05:28.490 Zack Gibbs: I’ll share my screen.
24 00:05:34.152 ⇒ 00:05:36.270 Zack Gibbs: So when I look at linear
25 00:05:38.570 ⇒ 00:06:07.030 Zack Gibbs: so! And I look at projects when I I view this as being like the Jira epic of you know what are the bundle of stories that are that are associated to, you know in my mind, like the inventory data mark that being finalized and and completed. So if I look at like the Dbt project, is that synonymous with like inventory data, mark completion? Or is it is that different in your in your
26 00:06:08.930 ⇒ 00:06:09.610 Zack Gibbs: okay?
27 00:06:11.857 ⇒ 00:06:14.719 Zack Gibbs: So anything that I see here?
28 00:06:17.010 ⇒ 00:06:23.610 Zack Gibbs: Status, show me the show me the story.
29 00:06:23.610 ⇒ 00:06:24.669 Amber Lin: Up top.
30 00:06:24.940 ⇒ 00:06:29.359 Amber Lin: Yes, go up top. Next to overviews. There’s issues. So click on issues.
31 00:06:29.360 ⇒ 00:06:30.060 Zack Gibbs: Oh, I see!
32 00:06:30.060 ⇒ 00:06:33.110 Amber Lin: That will give you all the tickets in there.
33 00:06:34.200 ⇒ 00:06:38.179 Zack Gibbs: Okay, yeah.
34 00:06:44.160 ⇒ 00:06:55.333 Zack Gibbs: yeah, from my, from my view. And I, you know, I was out for the 2 weeks, and I was kind of coming in, and you know I was trying to get an update from Emily on. You know where things were.
35 00:06:55.730 ⇒ 00:07:17.919 Zack Gibbs: The only thing that I had heard was that the like? Some of the stakeholders didn’t necessarily know where we were. Progress wise. That’s why, you know, I wanted to make sure that we were including, you know, including the stakeholder groups and the communication. I was curious as to like how well attended though the like analyst meetings were on Thursday. And
36 00:07:18.385 ⇒ 00:07:33.504 Zack Gibbs: yeah, I just wanna make sure that we were moving forward with. And there was like a clear end timeframe for the inventory data mart, which you know, was is kind of the most impactful, like revenue is revenues. Next would be next up.
37 00:07:35.540 ⇒ 00:07:38.509 Zack Gibbs: So I think what’s like the analysts.
38 00:07:39.040 ⇒ 00:07:55.481 Zack Gibbs: So let’s get feedback from you guys. The analyst folks like Pk and Felipe and Perry like. Do you think that they are engaged enough in the project so far?
39 00:07:56.210 ⇒ 00:07:58.540 Zack Gibbs: or do you need more engagement out of them?
40 00:07:59.380 ⇒ 00:08:17.620 Uttam Kumaran: Yeah, maybe I’ll give my sort of feedback. I think the 1st sort of 2 weeks we wanted to knock out all of the like deprecation work. So we we kicked off, probably in the first, st like 2, 3 days of the initial cycle. We got a the list of all the Etl, and we’re able to sort of
41 00:08:17.710 ⇒ 00:08:32.660 Uttam Kumaran: go through that and mark those and clear those out. We then work through Dbt, and then work through looker. So really, that’s I think there’s not much for them to do there. A lot of that was with Emily. And I think now we’re basically getting like
42 00:08:32.980 ⇒ 00:08:38.409 Uttam Kumaran: final sign off from them on like, Hey, we’re gonna move these. We want to get your buy in
43 00:08:38.669 ⇒ 00:08:44.609 Uttam Kumaran: and and sort of like, just make sure that if and when there’s any issues they’re bought in, I think, really, they’re
44 00:08:45.310 ⇒ 00:08:51.679 Uttam Kumaran: closer working with them happens now as we’re moving into working on the inventory models. I mean, I think
45 00:08:51.840 ⇒ 00:09:07.249 Uttam Kumaran: that’s where, probably in the 1st 2 weeks we didn’t have much to share with them about like broader progresses. It was all all deprecation related stuff. I think I would probably defer to Amber to talk to you about how that meeting structure is, and if, like we should
46 00:09:07.460 ⇒ 00:09:09.380 Uttam Kumaran: do something more focused.
47 00:09:10.790 ⇒ 00:09:13.574 Uttam Kumaran: Like, with smaller groups.
48 00:09:14.440 ⇒ 00:09:26.639 Uttam Kumaran: or like, yeah, basically, how to weave those folks in. I think, Zach, we did talk about trying to leverage them super heavily for anything in in looker and anything that actually gets passed to the business and reporting. So that’s
49 00:09:26.850 ⇒ 00:09:34.779 Uttam Kumaran: still what what our team is is looking to do but I guess Amber maybe give me a sense of like how those meetings have been going, and
50 00:09:34.960 ⇒ 00:09:37.380 Uttam Kumaran: if we want to make any changes.
51 00:09:38.390 ⇒ 00:10:01.679 Amber Lin: Yeah. So our meetings. We just had our second meeting with them. It happens bi-weekly. So every 2 weeks. And so for the 1st one. It was getting to know each other and introducing them on what we’re doing, where we’ll need their input and how we will affect them. And the second meeting, because they are most affected by looker, and their decisions are the most important. When we come to deprecating
52 00:10:01.680 ⇒ 00:10:25.599 Amber Lin: or archiving looker dashboards. Last meeting was for the stakeholders. That was present, because there was a few that was out of office on or on sick leave for those who are present. We went through all the dashboards that they use and made sure that we got their input on. If they can be deprecated. If there’s additional ones we can consider deprecating, or if there’s ones that they need. So
53 00:10:25.600 ⇒ 00:10:34.770 Amber Lin: the meeting was very productive in the terms of okay, we now know for at least for these people, what we can do on Looker.
54 00:10:35.130 ⇒ 00:10:51.709 Amber Lin: They’re still so for that meeting. My plan is, I still need input from a few other stakeholders. And then, since 2 weeks later we will have been very close to finishing up inventory, and that will be a good chance to
55 00:10:51.710 ⇒ 00:11:09.500 Amber Lin: go in and inform every person. Okay, these are the changes. What will impact you? What you might need to change, or what might get delayed? To make sure that everybody has a idea of things that our inventory work will be impacting them on.
56 00:11:12.016 ⇒ 00:11:12.713 Zack Gibbs: Okay?
57 00:11:13.930 ⇒ 00:11:25.931 Zack Gibbs: I mean, we have. So just to make sure that we’re we’re aligned the all the analyst teams that whether they’re on marketing or forecasting, demand, planning
58 00:11:26.700 ⇒ 00:11:42.010 Zack Gibbs: care. All of their managers have agreed like any time that we need of theirs we should have. And so, if they’re if you’re if we need more time with them, like, let’s make sure that we we book that it’s a little, I guess I’m a
59 00:11:42.120 ⇒ 00:11:52.140 Zack Gibbs: based on how I know the culture. Internally, my concern is if we, if we come 2 weeks from now and say, here’s all of the impacts of inventory changes. You know.
60 00:11:52.520 ⇒ 00:11:54.129 Zack Gibbs: you guys have to deal with them like.
61 00:11:54.130 ⇒ 00:11:54.840 Uttam Kumaran: Yes, I.
62 00:11:54.840 ⇒ 00:12:17.660 Zack Gibbs: That concerns me. High level like we should it we should be taking their time now. Make sure that they are included on like the working, there’s working sessions. Or if there’s proposed model changes like that way that that way, we’re we are working on the change management earlier and that they’re at least included and kinda understand the context behind the changes. I wouldn’t. I I think that we would.
63 00:12:17.710 ⇒ 00:12:25.970 Zack Gibbs: You know there would be some like back and forth internally if we were to present to them in 2 2 weeks. Here’s all the changes and sorry like. I don’t want that to happen.
64 00:12:26.200 ⇒ 00:12:26.760 Uttam Kumaran: Oh!
65 00:12:27.230 ⇒ 00:12:27.960 Zack Gibbs: So I think that.
66 00:12:27.960 ⇒ 00:12:48.779 Amber Lin: That makes sense, I think, for that, since now we’re doing every 2 weeks, I think we can do every weekly, and I use part of the time to update them on the current progress. And for anyone that’s directly related to the stuff we’re doing, we should book a direct working session with them, because not everybody is related to the inventory mark that we’re working with.
67 00:12:49.790 ⇒ 00:12:50.360 Zack Gibbs: Yeah.
68 00:12:50.360 ⇒ 00:12:51.549 Uttam Kumaran: Yeah. So I think that
69 00:12:51.670 ⇒ 00:12:58.930 Uttam Kumaran: the sessions that probably Demote and and Emily are doing, or Kyle and Emily are doing on inventory. We should just include that person?
70 00:12:59.384 ⇒ 00:13:04.340 Uttam Kumaran: Or, again, we should. We should basically map out who is the sign off.
71 00:13:04.630 ⇒ 00:13:06.949 Uttam Kumaran: And then that person we get buy in
72 00:13:07.350 ⇒ 00:13:12.379 Uttam Kumaran: like before the 2 weeks, or on a more frequent basis. While we’re going through each section.
73 00:13:18.210 ⇒ 00:13:18.890 Zack Gibbs: Yeah.
74 00:13:20.350 ⇒ 00:13:27.400 Uttam Kumaran: I don’t know if it has to be weekly with the whole crew, amber, but I think, while we’re in inventory mode for the next 2 sprints or so.
75 00:13:27.500 ⇒ 00:13:30.380 Uttam Kumaran: It should be weekly with that inventory person.
76 00:13:32.620 ⇒ 00:13:37.169 Uttam Kumaran: You know, and or that inventory person can attend our stand ups. They’re not that bad
77 00:13:38.950 ⇒ 00:13:44.749 Uttam Kumaran: and I think that’s that’s how I would do it. The the 2 week thing. I think it’s so helpful to just
78 00:13:44.970 ⇒ 00:13:49.010 Uttam Kumaran: continue to build rapport and share broadly. Especially, we’ll be presenting
79 00:13:49.230 ⇒ 00:14:01.810 Uttam Kumaran: pretty core Dvt changes, and we can field questions about looker or whatever you know, because partly they are sort of our our stakeholders as well. But I do think that while we are in inventory.
80 00:14:02.190 ⇒ 00:14:08.949 Uttam Kumaran: that whoever the one or 2 people that are really core to that need to basically be side by side as much as possible.
81 00:14:09.544 ⇒ 00:14:12.719 Uttam Kumaran: At least we should try to talk to them once a week.
82 00:14:13.980 ⇒ 00:14:14.450 Amber Lin: Yeah, it.
83 00:14:14.712 ⇒ 00:14:20.750 Uttam Kumaran: Max, they should join any sort of logic working sessions, or at least be in slack where we can run it by them.
84 00:14:20.750 ⇒ 00:14:21.980 Amber Lin: Okay, so.
85 00:14:21.980 ⇒ 00:14:28.350 Uttam Kumaran: Rotate off and start using it. They’ll they’ll be able to start doing the Qa work that I think we would have had to basically.
86 00:14:28.880 ⇒ 00:14:30.099 Uttam Kumaran: Anyways, you know.
87 00:14:30.490 ⇒ 00:14:45.880 Amber Lin: Okay. So I will include, first, st I’ll include Felipe and Perry in slack second, when we book working sessions. I’ll ask Emily if this relates to Felipe Perry, and we’ll include them. And then
88 00:14:46.120 ⇒ 00:14:52.860 Amber Lin: we I will include them in anything related to Qa or sign offs
89 00:14:53.292 ⇒ 00:15:03.389 Amber Lin: even if they don’t do the Pr review or check the quality, they will when they see the thing they will know. Okay, this might affect my work, and they have, they might have something to say.
90 00:15:05.100 ⇒ 00:15:16.300 Zack Gibbs: Yeah, I mean the core, the core analyst group, that we want them to be more self sufficient and have good context as a part of this engagement are Felipe Perry.
91 00:15:20.145 ⇒ 00:15:21.150 Zack Gibbs: Jesse
92 00:15:21.500 ⇒ 00:15:34.970 Zack Gibbs: and Pk, those are the 4 i i feel like they should just be included on most things. Because the other ones like Wilder, you know. Wilder Jessica Campbell.
93 00:15:37.695 ⇒ 00:15:43.644 Zack Gibbs: Santiago like they’re they are more very. They’re more like niche focused
94 00:15:44.140 ⇒ 00:15:44.590 Amber Lin: I’m not.
95 00:15:44.590 ⇒ 00:15:47.857 Zack Gibbs: And so like inventory cuts across lots of things.
96 00:15:48.680 ⇒ 00:15:59.234 Zack Gibbs: so I feel like those 4. We should just have them be required on most things because we want them to have the context of any of the changes. And we wanna get their buy in
97 00:15:59.880 ⇒ 00:16:05.880 Uttam Kumaran: So amber. One thing I would also suggest is leave the existing channel as just our data channel.
98 00:16:06.040 ⇒ 00:16:12.529 Uttam Kumaran: And I, my suggestion was to just create one related to inventory and include them there.
99 00:16:13.140 ⇒ 00:16:13.640 Amber Lin: No.
100 00:16:13.945 ⇒ 00:16:26.760 Uttam Kumaran: So that we can have inventory related questions there, the data channel. We’re gonna use internal our team, and also for like firefighting. So I don’t wanna have like a hundred. It’s gonna end up with like a hundred people in there.
101 00:16:26.760 ⇒ 00:16:27.260 Amber Lin: Valid.
102 00:16:27.554 ⇒ 00:16:35.219 Uttam Kumaran: I try to want to have some. If we can isolate the domain, and if it is inventory, let’s see, let’s create one channel with just
103 00:16:35.670 ⇒ 00:16:41.469 Uttam Kumaran: us and and the folks the analyst from inventory to just have for any sort of inventory data modeling related work.
104 00:16:41.928 ⇒ 00:16:50.290 Uttam Kumaran: The other thing is, I would I would try to isolate what dashboards we need to move to the new model, or what dashboards they need to create.
105 00:16:50.530 ⇒ 00:16:56.629 Uttam Kumaran: And 3, rd what analysis is currently blocked that way. We have, like very clear like.
106 00:16:57.100 ⇒ 00:17:12.249 Uttam Kumaran: By the end of this work they are able to go do this dashboard now. Right that way. There they have. Otherwise they may continue to sort of say, I want to see this over here. I would like to see this like we can have a really concrete goal.
107 00:17:13.589 ⇒ 00:17:20.859 Uttam Kumaran: and they will constantly try to attempt to do that. And then we’re missing a column we’re missing and join. We’ll work through that.
108 00:17:20.959 ⇒ 00:17:25.179 Uttam Kumaran: So it gives us, like a concrete, 2 or 3 sort of solutions to enable.
109 00:17:26.099 ⇒ 00:17:29.560 Amber Lin: Okay. Great. Yeah, I will. That will be really helpful.
110 00:17:29.560 ⇒ 00:17:36.449 Uttam Kumaran: And again, they’re gonna own everything looker and beyond. So they’re gonna get questioned
111 00:17:36.930 ⇒ 00:17:56.449 Uttam Kumaran: first, st like, what does this mean? What does this mean? So part of it is also like I don’t know how trained the analysts are. And okay, where to go into Github to go see the SQL. Logic, right like how to do basic debugging that stuff. I think spending time with Demalana and Kyle in those working sessions will help them fish for themselves a little bit.
112 00:17:57.230 ⇒ 00:18:02.110 Uttam Kumaran: Like, Okay, here’s go into the explorer, find the table. Okay, go to Github to see the logic.
113 00:18:02.570 ⇒ 00:18:04.650 Uttam Kumaran: or like things like that. You know.
114 00:18:08.190 ⇒ 00:18:09.589 Amber Lin: Yeah. And
115 00:18:09.820 ⇒ 00:18:21.769 Amber Lin: that could also be an item, because we’ll see more of that, as we include more people as we do revenue as well, that should be a artifact that we produce, as well
116 00:18:22.130 ⇒ 00:18:23.779 Amber Lin: of a training guide.
117 00:18:26.520 ⇒ 00:18:27.200 Uttam Kumaran: Yes.
118 00:18:29.940 ⇒ 00:18:34.320 Amber Lin: Okay, I wrote a few things down. Send you guys the list later.
119 00:18:35.800 ⇒ 00:18:56.793 Zack Gibbs: And then how’s it? How’s it generally going with Emily being? She’s kind of the point person I I’ve got? There’s a whole bunch of other initiatives that I’m like trying to drive forward. And so I’ve been less. I’ve been gone last 2 weeks. But I’m also I’m gonna join as much as I possibly can. And so like, how’s it going with Emily? And like, where do? Where can I help?
120 00:18:57.220 ⇒ 00:18:59.000 Zack Gibbs: you guys push things forward.
121 00:18:59.939 ⇒ 00:19:16.119 Amber Lin: Emily’s very. She’s very good to work with. She’s also responsible. The only thing is that one she gets overwhelmed with other work, which is this is an inevitable as her job and 2
122 00:19:16.180 ⇒ 00:19:33.280 Amber Lin: because there’s so much things going on she can. Her mind can go between different things and get sidetracked. But that’s not. That’s not a problem. It’s just a working style. And because we have more defined structures right now, we can guide that forward.
123 00:19:34.800 ⇒ 00:19:37.649 Uttam Kumaran: Yeah, I think part of it is like, I kind of want to.
124 00:19:38.408 ⇒ 00:19:58.119 Uttam Kumaran: Replace some of our reliance on Emily with some of the analysts amber like they, although they may not have the Dbt context, they have the business context just as good as Emily has. So Zack, hearing from you that we do have their time. That’s helpful. I sort of didn’t know exactly what their sort of bandwidth was, so
125 00:19:58.310 ⇒ 00:20:10.390 Uttam Kumaran: that’s sort of amber, I think a really good opportunity for us to sort of spread the wealth there. It’s still really crucial that Emily understands like deeper than any of them the Dbt mechanics. But like
126 00:20:10.630 ⇒ 00:20:19.968 Uttam Kumaran: the same, the business logic. I think there is like a game of telephone now between Emily and them. So we should just in. We should just get in there.
127 00:20:21.170 ⇒ 00:20:42.230 Uttam Kumaran: That’ll take some pressure off of her as well. And we’ll start to see also some of the I think the problems that are coming onto Emily’s plate, whether those are truly like Dbt model changes or like. It’s a definition problem. And like that, that I think I want to see if we can partly solve just by getting in the loop and saying, like helping some of the analysts.
128 00:20:42.370 ⇒ 00:20:47.539 Uttam Kumaran: oh, here’s how you can go diagnose and maybe get us like a little bit more information before we triage and execute
129 00:20:48.350 ⇒ 00:20:48.900 Zack Gibbs: Yeah.
130 00:20:49.100 ⇒ 00:20:49.760 Uttam Kumaran: Yeah.
131 00:20:50.120 ⇒ 00:20:50.790 Zack Gibbs: Yes.
132 00:20:50.790 ⇒ 00:21:16.650 Zack Gibbs: definitely. My goal. My goal is is to not, you know, I don’t want to go to this project and then be very single threaded with Emily, knowing lots like having all the context, and then something you know, she leaves or does something different, or you know, and then we’re we have a big hole like, I don’t want that either. So as a part of this, I absolutely want the that core group of Jesse Perry, Pk. And Felipe to know what’s going on. They may not have help, you know the Dvt stuff could be, you know.
133 00:21:16.650 ⇒ 00:21:22.829 Uttam Kumaran: Is anyone in that group like more technical like, would you say, than another like, Is there one person or 2 people that are like, okay.
134 00:21:23.090 ⇒ 00:21:36.540 Zack Gibbs: Yeah. Pk, pk, has his newer a newer addition. He’s on the like marketing team, but he has python skills, and like he, he is a he is somebody that that we should like focus on leveling up as a part of this.
135 00:21:36.540 ⇒ 00:21:37.230 Uttam Kumaran: Okay.
136 00:21:37.230 ⇒ 00:21:38.280 Uttam Kumaran: Okay. Okay.
137 00:21:38.410 ⇒ 00:21:39.559 Amber Lin: Good to know.
138 00:21:40.137 ⇒ 00:21:53.020 Amber Lin: Especially with revenue coming up. We do have a lot of stuff we want business definitions on. It’s great to know that we can go directly to the stakeholders. And also on I know
139 00:21:53.260 ⇒ 00:22:05.390 Amber Lin: not. Wanting Emily to be. The bottleneck is a is a concern, and we do have everything documented. So having that also helps anyone who wants to get on boarded to know what’s going on.
140 00:22:06.770 ⇒ 00:22:09.999 Uttam Kumaran: Yeah, I think part of this amber, too, is. And this is where like.
141 00:22:10.140 ⇒ 00:22:33.839 Uttam Kumaran: it’s just a constant struggle with sort of tech debt. But I what the moment we leave inventory world, it’s gonna be a brain drain of a lot of the discussion that we’re having. So I really want to find a way to make sure that there are in line comments in the core logic. And so this is something, I think. Just make sure to press the engineers on that like when they’re making Prs like really try to push for comments. We really
142 00:22:34.080 ⇒ 00:22:41.909 Uttam Kumaran: should take at least like one day per sprint to do like core documentation in the data platform. Doc.
143 00:22:42.100 ⇒ 00:22:56.979 Uttam Kumaran: it’s we’re gonna really kick ourselves. If if we don’t sort of prioritize that. But it’s not something they’re gonna want to do like that’s not that’s not gonna be like top of their mind. So really press for that. Especially, I would say
144 00:22:57.660 ⇒ 00:23:17.150 Uttam Kumaran: the inline comments. If the and this is maybe something we can talk to them a lot about as part of our Pr review process but to enable people to do that. As you can tell. Now, the code is, gonna sit there for a while, and so we want subsequent folks that come and interact with it, to really be able to understand what’s going on.
145 00:23:17.784 ⇒ 00:23:23.099 Uttam Kumaran: Like, we may lose our spreadsheet, you know, in 2 or 3 years. But like.
146 00:23:23.320 ⇒ 00:23:29.670 Uttam Kumaran: If it’s in the code, it’s really gonna be cemented there. So I that’s my would be my suggestion is
147 00:23:30.026 ⇒ 00:23:33.919 Uttam Kumaran: to see how we can carve out a little bit of stuff for for that sort of work.
148 00:23:35.330 ⇒ 00:23:37.440 Amber Lin: Okay, yeah, that’s great to hear.
149 00:23:40.940 ⇒ 00:23:57.690 Uttam Kumaran: Cool. So I think that probably overall we’re, you know, I I wanna make sure that we really hit inventory hard and that we go through these. I I sort of. I think we have some tickets for revenue as well. But like part of this is sort of biting off what we can take on. And and especially
150 00:23:58.000 ⇒ 00:24:03.029 Uttam Kumaran: I really now, hearing what you said, want to make sure that those the analysts are like
151 00:24:03.410 ⇒ 00:24:05.979 Uttam Kumaran: they’re really on the hook and that they are.
152 00:24:06.270 ⇒ 00:24:13.160 Uttam Kumaran: They’re gonna start to build that with us. I don’t know. I do. They do. They have like sort of dashboard tickets
153 00:24:13.650 ⇒ 00:24:14.510 Uttam Kumaran: like.
154 00:24:15.170 ⇒ 00:24:19.840 Zack Gibbs: And there’s for Emily. I’m not. I’m not sure. I mean.
155 00:24:19.840 ⇒ 00:24:21.379 Uttam Kumaran: Like analysis, sort of work.
156 00:24:22.070 ⇒ 00:24:51.650 Zack Gibbs: They? They don’t have any like. They’re not doing anything in Jira. They their interaction with our team and Emily is through our like Asana tickets. So like we have tech request forms anything anything that is a like, I need something. Goes through that that forum. And so they’re tracking tickets in there. But you know they’re they’re not. Maybe they have their own, like Asana project boards. Who use Asana.
157 00:24:51.650 ⇒ 00:24:53.320 Uttam Kumaran: Probably. Ad, hoc, yeah.
158 00:24:53.520 ⇒ 00:24:56.701 Zack Gibbs: Yeah, it’s so. I doubt they have much structure there.
159 00:24:57.020 ⇒ 00:25:07.330 Uttam Kumaran: So maybe amber. One thing that could be helpful is like, yeah, when we agree on like, Hey, we’re trying to overhaul a dashboard or create a new dashboard. Just create those placeholder tickets
160 00:25:07.700 ⇒ 00:25:08.460 Uttam Kumaran: for them.
161 00:25:08.820 ⇒ 00:25:19.119 Uttam Kumaran: With the requirements. Then we we can sort of continue to know. And for even for Kyle and demalade, they’ll, they’ll ask, is like, what are we? What is sort of building towards
162 00:25:20.690 ⇒ 00:25:31.339 Uttam Kumaran: like? They can create that in this in anywhere. But I just wanna make sure that we sort of go through at least like having like. Okay, there’s a 2 or 3 deliverables that hit the business.
163 00:25:31.510 ⇒ 00:25:46.269 Uttam Kumaran: not just getting Dbt models out, because without those putting constraints on. We’re never going to get the Dbt models right the 1st try. So those force us to sort of do a couple of passes once we get the course of them.
164 00:25:46.340 ⇒ 00:26:04.450 Uttam Kumaran: So that’ll be. My suggestion is when we meet with them. See if we can agree on like, Hey, this staff, this dashboard is out of date. It needs to move over to new models. Cool. There’s 1 ticket there. Second, we wanted to create a dashboard around this concept. Great 3.rd We wanted to enable this analysis that we haven’t been able to do great. So those are just like and don’t go. Don’t go like
165 00:26:04.970 ⇒ 00:26:13.670 Uttam Kumaran: we’re not trying to project, manage all that, but just get like 3 clear things that this work would enable. And we’ll that’s what we’re driving towards.
166 00:26:14.950 ⇒ 00:26:31.560 Amber Lin: great. I think I’ll I’ll book a ticket book a meeting between on us and those folks to get those requirements down before and before that meeting I’ll get the team to prepare of what? What we think, what will be affected. So we have something to discuss.
167 00:26:32.070 ⇒ 00:26:32.750 Uttam Kumaran: Okay.
168 00:26:34.150 ⇒ 00:26:45.110 Zack Gibbs: Yeah. And and like, I said, if we have their their like managerial support of, they are allocated to this, if we need them. So like feel free to.
169 00:26:45.320 ⇒ 00:26:49.820 Zack Gibbs: you know. Use their time. And if you’re not getting that, let me know, and I’ll I’ll make sure that.
170 00:26:50.200 ⇒ 00:26:50.880 Zack Gibbs: Oh.
171 00:26:50.880 ⇒ 00:26:51.520 Uttam Kumaran: Okay?
172 00:26:51.930 ⇒ 00:26:56.589 Uttam Kumaran: And then I guess, Zach, for you like, what do you like? How do you feel about the cadence? So far, I mean
173 00:26:56.860 ⇒ 00:27:09.130 Uttam Kumaran: like would you prefer like? I think the I I think the looms are like I was like, I know Zach is Super busy to send an overview loom, and you know, I’m sure you’ll watch. It. Is that still beneficial? We can try to continue to do that.
174 00:27:09.740 ⇒ 00:27:17.235 Zack Gibbs: Yeah, I don’t. I? As long as I’m around I don’t need. I don’t need extra stuff. I think it was helpful for me to see it, because I was out for 2 weeks. But
175 00:27:17.450 ⇒ 00:27:18.050 Uttam Kumaran: Okay.
176 00:27:18.050 ⇒ 00:27:29.379 Zack Gibbs: Yeah, I’m gonna I’m gonna still try to join a lot of the things as I as I can, so I don’t. I don’t need that now. Don’t feel like you have to create it going forward. If if I feel that way, then I’ll reach out and ask.
177 00:27:29.380 ⇒ 00:27:30.020 Uttam Kumaran: Okay.
178 00:27:30.930 ⇒ 00:27:31.640 Amber Lin: Okay.
179 00:27:33.780 ⇒ 00:27:34.360 Amber Lin: Awesome.
180 00:27:34.360 ⇒ 00:27:39.549 Uttam Kumaran: Oh, so I think next week, Amber like, yeah, I want to see. I mean, I’m I guess, like, this is where I’m a little bit like
181 00:27:40.520 ⇒ 00:27:45.721 Uttam Kumaran: I get a little bit hesitant about like when we do these sort of mass deprecations just because
182 00:27:46.580 ⇒ 00:27:56.758 Uttam Kumaran: like, I don’t want to lose anything. So we are trying our best to archive and like sort of keep things, so that in case they’re like, Oh, I pulled this report 3 months ago, like, Where is that?
183 00:27:57.210 ⇒ 00:28:07.099 Uttam Kumaran: But like as any migrations go like there is there, there will be some issues. So I’m trying to prioritize a team to do any changes early in the week. And then also, we’ve
184 00:28:07.220 ⇒ 00:28:26.100 Uttam Kumaran: basically tried to share with everybody like as much as possible. So at least that gives us something, but we’re not deleting anything. Every everything is trying to basically go in archive or getting commented out. So it’s easy to revert but it’s been quite dramatic, like, there’s it’s like tons and tons of stuff.
185 00:28:26.767 ⇒ 00:28:30.940 Uttam Kumaran: Yeah, so it’s a it’s a it’s a big win.
186 00:28:31.920 ⇒ 00:28:48.430 Zack Gibbs: Yeah, I mean, I want, I want us to start making changes and breaking stuff and figuring it out like, that’s I want us to move forward, and there’ll be things that come out of the woodworks, and that’s completely fine and expected. So as long as we can revert in in areas. Then, you know.
187 00:28:48.730 ⇒ 00:28:58.419 Zack Gibbs: I would rather we make changes, make deeper cuts and then see what happens. Personally, because I think that we need that because we have a so much, so much legacy garbage.
188 00:28:58.660 ⇒ 00:29:03.916 Uttam Kumaran: Yeah, okay, okay, Amber, there’s a green light. So.
189 00:29:04.960 ⇒ 00:29:12.935 Zack Gibbs: And I’ve told, I’ve told, like the leadership group that like they know my approach, which is like, let’s let’s make big changes, and then we’ll see what happens.
190 00:29:13.210 ⇒ 00:29:13.740 Uttam Kumaran: Yeah.
191 00:29:13.986 ⇒ 00:29:22.104 Zack Gibbs: And so like, nobody is concerned about that. If if there’s downstream impacts and things come out of the works, and then we have to, you know, revert some stuff, and that’s fine.
192 00:29:22.530 ⇒ 00:29:23.110 Uttam Kumaran: Okay.
193 00:29:23.110 ⇒ 00:29:28.079 Zack Gibbs: I’m on the hook there like I’ve told them. This is how this is, what’s what should be happening. So.
194 00:29:28.080 ⇒ 00:29:30.560 Uttam Kumaran: Okay, cool. So yeah, I think. And also, like the
195 00:29:30.780 ⇒ 00:29:42.053 Uttam Kumaran: the impacts are, gonna be like, quite big, like, there’s quite a bit of content and stuff. We’re moving around. So I think it’ll this is a huge win. I mean, I don’t think it’s been a while. So we worked on like
196 00:29:42.410 ⇒ 00:29:47.350 Uttam Kumaran: sort of deprecation initiative like this big where there’s been this many pieces across
197 00:29:47.480 ⇒ 00:29:52.540 Uttam Kumaran: the warehouse, the bi tool and then the Etl. So
198 00:29:53.040 ⇒ 00:29:58.130 Uttam Kumaran: like it should just be a huge tax on any data work that happens from here on out. So.
199 00:29:58.890 ⇒ 00:29:59.650 Zack Gibbs: Yep.
200 00:29:59.650 ⇒ 00:30:00.240 Uttam Kumaran: Cool.
201 00:30:00.590 ⇒ 00:30:01.940 Uttam Kumaran: Okay. Great.
202 00:30:04.550 ⇒ 00:30:05.480 Zack Gibbs: Alright, cool, anything else.
203 00:30:08.370 ⇒ 00:30:09.200 Uttam Kumaran: Perfect.
204 00:30:10.430 ⇒ 00:30:11.170 Amber Lin: That’s all.
205 00:30:11.170 ⇒ 00:30:11.850 Uttam Kumaran: Okay?
206 00:30:12.380 ⇒ 00:30:14.540 Uttam Kumaran: Well, have a good weekend. Appreciate the time.
207 00:30:14.960 ⇒ 00:30:16.549 Zack Gibbs: Yep, you as well appreciate it.
208 00:30:16.550 ⇒ 00:30:18.560 Amber Lin: Yeah, exactly. See you next week.
209 00:30:18.710 ⇒ 00:30:19.580 Amber Lin: Bye.