Meeting Title: Javvy Standup Date: 2025-03-13 Meeting participants: Uttam Kumaran, Steven, Robert Tseng, Awaish Kumar, Caio Velasco
WEBVTT
1 00:00:46.210 ⇒ 00:00:47.280 Uttam Kumaran: Hey! Steven.
2 00:00:47.280 ⇒ 00:00:48.809 steven: Hey? Can you hear me? I don’t know.
3 00:00:48.810 ⇒ 00:00:49.330 Uttam Kumaran: Yes.
4 00:00:49.330 ⇒ 00:00:50.060 steven: Okay.
5 00:00:54.740 ⇒ 00:01:08.849 Uttam Kumaran: Yeah, I think, for you know, for Eden, for Javi. I think the biggest thing that would be huge help, probably both for Robert and for the team is just to get stuff in linear. So I think that’ll be a good. That’ll be a good goal for coming into next week.
6 00:01:09.370 ⇒ 00:01:17.289 Uttam Kumaran: You know. I also sent a note in the in the Project management channel a little bit about our our conversation.
7 00:01:18.760 ⇒ 00:01:21.520 Uttam Kumaran: Like our our Ae team conversation today.
8 00:01:24.398 ⇒ 00:01:35.330 Uttam Kumaran: and I think it was. It was really really good. And I, you know, I sent a note in the Project management channel about, you know, setting those expectations and things like that. So we’re getting on the right track. I think, even just
9 00:01:35.730 ⇒ 00:01:40.670 Uttam Kumaran: for today, just being able to go through all of the what’s in flight. And
10 00:01:42.110 ⇒ 00:01:44.629 Uttam Kumaran: you know, start to be able to track, that is, is perfect.
11 00:01:44.850 ⇒ 00:02:02.610 steven: Yeah, I I think so too. And I think would help, too, is like, when I meet with like Akash and Amber, you know, like us figuring out like a universal way, you know, that reflects all clients, because I know it’s like I can put everything in. But then, if I like amber like. Does something.
12 00:02:02.610 ⇒ 00:02:03.130 Uttam Kumaran: Totally.
13 00:02:03.130 ⇒ 00:02:32.020 steven: That’s it. So that’s like one thing. I’m glad we’re gonna connect on. But that’s why, like, before, I hopped off yesterday, I was like here’s what I’m doing. If you want to mirror it so we’ll see. We’ll see how that goes. But yeah, I think like once that’s in. It’ll kind of just like pop everything in, and we’ll kind of go from there, too, and I know a cautious kind of putting some stuff with even in. So I’ll I’ll I’ll need to reach out to him as well, just to make sure we’re good. But yeah, I already I already had a few things moving and grooving with the task list from our last meeting. But yeah, I’ll kind of finish the rest out.
14 00:02:32.380 ⇒ 00:02:42.069 Uttam Kumaran: So for this meeting, I think, like, I mean, I think we could do something really really similar, like, what’s the best way like do do, should I? Should we should? Me and Kyle just go through like
15 00:02:42.250 ⇒ 00:02:45.759 Uttam Kumaran: what’s on the plate? And are you want to take notes like? Should we
16 00:02:45.940 ⇒ 00:02:48.520 Uttam Kumaran: write it together like what’s helpful.
17 00:02:49.030 ⇒ 00:02:56.145 steven: Yeah. So I think, going through and seeing what we’re currently working on and what we
18 00:02:56.810 ⇒ 00:03:04.149 steven: maybe it doesn’t have to be so long term, perhaps, but maybe just like what we’re working on, I guess, because these are daily correct.
19 00:03:04.720 ⇒ 00:03:17.490 Uttam Kumaran: Yes, these are daily. And and I’ll actually, you know, for both of these meetings, I will actually transfer both of them to you, and actually let you decide on how to run whatever process the Pm team wants to run.
20 00:03:18.120 ⇒ 00:03:20.919 Uttam Kumaran: So that’s another, I think set of expectations that
21 00:03:21.180 ⇒ 00:03:27.099 Uttam Kumaran: probably ask the Pm. Team about is like, do we want to do daily? Stand ups for every client?
22 00:03:27.240 ⇒ 00:03:33.741 Uttam Kumaran: Is it for certain clients? Do you want to do weekly planning. Do we want to do weekly retro? So I don’t think we still agreed yet on that.
23 00:03:34.390 ⇒ 00:03:36.420 Uttam Kumaran: so I would say
24 00:03:36.880 ⇒ 00:03:42.029 Uttam Kumaran: the meeting cadence is is prop more more up to you and and up to the team.
25 00:03:42.380 ⇒ 00:03:49.909 steven: Okay, yeah, that that’s good to know, too. You know, I come from a field where our tasks, you know.
26 00:03:50.300 ⇒ 00:03:54.029 steven: I feel like, take take a bit of time, and I feel like there’s a lot of like
27 00:03:54.220 ⇒ 00:03:58.649 steven: maybe smaller tasks to do bigger tasks here, you know. So I think like.
28 00:03:58.810 ⇒ 00:04:07.323 steven: I guess, like like the more I learned and see the process of everything, I think I got a better understanding of the cadence of how how often it needs to be
29 00:04:07.720 ⇒ 00:04:11.049 steven: But I mean, yeah, for for so daily, I think, like, just like.
30 00:04:11.640 ⇒ 00:04:19.142 steven: I don’t know, I guess, like, in terms of like what’s on the plate. Let’s run through that, and then that’ll even give me an idea of like
31 00:04:19.800 ⇒ 00:04:25.250 steven: you know. Come tomorrow for this. Stand up like, have we
32 00:04:25.350 ⇒ 00:04:27.850 steven: asked enough questions? Have we
33 00:04:28.720 ⇒ 00:04:45.100 steven: like proceeded with everything we’ve completed today to even have a meeting tomorrow? Or is it essentially like, you know, there’s like 3 days of work, like, you know, if you’re if you’re doing that work right like it can just be just like making sure you’re checking in right? So I think.
34 00:04:45.100 ⇒ 00:04:45.670 Uttam Kumaran: Exactly.
35 00:04:45.670 ⇒ 00:04:46.320 steven: Yeah.
36 00:04:46.520 ⇒ 00:04:50.072 Uttam Kumaran: Yeah, I’m in the same exact boat. And we were, you know, we were just talking about this this morning
37 00:04:50.350 ⇒ 00:04:56.250 Uttam Kumaran: where we have team. That’s sort of everywhere. So I actually think, like, I’m not a fan
38 00:04:56.420 ⇒ 00:05:01.809 Uttam Kumaran: I’m not a fan of, I mean like, and this is from my perspective. I’m not a fan of meetings in general, because I’m in too many of them.
39 00:05:01.810 ⇒ 00:05:02.140 steven: Yeah.
40 00:05:02.140 ⇒ 00:05:06.420 Uttam Kumaran: But I do think, I do think that
41 00:05:07.360 ⇒ 00:05:28.449 Uttam Kumaran: daily stand ups. There is something also to building camaraderie with the team, but also again daily can be too frequent, depending on the client. I think there’s always like what is necessary short term, and I think short term for this client as we get organized, maybe daily. But if if we’re coming to daily, stand up and there’s not much updates that should be a clear indication. But again, I want to leave that decision to
42 00:05:29.050 ⇒ 00:05:32.040 Uttam Kumaran: to you and the Pm. Team and and this client team like
43 00:05:32.300 ⇒ 00:05:38.630 Uttam Kumaran: it’s it’s about how you guys work, cause cause. If I set the standard then, and and I’m not doing work, then that’s
44 00:05:38.780 ⇒ 00:05:41.189 Uttam Kumaran: that’s it’s not a good way to do things so.
45 00:05:41.370 ⇒ 00:05:44.669 steven: Yeah, yeah, no, that makes sense. Yeah, I think that’s good. 1st step. So.
46 00:05:46.540 ⇒ 00:05:55.149 Uttam Kumaran: Cool. So I think, like if if you’re taking notes and we can maybe walk through me and Kyle on like, what’s what’s on our plate.
47 00:05:55.150 ⇒ 00:05:55.550 steven: Yeah.
48 00:05:55.550 ⇒ 00:06:01.470 Uttam Kumaran: And a lot of it is here right in slack.
49 00:06:01.720 ⇒ 00:06:06.690 Uttam Kumaran: So I think maybe the the 1st
50 00:06:07.260 ⇒ 00:06:14.670 Uttam Kumaran: one of the biggest items is there is a there is a migration item on moving
51 00:06:15.290 ⇒ 00:06:17.930 Uttam Kumaran: metabase to a new database connection.
52 00:06:19.850 ⇒ 00:06:25.510 Uttam Kumaran: I think, Kyle, we’ve talked about this a little bit, but this is probably will take some time. I don’t know what goes into this.
53 00:06:26.047 ⇒ 00:06:35.070 Uttam Kumaran: But I would say, this is one item here. Another thing, Steven, you can actually go here and and like, I don’t know if you’ve tried this, but you could actually create tickets directly from
54 00:06:35.710 ⇒ 00:06:36.570 Uttam Kumaran: here.
55 00:06:37.040 ⇒ 00:06:39.109 steven: Oh, interesting! I haven’t.
56 00:06:39.110 ⇒ 00:06:48.560 Uttam Kumaran: If you right, click this, and maybe it’s helpful to do while we’re walking through this right click. Here, go to more message shortcuts. I also think you could do slash
57 00:06:48.680 ⇒ 00:06:52.579 Uttam Kumaran: linear, and it’ll just open up a ticket.
58 00:06:52.950 ⇒ 00:06:55.789 steven: Oh, I see. I see some more slack shortcuts
59 00:06:56.550 ⇒ 00:06:58.650 steven: and then linear create new issue
60 00:07:01.340 ⇒ 00:07:03.890 steven: team. Oh, that’s actually really cool.
61 00:07:15.030 ⇒ 00:07:16.850 steven: Okay, perfect. Yeah. So
62 00:07:19.660 ⇒ 00:07:23.770 steven: so sorry. Let me ask. So do you? Do you want me to go ahead and create a ticket? For? What do you.
63 00:07:23.770 ⇒ 00:07:36.180 Uttam Kumaran: That would be great. And maybe when, as we’re walking through this like, maybe you can, just you can. You can just start to ask me or Kyle questions on like, Hey, this item like, What is it? Things like that? And I can sort of give you feedback. I can sort of give you the context.
64 00:07:37.060 ⇒ 00:07:46.920 steven: Let’s do that. So I guess I guess. Sorry. Where are we? We’re at the the. Is there a difference between Joby Snowflake? Okay? And just to confirm. So we want to change
65 00:07:47.050 ⇒ 00:07:55.860 steven: dashboard like where we do the dashboard like you. You said we were trying to get out of Meta base you. So you’re saying like, we, we want to go from Walmart to target. That’s.
66 00:07:55.860 ⇒ 00:08:03.179 Uttam Kumaran: No. So this is more of like we want to. We’re staying in metabase. But thus the database source.
67 00:08:03.180 ⇒ 00:08:03.630 steven: Okay.
68 00:08:03.630 ⇒ 00:08:10.629 Uttam Kumaran: Just needs to change. And there are. There are some configuration changes that are between Javi Snowflake and this
69 00:08:10.900 ⇒ 00:08:19.130 Uttam Kumaran: I don’t know what the implication of that is. But the problem is, we have 2 right now, and we want to move over to just this one.
70 00:08:19.680 ⇒ 00:08:24.099 steven: Okay. And and Snowflake is the like data extractor, like extracts. All the.
71 00:08:24.100 ⇒ 00:08:25.520 Uttam Kumaran: Click is the data warehouse.
72 00:08:25.520 ⇒ 00:08:27.819 steven: The data. Yeah, yeah, that’s what I meant. Okay.
73 00:08:27.820 ⇒ 00:08:28.320 Uttam Kumaran: Yes.
74 00:08:29.180 ⇒ 00:08:31.560 steven: It all goes into that data warehouse from.
75 00:08:31.560 ⇒ 00:08:36.969 Uttam Kumaran: Yes. So we’re pulling from the data warehouse in the bi tool to visualize the data.
76 00:08:37.169 ⇒ 00:08:38.260 Uttam Kumaran: And
77 00:08:38.720 ⇒ 00:08:48.840 Uttam Kumaran: right now that the bi tool is connected to one particular part of snowflake, we need to switch it to connect to its to a different part. The reason being is.
78 00:08:48.960 ⇒ 00:08:54.240 Uttam Kumaran: we have a we have a new way of naming some of our databases, and this has the most up to date.
79 00:08:54.750 ⇒ 00:08:56.149 Uttam Kumaran: You know version of that.
80 00:08:56.600 ⇒ 00:09:01.380 steven: Okay, so just moving Jovi Snowflake to broad, smart stuff.
81 00:09:01.380 ⇒ 00:09:03.090 Uttam Kumaran: Yeah. Prodmarts, snowflake.
82 00:09:03.090 ⇒ 00:09:04.680 steven: Okay, perfect. Yeah.
83 00:09:05.010 ⇒ 00:09:07.402 Caio Velasco: It’s it’s all
84 00:09:08.980 ⇒ 00:09:15.669 Caio Velasco: Are all dashboards connected already connected to broad marks to this one in metabase or not necessarily.
85 00:09:15.670 ⇒ 00:09:17.730 Uttam Kumaran: No, they’re all connected to here.
86 00:09:18.705 ⇒ 00:09:19.210 Caio Velasco: Quiz.
87 00:09:19.210 ⇒ 00:09:24.460 Uttam Kumaran: So this is why I don’t. So right now, what we’re doing is we we. This is connected to the analytics database
88 00:09:24.600 ⇒ 00:09:29.770 Uttam Kumaran: in Snowflake, which you probably see right now. All we’re doing is this runs, and I clone it over here
89 00:09:30.000 ⇒ 00:09:31.540 Uttam Kumaran: like it’s part of the job
90 00:09:32.780 ⇒ 00:09:44.679 Uttam Kumaran: because we did this because I don’t. I’m not sure yet what the level of effort is to move to migrate the dashboards to this database connection like I don’t know whether it breaks everything. I don’t know if it’s like a 2 second thing.
91 00:09:45.950 ⇒ 00:09:47.750 Uttam Kumaran: it’s just something that needs to be done.
92 00:09:52.110 ⇒ 00:09:57.489 steven: Sweet. So yeah, let’s get into general. And this is this is for all dashboards. Right.
93 00:09:58.190 ⇒ 00:09:59.929 Uttam Kumaran: This is for everything in Meta Base. Yes.
94 00:10:00.660 ⇒ 00:10:04.470 Uttam Kumaran: but this is more of like a tech debt, and this is where again, it’s probably good
95 00:10:05.010 ⇒ 00:10:13.519 Uttam Kumaran: for y’all as a Pm. Team to understand like, what are the ticket types. But I think like
96 00:10:14.840 ⇒ 00:10:20.440 Uttam Kumaran: I think it would be helpful to to to label this as something like data and like
97 00:10:20.990 ⇒ 00:10:23.460 Uttam Kumaran: tech debt or data engineering, or I don’t know.
98 00:10:23.620 ⇒ 00:10:29.449 steven: Okay? Yeah. Cause I have, like some milestonese, I’ve like data data modeling and data visualization.
99 00:10:30.520 ⇒ 00:10:33.390 steven: So you’re you’re saying, maybe add like a new milestone.
100 00:10:36.680 ⇒ 00:10:38.789 Uttam Kumaran: I don’t know. I I’m saying it’s up to you.
101 00:10:40.780 ⇒ 00:10:56.490 Uttam Kumaran: I’m saying. I I guess, like I’m being very careful for a reason, because I don’t want to. I don’t want to prescribe how it works, and then it doesn’t work. So I’m here to just give as much context to the problem how y’all organize it. I’m
102 00:10:56.860 ⇒ 00:11:01.109 Uttam Kumaran: I’m happy to provide feedback on that. Once you guys have a perspective, I guess. Let’s put it that way.
103 00:11:01.110 ⇒ 00:11:06.886 steven: Yeah, no, I that makes sense, too, I guess. Like my thing is just like, still, just like learning, like some of like the lingo. And like.
104 00:11:07.100 ⇒ 00:11:12.030 Uttam Kumaran: Yeah. Yeah. So if there’s questions on anything in terms of concepts or lingo, please hit me. I think
105 00:11:12.220 ⇒ 00:11:20.770 Uttam Kumaran: I just want to be careful to not over prescribe like, okay, this is how we’re gonna arrange all these because I’m not. Gonna I want it. This to be a system that you guys build, and that works for you.
106 00:11:20.890 ⇒ 00:11:29.410 Uttam Kumaran: So I could probably see around the corner on a few things. But again, I want, I want you guys to to own it. So I’m here mainly just to fill in the gaps on
107 00:11:29.590 ⇒ 00:11:35.329 Uttam Kumaran: on problems. And I I want to help act as the product owner here, you know, as that representation.
108 00:11:35.330 ⇒ 00:11:36.720 steven: Yeah, yeah, that makes sense.
109 00:11:36.840 ⇒ 00:11:38.260 steven: Right? Sweet.
110 00:11:39.670 ⇒ 00:12:08.900 Caio Velasco: And one thing that might be also helpful to you, Steven. I’m not sure how familiar you are with the all the well, let’s say, end to end pipeline lingual but if you want, we can have a quick chat, and I can walk you through, because I know you can always be proactive. But what helped me a lot when I started learning everything is that when I finally learned what are all the pieces of end to end, pipeline, let’s say, from from whatever source to whatever dashboard
111 00:12:09.261 ⇒ 00:12:13.120 Caio Velasco: it helped me quite a lot. So if you’re interested, we can, we can do that.
112 00:12:13.660 ⇒ 00:12:18.165 steven: Yeah, I think that would be helpful, too. I think maybe even like
113 00:12:19.560 ⇒ 00:12:24.570 steven: cause cause right now, I have like the joby dashboards kind of built out in
114 00:12:24.800 ⇒ 00:12:35.462 steven: and linear. And I think maybe even like if if you and I can like hop on a call and then like, I’ll show you like kind of the remaining tasks, because currently, in notion, there’s some things that don’t have like
115 00:12:36.533 ⇒ 00:12:50.200 steven: like labels or anything assigned to it. So I think, like even like going from there and like being like creating like certain milestones, to see like what area of the project that you go into, and then, like you kind of explain, like
116 00:12:50.430 ⇒ 00:12:54.259 steven: what the you know overarching
117 00:12:54.390 ⇒ 00:13:03.999 steven: like milestone it is. I think, that’d be really helpful for me cause then, like in the future, then it’s just like me popping everything when I have something I can look at and like, you know, reference. So I think that works.
118 00:13:04.760 ⇒ 00:13:07.690 Caio Velasco: Perfect perfect sounds, good.
119 00:13:08.290 ⇒ 00:13:08.960 steven: Sweet.
120 00:13:09.490 ⇒ 00:13:16.690 steven: And then, yeah, I think I’ll I’ll I’ll just connect with you after this about setting something up. Maybe if you have time today I could probably
121 00:13:16.820 ⇒ 00:13:18.730 steven: go through it with you. Yep.
122 00:13:18.730 ⇒ 00:13:19.350 Caio Velasco: Cool.
123 00:13:21.780 ⇒ 00:13:23.230 Uttam Kumaran: Awesome. Thanks, guys.
124 00:13:23.510 ⇒ 00:13:30.100 Uttam Kumaran: And then, yeah, I know. Robert, and a wish I’ve joined. I think just maybe I’ll I’ll do one sort of step back.
125 00:13:30.741 ⇒ 00:13:39.738 Uttam Kumaran: I think, Steven, I sent out this message, and maybe this is something also we can talk about in like a Pm. Retro. Tomorrow is assignments. So Kyle,
126 00:13:40.300 ⇒ 00:13:46.959 Uttam Kumaran: Kyle is the primary ae on this client. Robert is working as the primary analyst but also is
127 00:13:47.160 ⇒ 00:13:49.160 Uttam Kumaran: for the product owner.
128 00:13:49.760 ⇒ 00:14:10.619 Uttam Kumaran: we also have a way share as sort of support on secondary ae, we’re we’re sort of landing someone soon to take Robert out of this equation and sort of move him to more of like product owner. That way. He he is acting more as product owner across Eden and and Javi. But I just wanted to clarify that. That’s sort of the allocation. I’m of course.
129 00:14:11.170 ⇒ 00:14:13.706 Uttam Kumaran: here to do whatever you need me to do. But
130 00:14:14.690 ⇒ 00:14:18.370 Uttam Kumaran: I don’t wanna make any of these lists. I don’t want to put myself in any of these lists anymore. So
131 00:14:18.370 ⇒ 00:14:19.100 Uttam Kumaran: yeah.
132 00:14:19.100 ⇒ 00:14:27.934 Uttam Kumaran: I I this is sort of the crew. I think. But I think certainly, if we between this crew we can accomplish everything like this is, this is definitely
133 00:14:28.440 ⇒ 00:14:37.670 Uttam Kumaran: on paper lighter load than than on Eden. But I wanna make sure that we do have at least 2 folks for each role for redundancy.
134 00:14:39.340 ⇒ 00:14:41.949 Uttam Kumaran: But yeah, if any questions there let me know.
135 00:14:42.750 ⇒ 00:14:44.591 steven: Yeah, no, that makes sense.
136 00:14:48.310 ⇒ 00:14:52.980 steven: I don’t really know if I have a question about it. Maybe just kind of like a thought. So like.
137 00:14:53.840 ⇒ 00:15:02.727 steven: I know, Robert. On Monday we had our call with them, and then I think you kind of were just like, Yeah, I’ll go ahead and, like, you know. Take all those edits and and kind of put it in
138 00:15:03.380 ⇒ 00:15:07.099 steven: I guess like when it comes to
139 00:15:07.450 ⇒ 00:15:09.710 steven: moving forward and like putting those
140 00:15:09.880 ⇒ 00:15:16.619 steven: edits, and I think that’s just like whoever I don’t know what I’m trying to say here, like I’m trying to just like
141 00:15:17.740 ⇒ 00:15:26.199 steven: kind of flush out like usually does, it need to go to like someone else, or whoever like would be on the call kind of just like takes it? And does it.
142 00:15:26.240 ⇒ 00:15:38.740 Robert Tseng: Yeah, I guess I can. Yeah, I I would normally not. Take it on the call. But I think that was our 1st time like reconnecting with the CEO on the call. And
143 00:15:39.050 ⇒ 00:15:49.480 Robert Tseng: this they were just like looking at our work. And that’s what happens like we we demo stuff to them. And they ask for some edits. I actually, yeah, I’m I think
144 00:15:51.060 ⇒ 00:16:17.640 Robert Tseng: it’s kind of just an extension of existing work. But then the people who were who who started those work. Streams are no longer working on this project anymore. So like, I had to kind of just say that like I’m not. I got that. I’m gonna I’m just gonna take it. So I feel like, there, yeah, it’s just like a handoff error on on our side where we just like, yeah, there’s no, there’s no one really else right now to pick up on that on that work. But that’s why I I said that on the call.
145 00:16:17.640 ⇒ 00:16:22.111 steven: Yes. Okay, so yeah, kind of clarify what I was kind of talking about a little bit more.
146 00:16:22.510 ⇒ 00:16:25.026 steven: now that my brain’s working.
147 00:16:25.810 ⇒ 00:16:34.620 steven: essentially kind of like when I I like. Saw like notion that I feel like there’s not like a lot of like, cause you’re like, yeah, I’ll take, I’ll take it. But like I didn’t. I don’t think like there’s that
148 00:16:35.050 ⇒ 00:16:50.049 steven: I think, like moving forward. It’d be good if like. I would have to essentially like, build that out into like linear for you to then do, because, like looking at notion, I feel like it’s not really presented there. And it’s just like you know, I I don’t know unless I didn’t see it. But like.
149 00:16:50.190 ⇒ 00:17:02.830 steven: I think, you know, just getting everyone assigned the right thing, you know, that’s like definitely what I want to do and like making sure. Like as I continue. And I learn, I like, know exactly how to just like pop in. Whoever like needs to be on so.
150 00:17:03.850 ⇒ 00:17:23.900 Robert Tseng: Yeah, I mean frankly on Javi, like I I gave up on notion like a couple of weeks ago. So I have not touched anything there. We’ve maybe just like, maintained some of like the higher level, like project or objective level stuff. Just cause. That’s how Aman like approves like our roadmap.
151 00:17:24.050 ⇒ 00:17:41.339 Robert Tseng: So there is like a need to kind of migrate our tasks back over into linear and then to get like a project timeline view set up which I think Akash showed me yesterday that linear has that ability which is huge because we were trying to get that in notion for a long time.
152 00:17:41.340 ⇒ 00:17:42.129 Uttam Kumaran: Yeah, it sucked.
153 00:17:42.450 ⇒ 00:17:48.410 Uttam Kumaran: It’s horrible. I’m so done with with even talking about it. I think, Steven, 100 is that
154 00:17:48.630 ⇒ 00:17:51.380 Uttam Kumaran: the client this client is interested in seeing
155 00:17:51.620 ⇒ 00:17:56.400 Uttam Kumaran: a timeline view and seeing some sort of hourly breakdown one time
156 00:17:56.400 ⇒ 00:18:09.230 Uttam Kumaran: overall, too. And maybe this is part of maybe this is an issue in linear is to produce that for them, something that they can that I’m on can approve and say, I love this. This is exactly what I need to see
157 00:18:09.749 ⇒ 00:18:12.839 Uttam Kumaran: and for you to sort of take over that negotiation.
158 00:18:13.490 ⇒ 00:18:15.452 steven: Yeah, for sure. And I think
159 00:18:16.350 ⇒ 00:18:24.839 steven: even, I, I think Akash sent something the Pm. Channel, too. I kinda I I built out like a an example of it, too. Maybe. Let me just share my screen real quick.
160 00:18:24.840 ⇒ 00:18:29.479 steven: Yeah, please show it off real quick. Yeah. So this is kind of like
161 00:18:29.650 ⇒ 00:18:35.119 steven: ideally, this is all like, just not real. It’s just examples, but
162 00:18:35.380 ⇒ 00:18:40.170 steven: moving forward like, I think, like, whenever we build anything out, it’s just having these.
163 00:18:40.510 ⇒ 00:18:40.900 Robert Tseng: I don’t think.
164 00:18:40.900 ⇒ 00:18:47.350 steven: Oh, I’m not. Oh, yeah, I got it. I gotta confirm. Okay, so yeah, so essentially.
165 00:18:47.949 ⇒ 00:18:48.549 Robert Tseng: Yeah.
166 00:18:48.820 ⇒ 00:18:59.284 steven: These timelines right? So you have, like the main dashboard you’re working on the main dashboard you’re working on, and then the milestones to do it right, and but like within each of these milestones, right? So if I click here,
167 00:18:59.940 ⇒ 00:19:22.540 steven: I guess let’s see like it should have like additional issues within it that you should go and see. I think I’m still learning it. But I think like it should be right here. So it should be like, okay, maybe I build it out here. Let me go here because this is like a the general task, for, like adding some of the notion stuff in. But for here you’ll have, like your issues of what happens with each milestone. So
168 00:19:22.900 ⇒ 00:19:27.770 steven: you know, you can see that each of these is within
169 00:19:27.890 ⇒ 00:19:30.759 steven: a milestone if it will load.
170 00:19:31.210 ⇒ 00:19:34.190 steven: Oh, my gosh, maybe.
171 00:19:35.270 ⇒ 00:19:39.506 steven: Okay. I think I had it yesterday, still learning it. But
172 00:19:40.250 ⇒ 00:19:45.959 steven: oh, clear filters. Okay, so yeah. So like each of these will have. Oh, there it is. Yeah, the so this will kind of
173 00:19:46.470 ⇒ 00:19:50.060 steven: ideates what milestone it needs to be in
174 00:19:50.532 ⇒ 00:20:01.440 steven: and so like when it we have these milestones, like each milestone, has these like little tiny tasks in it in order to complete data visualization. So what we can do and show to the client
175 00:20:01.750 ⇒ 00:20:22.600 steven: is essentially we show them this, not on here, because we don’t want them to have access to like linear and everything, but like a way to show them. Starting. March 4th to April 4.th We are making the gross margin dashboard, and this step, this step, this step, this step, this step and this step are all gonna happen within that timeline and I guess, like
176 00:20:22.700 ⇒ 00:20:24.929 steven: I was using figma to kind of like.
177 00:20:25.130 ⇒ 00:20:29.086 steven: you know, explain that. So that’s like something maybe we can like do with that.
178 00:20:29.610 ⇒ 00:20:36.980 steven: I’m not super artistic. So maybe you know, once I finish it up. Maybe I’ll like meet with someone to try to like kind of like.
179 00:20:37.140 ⇒ 00:20:37.970 steven: you know.
180 00:20:38.370 ⇒ 00:20:50.830 steven: make it a little bit sexier, in a way. So. But yeah, I think like, this is like a good way, like, we utilize this with each step. It’s more specific than the client has, like their more broad overview of like this is all that’s happening.
181 00:20:50.960 ⇒ 00:20:52.990 steven: How does it look nice? Great.
182 00:20:54.600 ⇒ 00:21:11.542 Robert Tseng: Yeah, no. I think this makes sense having, like the project level or the objective, what whatever we call that like. And then the milestones, like, I think that’s the level of granularity they need to see. And then all the issue specific stuff that’s definitely for us to just like kind of hash that out internally.
183 00:21:12.060 ⇒ 00:21:18.440 Robert Tseng: but yeah, I think, yeah, this, this this is. This is, I think, exactly the view that we need to show to Ammon.
184 00:21:18.947 ⇒ 00:21:29.739 Robert Tseng: So he can know like what’s happening like, are there anything? Is there anything happening in parallel? He wants to know? Like, oh, like I mean, because he he’s really a stickler. On
185 00:21:29.980 ⇒ 00:21:36.299 Robert Tseng: making sure we maximize the hours, or whatever. So he he will. He would want to know like that.
186 00:21:37.360 ⇒ 00:21:39.769 steven: Okay, yeah, true. And then I guess.
187 00:21:39.940 ⇒ 00:21:47.790 steven: yeah, that’s that’s that’d be like, another thing, too, is like breaking out hours. And I think, like, maybe even like, let’s see like, can I put like
188 00:21:48.740 ⇒ 00:21:50.350 steven: hours and.
189 00:21:50.350 ⇒ 00:21:59.819 Robert Tseng: We. These are just estimated hours, like, I know we send him the clockify stuff, too, so he kinda I don’t know if we send it to him. But we we have it internally. So we know how many hours people are spending
190 00:22:00.100 ⇒ 00:22:00.759 Robert Tseng: like with.
191 00:22:00.760 ⇒ 00:22:01.470 Uttam Kumaran: Yeah.
192 00:22:01.470 ⇒ 00:22:09.340 Robert Tseng: Would this kind of work, I mean, I don’t know if we’re how often we’re like evaluating. This is what we estimated. This is what actually took and.
193 00:22:09.340 ⇒ 00:22:23.957 Uttam Kumaran: So like, I think, like, I want to even jump off of this topic like that is a function of us like messing up timelines. So like, I’m not even confident they want to know. They really like want to know this long term. If we just nail our shit.
194 00:22:24.720 ⇒ 00:22:28.920 Uttam Kumaran: I’m more concerned with us, nailing our stuff and then figuring out.
195 00:22:29.420 ⇒ 00:22:33.020 Uttam Kumaran: Okay, if we’re nailing our stuff like, why do you want to know what the hours are? So.
196 00:22:33.180 ⇒ 00:22:33.760 Robert Tseng: Yeah.
197 00:22:33.990 ⇒ 00:22:37.969 Uttam Kumaran: I’ll let, I think again. I think Steven is for probably for you and Aman to
198 00:22:38.080 ⇒ 00:22:51.130 Uttam Kumaran: you, Iman and Robert, to continue to litigate, but like it. Really, this started as a function of like, we weren’t getting stuff out on time. And they were like, what are we working on and like, I don’t want to. I don’t want to solve that problem by saying, Okay, we’ll give you what you want.
199 00:22:51.320 ⇒ 00:22:54.609 Uttam Kumaran: The problem is better solved getting stuff out of time.
200 00:22:54.830 ⇒ 00:22:56.469 steven: Yeah, no, that makes sense, too.
201 00:22:56.470 ⇒ 00:22:56.970 Uttam Kumaran: Off.
202 00:22:56.970 ⇒ 00:22:58.920 steven: And I think, like once, like.
203 00:22:59.400 ⇒ 00:23:02.409 steven: I just have like a better idea of like understanding of like.
204 00:23:02.650 ⇒ 00:23:06.870 steven: really, what happens in the project?
205 00:23:07.290 ⇒ 00:23:31.959 steven: We can build it out, and then, like, have it just like, have it ready to go with everyone on it, too, because I think, like my thing is like, I. I still like need to know the process of like what exactly the milestones happen during, like, you know, this discovery and requirement phase and like, see exactly what happens in it like, who needs to do it. And then I think, like, even just like, maybe just building out like.
206 00:23:32.330 ⇒ 00:23:53.419 steven: you know, maybe we haven’t even done a dashboard with them yet, but even just like building a dashboard out that we want to do with them, and then literally assign everyone to it, have a start, date and end date, and like, just like, you know, see what it looks like. I I think that’d be really helpful for me, too, because then it’s like, you know, without within, when it comes to them building everything else out, I’ll have like a really good concrete example.
207 00:23:55.540 ⇒ 00:24:00.620 Robert Tseng: Yeah, I mean, I would say that even with these milestones I know you probably just like randomly selected them. But
208 00:24:01.045 ⇒ 00:24:07.089 Robert Tseng: whether we keep this set or not. I would say that, like with these dashboard, with data projects.
209 00:24:07.170 ⇒ 00:24:31.669 Robert Tseng: a lot of the work like the timelines get dragged out at the begin at the at both ends, at the beginning, for the discovery and requirements, gathering, making sure that we really understand, like what we’re building, defining the metrics, etc. And then, after the dashboard is sent, then there’s this like long tail of like all these like random edits, adjustments that we have to make, because what we give them is not exactly what they expected, or they change their expectations after they’ve seen something live.
210 00:24:31.800 ⇒ 00:24:54.989 Robert Tseng: So it’s really not. We never put out anything that’s like one and done like it’s we always share it. There’s always like one, or, you know, one plus rounds of revisions, and you know, like oasis, and I just came back from a call with with them on. And it’s just like continuous revisions on some of this stuff that’s been in flight for for a while, and I don’t know. It makes it look like we dragged out the project, but it’s really not like it’s
211 00:24:55.510 ⇒ 00:25:01.910 Robert Tseng: like gross margin dashboard. We can even break it up into there. That was v, 1. There’s v, 1 like v, 2, VV. 3.
212 00:25:02.930 ⇒ 00:25:08.049 Robert Tseng: We should be doing that because I think that’s that’s the better way to. I mean, I don’t.
213 00:25:08.050 ⇒ 00:25:17.179 Uttam Kumaran: Totally right. We we had this conversation this morning, too. Where? How do we version changes and batch, because otherwise it all reverts back to
214 00:25:17.530 ⇒ 00:25:22.610 Uttam Kumaran: 24 h, just like, Wake up! What’s next? Wake up! What’s next? This is like the plague of
215 00:25:23.160 ⇒ 00:25:32.389 Uttam Kumaran: data teams like this is this is also something that is pretty common. So what I’ll be talking to the Pm. Team tomorrow about is like, how do we
216 00:25:32.560 ⇒ 00:25:56.309 Uttam Kumaran: one? How do we push back on like what is urgent. And then first, st how do we also like for those for the client? They may not see it as urgent, but they’re like there’s no other. I’m not given any other option. Is it either get done today or when does it get done? If we can say, Okay, we have a cadence of every Friday we do a release. Every or every Thursday we push changes, and then we sort of have versions that way that that at least gives us some breathing room.
217 00:25:56.450 ⇒ 00:26:07.070 Uttam Kumaran: So let’s talk about this today and in the tomorrow in the Pm. Retro, because I have a few items and then some notes from the Ae. Meeting today, this mor from the morning about this exact topic. So
218 00:26:07.320 ⇒ 00:26:13.049 Uttam Kumaran: totally with you, this, this client especially, and and with Eden and any dashboard client. We’re gonna have revisions.
219 00:26:13.240 ⇒ 00:26:17.980 Uttam Kumaran: So our ability to batch those and also revisions, like, maybe
220 00:26:18.230 ⇒ 00:26:21.769 Uttam Kumaran: cosmetic changes, modeling changes engineering changes like
221 00:26:22.020 ⇒ 00:26:29.240 Uttam Kumaran: it. We have to plan those out and assign sort of level of effort. So I think, Kyle, in a way, it’s just exactly what we were talking about this morning.
222 00:26:30.110 ⇒ 00:26:32.419 steven: Okay. So I think one thing.
223 00:26:32.834 ⇒ 00:26:44.715 steven: I’ve I’ve 2. I have a question in the little point I wanna make. But one thing we should build into this is sending like client sending it to the client for them to review as well as
224 00:26:45.040 ⇒ 00:27:06.490 steven: revision timelines. So like, you know they have 3 days to, you know, edit or review edit, and then, you know, we have 2 days to edit and send back example. But I guess, like it when when we send them the dashboard to review, is it literally only on the call when we meet with them to like, go over it with them, and then we gotta wait a week. Or how does it? How does that process like.
225 00:27:06.490 ⇒ 00:27:35.190 Robert Tseng: Yeah, no, I think, Steven, you’re onto something like, yeah, we send stuff over. And it’s like, Hey, review this most of the time. They don’t review it until we get on the call. And it’s like we’re walking it through. Them live. And they’re just like reacting to it. Live? I don’t like that. I think that I would prefer them to actually review and kind of have more ownership of like what we’re giving them, which I think we’re we’re at a better place now, because I’m actually requiring them to review it before I meet with them. But, like, yeah, there wasn’t necessarily like a strong voice, or someone pushing them to do that before.
226 00:27:35.487 ⇒ 00:27:41.370 Robert Tseng: Obviously we can’t do that with the CEO, but, like with them on, I will not meet with him unless he’s actually reviewed what I’ve what I.
227 00:27:41.370 ⇒ 00:27:42.010 Uttam Kumaran: And then.
228 00:27:42.010 ⇒ 00:27:42.660 Robert Tseng: Anymore.
229 00:27:42.920 ⇒ 00:27:48.050 steven: Okay. Alright, that’s good to know, too. And I even like, I wonder if it’s like
230 00:27:48.360 ⇒ 00:27:56.800 steven: creating a loom, and then kind of like sending them a loom of us like walking through the dashboard and be like watch, please review and like send back, and and then even just like, give an end, dates right, and say like, Hey.
231 00:27:56.800 ⇒ 00:27:57.370 Uttam Kumaran: Totally.
232 00:27:57.370 ⇒ 00:28:01.430 steven: This is the we need this due by wednesday, you know.
233 00:28:01.430 ⇒ 00:28:08.459 Uttam Kumaran: Aman is a great way to to gut check pretty much everything. This is why, even as a whole, I think he, we should try to get him
234 00:28:08.670 ⇒ 00:28:33.910 Uttam Kumaran: so to be the product owner in some in some form, for, like one of these work streams right and push him to go get requirements from the Ceos, and like push him to start to give us really clear requirements. Right now we’re doing partly what he should be doing. And now there’s 4 layers. There’s now the CEO, there’s him! There’s Robert, and then it comes down to the team, and then, of course, between us there’s layers right? So it’s telephone
235 00:28:34.395 ⇒ 00:28:44.510 Uttam Kumaran: so we can shorten the layers. Push more on him. I think that’ll be a little bit of like a few week goal, which is like, how do we start to involve him more? Because if if buy-in comes from him, then also
236 00:28:44.840 ⇒ 00:28:50.169 Uttam Kumaran: accountability goes to him like, if he tells us the wrong thing. We can’t be on the hook for it right.
237 00:28:50.170 ⇒ 00:28:50.780 steven: Yeah.
238 00:28:50.780 ⇒ 00:28:58.150 Uttam Kumaran: Like there are no nuances to this business that, like he has a relationship with the CEO, we’re gonna start to have to build that it’s gonna take us a long time. So
239 00:28:58.450 ⇒ 00:29:05.050 Uttam Kumaran: that’s something to keep in the back of your mind is we want to engage him on like as much as possible, also the renewal. He will fight for us, too.
240 00:29:05.330 ⇒ 00:29:06.090 Uttam Kumaran: you know.
241 00:29:06.420 ⇒ 00:29:21.280 steven: Okay, yeah, that makes sense, too. And another question, how? How often? Like? So how many? Let’s say, let’s say, we’re sending out the gross margin dashboard. How many rounds of edits like we’re sending it edits setting. It edits like how many like rounds is it usually typically.
242 00:29:21.280 ⇒ 00:29:24.530 Robert Tseng: Even for this one. We’ve been working on this since the beginning of.
243 00:29:24.530 ⇒ 00:29:30.520 Uttam Kumaran: Well, I don’t think it stops, because to give you a sense of it like, let me let’s talk. Let’s talk about brain Forge, for example.
244 00:29:30.840 ⇒ 00:29:38.930 Uttam Kumaran: when would I ever stop looking at our financial health dashboard when maybe when the company sells, or if the company dies, that’s what you know. There’s no stopping
245 00:29:39.050 ⇒ 00:29:39.990 Uttam Kumaran: right?
246 00:29:40.120 ⇒ 00:29:46.209 Uttam Kumaran: So let’s say you were a small business owner. When would you stop looking at the health of your Amazon business
247 00:29:46.930 ⇒ 00:29:47.690 Uttam Kumaran: right.
248 00:29:47.690 ⇒ 00:29:48.600 steven: Yeah. Yes.
249 00:29:48.600 ⇒ 00:29:51.919 Uttam Kumaran: So that’s the answer. In in fact, the answer is that.
250 00:29:52.350 ⇒ 00:29:59.169 Uttam Kumaran: like there will always be changes to the business that reflect in either new dashboards or modifications dashboard. It’s it does not end
251 00:29:59.826 ⇒ 00:30:09.550 Uttam Kumaran: right? And I think that’s the key point in our business compared to the creative, is that creative. There is an activation. You get all the assets done, wipe your hands and you go
252 00:30:10.040 ⇒ 00:30:21.149 Uttam Kumaran: for us. It I actually love that there is. There is endless work, and we want to continue to help them become a better business. And so these do live in perpetuity. Most likely.
253 00:30:21.380 ⇒ 00:30:23.165 steven: Okay. So would you say, there’s like.
254 00:30:23.880 ⇒ 00:30:26.740 steven: essentially like there, like, there’s a 1st round like
255 00:30:26.910 ⇒ 00:30:43.030 steven: we’ve made it. We send it to them. They review. And then we make edits. And then they like those edits. Right? I think we can like what we can do is we can build in like just that that like 1st or second round of hey? Send it! Get it back, send it, get it back! And then from there we build out like a weekly review for them to do.
256 00:30:43.030 ⇒ 00:30:43.690 Uttam Kumaran: Yes.
257 00:30:43.690 ⇒ 00:30:57.399 steven: Cause it. Cause if it is that case of yeah, cause they do want to keep looking at. Keep looking at it. You know. There’s more data that’s coming in right? So then it’s then it’s a weekly check in at that point. Right? Then, you know, it’s not us
258 00:30:57.950 ⇒ 00:31:17.050 steven: sending it back. You know we pay. We made your changes here you go. It’s us, you know, trying to be proactive, and also like getting like information. They would now want to see taking it in. So by that point we can call it done right, and then you finish it, and then you just like monitor it. If that makes sense.
259 00:31:17.050 ⇒ 00:31:28.870 Uttam Kumaran: So that that’s what I’m saying is like increase like increase the time of the cycles, right? Like the cycles, need to move from 24 h change comes in, change gets made because not all changes take
260 00:31:29.070 ⇒ 00:31:54.960 Uttam Kumaran: 24 h like some. Changes are more institutional. Some changes are cosmetic, right? So we do need a really clear triage. But the one thing that I can guarantee you is that work will not stop coming our way forever, for the life of the company, and these dashboards will continue to live. We may move to looker, we may add more sources. We may need to do blah blah! These are going to continue to go and so the thing is to increase the breathing room for folks.
261 00:31:55.160 ⇒ 00:31:56.959 Uttam Kumaran: and ideally, that’s a week.
262 00:31:57.760 ⇒ 00:32:07.339 Uttam Kumaran: Some clients that maybe 2 weeks. Some clients like I, I just anything that happens on a daily basis. My, my perspective is gonna start to shift towards
263 00:32:07.630 ⇒ 00:32:11.540 Uttam Kumaran: more playing defense for the engineers on like, why is this urgent?
264 00:32:12.235 ⇒ 00:32:16.670 Uttam Kumaran: Right? And then, like, there, there, there just needs to be multiple.
265 00:32:17.170 ⇒ 00:32:30.559 Uttam Kumaran: Right? This is the triforce, right? So there’s gonna be multiple angles to this problem. I think one clear thing that we should talk as a Pm team tomorrow is, how do we version dashboards, version analyses and batch changes.
266 00:32:30.840 ⇒ 00:32:38.839 Uttam Kumaran: There will be some stuff that like is urgent, though, like, for example, if they’re going to a capital raise meeting, and they need some dashboard, and it’s fucked up.
267 00:32:39.670 ⇒ 00:32:47.790 Uttam Kumaran: That’s also where we shine right. But if you cry Wolf every day, then we’re we can’t ever see that. That’s the urgent thing.
268 00:32:48.404 ⇒ 00:32:57.052 Uttam Kumaran: It’s not that we can’t do stuff in 24 h. In fact, we have been for the life of the business, so we definitely can. It’s just that all of us will burn out.
269 00:32:57.300 ⇒ 00:32:57.639 steven: Yeah.
270 00:32:57.980 ⇒ 00:32:58.660 Uttam Kumaran: You know so.
271 00:32:58.660 ⇒ 00:33:02.680 steven: Yeah, that that makes sense. And I think, like.
272 00:33:03.400 ⇒ 00:33:07.369 steven: I don’t know. Maybe it’s even like, you know, we
273 00:33:07.850 ⇒ 00:33:34.280 steven: you know, they review the dashboard, and then they come with questions on our weekly touch bases with them like we like get in and like, you know, you know, we go over it, and then they like, say, like what they want to say, you know, but they already have it, which I think like you know, Robert already mentioned. You know, mom’s doing it. So I think just like figure out like a way to. I think I have an idea of it. But just like building it in like, almost yeah, like you said, like a weekly check in or like a weekly task for us to just like keep updating it on a weekly level.
274 00:33:35.390 ⇒ 00:33:37.119 steven: I think, is smart.
275 00:33:42.810 ⇒ 00:33:48.550 Uttam Kumaran: Okay, great, do we? Wanna I know we’re over on time like I would love to keep going through
276 00:33:49.180 ⇒ 00:33:53.179 Uttam Kumaran: everything else that’s in flight on Javi. So, Steven, you have it to document.
277 00:33:53.960 ⇒ 00:33:55.230 steven: Yeah, we can do that. I think, like.
278 00:33:55.230 ⇒ 00:33:56.259 Uttam Kumaran: How are you guys on time.
279 00:33:56.970 ⇒ 00:33:59.959 steven: I do have that Eden called.
280 00:33:59.960 ⇒ 00:34:00.670 Uttam Kumaran: Oh, okay.
281 00:34:00.670 ⇒ 00:34:02.300 steven: Product mapping on it.
282 00:34:02.460 ⇒ 00:34:04.787 Uttam Kumaran: Then maybe that’s best to go to
283 00:34:05.650 ⇒ 00:34:14.439 Uttam Kumaran: like what’s what’s easy for me and Kyle, and a ways to work on in terms of getting you a list of things like, can you give us like a a format? Or
284 00:34:14.560 ⇒ 00:34:18.580 Uttam Kumaran: however, we can help to just like list out everything that was on our plates.
285 00:34:19.770 ⇒ 00:34:24.923 steven: Yeah, I think I think currently, if you can send me like just
286 00:34:26.270 ⇒ 00:34:34.570 steven: oh, so just like whatever the main like that like, what is the dashboard you’re working on? And then what is
287 00:34:34.770 ⇒ 00:34:37.880 steven: what is the task that you’re doing?
288 00:34:38.210 ⇒ 00:35:01.010 steven: Or so, I guess, like, what’s the what’s the dashboard or project you’re working on for joby coffee. And then what is them like the the main milestone with it? Right? Is it client edits, or is it? You know the data modeling. You’re doing that and then break it down one step further with the the issues. Right? So I think, like it. It should be something, you know. It’s like, I’ll type it out so it’s like.
289 00:35:01.490 ⇒ 00:35:05.879 Uttam Kumaran: Yeah, so I would. What is a dash for a project? What is a task? Cosmetic data, modeling
290 00:35:06.010 ⇒ 00:35:11.009 Uttam Kumaran: data ends something like that. And then, like just like notes on the issue.
291 00:35:11.460 ⇒ 00:35:12.080 steven: Yeah.
292 00:35:12.520 ⇒ 00:35:22.740 steven: okay, so that’s kind of what I said. So just product the milestones, and then issues to meet that milestone. And I think, like. If you just send me a list I’ll have like a really good understanding of how to then like, break it out and like, get a good idea of it. So.
293 00:35:22.970 ⇒ 00:35:28.060 Uttam Kumaran: So wish Kyle, can we work on this just over the next hour in slack.
294 00:35:29.520 ⇒ 00:35:30.270 Awaish Kumar: Clearly.
295 00:35:30.270 ⇒ 00:35:30.660 Caio Velasco: Sure.
296 00:35:30.660 ⇒ 00:35:32.020 Awaish Kumar: For joby. Irony.
297 00:35:32.783 ⇒ 00:35:41.590 Awaish Kumar: I like only have work on the adding a field for Okendo dashboard. And then
298 00:35:42.190 ⇒ 00:35:49.669 Awaish Kumar: we in. In this meeting with Aman we discuss about this cogs for shipping cogs.
299 00:35:50.383 ⇒ 00:35:51.229 Awaish Kumar: For E
300 00:35:51.400 ⇒ 00:35:57.980 Awaish Kumar: order item level. But he said, it doesn’t make sense. We can remove that from line item, level.
301 00:35:57.980 ⇒ 00:35:58.779 Awaish Kumar: okay? And keep it.
302 00:35:58.780 ⇒ 00:35:59.900 Awaish Kumar: Yeah, loader level.
303 00:36:00.160 ⇒ 00:36:03.359 Uttam Kumaran: So can you just put I’m gonna send like I’m gonna send this note.
304 00:36:03.890 ⇒ 00:36:13.250 Uttam Kumaran: I’m gonna send a note in slack. Just start putting in any of like the work that’s on your plate, or even updates you got today just in slack. So Steven can track.
305 00:36:13.630 ⇒ 00:36:21.969 Uttam Kumaran: Steven will work on getting that into into linear, and then we’ll start running standups from linear, most likely, or whatever process
306 00:36:24.750 ⇒ 00:36:26.360 Uttam Kumaran: is that good for for both? Y’all.
307 00:36:27.930 ⇒ 00:36:29.580 Caio Velasco: Yep, yeah.
308 00:36:29.580 ⇒ 00:36:39.300 Caio Velasco: For me, it works. Maybe we should centralize like in me, you can open a thread in slack, and then we comment there, so so that Stephen can have just a 1 place to go and check.
309 00:36:39.300 ⇒ 00:36:46.640 Uttam Kumaran: Yeah, let’s let’s do it. Here, I’ll just put this. Add all things to this thread cool
310 00:36:47.380 ⇒ 00:36:50.540 Uttam Kumaran: so you could just thread it under my my message.
311 00:36:53.350 ⇒ 00:36:54.300 Caio Velasco: Terrific.
312 00:36:57.250 ⇒ 00:36:57.790 Uttam Kumaran: Okay.
313 00:36:58.230 ⇒ 00:36:59.100 steven: Alright.
314 00:37:00.320 ⇒ 00:37:01.300 steven: See?
315 00:37:02.700 ⇒ 00:37:07.290 steven: Okay, sweet, awesome, perfect. Thank you guys so much. Alright, I’m gonna jump. So bye.
316 00:37:07.440 ⇒ 00:37:08.920 Uttam Kumaran: Thanks, guys, bye.