Meeting Title: Eden Team Project Retrospective and Planning Date: 2026-02-12 Meeting participants: Robert Tseng, Ryon
WEBVTT
1 00:00:59.230 ⇒ 00:01:00.600 Ryon: Hey, Robert, how’s it going?
2 00:01:01.550 ⇒ 00:01:02.720 Robert Tseng: Good, how are you?
3 00:01:03.000 ⇒ 00:01:10.950 Ryon: Good, good, good. Thanks so much for being flexible. I know the, week has been, interesting.
4 00:01:10.950 ⇒ 00:01:11.300 Robert Tseng: Yeah.
5 00:01:11.860 ⇒ 00:01:15.750 Ryon: How’s it been for you? I saw you were traveling recently.
6 00:01:15.750 ⇒ 00:01:24.259 Robert Tseng: Yeah, I was, in Orlando over the weekend. My wife and I were celebrating our 5-year anniversary, so…
7 00:01:24.440 ⇒ 00:01:25.680 Ryon: This last weekend?
8 00:01:25.680 ⇒ 00:01:26.380 Robert Tseng: Yeah.
9 00:01:26.380 ⇒ 00:01:30.920 Ryon: Oh my gosh, that’s my wedding anniversary too! 9 years!
10 00:01:30.920 ⇒ 00:01:33.059 Robert Tseng: No way! Yeah. Oh.
11 00:01:33.060 ⇒ 00:01:35.440 Ryon: Yeah, yeah, yeah, February 3rd.
12 00:01:35.440 ⇒ 00:01:36.130 Robert Tseng: Okay.
13 00:01:36.130 ⇒ 00:01:48.540 Ryon: So, I, I gotta pull out all the… I gotta pull out all the stops for Valentine’s Day, because I was supposed to have a dinner reservation, didn’t quite wait till the last minute, didn’t quite work out, but, okay.
14 00:01:49.660 ⇒ 00:01:53.340 Ryon: But, yeah, congratulations, congratulations.
15 00:01:53.340 ⇒ 00:01:55.530 Robert Tseng: Thank you. You said 9 years for you?
16 00:01:55.530 ⇒ 00:01:56.689 Ryon: Nine years, yeah. Nice.
17 00:01:56.800 ⇒ 00:01:59.220 Robert Tseng: Yeah, that’s, that’s, that’s great.
18 00:01:59.430 ⇒ 00:02:04.329 Ryon: We’ve, I sort of jokingly tell Hannah, occasionally, I’m like.
19 00:02:05.170 ⇒ 00:02:10.959 Ryon: Seems like a long… I know it’s not actually a long, you know, in terms of, like, some people’s marriage, but, like, yeah, it seems like a while.
20 00:02:11.060 ⇒ 00:02:13.370 Robert Tseng: But 5 years is a good year. I liked 5 years.
21 00:02:13.820 ⇒ 00:02:19.489 Robert Tseng: I should ask you for some Irish advice on what changes from 5 to 10, then, at some point.
22 00:02:19.490 ⇒ 00:02:21.940 Ryon: Oh, yeah,
23 00:02:22.450 ⇒ 00:02:29.000 Ryon: honesty, and just work it out. I remember one thing my dad told me was, you know, never let the sun go down on your anger.
24 00:02:29.250 ⇒ 00:02:32.759 Robert Tseng: Oh, yeah, yeah. That was in my wedding vows, so, yeah.
25 00:02:32.760 ⇒ 00:02:39.180 Ryon: Yeah, never let that… that is legit, like, it’s not a joke, it’s not some random thing, like, definitely don’t… don’t let that happen.
26 00:02:39.530 ⇒ 00:02:40.310 Robert Tseng: That way.
27 00:02:40.350 ⇒ 00:02:51.740 Ryon: Cool. Yeah. Alright, let’s chat here for a second. I sort of just hope this is kind of to be, like, a two-way, like, discussion dialogue. I don’t want to, like, always be talking, like, the whole time, so feel free to interrupt at any time.
28 00:02:51.740 ⇒ 00:02:52.280 Robert Tseng: Yeah.
29 00:02:52.520 ⇒ 00:03:11.259 Ryon: But, I need to just kind of retro with you on some of the stuff that’s happened recently, and then also kind of get some updates on some different things, and then talk about kind of how we got to move forward with some different stuff, because we’re sort of solving through, you know, fire after fire here, and some stuff is still kind of, like, on fire, but also not.
30 00:03:11.260 ⇒ 00:03:32.720 Ryon: And I want to make sure we sort of get to resolution quickly. So, couple of things. First, right now, open tasks are really kind of the TikTok tracking, the Facebook stuff, the team’s working on that, that’s good. And also, Catalyst remains an issue. I say this to you cautiously, please don’t share, but we might not be on Catalyst long-term. There’s still TBD on that, but… Yeah.
31 00:03:32.720 ⇒ 00:03:39.550 Ryon: It has really just been, like, a headache of not balancing server-to-server plus client-side solutions as well.
32 00:03:39.550 ⇒ 00:03:39.870 Robert Tseng: Yeah.
33 00:03:39.920 ⇒ 00:03:43.439 Ryon: So, that’s always been fun, but,
34 00:03:43.640 ⇒ 00:03:47.499 Ryon: What do we gotta do with the team to sort of
35 00:03:48.630 ⇒ 00:04:04.390 Ryon: forecast the fires a little better and not, you know, come out down to the last second and, like, spontaneously tell you guys, oh my god, we gotta launch Facebook, you know, do we… do I need to be in regular stand-up with you guys? I know I already have my sprint planning meetings, but, like, what do I need to… what do we need to do to increase the communication there?
36 00:04:04.660 ⇒ 00:04:22.779 Robert Tseng: Yeah, I mean, I guess I can answer… before I kind of answer that one, I guess what I came to this call with is… well, I want to just… I can share kind of a summary of, like, what we have in place in terms of, like, data tests and automation for, like, the work that we do, and I’d like to better understand, kind of, like, on your side.
37 00:04:23.160 ⇒ 00:04:37.240 Robert Tseng: how we can set up something similar for you there. And if that involves, like, putting in more meetings or whatever, like, we could do that. But, I just wanted to… I mean, that’s what I had in mind coming into this call. So.
38 00:04:37.480 ⇒ 00:04:45.180 Ryon: I’m sort of… I’m sort of blindsiding you a little bit, I do apologize. But yes, I do want to get to QA stuff. I really do. That as well.
39 00:04:45.820 ⇒ 00:04:56.959 Robert Tseng: Okay, cool. Well, yeah, I mean, as far as, like, I feel like it’ll answer the, how do we get ahead of it, because, like, I don’t fully know what that means for… for you, like, I… I think, like,
40 00:04:57.040 ⇒ 00:05:06.249 Robert Tseng: obviously, you know, we… the things that we keep circling around, BASC pushing API changes, or… I mean, even on the Eden OS side, we’re experiencing
41 00:05:06.360 ⇒ 00:05:21.860 Robert Tseng: Pharmedica API recently just pushed a random change, and it’s like, well, the heck, like, the project’s supposed to wrap up in a week, and so, you know, the team is kind of rallying around that to try to fix that. But, you know, I think what we don’t control is when vendors, like, change their
42 00:05:22.400 ⇒ 00:05:27.189 Robert Tseng: change the data that they send us, and then it’s a scramble for us to basically
43 00:05:27.220 ⇒ 00:05:31.150 Robert Tseng: patch things up. It’s never that hard to figure out, like, I feel like we’re able to…
44 00:05:31.150 ⇒ 00:05:55.690 Robert Tseng: you know, swarm and just, like, get to the problem faster, and… and I think that’s just a… I think there’s a lot of… a lot of credit for that is due to a lot of the things that we have set up in place, so we can… we can… we can go and… and… and figure things out pretty quick. But yeah, there’s always going to be some, like, drift between, like, we don’t know what the vendors are gonna tell us, and so, like, we’re always gonna… there’s always that reactive element to the… to data
45 00:05:56.740 ⇒ 00:06:06.140 Robert Tseng: So, I feel like that’s… that’s always part of it. But, like, what we can do is try to, like, just, like, figure out what are all the possible…
46 00:06:06.390 ⇒ 00:06:10.610 Robert Tseng: What are the possible changes, in each, and…
47 00:06:10.730 ⇒ 00:06:20.960 Robert Tseng: And di… so we could pre-diagnose that and set some, like, tests… like, set some alerts faster. So, for example, on the data side, like.
48 00:06:20.960 ⇒ 00:06:33.530 Robert Tseng: you know, when I first came in and we were just using straight FASC to, like, Looker Studio or whatever, like, there were no data tests. It was just, like, a bunch of random SQL models kind of, like, sprawled out everywhere, that, like, people were just running off one-off queries.
49 00:06:33.530 ⇒ 00:06:51.659 Robert Tseng: And so, you know, we follow, kind of, like, software engineering practices here. It’s called CICD, and where we basically, every model is… we run it through a framework called dbt, which is basically, like, version-controlled, like, data modeling, so that I can figure out
50 00:06:51.660 ⇒ 00:07:07.560 Robert Tseng: So, yeah, I can figure out what changes we’re making. We align on the same types of… same definitions of models. Like, that’s just made, like, QA much faster for us, and if there’s any fix, like, I don’t think there’s been a data modeling problem that we haven’t been able to root cause within the same day, so…
51 00:07:07.880 ⇒ 00:07:25.360 Robert Tseng: Like, yeah, I think, like, that’s… that’s what I… that’s what I can do once… once we turn data into SQL. Like, I think I feel very confident in our ability to be able to react to things once… once it’s in… once it’s in that format. But we’re working with a lot of external data sources that don’t…
52 00:07:25.360 ⇒ 00:07:40.740 Robert Tseng: give us direct API access, and we don’t… we can’t bring it in in SQL. So there’s stuff that floats around in Google Sheets, that’s where, like, the offline, the upluent stuff, we’re doing manual… manual reporting there, that’s fine. Like, the worst thing is, like, I just have Zora on set a weekly.
53 00:07:40.740 ⇒ 00:07:44.320 Robert Tseng: he has a weekly… I have a weekly thing with him on his calendar, where
54 00:07:44.320 ⇒ 00:08:06.670 Robert Tseng: He has a reminder, he needs to go and do the manual reconciliation, needs to send me the Slack message, and if everything looks fine, then fine, like, he can… he can send it to you and the Eden team. So, like, we will have to… there’s going to be some data sources like that, or some processes like that, where it’s just gonna have to be a manual thing that we set up like that. But that’s… that’s fine, like, I think…
55 00:08:06.700 ⇒ 00:08:09.550 Robert Tseng: There’s never been a situation where that has not
56 00:08:09.550 ⇒ 00:08:27.929 Robert Tseng: that has ceased to exist in my world. So, like, we can figure out what are… what more of those checks we need, and ideally we can just batch them together so that Zoran can just do his checks, or whoever I assign can just do their checks all in one go, and that way they’re not, like, feeling like they’re having to ping-pong back and forth
57 00:08:27.930 ⇒ 00:08:31.360 Robert Tseng: Throughout the week, because obviously they get frustrated that, like.
58 00:08:31.360 ⇒ 00:08:54.229 Robert Tseng: they don’t get to go deeper on the more proactive projects that we’re working on, they’re just reacting throughout the week. So, I mean, that’s… that’s, like, one direction that I would suggest, like, we could really figure out what are the… where… where are, like, the touchpoints where, like, someone on my team needs to be doing QA with you, alongside you, or for you, and just be able to go and catch that and
59 00:08:54.230 ⇒ 00:09:00.699 Robert Tseng: We just kind of… we try to batch it together, with the other manual workflows that we already have in place.
60 00:09:01.540 ⇒ 00:09:02.170 Robert Tseng: Oh, yeah.
61 00:09:02.170 ⇒ 00:09:25.460 Ryon: So let’s do this. I’ll take this away as maybe I should come up with some different things, like, this is where I need support regularly for the, you know, we’ll call them single points of failure. But one of the things I want to do, and I’ve been pushing Adam Palma for this a little bit, and then also one of the guys on my side, Nick, because I want to automate a lot of this so that we can keep a record of changes, like, as much as possible.
62 00:09:25.690 ⇒ 00:09:29.789 Ryon: And is that something your guys’ system can do?
63 00:09:29.790 ⇒ 00:09:30.210 Robert Tseng: Yeah.
64 00:09:30.210 ⇒ 00:09:39.679 Ryon: I’m thinking, like, we really struggle, like, you know, Basque be bask, you know, I shouldn’t complain, we just need to be better than them. But we…
65 00:09:39.740 ⇒ 00:09:53.959 Ryon: we’ve got to have, like, a GTM monitoring QA system, and I know that’s not easy to do, so that sort of brings me to this next question of… and I’m not against this idea, but, like, is GTM the solution for us, or should we just adopt segment? I’m totally fine either way. I really do not…
66 00:09:53.960 ⇒ 00:10:00.840 Robert Tseng: Yeah, I think that, obviously, like, GTM is easier to…
67 00:10:01.290 ⇒ 00:10:16.430 Robert Tseng: like, make changes on the fly, but obviously, we’re moving to a place where we don’t really want that many people kind of going in and touching it, so, like, having… having segment, you know, everything would pretty much be server-side there. Like, if you’re going to be using, you know.
68 00:10:16.530 ⇒ 00:10:23.449 Robert Tseng: more client-side tagging, like, you do… you do need GTM. I don’t really see a world where, like, you completely don’t have it altogether.
69 00:10:23.450 ⇒ 00:10:41.070 Robert Tseng: But we should be able to set up more GTM container health checks. Like, that’s… that is, like, a level of rigor that we haven’t really set up here that I’ve seen in other places. So, I mean, I would like to, like, spend a sprint of just doing that. So I think, you know, we can… we can figure out, like.
70 00:10:41.070 ⇒ 00:10:52.549 Robert Tseng: what are… what are those… like, any time, you know, we… we push a change in GTM, obviously not everything is… not every change we make is gonna be… is gonna… is gonna go well, so we’ve had to revert on changes. Like, I think…
71 00:10:53.390 ⇒ 00:11:06.369 Robert Tseng: That’s just part of data work as well. So, if it’s, like, a matter of we don’t really know what we need to revert back to, like, you know, that’s where some of the practices that we have in
72 00:11:07.010 ⇒ 00:11:12.260 Robert Tseng: like, set up in the SQL modeling side come into play, where, there…
73 00:11:12.260 ⇒ 00:11:34.299 Robert Tseng: I can see any change that any engineer on my team pushes. That’s why when I… even with very little context, if I get a random, like, fire drill call from someone, I can go review two PRs and figure out what change they pushed that could have, like, led to… led to the inconsistency that we’re seeing. I don’t have that ability to do that with the GTF. I’m…
74 00:11:34.300 ⇒ 00:11:40.029 Robert Tseng: because it’s just you and Zoran pressing changes currently, I kind of just, you know, trust…
75 00:11:40.080 ⇒ 00:11:58.740 Robert Tseng: I have to just trust what you guys are pointing out, and then if Zora needs to talk to me about, you know, something that relates to the modeling that we push through server… through… through segment for a server side as well, then, like, that’s when I get looped in. So, I believe that we can build something better on the GTM side. We just don’t have it there.
76 00:11:58.740 ⇒ 00:12:12.040 Ryon: Okay. So, I’m gonna… I have my own board, I’m tracking everything in that, I’m gonna try and, you know, create tickets and also action items for myself to sort of set up stuff that, like, I need support here, I need support there, these reports of failure, that kind of thing. But.
77 00:12:12.170 ⇒ 00:12:17.680 Robert Tseng: Yeah, that is a big win here, is like, we gotta get better at that, and I know.
78 00:12:17.680 ⇒ 00:12:20.780 Ryon: It’s taken a while, but we gotta get better at that, so… okay, cool.
79 00:12:20.840 ⇒ 00:12:33.990 Robert Tseng: And then beyond, like, the system stuff, like, where Greg, I feel like, is helpful is, I mean, he’s more on the product analytics world, and I brought him in to basically help drive experimentation in a way that Henry could not.
80 00:12:34.170 ⇒ 00:12:52.680 Robert Tseng: But he comes with a lot more of these, like, best practices of, like, pre… pre-campaign, pre-experiment launch checklist, post-experiment validation. Like, I do think that is, like, important, because we do need to make sure that we’re consistently running experiments, checking all the boxes, so we’re not, like, just, like.
81 00:12:52.680 ⇒ 00:13:04.160 Robert Tseng: failing because, like, someone changed UTMs, UTMs got dropped, or, like, something stupid like that, where, like, it just conflates whatever campaign we were running, or, like, experiment that we’re running, and, like.
82 00:13:04.160 ⇒ 00:13:18.870 Robert Tseng: it’s… the change… it distracts from the change that you’re trying to make, because, like, the team just, like, effed up on something else, you know, along the way in the deployment. So, like, I feel like we’ve run into situations like that, you know, in the past…
83 00:13:18.870 ⇒ 00:13:24.440 Robert Tseng: past month, you know, you’ve said so yourself, when we rush a change, like, something happens,
84 00:13:24.440 ⇒ 00:13:25.619 Robert Tseng: Yeah, I think, like.
85 00:13:25.760 ⇒ 00:13:32.890 Robert Tseng: maybe, like, 2 or 3 weeks ago, we, like, rushed, like, this Catalyst model change, and then it ended up, like, not…
86 00:13:32.890 ⇒ 00:13:56.520 Robert Tseng: like, we reverted, like, the day… the day afterwards, because, like, it was someone on my… some engineer on my… on my team kind of, like, mistranslated whatever Zoran was trying to tell him to push, and, yeah, I mean, needless to say, like, I’ve… like, that… that didn’t go well, I pulled that engineer off the project. But, like, you know, stuff like that will happen if we’re just not very, like, if we don’t have, like, the checks and balances in place,
87 00:13:56.520 ⇒ 00:14:02.630 Robert Tseng: When we’re, like, pushing some… when we’re making… when we’re pushing… when we’re pushing a change.
88 00:14:03.870 ⇒ 00:14:05.630 Ryon: Okay, cool.
89 00:14:05.910 ⇒ 00:14:13.219 Ryon: goes without saying, I actually really like Greg. He’s been contributing a lot to our testing framework and the process that we go through.
90 00:14:13.220 ⇒ 00:14:13.630 Robert Tseng: Yeah.
91 00:14:13.630 ⇒ 00:14:32.780 Ryon: those things I’m gonna, adopt internally, across the board. Do we need more people for this, beyond what we already have? Like, does this need to be, like, a dedicated thing? Because I want to try and get, like, stuff deployed ASAP that is going to help me tell ELT, like, yep, this is being looked at, and it won’t happen again, kind of thing.
92 00:14:33.710 ⇒ 00:14:53.720 Robert Tseng: Yeah, well, I mean, I guess from, like, our capacity… one, we’re moving off Tableau, so that’s, like, you know, Danny’s request, like, you know, something that we need to get done in the next two weeks, so we’re kind of rushing that. I told Greg to slow down on other things, because he’s driving that migration, we’re moving off Tableau. Target is February 23rd, so,
93 00:14:54.000 ⇒ 00:15:03.329 Robert Tseng: yeah, we’ve already started to migrate some of the ports, but that… he’s got his hands tied there. I mean, Zoran obviously just has a steady stream of work from you guys,
94 00:15:03.470 ⇒ 00:15:16.829 Robert Tseng: And, I mean, I… we… beyond those two, like, I mean, I have a couple other engineers, Dave Milate and Awash, kind of working in the background, so we do have some more capacity to take on stuff, but…
95 00:15:16.980 ⇒ 00:15:18.050 Robert Tseng: I mean…
96 00:15:18.190 ⇒ 00:15:23.789 Robert Tseng: like, I… I mean, I don’t think this is a big lift. I think we just need to, in the next…
97 00:15:25.240 ⇒ 00:15:37.590 Robert Tseng: you know, pick something off from your roadmap on what’s the most urgent thing, and we try to just do it in a way that’s not so reactive. Like, we try to actually build out the process as we’re doing it this time, rather than
98 00:15:37.590 ⇒ 00:15:45.440 Robert Tseng: kind of just defaulting to what we were doing before. I think that would probably be, a good way to kind of get, get kind of actually
99 00:15:45.440 ⇒ 00:15:46.690 Robert Tseng: shift.
100 00:15:47.220 ⇒ 00:15:49.349 Robert Tseng: The way that we’re approaching this.
101 00:15:49.860 ⇒ 00:15:50.430 Ryon: Okay.
102 00:15:51.210 ⇒ 00:16:00.850 Ryon: Yeah. I’m gonna build everything out. I’m already working with the team and my board to establish things. I feel like, between all these different fires.
103 00:16:00.980 ⇒ 00:16:10.399 Ryon: Zahn and I are kind of running around, trying to deal with fire after fire, but there’s other, like, very critical work that still needs to get done. Great example, attribution report.
104 00:16:10.400 ⇒ 00:16:22.069 Ryon: a different channel-level KPI document, that kind of thing. These are all things that I think we’re pretty far behind on, with Mitesh, and the reason I ask, like, maybe it might be a good idea for us to, like, have somebody who’s
105 00:16:22.110 ⇒ 00:16:22.920 Ryon: you know.
106 00:16:23.000 ⇒ 00:16:33.850 Ryon: junior-ish, chasing the fires in GTM or something, just an idea. I mean, I’m not sure what to do, but, like, we do need to… Zora and I, in particular, need to get back to the KPI stuff.
107 00:16:33.850 ⇒ 00:16:42.530 Robert Tseng: Yeah, I mean, maybe you just have hired someone who’s just doing QA for GTM. Like, at previous teams I’ve been on, like, I’ve had somebody like that on staff, so,
108 00:16:43.210 ⇒ 00:16:48.150 Robert Tseng: I… I think that’s… that’s totally valid. You could bring someone to take that off.
109 00:16:48.790 ⇒ 00:17:00.630 Robert Tseng: even if it saves you 25% of your time, and it takes somebody else 4X as long, like, that, you know, you being in the position you’re in, that’s way more leverage than you’ve, like, kind of…
110 00:17:01.380 ⇒ 00:17:04.640 Robert Tseng: Having to jump… jump into… jump into the fire, so…
111 00:17:05.140 ⇒ 00:17:06.230 Ryon: Okay, cool.
112 00:17:06.410 ⇒ 00:17:11.700 Ryon: Is Amber still in the project? Who’s the PM? She told me the other day she’s not the PM. Who’s our PM?
113 00:17:11.700 ⇒ 00:17:19.549 Robert Tseng: Yeah, I guess, like, we don’t have a PM anymore at this point. It’s really just me, and I guess everyone… I kind of just…
114 00:17:19.849 ⇒ 00:17:25.329 Robert Tseng: everyone just PMs their own work. I’ve kind of done away with PMs, to be honest, so…
115 00:17:25.650 ⇒ 00:17:32.770 Robert Tseng: Yeah, I think, Amber is on the project, like, she’s… I was only doing one thing right now, and that’s just,
116 00:17:33.180 ⇒ 00:17:37.500 Robert Tseng: telehealth, like, margin reporting with… with Brad, so,
117 00:17:37.840 ⇒ 00:17:55.480 Robert Tseng: I think the… we’re… I’m unsure, like, if I want… if… because if Greg’s time ends up kind of… it continues to increase, and he, like, gets… he’s solid there, then we’re done. We don’t have more time to give to Amber. So, they’re kind of, like, both working on stuff right now, and I’m assessing…
118 00:17:55.480 ⇒ 00:18:03.010 Robert Tseng: Like, do we give the time to Greg, or do we just… or to Amber? Like, I haven’t made that decision yet.
119 00:18:03.720 ⇒ 00:18:06.759 Ryon: Okay. Alright, cool. Excellent.
120 00:18:06.810 ⇒ 00:18:21.860 Ryon: Alright, thanks so much. As far as next steps are concerned, I’m gonna go away from this meeting, and I’m gonna continue building tickets in my board, but I’m gonna start to create lists of things, areas where I want to see some support, and then share those out, in different channels.
121 00:18:21.860 ⇒ 00:18:30.220 Ryon: to kind of help the process along, and then, of course, we’ll keep working with the team. But, if there’s anything more I can do.
122 00:18:30.230 ⇒ 00:18:33.140 Ryon: Aside from calling it out, just let me know. I’ll be available.
123 00:18:33.140 ⇒ 00:18:33.840 Robert Tseng: Okay.
124 00:18:33.990 ⇒ 00:18:44.319 Robert Tseng: Yeah, yeah, let’s… we’ll touch base again on this. I mean, I think the GTM, like, auto… automation…
125 00:18:44.320 ⇒ 00:18:56.020 Robert Tseng: alerting system, I think, is something I would like to put on the roadmap, but I just… I just don’t think we’re gonna get to it until the migration is done. So, yeah, I think that’s… that’s kind of where… where we’re at.
126 00:18:56.360 ⇒ 00:19:03.290 Ryon: I’ll put pause on that, and then just continue to spec it out, and then we can talk about it next week. You guys are still running on one-week sprints, right?
127 00:19:03.550 ⇒ 00:19:04.420 Robert Tseng: Yeah.
128 00:19:04.800 ⇒ 00:19:09.980 Ryon: Okay, okay, cool. How long do you think Greg’s gonna take for the Omni-Tableau thing?
129 00:19:10.000 ⇒ 00:19:15.389 Robert Tseng: He has until the 23rd, so… I mean, he’s pretty much got, like, another…
130 00:19:15.670 ⇒ 00:19:19.260 Robert Tseng: 8 to 10 days to finish it, we’ll see if he finishes it, yeah.
131 00:19:19.520 ⇒ 00:19:20.350 Ryon: Okay.
132 00:19:20.350 ⇒ 00:19:20.950 Robert Tseng: Yeah.
133 00:19:21.760 ⇒ 00:19:37.419 Ryon: All right, cool. Thanks so much, man, I appreciate it. And then again, yeah, congratulations on your anniversary, and let’s stay in touch. If you need anything, feel free to call anytime. I will be available. This is critical for me to keep, kind of, delivering the data that people need as best they can. I think ELT sort of expects me to kind of
134 00:19:37.420 ⇒ 00:19:43.880 Ryon: be looking at this stuff and understand stuff, like, from a CRO conversion perspective, but also kind of like, you know, what’s the health of the client?
135 00:19:43.980 ⇒ 00:19:48.960 Ryon: side performance, like the website performance, like, how are we doing? So, yeah, cool.
136 00:19:49.160 ⇒ 00:20:01.430 Robert Tseng: I mean, I know you have… you track stuff in Monday. I think what’s most helpful for us, we were more of, like, a docs kind of team here, so I want to basically put together… I mean, I don’t want to be so formal, but it’s not like a… it’s like a PRD, but basically, like, a…
137 00:20:01.430 ⇒ 00:20:11.489 Robert Tseng: like a re… like a… like a full requirement stock of, like, all the different things. If you surface kind of where, like, the, you know, the single points of failure are, like, yeah.
138 00:20:11.630 ⇒ 00:20:12.410 Robert Tseng: like…
139 00:20:13.110 ⇒ 00:20:25.699 Robert Tseng: Yeah, you just gotta tell me where the breaking points are, and I can basically turn that into specs for my team to be able to build something for. So, like, yeah, I think that’s probably how we could best collaborate.
140 00:20:26.100 ⇒ 00:20:33.449 Ryon: Send me a template, if you have one, of, like, what you want your doc template to look like, your spec document, and I’ll start working and deliver that to you guys. Does that work?
141 00:20:33.450 ⇒ 00:20:34.830 Robert Tseng: Okay, yeah, that works.
142 00:20:34.970 ⇒ 00:20:36.980 Ryon: Cool. Awesome. Thanks, Robert.
143 00:20:36.980 ⇒ 00:20:37.760 Robert Tseng: I appreciate that.