Meeting Title: Zoom Meeting Date: 2025-03-12 Meeting participants: Uttam Kumaran, Demilade Agboola, Robert Tseng, Awaish Kumar
WEBVTT
1 00:01:40.760 ⇒ 00:01:42.815 Uttam Kumaran: Okay, I messaged. Robert.
2 00:01:46.480 ⇒ 00:01:49.910 Uttam Kumaran: is there anything else we want to chat about? Maybe before they get here.
3 00:02:02.560 ⇒ 00:02:03.400 Demilade Agboola: Oh, that’s okay.
4 00:02:03.400 ⇒ 00:02:05.979 Demilade Agboola: Nothing comes to mind.
5 00:02:06.180 ⇒ 00:02:10.739 Uttam Kumaran: Okay, what do you think about the bigquery like? Dbt. Mart setup?
6 00:02:12.890 ⇒ 00:02:13.480 Uttam Kumaran: The only
7 00:02:13.480 ⇒ 00:02:19.350 Uttam Kumaran: the only thing I, the only thing I have is like, we’re not removing models that get renamed.
8 00:02:20.570 ⇒ 00:02:21.390 Demilade Agboola: Yeah.
9 00:02:23.420 ⇒ 00:02:24.850 Uttam Kumaran: Do that? What do I do?
10 00:02:27.730 ⇒ 00:02:29.769 Uttam Kumaran: Should I like just trunk? Should I just like.
11 00:02:30.430 ⇒ 00:02:32.690 Uttam Kumaran: clean everything out and then rerun it.
12 00:02:34.350 ⇒ 00:02:37.700 Demilade Agboola: Yeah, so that’s potentially what we could do. So we could drop.
13 00:02:37.980 ⇒ 00:02:53.180 Demilade Agboola: 1st of all, we have multiple Mods. By the way, so like we actually will have stg Mods appear multiple times. So sometimes when I search for a particular model like 3 or 4 different things up here, and it’s a bit like weird site to know which one to use.
14 00:02:53.947 ⇒ 00:02:57.223 Demilade Agboola: So we should have a cleanup process.
15 00:02:59.440 ⇒ 00:03:07.849 Demilade Agboola: a process where we drop all like maybe the the mask that we have created, and then on the next dbt. Run, it creates the new one, and we have everything set up
16 00:03:07.990 ⇒ 00:03:12.059 Demilade Agboola: in a cleaner way. But we should think of a way to automate it. Basically.
17 00:03:13.750 ⇒ 00:03:16.720 Uttam Kumaran: Okay, okay, I’ll think about it. I’ll ask some folks.
18 00:03:17.357 ⇒ 00:03:23.002 Uttam Kumaran: yeah, I guess we can spend this time today just talking through that revenue issue and any other items.
19 00:03:24.760 ⇒ 00:03:25.410 Robert Tseng: Okay.
20 00:03:25.410 ⇒ 00:03:28.259 Uttam Kumaran: Or you guys, you and Robert, if you want to take it away.
21 00:03:28.930 ⇒ 00:03:34.060 Robert Tseng: Yeah, sure. I mean, I know kind of commented on some stuff. So I’ll just.
22 00:03:34.970 ⇒ 00:03:36.384 Robert Tseng: you know, I might even just
23 00:03:37.600 ⇒ 00:03:42.612 Robert Tseng: share my slide the rest and just go through these on my line. So
24 00:03:43.480 ⇒ 00:04:04.789 Robert Tseng: yes, I think, you guys are aware, like this profitability dashboard. I don’t know if you guys can see me when I blow that up. But yeah, basically, this was built on what like pro like cap by product, by product, whatever. Whichever one that was. Reason was that it has membership plan filters. Yeah, we know that the total revenue here is off.
25 00:04:04.880 ⇒ 00:04:24.320 Robert Tseng: You called out that end revenue seems off. This is actually not total revenue. This is just revenue from new customers, and the Karna fees only impact membership plans. I think quarterly, 6 month yearly or something. So we we take 5% off of those. That’s that’s why the logic’s there. So I actually think.
26 00:04:24.320 ⇒ 00:04:24.690 Demilade Agboola: That’s okay.
27 00:04:24.690 ⇒ 00:04:25.340 Robert Tseng: Okay.
28 00:04:25.960 ⇒ 00:04:33.349 Demilade Agboola: What I’m what I’m saying is total revenue. Because I looked at the card dress. Right now. Total revenue is calculated using N revenue Klana.
29 00:04:34.910 ⇒ 00:04:36.400 Demilade Agboola: That is the problem.
30 00:04:36.740 ⇒ 00:04:42.669 Demilade Agboola: And because N revenue planner is calculated using first, st like I could let me quickly share my screen.
31 00:04:42.910 ⇒ 00:04:43.850 Robert Tseng: Yeah, yeah.
32 00:04:48.560 ⇒ 00:04:57.959 Demilade Agboola: 2 shit alright. So I, because it was I dove into the dashboard.
33 00:04:58.210 ⇒ 00:05:01.610 Demilade Agboola: I clicked on. Total revenue, hopped into the tab.
34 00:05:02.090 ⇒ 00:05:09.520 Demilade Agboola: and I can see that this revenue is the sum of N revenue planner, and I dove into that.
35 00:05:09.730 ⇒ 00:05:13.770 Demilade Agboola: and I can see that that is a function of this.
36 00:05:14.250 ⇒ 00:05:16.980 Demilade Agboola: And I was like, Okay, so what is N revenue itself?
37 00:05:17.470 ⇒ 00:05:23.239 Demilade Agboola: And when I go to end revenue and I look at it, it is
38 00:05:24.490 ⇒ 00:05:32.339 Demilade Agboola: 1st time revenue. So we’re we’re defining total revenue as a function of 1st time revenue, which is sort of what I was trying to say.
39 00:05:32.960 ⇒ 00:05:39.789 Robert Tseng: Okay, yeah, I mean, that’s that’s obviously wrong. But if we were to actually update it with the right definition, does it actually match
40 00:05:40.100 ⇒ 00:05:45.080 Robert Tseng: back transactions, product sales. Summary, right? Cause. It’s showing 14 million.
41 00:05:45.320 ⇒ 00:05:51.520 Robert Tseng: You you’re saying it should be 64 million that you know. That seems more right to me. So.
42 00:05:52.250 ⇒ 00:06:04.710 Demilade Agboola: Yeah, but it it won’t exactly, especially if we add the, you know, 95% off on the membership plans. But yeah, it will be definitely much closer to the 64 million. Once we change the reference to end revenue
43 00:06:05.536 ⇒ 00:06:09.409 Demilade Agboola: or 1st time revenue, if you actually just tied to the actual total revenue.
44 00:06:09.570 ⇒ 00:06:12.149 Demilade Agboola: This column of the we should be fine.
45 00:06:13.470 ⇒ 00:06:14.210 Robert Tseng: Okay.
46 00:06:14.500 ⇒ 00:06:30.039 Robert Tseng: So if it’s not gonna match, and we want to just keep this Cac my product table, I thought we were not maintaining this model, which is why we were trying to move everything over to pack transactions or product sales summary basically adding membership plans and product sales summary.
47 00:06:31.890 ⇒ 00:06:41.549 Demilade Agboola: Yeah. So this is just like the cause we’re talking about the products, profitability dashboard. And why? It’s not working. So my guess is
48 00:06:41.730 ⇒ 00:06:47.229 Demilade Agboola: a similar logic is being applied to our because this cut this way isn’t. This is cut by product 2,
49 00:06:47.470 ⇒ 00:06:48.280 Demilade Agboola: right?
50 00:06:49.023 ⇒ 00:07:09.080 Demilade Agboola: And it still gives us about 64 million, if you sum up everything just directly. So my my guess is the same. Like. Similar logic has been applied somewhere in our like dashboards and everything, and that’s why our what it’s been thrown off. But if we use product sales summary, it would still be quite similar, because I’ve done the sum of
51 00:07:09.860 ⇒ 00:07:15.259 Demilade Agboola: of like the revenues, and there you’ll be getting about 64.
52 00:07:15.650 ⇒ 00:07:22.579 Robert Tseng: Right. I’m just saying that the reason why they used tech by product is to have the membership plan filter.
53 00:07:23.560 ⇒ 00:07:25.359 Awaish Kumar: But otherwise it is.
54 00:07:25.360 ⇒ 00:07:26.030 Robert Tseng: Yes, it’s.
55 00:07:27.422 ⇒ 00:07:40.903 Awaish Kumar: Yeah, like as we were are working on adding this membership plan field in production summary, I’ve shared a sheet in the slack channel like under our like the the thread
56 00:07:41.500 ⇒ 00:08:09.329 Awaish Kumar: where I’m showing that, like the the difference between the membership plan field which is coming from bus orders and the membership plan field which is coming from product mapping mapping sheet. So it shows clear differences how how the data is different. And then we can share it with Aiden team to get their feedback on which one is correct, or they might need to fix the data quality issue in in there.
57 00:08:11.490 ⇒ 00:08:15.600 Robert Tseng: Yeah. So I’ve seen that sheet. Let me. Just
58 00:08:18.100 ⇒ 00:08:20.140 Robert Tseng: this is the sheet that you’re talking about.
59 00:08:21.100 ⇒ 00:08:21.780 Robert Tseng: Hold on.
60 00:08:22.760 ⇒ 00:08:30.810 Robert Tseng: This is what we currently use. And this is what we would use if we use if we switch to product mapping.
61 00:08:31.020 ⇒ 00:08:33.470 Robert Tseng: Is that correct like, how how should.
62 00:08:33.470 ⇒ 00:08:43.930 Awaish Kumar: What I’m saying is that so? Cake by product is using bus membership schedule and and the product sales summary is using membership schedule.
63 00:08:44.585 ⇒ 00:08:56.459 Awaish Kumar: Yes. And so what book called out when he was working on this he he said that when we are using membership schedule I cannot see the yearly plan.
64 00:08:56.630 ⇒ 00:09:02.490 Awaish Kumar: So you can see that we don’t have any yearly plan label for the membership schedule
65 00:09:04.630 ⇒ 00:09:32.160 Awaish Kumar: and and on the other side, we see that there is basically the yearly plan. But it’s just like 8 43 orders. And for most of the order is just null. So it’s clearly a a data quality issue in bask orders. So we cannot directly use that one. So we just have to confirm that for them, like the membership schedule which is coming from product mapping, is it? Is it up to date? We don’t have a yearly level. But is that?
66 00:09:32.650 ⇒ 00:09:37.459 Awaish Kumar: Is that what they agree with or like? Is there something to fix on their side?
67 00:09:39.180 ⇒ 00:09:44.756 Robert Tseng: Okay. But even if I were to hand this to them, they’re just gonna look at this and
68 00:09:45.260 ⇒ 00:09:50.740 Robert Tseng: I don’t think they’re I don’t. I don’t think they would know like I I think but I I guess
69 00:09:51.670 ⇒ 00:10:18.659 Robert Tseng: I mean I can send. I can send this to them, but I’m kind of like I’m putting myself in Rebecca’s shoes, and I’m looking at this, and I’d be like, well, what do I do with this like? How do I actually validate this? We we would. We need to. We kind of need to share, share that with them, or I don’t know. She needs to go into bask or ask the pharmacy like I don’t know we need to like. I mean, I think that’s just. It’s not clear like what the action is for for them. They’ll look at this, and it’ll be like, Yeah, something looks off. But like
70 00:10:19.010 ⇒ 00:10:22.219 Robert Tseng: I’m not really sure what to advise them to do off of this.
71 00:10:22.220 ⇒ 00:10:27.410 Awaish Kumar: Yeah, we can share some samples. For example, where the
72 00:10:27.955 ⇒ 00:10:48.139 Awaish Kumar: for example, an order where the bask membership schedule shows null, and the other one from product mapping shows some other label. And we can say, Okay, see? Like these 3, 4, 5 orders we have, and which which field you think think should be the correct one for these orders, or something like that? We can like share those sample as well.
73 00:10:48.540 ⇒ 00:10:54.470 Robert Tseng: Yeah, let’s do that. Maybe we’ll pick a sample from each of these different areas. So yeah.
74 00:10:54.470 ⇒ 00:11:01.180 Awaish Kumar: I will create separate sheets in the same spreadsheet. I will create separate sheets for each of.
75 00:11:02.320 ⇒ 00:11:04.009 Robert Tseng: Yeah, yeah, just a separate tab.
76 00:11:04.010 ⇒ 00:11:05.790 Awaish Kumar: And sure you can speak with them.
77 00:11:06.030 ⇒ 00:11:06.580 Awaish Kumar: Yep.
78 00:11:06.580 ⇒ 00:11:08.829 Robert Tseng: Great. I think that that sounds good.
79 00:11:11.062 ⇒ 00:11:31.310 Robert Tseng: Okay, well, so yeah, I mean, kind of tying that back to Dave’s point, like, yeah. So this is this is also why I’m asking, which model are we using? Because if we use Cac by product, then the membership plan spread is actually looks pretty different than if we were to use product sales summary or or not. Sorry. It’s not product sales summary. It’s just
80 00:11:32.610 ⇒ 00:11:55.930 Robert Tseng: Basque orders versus we going through our mapping. So like, it seems like right now, we’re using this approach, which seems off because doesn’t have anything yearly or or anyway, we we just like I think there’s there’s still like a missing step here on like I don’t know if I trust the the membership plan split so it seems like.
81 00:11:55.930 ⇒ 00:11:56.490 Demilade Agboola: Cool.
82 00:11:57.480 ⇒ 00:11:58.800 Robert Tseng: Let me see.
83 00:11:59.180 ⇒ 00:12:00.030 Robert Tseng: Yeah.
84 00:12:01.100 ⇒ 00:12:05.970 Awaish Kumar: She. The the web field which is being used in Cac by product is the bask membership schedule.
85 00:12:06.440 ⇒ 00:12:14.819 Awaish Kumar: And using this, they are trying to get the ratio and then multiply it with, add span to get some, add span for each label
86 00:12:15.000 ⇒ 00:12:23.150 Awaish Kumar: so, and it. It doesn’t make sense, because 200,000 orders are just null, so like it did.
87 00:12:23.420 ⇒ 00:12:28.429 Awaish Kumar: They are like, like, not in, even in like, in the in.
88 00:12:28.640 ⇒ 00:12:37.319 Awaish Kumar: When we are doing this spread, we’re just ignoring these 200,000 orders. We don’t know what the membership schedule is. So it’s it’s happening in the cake by product
89 00:12:37.680 ⇒ 00:12:40.160 Awaish Kumar: like this table.
90 00:12:41.410 ⇒ 00:12:49.240 Demilade Agboola: Yeah. So what I was, I was trying to say is that, yeah, it’s currently what they use in the past membership schedule. I think that
91 00:12:49.990 ⇒ 00:12:51.010 Demilade Agboola: because
92 00:12:51.170 ⇒ 00:12:58.420 Demilade Agboola: it’s been yearly has a business impact of like a 5% off. Not huge, but it. There’s a business impact to it.
93 00:12:58.900 ⇒ 00:13:03.499 Demilade Agboola: Long term. What I’m thinking, what might be helpful is that
94 00:13:03.870 ⇒ 00:13:11.659 Demilade Agboola: we use the past membership schedule. But the null values we map it using the membership schedule so that provides even more information.
95 00:13:11.800 ⇒ 00:13:17.240 Demilade Agboola: so we can say, out of 200,000 we would only end up with about 146. No.
96 00:13:17.510 ⇒ 00:13:21.950 Demilade Agboola: so I think that might be a better way to be able to map it, and then
97 00:13:22.980 ⇒ 00:13:25.760 Demilade Agboola: potentially, that might be what we’ll do or consider doing.
98 00:13:26.220 ⇒ 00:13:38.460 Robert Tseng: Okay, I mean, my take on. This is membership schedule was not introduced until this year, so pretty much all the orders like it’s not surprising to me that in bask they they were never labeled with anything before.
99 00:13:38.620 ⇒ 00:13:51.379 Robert Tseng: We recently moved to this, the mapping sheet kind of helps backfill previous orders, which is why the spread is different. I would assume that these numbers add up to whatever is here. So that is fine to me.
100 00:13:52.072 ⇒ 00:13:56.749 Robert Tseng: I guess, like, or actually, it doesn’t really add up, it does. Yeah, so
101 00:13:57.256 ⇒ 00:14:12.839 Robert Tseng: but like, for these yearly orders, are, they actually yearly is kind of like we need. We need them to tell us like, why are these coming in as yearly? But then, through our mapping sheet, we see them split up in this way. So
102 00:14:13.380 ⇒ 00:14:34.479 Robert Tseng: it, it is like a mix of this is what we actually get from bask. This is what the mapping sheet that the pharmacy team needs to maintain like they have to help us to break this out into something that is actually what they what they use. Because we can’t just use the Basque source.
103 00:14:40.050 ⇒ 00:14:45.580 Robert Tseng: I think we’re we’re not like disagreeing. I think we’re kind of saying similar things. But I feel like.
104 00:14:45.820 ⇒ 00:14:51.809 Robert Tseng: Yeah, I think we need to just keep that in mind like where each of these is coming from.
105 00:14:52.000 ⇒ 00:15:02.530 Robert Tseng: This is this is customer maintained like this is customer managed like client managed. It’s a single Google sheet that needs to be updated from their from their side.
106 00:15:03.290 ⇒ 00:15:11.959 Robert Tseng: We don’t know how they maintain it or whatever they they tell us that it only changes once a quarter. But I don’t know if that’s really true, based on what we’re seeing in the data.
107 00:15:13.087 ⇒ 00:15:23.740 Robert Tseng: And then this is just straight from there, from from bask and yeah, we we kind of need both working together in order to get the right spread.
108 00:15:26.852 ⇒ 00:15:40.310 Robert Tseng: Okay, so sounds like, yeah. Wish if we can get that, send over for clarification. That’s fine. I think that buys us a little more time on the profitability dash. Assuming that we, we get the, we get our answer to this.
109 00:15:41.530 ⇒ 00:15:52.400 Robert Tseng: yeah, are we going to update the Cac by product model? Or are we going to change the model to a different model and have that whole dashboard be redone? Because that entire
110 00:15:53.420 ⇒ 00:15:56.140 Robert Tseng: built off of gap by product.
111 00:15:57.050 ⇒ 00:16:01.999 Awaish Kumar: I like. I think we are going to add this membership plan field in product sales, summary.
112 00:16:02.960 ⇒ 00:16:07.959 Robert Tseng: Okay? So then, we end up just switching this to product sales summary.
113 00:16:08.740 ⇒ 00:16:15.910 Robert Tseng: I believe that we could calculate everything from here using the product sales summary. It’s just that we didn’t have the membership plan field. That was.
114 00:16:18.140 ⇒ 00:16:32.820 Robert Tseng: I’m I’m okay with that. And yeah, that’s probably once we’re once we’re clear on that. And we have that model updated. I will have James kind of go and update kind of recreate this dash with the product sales summary model. I think that’s the way forward.
115 00:16:36.830 ⇒ 00:16:52.870 Robert Tseng: So cac, by product, that’s a legacy model, right? We’re not maintaining it. We’re not making any changes to it. We can, if if we need to pull anything else over like membership plan, or I don’t know if there was anything else in that model that we needed to bring over. But
116 00:16:53.220 ⇒ 00:16:55.459 Robert Tseng: that’s I’m assuming that
117 00:16:55.730 ⇒ 00:17:03.450 Robert Tseng: product sales summary track transactions. And, like, you know, we have a set of models that we do maintain. So I don’t. I don’t want
118 00:17:03.760 ⇒ 00:17:14.310 Robert Tseng: people building dashboards using order details or using tack by product or any anything that’s like a legacy model that we don’t actually maintain.
119 00:17:15.380 ⇒ 00:17:25.539 Uttam Kumaran: So let me, I think this is a great point. We’re literally just talking about something similar. So guys, I have a Pr, that’s basically renames all the legacy stuff that’s 1 option.
120 00:17:26.300 ⇒ 00:17:30.009 Uttam Kumaran: The I, the second option, is just to drop those tables.
121 00:17:32.740 ⇒ 00:17:34.690 Uttam Kumaran: Our 1st option is lighter.
122 00:17:34.890 ⇒ 00:17:37.670 Uttam Kumaran: If I push that, though it’s gonna break anything that’s
123 00:17:37.880 ⇒ 00:17:40.979 Uttam Kumaran: well, it won’t break unless we drop the old ones.
124 00:17:41.130 ⇒ 00:17:45.959 Uttam Kumaran: But basically it’ll be painfully obvious in tableau. What’s legacy?
125 00:17:46.150 ⇒ 00:17:48.799 Uttam Kumaran: Ideally, we get to a point where we can drop.
126 00:17:49.270 ⇒ 00:17:51.969 Uttam Kumaran: But I want that. That decision’s up to both of you guys.
127 00:17:52.950 ⇒ 00:18:07.359 Robert Tseng: I, personally am not comfortable dropping it because of all the issues that we’ve seen so far, and everybody in on the Eden side is still using order details to Qa, our work. So until we’re confident that, like our models.
128 00:18:07.540 ⇒ 00:18:21.569 Robert Tseng: are in a better place, then that that’s the case. What I do actually like about order details is that it is like a 1 big table that, like we don’t need to maintain so many different models. It’s just like a single flat table
129 00:18:21.780 ⇒ 00:18:27.799 Robert Tseng: that I can that we can use to build a lot of stuff on top of. I mean, that’s kind of how I
130 00:18:28.220 ⇒ 00:18:45.449 Robert Tseng: basically did it at Ruggle. I didn’t really have to do all this other complicated sub mart sub model stuff. And it seemed fine for us. So like, I don’t know. Are we over complicating it by creating a separate model for every use case? Because that we?
131 00:18:45.450 ⇒ 00:18:47.550 Robert Tseng: It’s not much stuff that we have to maintain.
132 00:18:48.320 ⇒ 00:19:00.290 Awaish Kumar: So actually, we build a sales MoD, which is which is like trying to create separate dimension fact tables to to like. We, we have a clear understanding of the data.
133 00:19:00.350 ⇒ 00:19:22.450 Awaish Kumar: But on top of that we have order. Summary table, which I introduced like in in some examples order summary is basically just joins between fact transaction and the dim tables like dim products and the dip shipments. So it’s kind of if you want to use order details, you can directly use order summary, so you don’t have to make those joins yourself.
134 00:19:22.450 ⇒ 00:19:31.400 Uttam Kumaran: It sound it. It sounds like for Demolata in a wish one. We need to do a training with everybody on what tables to use. Second in terms of your point on over engineering.
135 00:19:32.180 ⇒ 00:19:42.340 Uttam Kumaran: The the this feedback is, is helpful, and ideally, we need to build you the summary tables that take the that sort of pain out of figuring out how to join things.
136 00:19:42.460 ⇒ 00:20:03.479 Uttam Kumaran: Our ability to separate these entities out is our the only way we can actually Qa and make sure things are fine, because that the other table was like an 800 line table with like, basically all the logic of the business, and it it took like 3 months to understand that. So I would say, the critique here is for demolan. In a way she is that we need better summary tables.
137 00:20:04.202 ⇒ 00:20:17.649 Uttam Kumaran: So that’s 1 thing is like if the team should be using order summary. I don’t think anyone has awareness of its availability. And and what use case they should be using it. So that’s so. That’s 1 thing. Second piece is.
138 00:20:18.160 ⇒ 00:20:23.039 Uttam Kumaran: yeah, we need to do something about the legacy models that are still there.
139 00:20:23.220 ⇒ 00:20:26.689 Uttam Kumaran: I think, like my recommendation is that
140 00:20:27.270 ⇒ 00:20:34.020 Uttam Kumaran: we, if we’re not able to adhere to, just don’t use those, then we should rename them to legacy.
141 00:20:36.760 ⇒ 00:20:40.490 Uttam Kumaran: I don’t know, I guess, like Demo Lade, or wish like. What do you think we should do.
142 00:20:42.520 ⇒ 00:20:50.190 Awaish Kumar: But I’m not sure if we should rename it, because, as Robert mentioned that Eden team is still using it to Qa.
143 00:20:50.400 ⇒ 00:20:51.871 Awaish Kumar: some of the stuff.
144 00:20:52.240 ⇒ 00:20:52.950 Uttam Kumaran: Okay.
145 00:20:54.390 ⇒ 00:20:57.860 Robert Tseng: Or I’m saying we shouldn’t drop it renaming. It is fine, like everyone.
146 00:20:58.030 ⇒ 00:21:20.280 Robert Tseng: I don’t even think I don’t think anybody’s using our march outside our team. To be honest, like Rob just uses his materialized views more details, and he’s the only one that’s qaing our work. That’s why they keep him around, because there isn’t like a true sense of trust that we have it down yet. And so he’s still around because the team will ask him to Qa. Everything we put out.
147 00:21:22.360 ⇒ 00:21:36.480 Demilade Agboola: Yeah, I I don’t. I also don’t think we should drop it, at least not until we’ve established some form of confidence in the business. Then we can propose that we we want to like drop it.
148 00:21:37.370 ⇒ 00:21:38.930 Demilade Agboola: I also feel like
149 00:21:39.910 ⇒ 00:21:46.420 Demilade Agboola: the renaming. The mouse will be extreme. I think the the more natural thing is like, once we show
150 00:21:46.650 ⇒ 00:22:09.380 Demilade Agboola: the viability of what we’re doing and like the shows, if we show that we, there’s enough confidence in what we’re doing. It’s more natural to be able to approach that topic and be like, Hey, we’re going to be migrating off this and we’re going to be using, you know, our own dashboards instead. I think our own data models instead for everything. And I think that would.
151 00:22:09.710 ⇒ 00:22:22.742 Demilade Agboola: It’s at that point. It’s it’s more, it’s much more easier to then go, hey, we’re setting a deadline where we’ll be renaming or dropping or doing whatever at that point. Yeah, it’s more easier. It’s easier to accept than just
152 00:22:24.020 ⇒ 00:22:25.769 Demilade Agboola: saying it. Now, I guess.
153 00:22:26.740 ⇒ 00:22:36.600 Robert Tseng: Sure. Yeah. And if order. So, if Order Summary is supposed to be that like order, details replacement in terms of like having, like a 1 flat table for orders.
154 00:22:36.760 ⇒ 00:22:56.659 Robert Tseng: If I can just get like a clear summary of like, why, this is better like, I want to start socializing that. So whenever someone tells me. But order details, says this and like, Well, no, we’re using order sales summary. It considers all these things that order details, doesn’t we, you should be looking at order sales summary like I. I want to start having that
155 00:22:57.291 ⇒ 00:23:12.229 Robert Tseng: as like a back in my pocket, so that when I’m having when I’m in meetings, and people are criticizing our work. Because they’re used. They’re they’re seeing some discrepancy with order details that I can push back on that live right now, I just kinda
156 00:23:12.420 ⇒ 00:23:17.400 Robert Tseng: listen to what they have to say, and then I don’t say anything. I just go back and try to
157 00:23:17.540 ⇒ 00:23:29.759 Robert Tseng: rework it with this team. But you know, if we, if we are trying to build that confidence, yeah, I need to be able to to change those paradigms for people I need to be able to. To.
158 00:23:29.880 ⇒ 00:23:39.580 Robert Tseng: I mean, yeah, just give me something to defend, defend like our our what we’ve built on so. It’s not very clear to me like.
159 00:23:39.840 ⇒ 00:23:43.049 Robert Tseng: what is the order? Details replacement at this point.
160 00:23:46.510 ⇒ 00:23:56.620 Demilade Agboola: Sounds good. It’s something we could work on. This week, I guess. Just like a document where we put up the advantages and like the benefits of switching over to
161 00:23:57.264 ⇒ 00:23:58.569 Demilade Agboola: our current structure.
162 00:23:59.240 ⇒ 00:24:24.636 Robert Tseng: Yeah, so okay, I mean a couple last things. So this, this, the exact dash, is probably shipped profitability. Dash hopefully, you guys will get down to the model and update that. So we can ship this to. I mean, this is already live. It makes me nervous because it’s been live for more than a week. And it’s like, just not right. So I’m trying to get this one. This is more catch up work. And then we have?
163 00:24:25.380 ⇒ 00:24:42.759 Robert Tseng: yeah, I mean, there’s a couple I mean, I’m just getting a progress check on the ship. Oh, and the new data sources. Because we yeah, you know, like, I think this is this to me is all work that should have been done like a couple of weeks ago, so I need to be able to talk about our current roadmap, too, and and the stuff that we’re we’re we’re working through right now.
164 00:24:43.150 ⇒ 00:25:00.560 Robert Tseng: So whether it’s on this call, actually, I can’t. I have to drop in a couple of minutes. But if you guys could kind of give me an update on where we’re at with the Zendesk with the ship. Oh, you know, and helping Sahana with her, her pharmacy and Cx dashboard, which I haven’t heard anything about in 2 weeks, like I think that’s
165 00:25:00.680 ⇒ 00:25:10.319 Robert Tseng: I, wanna know. Be knowing. I want to know, like what’s going on with the the stuff that is supposed to be in current current. And that’s supposed to be current right now.
166 00:25:13.460 ⇒ 00:25:37.589 Uttam Kumaran: Yeah, I’ll send a I’ll send a little bit of a note with everything. I’ll sort of act. Continue to act as Pm. And sort of send a note with each item, I think, for Demo and wish one. We we just need to really socialize with anyone who’s in tableau about what tables they can. They should pull from right right. And we just added one more person to help with tableau work, James. He’s gonna land to the same issue.
167 00:25:37.820 ⇒ 00:25:54.219 Uttam Kumaran: So if you guys have a short term solve for that, let’s let’s do that. I’ll I’ll send a note there second for for any of these changes in tableau, Robert, are we good to go? Make those, or like what is what is the takeaway.
168 00:25:55.040 ⇒ 00:26:05.183 Robert Tseng: Yeah, I mean right now, like it was just me. I’ve just been managing all the deployment, which is kind of because it takes a lot of time for me. But
169 00:26:05.610 ⇒ 00:26:28.790 Robert Tseng: I mean for everything that’s in the 2 collections of executive and marketing I’ve already published. I kind of yeah, so anything new. I’m hoping the team can can publish it. There’s a there’s a. The procedure is just to publish this data sources separately, so that we can schedule daily refreshes in the morning. That’s kind of what I have set up for every dashboard.
170 00:26:29.283 ⇒ 00:26:30.920 Robert Tseng: I don’t. Yeah, I don’t know who’s
171 00:26:31.030 ⇒ 00:26:42.899 Robert Tseng: I’m I was expecting the analysts to kind of own that deployment, but I don’t think, you know we we’ve we’ve not really arrived at that yet, so it’s so far it’s just been on me to to manage all the deployments.
172 00:26:43.090 ⇒ 00:26:57.350 Uttam Kumaran: Okay, let’s see if we can coordinate between this team and James and Sahana today. So I’ll just send a note about that. So we have that we have fixing this revenue issue. We have the legacy model issue.
173 00:26:58.800 ⇒ 00:27:02.139 Uttam Kumaran: I will send an update about Shippo, and then
174 00:27:02.890 ⇒ 00:27:05.709 Uttam Kumaran: I I will send just a poke about
175 00:27:06.371 ⇒ 00:27:10.869 Uttam Kumaran: now that we’re at, we’re sort of finishing up these. What’s the update for
176 00:27:11.100 ⇒ 00:27:13.210 Uttam Kumaran: pharmacy dash? Is there anything else.
177 00:27:15.688 ⇒ 00:27:40.639 Robert Tseng: Yeah, I mean, there’s a couple of marketing things that are coming through the pipeline data sources that I’ve said no to. So I. Kinda I brought that up yesterday. We have grin, we have parallel, we have other. I forgot what the other one is like. So there’s more of that kind of stuff coming our way. But I’ve been saying No to everything for now. And so I think that’s probably gonna be put on our our roadmap soon.
178 00:27:40.640 ⇒ 00:27:51.969 Uttam Kumaran: Okay, yeah, I mean, if we if we can start ingesting those, then I would just start to get if I can get, we can get one person, our team or our joint email can get access to that.
179 00:27:52.440 ⇒ 00:27:56.350 Uttam Kumaran: That’s what I. That’s what we would need. So I can send a note about that, too.
180 00:27:56.810 ⇒ 00:28:04.839 Robert Tseng: I would say, the intake stuff is probably higher priority. I know that, like we were kind of going back and forth on what does best actually give us some questionnaire.
181 00:28:04.840 ⇒ 00:28:05.630 Uttam Kumaran: Yeah.
182 00:28:05.630 ⇒ 00:28:12.310 Robert Tseng: Platform do so, I think kind of having a clear understanding of that. I think is important, because that’s.
183 00:28:12.610 ⇒ 00:28:18.342 Robert Tseng: you know, that’s I think that’s the data that that they care about the most right now.
184 00:28:19.410 ⇒ 00:28:25.770 Robert Tseng: I kind of shared my understanding of it with with the team already. And yeah, I mean.
185 00:28:25.880 ⇒ 00:28:42.740 Robert Tseng: there’s some analysis that needs to be done there. I’ve I’ve flashed like a legacy type form dashboard that we needed to kind of replace with, I don’t know. There’s like some some work around around. What? What do customers actually tell us from questionnaires that we cannot actually that we can’t answer.
186 00:28:43.446 ⇒ 00:28:46.259 Robert Tseng: So I think that’s that’s like.
187 00:28:46.420 ⇒ 00:28:51.269 Robert Tseng: yeah, that that’s like a whole thing that we haven’t really done anything on.
188 00:28:52.220 ⇒ 00:28:52.860 Uttam Kumaran: Okay.
189 00:28:54.010 ⇒ 00:29:00.159 Uttam Kumaran: okay, I have a list of stuff. I’ll send a message. I mean, it looks like my priority is really to get updates on
190 00:29:00.330 ⇒ 00:29:03.370 Uttam Kumaran: the revenue in tableau, the pharmacy dashboards.
191 00:29:03.500 ⇒ 00:29:07.250 Uttam Kumaran: and then we’ll we can. I’ll basically. What’s next is
192 00:29:07.380 ⇒ 00:29:09.989 Uttam Kumaran: stuff for intake and marketing sources.
193 00:29:10.190 ⇒ 00:29:10.810 Robert Tseng: Yeah.
194 00:29:13.300 ⇒ 00:29:21.169 Uttam Kumaran: Okay, cool. I’ll send a message to everything. Yeah, guys, we just be responsive today. And then James is coming on just to like onboard onto
195 00:29:21.803 ⇒ 00:29:24.419 Uttam Kumaran: tableau stuff, so we’ll chat with him.
196 00:29:27.650 ⇒ 00:29:29.270 Robert Tseng: Alright! Thanks everyone. Bye.
197 00:29:29.270 ⇒ 00:29:29.850 Uttam Kumaran: Thank you.
198 00:29:30.450 ⇒ 00:29:31.180 Uttam Kumaran: Bye.