Meeting Title: Eden Internal Deck Review Date: 2025-01-03 Meeting participants: Luke Daque, Nicolas Sucari, Uttam Kumaran, Sahanaasokan, Robert Tseng
WEBVTT
1 00:00:42.200 ⇒ 00:00:43.310 Nicolas Sucari: Hey, guys.
2 00:00:44.310 ⇒ 00:00:44.865 sahanaasokan: Hello!
3 00:00:46.230 ⇒ 00:00:47.210 Uttam Kumaran: Hey!
4 00:00:48.150 ⇒ 00:00:50.079 Nicolas Sucari: Hey, Zahana! Nice to meet you.
5 00:00:50.370 ⇒ 00:00:51.350 sahanaasokan: Meet you.
6 00:00:51.350 ⇒ 00:00:53.040 Robert Tseng: Whoa! Hey! Sahana!
7 00:00:53.690 ⇒ 00:00:54.810 sahanaasokan: Hello!
8 00:00:56.160 ⇒ 00:00:57.240 Robert Tseng: Welcome!
9 00:00:58.190 ⇒ 00:00:59.590 Uttam Kumaran: Welcome.
10 00:01:00.540 ⇒ 00:01:05.070 Uttam Kumaran: dude I’m pumped for I’m pumped for this client, Dude. I think we have a lot of work, and
11 00:01:05.250 ⇒ 00:01:08.289 Uttam Kumaran: I think this industry is like blowing up so.
12 00:01:11.130 ⇒ 00:01:11.960 Robert Tseng: Holy.
13 00:01:14.180 ⇒ 00:01:19.950 Robert Tseng: Okay? Well, I think this is it right? We’re not waiting on anyone.
14 00:01:21.200 ⇒ 00:01:22.400 Uttam Kumaran: Is Luke coming?
15 00:01:22.400 ⇒ 00:01:23.420 Robert Tseng: Oh, maybe Luke!
16 00:01:24.570 ⇒ 00:01:25.730 Nicolas Sucari: I’m meeting him.
17 00:01:26.280 ⇒ 00:01:27.000 Robert Tseng: Okay.
18 00:01:27.770 ⇒ 00:01:32.230 Robert Tseng: Well, I think what I’ll do is probably I’ll share my screen. Kinda just
19 00:01:32.430 ⇒ 00:01:37.689 Robert Tseng: give you all the lay of the land. Yeah, I guess more specifically.
20 00:01:39.111 ⇒ 00:01:48.020 Robert Tseng: hoping to get yeah, just get feedback from probably Utam, Sahana and Nico more more specifically on on this call. Just so, you guys.
21 00:01:50.120 ⇒ 00:01:58.250 Robert Tseng: make sure. Yeah, I’m trying to get to catch you up on the context of where we’re at now and then. Yeah, I think things are gonna ramp up starting next week.
22 00:02:01.470 ⇒ 00:02:03.780 Robert Tseng: Okay, so
23 00:02:05.040 ⇒ 00:02:14.710 Robert Tseng: here we go. Yeah. So this is kind of a deck that shared so kind of. In short, we’re basically kind of brought in to kind of like, do some
24 00:02:15.620 ⇒ 00:02:21.929 Robert Tseng: transformation like to tre to basically lead their data function. At least that was like kind of the ask for me.
25 00:02:22.496 ⇒ 00:02:27.839 Robert Tseng: And then, as a result, I’m kind of like bringing this this team together to do it.
26 00:02:28.274 ⇒ 00:02:36.219 Robert Tseng: So I think what’s unique about this client is that they already have a lot of things set up. I kind of like to put together a diagram here.
27 00:02:36.709 ⇒ 00:02:48.269 Robert Tseng: So I guess, for the more technical folks on the call. Yeah, they already have a bunch of data sources kind of plugged in. They have some semblance of a data warehouse. But it’s just like not very
28 00:02:48.280 ⇒ 00:03:11.163 Robert Tseng: formalize is just a single de who’s maintaining it. No dbt, no no visibility into his work. He just has, like a bunch of massive scheduled sequel queries that run on like an hourly basis to kind of model out the data into a few different tables segment is like probably the tool they rely on the most to do data movement to do
29 00:03:11.890 ⇒ 00:03:25.370 Robert Tseng: like some basic transformations, just like renaming fields and stuff. And then also to build like user profiles. And and some some comp computed traits about that. So like.
30 00:03:25.960 ⇒ 00:03:31.609 Robert Tseng: predicted. Ltv, or like, you know, some of these, like other
31 00:03:32.270 ⇒ 00:03:39.179 Robert Tseng: like value based metrics that, are kind of just like a calculation off of the existing behavior data that they have.
32 00:03:41.320 ⇒ 00:03:55.889 Robert Tseng: I’ll kind of just pause here on this on this system kind of diagram, just to see if anybody had any questions here. I’m assuming that you all already kind of like read up on like what this, what this client is. So I didn’t jump into that. But let me just kind of pause there to see if there are any questions on this.
33 00:03:57.610 ⇒ 00:04:00.420 Luke Daque: Yeah, I have a just a quick question. I also
34 00:04:00.570 ⇒ 00:04:05.844 Luke Daque: did look into the the deck yesterday. Get familiar with it. But,
35 00:04:06.400 ⇒ 00:04:10.509 Luke Daque: You did mention. They already have big query set up right? So I guess
36 00:04:11.610 ⇒ 00:04:18.390 Luke Daque: that would mean they already have their sources in bigquery and like some sort of data transformation like you mentioned.
37 00:04:18.860 ⇒ 00:04:27.370 Luke Daque: So I guess the plan is to migrate all of that to Dbt or something.
38 00:04:27.980 ⇒ 00:04:40.180 Robert Tseng: Yeah, I think we’re one of the yeah. I don’t think we’re gonna move them off of bigquery in the short term. I don’t wanna like introduce too much change. But I do think I want I’m trying to like really push on the migrating to a Dbt workflow
39 00:04:40.755 ⇒ 00:04:43.010 Robert Tseng: and just make it so that
40 00:04:43.230 ⇒ 00:05:05.490 Robert Tseng: the de is not the only own owner of the the data transformations right now, because he’s basically doing everything from like building custom connectors to well, I mean, most of the connectors are not custom. They’re just through segment. But yeah, he’s kind of doing ae work right now as well. But that’s like not I don’t really. I mean, I want. I want us to own that.
41 00:05:07.410 ⇒ 00:05:12.649 Nicolas Sucari: So they don’t have a Github environment with everything right? It’s just everything is in bigquery.
42 00:05:13.284 ⇒ 00:05:19.330 Robert Tseng: No, he probably has a github, but I don’t think anybody looks at it except for him, and maybe their data scientists.
43 00:05:20.270 ⇒ 00:05:20.890 Nicolas Sucari: Okay.
44 00:05:22.790 ⇒ 00:05:25.819 Luke Daque: Yeah, I don’t. I don’t think there’s like version control in
45 00:05:25.970 ⇒ 00:05:28.250 Luke Daque: just scheduled queries and and stuff.
46 00:05:28.250 ⇒ 00:05:28.699 Robert Tseng: There is not.
47 00:05:28.700 ⇒ 00:05:29.210 Luke Daque: And be crazy.
48 00:05:29.210 ⇒ 00:05:29.780 Robert Tseng: Yeah.
49 00:05:30.300 ⇒ 00:05:44.989 Robert Tseng: So yeah, Luke, to give you an example. Like this past week. There was like over 3 days one of the execs asked to change the definition of a metric. The d got it wrong, and then, let’s see.
50 00:05:45.290 ⇒ 00:05:57.889 Robert Tseng: it got wrong, like probably 2 times. So it took like 3 iterations to just change one definition, and that took like 4 days and like nobody could really validate what he was doing. And that’s why he was getting it wrong every time he was trying.
51 00:05:59.300 ⇒ 00:05:59.880 Luke Daque: Right.
52 00:06:00.160 ⇒ 00:06:01.350 Robert Tseng: Yeah, since.
53 00:06:02.490 ⇒ 00:06:03.940 Luke Daque: Okay. Cool.
54 00:06:05.470 ⇒ 00:06:06.190 Robert Tseng: Cool.
55 00:06:06.956 ⇒ 00:06:08.490 Robert Tseng: Any other questions on this?
56 00:06:11.800 ⇒ 00:06:17.880 Robert Tseng: Nope, okay. Well, then, I’ll come. I’ll kind of call out a couple of things. Maybe this is more for kind of Sahana.
57 00:06:18.426 ⇒ 00:06:21.089 Robert Tseng: So I think more, I feel like we’re gonna
58 00:06:21.200 ⇒ 00:06:50.033 Robert Tseng: we’re gonna work more closely on the analytics side. So yeah, I mean this is, there’s still some blanks here like I haven’t been able to see every possible report out there, but it is quite fragmented, and I think there’s just like a big need to know which tools like, where is reporting gonna live in in which tools the problem is that, like at the C-suite level. All 3 execs are kind of pushing for different tools. The CEO wants mixed panels to do everything.
59 00:06:50.640 ⇒ 00:07:11.990 Robert Tseng: the you know President doesn’t care about mixed panel, just, you know, traditional finance. Guy just wants to see everything in pretty much in like spreadsheets or like looker. He can. He can accept. And then there’s a marketing person who, just like is really held that on on Looker. And so I think a lot of it on my end is like kind of setting
60 00:07:12.290 ⇒ 00:07:27.550 Robert Tseng: kind of just educating and setting expectations on where we’re gonna have reports live in different places. But there’s a lot of overlap between these different like reporting systems right now. So I think I’ll just kind of like call that out at a high level.
61 00:07:28.120 ⇒ 00:07:29.697 sahanaasokan: Okay, thanks for letting me know.
62 00:07:30.505 ⇒ 00:07:44.169 sahanaasokan: I I guess I’m just curious. I don’t know if we had the conversation. I look. I’m seeing your objectives, but from like a priority list. Have they kind of had any suggestions or opinions on, like what they want done immediately.
63 00:07:45.050 ⇒ 00:07:48.624 Robert Tseng: Yeah, so okay, we’ll jump to that. That’s a good question.
64 00:07:49.100 ⇒ 00:07:51.459 Robert Tseng: so yeah, I think, we.
65 00:07:51.570 ⇒ 00:08:00.959 Robert Tseng: I’m gonna put this in front of them, like, I’m having a chat with the leadership in a couple of hours. And so I’m gonna make sure that these are the objectives that they’re okay with us going after?
66 00:08:02.330 ⇒ 00:08:06.960 Robert Tseng: I think there, there hasn’t really been like any
67 00:08:08.340 ⇒ 00:08:20.529 Robert Tseng: like. The only directive that I received was like, Hey, we want to get marketing analytics right. And I think there’s just like, you know, they’re they’re a growth stage company at this point, like they just wanna be able to
68 00:08:21.040 ⇒ 00:08:29.739 Robert Tseng: all all things reporting to support their performance. Marketing team like that’s their biggest priority on the reporting side, and that kind of aligned the objective to just the marketing piece.
69 00:08:29.820 ⇒ 00:08:36.850 Robert Tseng: They’re also doing stuff like operationally. There’s operational financial reporting that needs to be done as well.
70 00:08:37.144 ⇒ 00:09:06.180 Robert Tseng: But I’m trying to not like distract them too much. And just try to like, keep basically 2 objectives, one that’s more like front facing that the execs can see. And then one that’s more back end. This is like the info work and the process, the the data management work that we need to do in order to speed up the development for them. So that’s kind of why I structured it this way. But yeah, these are really the main pain points that I was like kind of hearing consistently across people. The past past couple of weeks.
71 00:09:08.270 ⇒ 00:09:09.670 sahanaasokan: Okay. Thank you.
72 00:09:12.790 ⇒ 00:09:13.490 Robert Tseng: Yeah.
73 00:09:13.750 ⇒ 00:09:23.020 Robert Tseng: okay. So I think these slides kind of came out later this morning. I just kind of reviewed them. So I think I’ll probably spend time here and just kind of align us on the recommendations.
74 00:09:23.543 ⇒ 00:09:25.810 Robert Tseng: Yeah, I, you know, feel free to.
75 00:09:26.090 ⇒ 00:09:36.740 Robert Tseng: They could give your 2 cents. But so this, each slide is like the objective, the same thing that was measured here, and then kind of like the recommendations that I think will get us to these results.
76 00:09:37.575 ⇒ 00:09:43.280 Robert Tseng: So yeah, one like biggest priority for them is like they have
77 00:09:43.580 ⇒ 00:09:57.520 Robert Tseng: different pockets of reporting already, but they want to be able to see it all in one place. And so there’s like this consolidation of new and old dashboards that they already have in various vendor tools, north theme they use for attribution, reporting
78 00:09:58.072 ⇒ 00:10:02.790 Robert Tseng: they already have a looker dashboard that was doing like Cac Cac reporting
79 00:10:03.360 ⇒ 00:10:11.870 Robert Tseng: but that wasn’t at the product level. And so I think there’s like it’s missing granularity. And that, I think there’s yeah, there’s a
80 00:10:12.470 ⇒ 00:10:13.290 Robert Tseng: oh.
81 00:10:13.450 ⇒ 00:10:30.809 Robert Tseng: I I think I owe it to this team to kind of like translate, like, what are all the things that we want to keep from the existing dashboard? And then we can I? I would say that this is probably me and Sahana to kind of like work together on designing what this new dash is gonna look like. And then where is it gonna live.
82 00:10:33.690 ⇒ 00:10:36.330 Robert Tseng: so I think this would probably be the lowest hanging fruit here.
83 00:10:38.730 ⇒ 00:10:40.820 Robert Tseng: Yeah. And then, as far as like.
84 00:10:41.170 ⇒ 00:10:48.399 Robert Tseng: there’s all kinds of like data inconsistencies. Right? And so I think this is really just like running through our kind of like typical.
85 00:10:48.540 ⇒ 00:11:00.379 Robert Tseng: just like analytics modeling process. So making sure that the tracking plan, even data modeling is solid. They have too many like events right now, and so kind of like
86 00:11:00.500 ⇒ 00:11:06.829 Robert Tseng: I don’t want us to focus on like feeding them up and whatever removing them, but at least like getting organized around.
87 00:11:07.080 ⇒ 00:11:22.570 Robert Tseng: Okay, like the CEO wants to see a very clear like full funnel report on like user journey from pre sales, post sale and subscription. He can’t see that right now, and nobody really is able to wrangle the events in in a way to like present that
88 00:11:23.010 ⇒ 00:11:35.479 Robert Tseng: so I think that’s probably not hard. It’s just like we’re already probably tracking those events, but trying to pick which are the ones that we that we want to build the report around. And yeah, just kind of getting organized there.
89 00:11:35.650 ⇒ 00:12:03.280 Robert Tseng: I’ll call out for nico because they have so many tools. I think one high leverage like thing that we need to be doing for them as well is to do some sort of like cost monitoring like we did for Javi. So we’re not gonna do any vendor negotiations and stuff like that for them yet. But at least like I want to like, have a single place where we can kind of tell them how much they’re paying, you know, monthly for these tools, and then have some of these conversations about.
90 00:12:03.350 ⇒ 00:12:20.299 Robert Tseng: hey? In the future, maybe a quarter from now. If we want to move, if we want to change their data, stack. I think we can. We can have those conversations about like, hey? You’ll save money if you move off segment, and you use 5 chat or whatever, and we can try to play around with with that as well.
91 00:12:20.480 ⇒ 00:12:26.780 Uttam Kumaran: Was this a Google sheet, the one we built for Javi? And like, What’s the artifact for this one? Are we gonna leave leave this in notion.
92 00:12:27.576 ⇒ 00:12:43.880 Robert Tseng: I think it’s up to our discretion. I want to share this notion with them, too. Probably I won’t share with them today yet, just because it’s not. Yeah, I don’t. I don’t really think they’ll look into it, anyway. But yeah, I guess I want to leave it to to our, to our team to decide like what artifact it should be. I know they don’t have this yet. Yeah.
93 00:12:43.880 ⇒ 00:12:59.890 Uttam Kumaran: I think this is going to be right alongside. Basically, a bunch of planning artifacts like one will work on a Kpi sort of spreadsheet. I I honestly, I maybe we just do some Google sheets and like, kind of just make the decision. And we can think about something more branded later. But
94 00:13:00.020 ⇒ 00:13:04.827 Uttam Kumaran: one, we’re gonna have a kpi spreadsheet, which is just like what are the Kpis? How we’re tracking sources?
95 00:13:05.468 ⇒ 00:13:08.810 Uttam Kumaran: We. I think we talked a little bit about that. Yep, exactly.
96 00:13:08.810 ⇒ 00:13:12.119 Robert Tseng: Yeah, so yeah, I want something like this in our in our spreadsheet.
97 00:13:12.550 ⇒ 00:13:13.879 Robert Tseng: Yeah, I think we.
98 00:13:13.880 ⇒ 00:13:19.440 Uttam Kumaran: We just make in a separate, we just in a separate sheet. We just have the cost per system.
99 00:13:19.550 ⇒ 00:13:20.145 Robert Tseng: Yep.
100 00:13:21.020 ⇒ 00:13:25.900 Uttam Kumaran: So let’s just plan that, Nico, if you want to start that, and then just go ahead and like, list
101 00:13:26.030 ⇒ 00:13:28.990 Uttam Kumaran: the sources systems that we already know.
102 00:13:29.524 ⇒ 00:13:32.220 Uttam Kumaran: Then I can. I can help kind of like guide on like
103 00:13:32.530 ⇒ 00:13:38.749 Uttam Kumaran: the end. State there and then. Probably, Luke, I’ll have you build out the Kpi stuff, too.
104 00:13:40.830 ⇒ 00:13:43.830 Uttam Kumaran: So great. And then basically, they have one place to go for that.
105 00:13:44.080 ⇒ 00:13:49.570 Uttam Kumaran: If we can’t, I don’t. Wanna if it’s the notion is too complicated for now let’s just do the sheets. I want to get that to them
106 00:13:49.900 ⇒ 00:13:52.110 Uttam Kumaran: soon, cause that’s the easy, easy thing.
107 00:13:52.750 ⇒ 00:13:59.490 Robert Tseng: Yeah, I think spreadsheets will work. They’re they’re they’re familiar with that rent for now we can keep running notion for us internally. And but yeah.
108 00:14:00.440 ⇒ 00:14:06.629 Robert Tseng: okay, and then I think this is more for Luke. I don’t know. This is a bit vague right now, but basically
109 00:14:07.120 ⇒ 00:14:10.489 Robert Tseng: I’m hoping to plug you in the next week or 2. And
110 00:14:10.860 ⇒ 00:14:38.010 Robert Tseng: you know, I think the D needs help like getting to product level like segmentation. So we’ve done this for for Joby, and but they just haven’t been able to do it for for them themselves yet. So they’re not using shopify data. It’s it’s going. It’s it’s called bask bask is basically shopify for like health based Ecom companies. So I I mean, it may take you some time to kind of get used to the schema there, but it should be.
111 00:14:38.180 ⇒ 00:14:51.989 Robert Tseng: for all intents and purposes like should be pretty pretty similar. So I think that. That’s that’s kind of a goal on the modeling side to at least be able to tell them by the end of month, one like, Hey, we’ve given you product level segmentation across all your metrics.
112 00:14:55.210 ⇒ 00:14:56.110 Robert Tseng: Cool?
113 00:14:57.275 ⇒ 00:15:22.670 Robert Tseng: Last thing on this. Yeah. I think mixed panel. I think that’s just like the the CEO’s bias. Towards that I can probably own the mixed panel like requirements. And yeah, just like the the building, the reporting side for now. So I think this is really gonna just be enabled by the work that we’re doing up here. Mixed panel development super. Quick. I can. I would see this from a timeline perspective happening towards the end of the 1st month.
114 00:15:24.140 ⇒ 00:15:29.999 Robert Tseng: Yeah. And then we’re gonna just keep continuing to gather requirements for other custom reporting.
115 00:15:30.450 ⇒ 00:15:53.149 Robert Tseng: basically, the way that I see it is that this this funnel report enables us to see, like the full customer lifetime. Then every stage there’s going to be drop off. And the the team the team wants to be able to, you know, drive some sort of conversion rate optimization there. So whether it’s getting more sales in the beginning, driving more renewals, finding opportunities to upsell across products like
116 00:15:53.200 ⇒ 00:16:12.509 Robert Tseng: those are the types of additional reports, slash dashboards that will kind of complement the life, the full life like the lifecycle like funnel that we’re gonna that we’re gonna put out first.st So yeah, I think I’m gonna try to get us organized around like a timeline for this moving forward.
117 00:16:13.990 ⇒ 00:16:30.080 Robert Tseng: from a kind of like project management perspective just for those of you who aren’t familiar. Yeah, we’re kind of run everything off notion. I think you should have access to this by now. But I basically am building out cards here. So there’s like 3 different tabs. There’s planning stage. So
118 00:16:30.230 ⇒ 00:16:43.239 Robert Tseng: I would say, we can meet, maybe like once a week or something on this, just to discuss kind of like prioritization. And like, if we need, if I need help, kind of defining these requirements, I can.
119 00:16:44.370 ⇒ 00:16:56.800 Robert Tseng: We can kind of work on this Async. The active cards? Yes, it’s just been these so far. So there isn’t really anything that in here other than a couple of things in the backlog that we need to to kick off.
120 00:16:57.327 ⇒ 00:17:04.162 Robert Tseng: But yeah, I’m hoping to just like kind of that will just manage this. A project kind of off of off of this
121 00:17:04.800 ⇒ 00:17:06.000 Robert Tseng: this notion.
122 00:17:06.180 ⇒ 00:17:26.279 Robert Tseng: What’s complicated a bit about this is that they do have an existing data team. They do have a data scientists. Well, this guy’s not a data scientist. He’s just Cro, okay, they have an engineer data scientist. That we may, we’ll have to like, lean on, or like kind of work with pretty closely in the beginning, as we’re kind of getting up to speed.
123 00:17:27.650 ⇒ 00:17:33.509 Robert Tseng: But yeah, so I think I’ll do my best to kind of like manage like the internal external comms
124 00:17:33.930 ⇒ 00:17:40.779 Robert Tseng: just for now, like no one’s gonna be client facing. I think we’ll just try to get organized internally. I’m gonna try to
125 00:17:41.860 ⇒ 00:18:02.970 Robert Tseng: set the right expectations with the client and then give us. I don’t want everyone to have access to you guys and overwhelm me with questions. I don’t think that’s a good use of our time. I’d rather kind of buffer or triage that so just kind of give me another, probably week to figure out how to introduce you to the to the main stakeholders that we’ll need to be working with to get to get stuff done.
126 00:18:04.550 ⇒ 00:18:05.210 Uttam Kumaran: Cool. Yeah.
127 00:18:05.210 ⇒ 00:18:19.669 Uttam Kumaran: I think I think we’ll start to also build out like I already, there’s already come clear, like data engineering tasks and data modeling stuff that we can build out the tasks for. One is like organization on bigquery side. Implementing dbt, implementing github.
128 00:18:19.840 ⇒ 00:18:25.229 Uttam Kumaran: moving the shape queries all that stuff like we’ll just create boilerplate tickets for
129 00:18:25.858 ⇒ 00:18:32.319 Uttam Kumaran: and then I think we can also just start to whatever tickets we have on the event side
130 00:18:32.420 ⇒ 00:18:36.930 Uttam Kumaran: for Sahana or the analytics side. We can just start to create boilerplate tickets for
131 00:18:37.379 ⇒ 00:18:41.149 Uttam Kumaran: and then get a sense from you on. When we can get access, to start to do those.
132 00:18:41.870 ⇒ 00:18:47.690 Robert Tseng: Okay, cool. That sounds good. Let me just kind of spend the last couple of minutes chatting through the second objective.
133 00:18:48.153 ⇒ 00:18:55.249 Robert Tseng: Yeah. So thank you, Tom, for filling this in. I kind of just left these all yellow, because I’m not really sure like what’s reasonable to commit to
134 00:18:56.680 ⇒ 00:19:09.000 Robert Tseng: yeah, I kind of took out one of the sections that was about like documentation and stuff. Because I just felt like, you know, that’s not really something they probably care about, and we didn’t really have any like clear. I felt like there was redundant recommendations with what we had here already.
135 00:19:09.625 ⇒ 00:19:26.224 Robert Tseng: So yeah, I think, really reducing reporting errors is something I want to push on like, hey, if you let us do this infrastructure work like and prioritize it, we’re gonna reduce these, like the reporting errors, like the example I gave to Luke earlier. So yeah, I think
136 00:19:26.690 ⇒ 00:19:29.060 Robert Tseng: probably the deliverable would be like
137 00:19:29.570 ⇒ 00:19:43.880 Robert Tseng: by the end of like the 1st 1st month we kind of do what we did with Javi, and just give like an end to end like showcase of just like walking through. This is how the data flows from X to Y to Z, and like, just kind of
138 00:19:44.050 ⇒ 00:19:49.289 Robert Tseng: yeah, yeah. Hope, just like, Intro. Introduce that on the on the, on the marketing reporting side.
139 00:19:49.706 ⇒ 00:19:56.980 Robert Tseng: I think that would probably be a good way to like get more buy in on like this new process that we’re introducing.
140 00:19:57.606 ⇒ 00:20:01.040 Robert Tseng: So yeah, that’s kind of how I thought about the 1st part
141 00:20:01.644 ⇒ 00:20:06.570 Robert Tseng: the second part, I think. Yeah, I guess
142 00:20:07.910 ⇒ 00:20:10.209 Robert Tseng: maybe we thought maybe kind of you want to just talk me through.
143 00:20:10.210 ⇒ 00:20:12.090 Robert Tseng: Yeah, you were thinking, here, yeah.
144 00:20:12.330 ⇒ 00:20:33.359 Uttam Kumaran: Yeah. So the main stuff here is one like off the bat, we’ll implement like role based access control across, like all the different tooling. So basically, they they come to the table with, you know, really pretty good governance over their data. Second, I’m sure they have restrictions. Based on medical data or whatever. So just making sure that those are implemented.
145 00:20:33.490 ⇒ 00:20:49.300 Uttam Kumaran: 3rd is just like, okay, how do they actually get access to it? Like, is it through Bi? Is it self service who has access? I know they have a mix of roles. So just making sure that everybody has the right access. And that’s there’s an audit log. And and like, you know, we just basically establish.
146 00:20:49.730 ⇒ 00:20:56.250 Uttam Kumaran: establish that for them. So again, they, there’s technical stakeholders. There’s people that are going to access via bi tools. There’s folks like us.
147 00:20:56.410 ⇒ 00:21:04.359 Uttam Kumaran: So one is like, how do they measure and manage all that? And then also for the 1st piece, you know. The one thing I said is not only just reduce reporting, but track.
148 00:21:04.530 ⇒ 00:21:05.979 Uttam Kumaran: So this is something where for any.
149 00:21:05.980 ⇒ 00:21:06.590 Robert Tseng: Thank you. Got.
150 00:21:06.590 ⇒ 00:21:11.739 Uttam Kumaran: Come up. I want to just make sure that they end up in our notion, tracked like as a bug.
151 00:21:12.400 ⇒ 00:21:23.689 Uttam Kumaran: That way. It’s very clear when we were like cool when we started. We were getting like this many bugs. And now we’re getting this much right right now. I’m sure there’s nobody doing that. It seems like there’s a bunch of like individual people.
152 00:21:24.040 ⇒ 00:21:43.309 Uttam Kumaran: So that’s the one thing that’s I think it’s much needed, you know, on the Pm. Side here is just to make sure that we’re really everything that comes from them as a ticket or a bug gets tracked and tossed in the backlog. The other thing is, look, we, we have a fixed, you know, amount of time that we’re going to be spending on. This doesn’t mean we can’t build up the backlog with a lot of stuff.
153 00:21:43.639 ⇒ 00:22:00.340 Uttam Kumaran: And so that’s the thing I want to also do is any sort of opportunity that we hear that there is a need whether we need a spike or whether we actually have like a pretty well defined problem, we should just track especially around data issues. I would love to track. And then we just try to chase and resolve.
154 00:22:01.950 ⇒ 00:22:06.220 Uttam Kumaran: Right? I’m sure that they there’s nobody sort of doing that proactively right now.
155 00:22:07.470 ⇒ 00:22:32.510 Robert Tseng: Yeah, no, this is all great stuff. And you know as much as I. You know, it’s it’s harder to like visualize like, kind of the work that we’re doing here. I think getting this right is what’s gonna help us to like show that we’re executing, like, you know, 5 x 10 x better than like the existing team. And I think that’s just gonna give us more that we’re gonna have. This is this is what’s gonna really grow, grow our grow, our contract with them if we do this? If we do, if we establish as well.
156 00:22:35.850 ⇒ 00:22:46.089 Nicolas Sucari: Question here communication. Wise, you said you’re gonna introduce us to the key stakeholders. But are we gonna have, like, I mean, as connected slack channel, or something like that.
157 00:22:46.550 ⇒ 00:23:12.709 Robert Tseng: Yeah, I think that’s probably what I want to do. Right now. I’ve just been in their in their slack everyone just pings me directly when they have this analytics channel. That’s just like on fire all the time. I don’t want you guys to see that I think that’s just like not helpful for kind of like staying focused on our objectives. So I need to just kind of set clear expectations with them that yeah, we’re gonna have 1, 1 slack channel that everyone could just like. Talk to things with with us about
158 00:23:13.169 ⇒ 00:23:16.169 Robert Tseng: but I think I’m just a bit like not sure.
159 00:23:17.082 ⇒ 00:23:24.370 Robert Tseng: Oh, yeah, that. Well, yeah, I think whether or not we’ll have like one or 2 channels like, I think that’s something I’m I need to figure out with them.
160 00:23:25.170 ⇒ 00:23:25.920 Nicolas Sucari: Okay.
161 00:23:25.920 ⇒ 00:23:26.540 Robert Tseng: Yeah.
162 00:23:30.630 ⇒ 00:23:34.750 Luke Daque: One more question. Are we like limited in the number of hours?
163 00:23:36.740 ⇒ 00:23:39.700 Luke Daque: To work with them, or like similar to Javi?
164 00:23:40.610 ⇒ 00:23:50.389 Robert Tseng: I would say. We have more hours in Javi. Honestly, I think we just have to decide like what they’re they’re not managing us as closely as Javi was. It was, this is a very different kind of like
165 00:23:50.540 ⇒ 00:24:10.590 Robert Tseng: contract. Javi was like tracking every hour, and we had to do hourly report logs. I don’t think they care anything about that. They just have a budget that they’ve given, that they’ve given me and then I think, who Tom is probably on us internally to kind of decide how many hours we want to put into it, and then we just stand by that. If they want more than we ask for more hours.
166 00:24:11.010 ⇒ 00:24:17.211 Uttam Kumaran: Yeah, so we have. I think I have like a basic guideline. I could give you so for this project, let me just
167 00:24:18.290 ⇒ 00:24:20.480 Uttam Kumaran: Pull this up. Sorry. One second.
168 00:24:20.520 ⇒ 00:24:29.890 Nicolas Sucari: Independently of the fixed amount of hours or hours that we’re spending, we should track everything in 25 everything. Everyone should have access to
169 00:24:30.020 ⇒ 00:24:33.249 Nicolas Sucari: docify client and project Eden, I think.
170 00:24:33.360 ⇒ 00:24:35.009 Nicolas Sucari: And we should track.
171 00:24:35.120 ⇒ 00:24:36.290 Nicolas Sucari: Yeah, everything.
172 00:24:36.650 ⇒ 00:24:47.380 Robert Tseng: Yeah, internally, we should be tracking but yeah, I think just like in in talking about it with them like I I don’t think they? I think they’re probably open to us pushing like. What? What? This, what this looks like.
173 00:24:47.380 ⇒ 00:24:53.289 Uttam Kumaran: Okay, yeah, I would say, I would say, overall like, on this project, we’re probably aiming for like 10 h each.
174 00:24:54.129 ⇒ 00:25:01.579 Uttam Kumaran: Both for Sahana, and for for Luke, I think there’s flexibility like I would say, 5 h on like either side.
175 00:25:02.029 ⇒ 00:25:14.899 Uttam Kumaran: But like sort of aim for that range, I think, you know, as the project starts, it’ll be probably a little bit heavy on the modeling side, and then it’ll sort of slow down a little bit. But I hope that gives some sort of guidance.
176 00:25:16.150 ⇒ 00:25:23.009 Uttam Kumaran: and then, yeah, please, just track on clockify. And then if there’s any questions about going over anything just reach out to reach out to Nico.
177 00:25:25.550 ⇒ 00:25:26.120 Robert Tseng: Cool.
178 00:25:26.220 ⇒ 00:25:53.010 Robert Tseng: Yeah. And I know this is an Async team. So I don’t want us to like we don’t have to wait. Scheduled calls to like there do handle issues. It’s weird, because, like, we’re part time. But they’re the client is full time. And so they’re gonna be pinging us stuff real time, anyway. So if there are any issues like anything, just, you know, use the slack channel if we need to. If we, if I need to meet with anybody. You know, pretty ad hoc, just like, just just let me know.
179 00:25:53.330 ⇒ 00:26:17.449 Uttam Kumaran: Yeah, I think the biggest thing for me. You know. And we’re we’ve we made a lot of improvements to how we’re tracking work in notion. And I think hopefully for work that that’s like doesn’t have code associated with it like some stuff on the analysis side as much as we can track, and notion would be best if if at all. If you have work that’s coming up, and you don’t have time to create a notion page or whatever. Just throw it in slack, and then one of us will get to it.
180 00:26:17.771 ⇒ 00:26:36.379 Uttam Kumaran: With any information that you have. I think the biggest, you know, challenge we’ve had with sometimes the clients who themselves are disorganized. Is it causes us to have a tendency to match their disorganization just because of like. That’s just the way it works. So for us not only to show the amount of work we’re doing, but to show our to show our work.
181 00:26:36.792 ⇒ 00:26:46.050 Uttam Kumaran: The tracking is everything. So no matter what you’re doing, just make sure it’s attached to a ticket. But again, in terms of hours like I’m not. We’re not looking at like
182 00:26:46.170 ⇒ 00:26:53.950 Uttam Kumaran: this ticket took this many hours, or whatever it’s more just like looking at the amount of work. And what type of work so appreciate it in advance.
183 00:26:57.520 ⇒ 00:26:58.170 Robert Tseng: Cool.
184 00:26:58.310 ⇒ 00:27:03.400 Robert Tseng: That’s I think that’s all I wanted to get through. Any other questions.
185 00:27:03.740 ⇒ 00:27:10.109 Uttam Kumaran: Yeah, I think one more thing from my side. You know, we’re we’re planning on having just like one data team meeting per week.
186 00:27:10.210 ⇒ 00:27:28.760 Uttam Kumaran: mainly just to talk about like from a technical standpoint, like everything across the data stack that we’re doing. I’m just gonna host that probably like once a week on like Tuesdays or something. If everybody’s okay, I think it’ll just be me, Luke Sahana and Pius, and we’ll just kind of talk about any blockers in terms of like technical work?
187 00:27:29.151 ⇒ 00:27:33.429 Uttam Kumaran: Hopefully, that meeting is short. For the most part it’ll just be like, how can I
188 00:27:33.600 ⇒ 00:27:35.149 Uttam Kumaran: help out where needed? So.
189 00:27:36.650 ⇒ 00:27:37.310 Robert Tseng: Okay.
190 00:27:38.130 ⇒ 00:27:38.870 Uttam Kumaran: Cool. And yeah.
191 00:27:38.870 ⇒ 00:27:53.539 Nicolas Sucari: Cool. And yeah, apart from that meeting we have the Monday like data team planning meeting that we just scheduled Robert, I’m gonna add you for the 1st ones so that we can discuss like tasks
192 00:27:53.986 ⇒ 00:28:16.659 Nicolas Sucari: for all of the projects. Ideally. At some point you’ll drop that one, and we can manage it only with Luke Sahana. Pay us, maybe, and me. But the idea of that meeting is just to plan the entire week of all of the projects, because we are working in different clients. So we know, like, what are the priorities and what we are aiming to achieve that every week. Okay.
193 00:28:16.980 ⇒ 00:28:18.589 Robert Tseng: Yeah, okay, that sounds good.
194 00:28:18.590 ⇒ 00:28:29.530 sahanaasokan: Okay? So question. So just to make sure I understand properly, we’ll have a planning meeting next week, right to talk about like the action items for each of us.
195 00:28:29.530 ⇒ 00:28:34.949 Robert Tseng: Yeah, we’ll do this. We’ll do like I’ll actually assign cards and stuff on Monday, I guess, or whatever that meeting is. Yeah.
196 00:28:35.140 ⇒ 00:28:35.520 sahanaasokan: Awesome.
197 00:28:35.520 ⇒ 00:28:54.309 Nicolas Sucari: Exactly. That’s on my and what what I was telling about the meeting for Tuesday or other day in the week is more like specifically to talk about data engineering stuff or analytics on how to do to do things. If you don’t need to discuss anything with him.
198 00:28:54.769 ⇒ 00:29:09.149 Nicolas Sucari: Apart from that, Robert. I’ll create the timelines with these objectives and the weeks that you are aiming there in the data fields. But let me know if you need anything else in notion, I’ll I’ll create it. Okay.
199 00:29:09.550 ⇒ 00:29:24.469 Robert Tseng: Okay, yeah, that sounds good. And Nico, you can. Yeah, phase like, these are kind of fluid, you know. Let’s just like, kind of map it out over over a quarter. So let’s do a 3 month, timeline, and we’ll we’ll we’ll figure out how to arrange it. Okay, thanks.
200 00:29:24.630 ⇒ 00:29:25.410 Nicolas Sucari: Okay.
201 00:29:25.890 ⇒ 00:29:26.630 Uttam Kumaran: Thanks guys.
202 00:29:26.910 ⇒ 00:29:27.460 Robert Tseng: Thanks. Everyone.
203 00:29:28.150 ⇒ 00:29:28.690 Uttam Kumaran: Bye.
204 00:29:28.980 ⇒ 00:29:29.510 Robert Tseng: Bye.
205 00:29:29.680 ⇒ 00:29:30.610 Nicolas Sucari: Thanks. Bye-bye.