Meeting Title: EP Leads Weekly Sync Date: 2026-02-05 Meeting participants: Mustafa Raja, Amber Lin, Clarence Stone, Sheshu Chandrasekar, Sheshu Chandrasekar
WEBVTT
1 00:01:34.410 ⇒ 00:01:35.620 Amber Lin: Hi there.
2 00:01:36.850 ⇒ 00:01:37.500 Mustafa Raja: 8.
3 00:01:38.500 ⇒ 00:01:39.420 Mustafa Raja: How are you?
4 00:01:40.310 ⇒ 00:01:42.290 Amber Lin: I’m good.
5 00:01:42.490 ⇒ 00:01:46.939 Amber Lin: Not a lot of show up to this meeting.
6 00:01:50.770 ⇒ 00:01:52.010 Mustafa Raja: What’s the time there?
7 00:01:53.270 ⇒ 00:01:53.920 Amber Lin: Huh?
8 00:01:54.100 ⇒ 00:01:57.109 Mustafa Raja: What’s the time? My time here? It’s 10 AM.
9 00:01:58.480 ⇒ 00:01:59.230 Amber Lin: Yeah.
10 00:01:59.880 ⇒ 00:02:02.660 Mustafa Raja: The meeting for you would be really early then, right?
11 00:02:03.630 ⇒ 00:02:07.669 Amber Lin: My earliest one’s at 7, it’s not too bad.
12 00:02:11.910 ⇒ 00:02:17.009 Amber Lin: Okay, well, it seems like everybody else is free, so… let’s wait a bit.
13 00:02:17.780 ⇒ 00:02:19.040 Clarence Stone: Hello, hello!
14 00:02:19.630 ⇒ 00:02:20.520 Amber Lin: members…
15 00:02:22.150 ⇒ 00:02:23.830 Clarence Stone: How’s everyone doing?
16 00:02:24.000 ⇒ 00:02:29.580 Amber Lin: Pretty good. We tried to have this meeting on Tuesday, but then we just had two people, so…
17 00:02:29.580 ⇒ 00:02:30.220 Clarence Stone: Yeah.
18 00:02:30.290 ⇒ 00:02:32.649 Amber Lin: I moved it to this time instead.
19 00:02:35.740 ⇒ 00:02:37.220 Clarence Stone: Sounds good.
20 00:02:59.790 ⇒ 00:03:00.670 Amber Lin: Hmm…
21 00:03:23.250 ⇒ 00:03:28.219 Amber Lin: Okay, Mustajo, let’s just go through this, just you and I, and then we’ll figure out…
22 00:03:29.030 ⇒ 00:03:32.210 Amber Lin: I guess the rest of folks can watch the recording.
23 00:03:32.360 ⇒ 00:03:37.080 Amber Lin: Let me pull up the doc…
24 00:03:43.410 ⇒ 00:03:44.320 Amber Lin: Alright.
25 00:03:46.940 ⇒ 00:03:47.860 Sheshu Chandrasekar: Hey, Amber!
26 00:03:48.650 ⇒ 00:03:49.290 Amber Lin: Hello!
27 00:03:49.290 ⇒ 00:03:49.930 Mustafa Raja: Mmm…
28 00:03:52.380 ⇒ 00:03:53.090 Amber Lin: Alright.
29 00:03:53.520 ⇒ 00:04:02.410 Amber Lin: So I think today we’ll go through the section 2 and 3, I may be…
30 00:04:03.300 ⇒ 00:04:10.399 Amber Lin: maybe stuff here, I do want to save this financial stuff for a separate section, but if we can go through…
31 00:04:10.610 ⇒ 00:04:14.060 Amber Lin: Like, stuff here as well, it’ll be great.
32 00:04:16.579 ⇒ 00:04:24.419 Amber Lin: let’s just talk about how we… how we do this. How do you approach, say, these issues currently?
33 00:04:26.360 ⇒ 00:04:33.919 Mustafa Raja: So, I guess, for the client interactions and meeting notes, that would be,
34 00:04:34.220 ⇒ 00:04:52.989 Mustafa Raja: that would be totally on, what’s it called? Platform, right? So, platform does, take good care of action items and stuff like that. Okay. Other than that, client interaction would be, apart from meetings, would be in Slack. Client general. So that’s pretty much it.
35 00:04:52.990 ⇒ 00:04:59.830 Amber Lin: Okay, so if I were to look at Notion, is there a way for…
36 00:05:00.740 ⇒ 00:05:04.320 Amber Lin: Say, for example… sorry, let me go back to…
37 00:05:08.830 ⇒ 00:05:10.579 Amber Lin: Like, right here…
38 00:05:11.820 ⇒ 00:05:14.159 Mustafa Raja: I think we could add the quick links, right?
39 00:05:14.740 ⇒ 00:05:20.359 Amber Lin: Yeah, we can. So, let’s say if I want to see the meeting links and meeting…
40 00:05:20.470 ⇒ 00:05:27.340 Amber Lin: reading notes. Should we also add a link to the client?
41 00:05:27.340 ⇒ 00:05:29.130 Mustafa Raja: Yeah, let’s… yeah, I think that…
42 00:05:29.130 ⇒ 00:05:29.510 Amber Lin: Sick?
43 00:05:29.510 ⇒ 00:05:30.190 Mustafa Raja: Pacific?
44 00:05:30.190 ⇒ 00:05:32.160 Amber Lin: classify it correctly.
45 00:05:32.370 ⇒ 00:05:39.230 Mustafa Raja: Yes, the client meetings, the meetings with clients directly would be classified correctly.
46 00:05:39.660 ⇒ 00:05:50.290 Amber Lin: Okay, so I’m going to… Copy this link… Let’s say… Oink.
47 00:05:51.340 ⇒ 00:05:54.900 Amber Lin: Meeting those siblings.
48 00:06:03.190 ⇒ 00:06:05.160 Amber Lin: So let’s put that there.
49 00:06:08.090 ⇒ 00:06:10.360 Amber Lin: Meeting recordings…
50 00:06:10.360 ⇒ 00:06:15.379 Clarence Stone: I always made it difficult time. Hey, Amber, can I get your thoughts on something once you’re done with this one?
51 00:06:15.850 ⇒ 00:06:25.389 Amber Lin: Yeah, totally. And… Mustafa, you said other than this, it would be in Slack, right?
52 00:06:25.390 ⇒ 00:06:27.890 Mustafa Raja: Yeah, other than this, it’s just Slack, right?
53 00:06:29.900 ⇒ 00:06:36.280 Amber Lin: Gotcha. Is there any client hub agents and stuff that we can also reference?
54 00:06:37.560 ⇒ 00:06:41.939 Mustafa Raja: I don’t think that we are using client hubs as much.
55 00:06:42.120 ⇒ 00:06:43.350 Amber Lin: Gotcha, okay.
56 00:06:44.820 ⇒ 00:06:48.080 Amber Lin: Cool. Okay. Clarence, what was your question?
57 00:06:49.750 ⇒ 00:06:52.590 Clarence Stone: So, in the SL meeting on Monday, Amber.
58 00:06:53.000 ⇒ 00:07:03.270 Clarence Stone: The SLs were saying that one of their biggest challenges is when they’re not, like, actually working directly on the project, it’s hard for them to keep up on what’s going on, because all the…
59 00:07:03.710 ⇒ 00:07:07.190 Clarence Stone: like, all the communications keep happening in Slack.
60 00:07:08.290 ⇒ 00:07:19.700 Clarence Stone: And you know, like, how you… you miss one Slack message, and you don’t know if that was super important or not, right? So, what they were asking me is, like, what is… what is the…
61 00:07:20.190 ⇒ 00:07:31.679 Clarence Stone: strategy that EPs would use to store something like, for example, Amber, if… if ABC told us, like, hey, we like our charts and graphs formatted in this way.
62 00:07:31.880 ⇒ 00:07:44.960 Clarence Stone: Right, they never would, because they’re super nice, but… but there are some clients that are a little bit more picky. Where can we save that, right, so the whole team knows that these are, like, formatting standards, or communication standards, or average standards?
63 00:07:45.190 ⇒ 00:07:46.000 Mustafa Raja: neat.
64 00:07:46.840 ⇒ 00:07:49.780 Amber Lin: I see. Msar, what do you think?
65 00:07:50.000 ⇒ 00:07:52.439 Mustafa Raja: Yeah, I guess we have internal channels…
66 00:07:53.050 ⇒ 00:07:55.370 Mustafa Raja: We do talk about stuff like that, right?
67 00:07:55.990 ⇒ 00:08:03.900 Clarence Stone: Yeah, and that’s the problem with the Slack, like, it’ll go away, right? And it’s not easy to find that information back again.
68 00:08:05.030 ⇒ 00:08:05.890 Mustafa Raja: Yeah.
69 00:08:09.650 ⇒ 00:08:12.969 Mustafa Raja: I guess we, I guess then we need some mode for…
70 00:08:21.250 ⇒ 00:08:23.460 Mustafa Raja: Yeah, Amber, what are your thoughts on that?
71 00:08:25.350 ⇒ 00:08:30.340 Clarence Stone: I don’t have an answer, guys. I was just passing it over to… to see what you guys can get. Yeah, I’m just thinking…
72 00:08:30.340 ⇒ 00:08:40.570 Amber Lin: I see. Let’s… I think Robert had a pretty good… let’s go look at the Eden page. I think Robert’s page is, like, he spent a lot of effort here.
73 00:08:40.570 ⇒ 00:08:58.619 Amber Lin: So, like, he has the schedule, and then he has the key team artifacts. They’re not 100% up-to-date, but for example, like, these are the specs and the logic things that we should do. There’s stuff for Eden, stuff for Brainforge, so I think what we can do is,
74 00:08:58.620 ⇒ 00:09:11.350 Amber Lin: like, I keep my documents like this. I would put it in the live section, or this could be, because we also have cursors set up for every client, I think that’s something that
75 00:09:11.410 ⇒ 00:09:21.029 Amber Lin: we could share an update in GitHub, like, to have a document that syncs. So, for example,
76 00:09:21.920 ⇒ 00:09:27.919 Amber Lin: It would be… Specs and specifications…
77 00:09:28.090 ⇒ 00:09:40.719 Amber Lin: for this client, there could also… that could also include, like, communication requirements, or… Like, stakeholder preferences.
78 00:09:41.060 ⇒ 00:09:47.109 Amber Lin: What would you call that type of document? Is it just, like, client-specific?
79 00:09:47.660 ⇒ 00:09:49.440 Amber Lin: specifications?
80 00:09:49.780 ⇒ 00:09:52.239 Amber Lin: Or, like, how would that be?
81 00:09:52.840 ⇒ 00:10:04.879 Clarence Stone: Yeah, so Amber, I’ll share with you, like, how it worked where I came from. I don’t think it’s a perfect system by any means, so don’t use it as a suggestion at all, but, like, we had a portal that tracked, like.
82 00:10:05.120 ⇒ 00:10:08.650 Clarence Stone: All our clients and all the projects that we work with on with them.
83 00:10:09.360 ⇒ 00:10:11.550 Clarence Stone: Right? And in that portal, like.
84 00:10:11.720 ⇒ 00:10:26.649 Clarence Stone: We also list their leadership, who they are, and, like, who’s the stakeholders on these projects, and then we have, like, links to SOWs and stuff, and then, like, people who are on that engagement, leave notes.
85 00:10:27.940 ⇒ 00:10:40.960 Clarence Stone: like, hey, we talked to this client, and this is, like, you know, they are… they’re planning a new IPO, so, you know, we need to make sure that our documents here, here, and here are up to date, right? Like, and it’s almost like a stream.
86 00:10:41.130 ⇒ 00:10:43.569 Clarence Stone: For everybody that’s on the project.
87 00:10:43.770 ⇒ 00:10:45.200 Clarence Stone: about the client.
88 00:10:47.650 ⇒ 00:10:48.560 Clarence Stone: It’s…
89 00:10:48.680 ⇒ 00:11:04.310 Clarence Stone: it sounds pretty cool, but it’s not because they use Yammer, Amber, so… that’s, like, that’s where I came from. But yeah, like, that’s one solution, but it’s still, to me, repetitive, right? Because, like, you’re in the meeting, Brian says something to you, you just go, oh, I have to save that.
90 00:11:04.310 ⇒ 00:11:12.379 Clarence Stone: Right? Instead of just pinging it into Slack, you also have to save it somewhere. I think the challenge here overall is that, like, Slack is not a system of record.
91 00:11:12.410 ⇒ 00:11:14.259 Clarence Stone: Right, like, stuff disappears.
92 00:11:16.660 ⇒ 00:11:21.280 Amber Lin: I think that’s something for the AI team, like, if you can specify
93 00:11:21.390 ⇒ 00:11:34.450 Amber Lin: what that is, and what the requirements are, I think the AI team would be able to help you extract that automatically. Like, currently, what we’re able to do, like, with the current set of tools is to
94 00:11:34.550 ⇒ 00:11:42.240 Amber Lin: copy and paste that into Notion somewhere. Like, I don’t see an immediate way to automate it.
95 00:11:42.360 ⇒ 00:11:47.260 Amber Lin: Because it is, as you say, you have to remember to write it down.
96 00:11:47.730 ⇒ 00:11:58.310 Clarence Stone: Yeah, yeah, okay, sounds good. Well, I guess, like, for the EPs, just keep that in mind, right? If something’s, like, really super important, make sure you just put it in the Notion somewhere, too.
97 00:11:58.930 ⇒ 00:12:01.959 Sheshu Chandrasekar: Hey, yeah, just wanna… just wanna…
98 00:12:01.960 ⇒ 00:12:02.570 Clarence Stone: echo.
99 00:12:02.570 ⇒ 00:12:03.290 Sheshu Chandrasekar: I guess.
100 00:12:08.230 ⇒ 00:12:13.259 Clarence Stone: Yeah, so just put it somewhere in the notion for now, right? And then we’ll figure out a better notion.
101 00:12:24.000 ⇒ 00:12:25.240 Sheshu Chandrasekar: Hey, can you hear me now?
102 00:12:25.240 ⇒ 00:12:25.880 Mustafa Raja: Yeah.
103 00:12:26.370 ⇒ 00:12:26.930 Clarence Stone: Yup.
104 00:12:26.930 ⇒ 00:12:27.530 Sheshu Chandrasekar: So…
105 00:12:27.710 ⇒ 00:12:37.949 Sheshu Chandrasekar: just want to kind of shed some light here. So, we are doing the Notre revamp, as you may know, and we’re actually reclassifying document types. So, in this case.
106 00:12:38.180 ⇒ 00:12:41.469 Sheshu Chandrasekar: If you have meeting notes for ABC,
107 00:12:41.630 ⇒ 00:12:49.090 Sheshu Chandrasekar: you could categorize it as internal or client, and in this case, it would be client, and I think it would be easier if I just showed it to you, if that makes sense.
108 00:12:49.090 ⇒ 00:12:51.980 Amber Lin: Yeah, let me… here, you can share screen now.
109 00:12:55.290 ⇒ 00:12:56.540 Sheshu Chandrasekar: One second…
110 00:13:03.750 ⇒ 00:13:09.329 Sheshu Chandrasekar: Okay, so we have everything in this new notion right here.
111 00:13:09.720 ⇒ 00:13:15.470 Sheshu Chandrasekar: And if you were to go to… Wrong one.
112 00:13:19.390 ⇒ 00:13:21.150 Sheshu Chandrasekar: If you were to go to ABC,
113 00:13:22.170 ⇒ 00:13:24.129 Sheshu Chandrasekar: And you were to create a document.
114 00:13:28.110 ⇒ 00:13:33.640 Sheshu Chandrasekar: We have all the documents here, but our main documents will start living in here right now.
115 00:13:35.800 ⇒ 00:13:36.750 Mustafa Raja: Rookie.
116 00:13:37.470 ⇒ 00:13:40.699 Sheshu Chandrasekar: Which… Sorry, give me one second.
117 00:13:42.820 ⇒ 00:13:53.030 Sheshu Chandrasekar: Cool, so these are the document types that we have here, right? So if you have a guide, or meeting notes, or templates, or SOPs, these are the type of categories we have, and then the access level would be, like.
118 00:13:53.240 ⇒ 00:13:59.770 Sheshu Chandrasekar: Public, internal, role-specific status, and then what kind of team tags there would be, and then
119 00:13:59.880 ⇒ 00:14:02.230 Sheshu Chandrasekar: We’d also have, like.
120 00:14:02.720 ⇒ 00:14:10.299 Sheshu Chandrasekar: different types of case studies, right? Like, everything will be categorized in a way, and it’d be easier, so… I’m… my question really is, like.
121 00:14:10.940 ⇒ 00:14:16.879 Sheshu Chandrasekar: do you store your meeting notes after a client, meeting, like, in Notion, or…
122 00:14:17.130 ⇒ 00:14:23.720 Sheshu Chandrasekar: Does it… do you just reference a platform? Because it sounds like Slack is, like, kind of, like you said, the system of record, but it’s not the most…
123 00:14:23.840 ⇒ 00:14:24.520 Sheshu Chandrasekar: Efficient.
124 00:14:25.210 ⇒ 00:14:37.129 Amber Lin: Yeah, I guess I had two things, so one on the meeting notes. When I have a longer client call that I need to take notes on a Notion, I would try and store it in, like.
125 00:14:37.270 ⇒ 00:14:41.860 Amber Lin: Either in the documentation, Database, or in the…
126 00:14:42.000 ⇒ 00:14:48.329 Amber Lin: So, it was stored in Notion. Smaller meetings, meetings I forgot to take notes on.
127 00:14:48.330 ⇒ 00:15:03.289 Amber Lin: I would just use the platform and summarize the action items, and usually that just goes straight to linear, or it gets sent on Slack. So, as you can see on ABC, I don’t have too many meeting note documents, and I’ve archived all of them, because they’re, like.
128 00:15:03.290 ⇒ 00:15:14.759 Amber Lin: they’re not valid anymore. So that’s on how I do meeting notes. And in terms of the tagging, I would love to use it. Would you guys be able to create, say, like, a…
129 00:15:15.110 ⇒ 00:15:22.260 Amber Lin: Database template with all the fields that you think is necessary, so we can standardize across different clients.
130 00:15:22.550 ⇒ 00:15:22.920 Sheshu Chandrasekar: Yeah.
131 00:15:22.920 ⇒ 00:15:30.480 Amber Lin: it’s harder to, like, add the tags individually, add the fields individually. I think that creates way too much friction.
132 00:15:30.840 ⇒ 00:15:43.199 Sheshu Chandrasekar: Yeah, we can absolutely do that. And that’s actually great, because it’ll automatically, like, upload it to this documents database, so we don’t have to always do, like, bookkeeping of any sort, so we can definitely have that for you.
133 00:15:43.670 ⇒ 00:15:44.500 Amber Lin: Great. Cool.
134 00:15:45.460 ⇒ 00:15:47.349 Amber Lin: Awesome. Mustafa had something.
135 00:15:47.530 ⇒ 00:16:00.539 Mustafa Raja: Yeah, I’m also wondering if we should, you know, add another step to this automation that we have on the front end, or in the platform, so it creates the, what’s it called? A summary,
136 00:16:00.540 ⇒ 00:16:07.569 Mustafa Raja: of the meeting, you know? So I’m wondering if it’s helpful if the meetings with the client directly, it should also land in the…
137 00:16:07.660 ⇒ 00:16:13.110 Mustafa Raja: Notion pages, relevant Notion pages. Like, for my meetings.
138 00:16:13.310 ⇒ 00:16:21.380 Mustafa Raja: Default, there should be a database regarding that, and the transcript and the summary could land there.
139 00:16:22.730 ⇒ 00:16:25.259 Mustafa Raja: It might be helpful for SLs.
140 00:16:26.070 ⇒ 00:16:27.519 Mustafa Raja: If they want to look at that.
141 00:16:30.050 ⇒ 00:16:36.369 Sheshu Chandrasekar: Gotcha, so you’re saying all the… all the Notion doc… all the notes should be in the Notion. It should live in Notion, but…
142 00:16:36.780 ⇒ 00:16:40.750 Sheshu Chandrasekar: There should only be summaries, not, like, individual task items or anything like that.
143 00:16:43.170 ⇒ 00:16:44.630 Mustafa Raja: I guess it,
144 00:16:48.290 ⇒ 00:16:50.160 Mustafa Raja: I’m wondering if it’s helpful or not.
145 00:16:51.430 ⇒ 00:16:53.400 Mustafa Raja: You know? These summaries…
146 00:16:53.400 ⇒ 00:16:53.720 Sheshu Chandrasekar: Yeah.
147 00:16:53.720 ⇒ 00:16:54.870 Mustafa Raja: You know?
148 00:16:55.170 ⇒ 00:16:56.829 Mustafa Raja: If these are useful or not.
149 00:16:58.270 ⇒ 00:17:08.750 Clarence Stone: Well, I’ll say it this way, Mustafa. How about, like, if you think it’ll be useful for your projects, feel free to try it, and if it works, you know, share it with the group, right?
150 00:17:08.770 ⇒ 00:17:25.289 Clarence Stone: Like, one of the biggest things is, I know this looks very standardized right now, by the way, I gave that template to Amber, but, like, I don’t want to dictate to you guys how to keep track of your documents, I just want to be able to tell you these are the things that are, like, like,
151 00:17:25.290 ⇒ 00:17:34.340 Clarence Stone: You’re gonna be asked, so, like, if you’re gonna have to, you know, save that information somewhere to be able to answer those questions, then, you know, create a system that works for you and your team.
152 00:17:34.820 ⇒ 00:17:35.540 Mustafa Raja: Okay.
153 00:17:38.000 ⇒ 00:17:44.549 Clarence Stone: But Amber is showing you her best practices, because, like, she’s been doing this like a champ for a while, so I think, like, it’s a really great starting point.
154 00:17:53.840 ⇒ 00:17:59.460 Sheshu Chandrasekar: Yeah, and honestly, now I think about it, so I was talking to a CSO yesterday.
155 00:17:59.660 ⇒ 00:18:04.200 Sheshu Chandrasekar: And he was telling me how EPs would find it useful if
156 00:18:04.310 ⇒ 00:18:09.620 Sheshu Chandrasekar: you can summarize, like, on a week-to-week basis, what was happening in each client’s Slack channel.
157 00:18:10.170 ⇒ 00:18:14.949 Sheshu Chandrasekar: Would that be helpful for an EP to… Quickly get information.
158 00:18:15.260 ⇒ 00:18:20.139 Clarence Stone: That’d be helpful for everybody. That’s the same feedback I got from SLs. Amber…
159 00:18:20.140 ⇒ 00:18:20.890 Sheshu Chandrasekar: No way.
160 00:18:21.500 ⇒ 00:18:35.309 Clarence Stone: Right? Like, the SLs are saying, like, hey, like, there’s some times, sir, there’s so many projects, and, like, I don’t have any data work, you know, associated that week, or, you know, that month. I don’t really know what’s going on.
161 00:18:35.990 ⇒ 00:18:44.849 Clarence Stone: Right? Like, those little comments and communications that happen in Slack, it’s hard to keep up when there’s, like, 6 of them that they have to run for stand-up.
162 00:18:47.110 ⇒ 00:18:59.660 Sheshu Chandrasekar: Yeah, that’s a great point. Maybe I’ll bring it up with Gabe, because that should be a platform feature, in my opinion, where you can just search out what was happening on a week-to-week basis, or, you know, even, as you said, on a month-to-month cadence as well.
163 00:19:00.910 ⇒ 00:19:08.940 Clarence Stone: Yeah, and I think, like, Slack communications are the weirdest ones to design a solution like that for, because
164 00:19:09.070 ⇒ 00:19:10.060 Clarence Stone: like…
165 00:19:10.530 ⇒ 00:19:16.389 Clarence Stone: we wouldn’t say, like, unless you guys disagree, let me know, right? Like, let’s say there was a meeting.
166 00:19:16.750 ⇒ 00:19:22.680 Clarence Stone: We weren’t… we’re not gonna, like, post anything about that until the meeting is done, and then somebody pings, how did it go?
167 00:19:23.400 ⇒ 00:19:34.730 Clarence Stone: Right? And then, like, somehow AI has to understand, like, when it gets a message, something like that, right? How was the meeting? How did it go? Or, like, whatever comes after, that’s important.
168 00:19:37.510 ⇒ 00:19:38.790 Sheshu Chandrasekar: That makes a lot of sense.
169 00:19:39.020 ⇒ 00:19:40.090 Clarence Stone: Right.
170 00:19:40.090 ⇒ 00:19:40.420 Sheshu Chandrasekar: Yeah.
171 00:19:40.420 ⇒ 00:19:43.770 Clarence Stone: Because there’s no other event. It doesn’t understand…
172 00:19:43.940 ⇒ 00:19:45.719 Clarence Stone: That there was a meeting, because…
173 00:19:45.850 ⇒ 00:19:49.030 Clarence Stone: like, we don’t use Slack for meetings.
174 00:19:53.080 ⇒ 00:20:00.770 Sheshu Chandrasekar: Yeah, I mean, sometimes we huddle, but I guess those are, like, only for short-term conversations, not formal, right? It’s like, hey, let me hop on quickly, so…
175 00:20:00.770 ⇒ 00:20:04.190 Clarence Stone: Yeah, same for the, like, client meetings are all on Zoom, right?
176 00:20:04.480 ⇒ 00:20:05.110 Sheshu Chandrasekar: Yeah.
177 00:20:05.670 ⇒ 00:20:06.130 Clarence Stone: So, it’.
178 00:20:06.130 ⇒ 00:20:07.370 Sheshu Chandrasekar: No, that’s a great point.
179 00:20:08.510 ⇒ 00:20:15.049 Sheshu Chandrasekar: Because the reason why I… want to implement this tool is because if we’re onboarding new folks, right,
180 00:20:15.230 ⇒ 00:20:19.889 Sheshu Chandrasekar: I feel like there’s one way to go about doing, like, reading, like, oh, what’s, like.
181 00:20:20.140 ⇒ 00:20:34.499 Sheshu Chandrasekar: brain forge about, or, like, how do I use this tool, or how do I understand the client, versus just talking with the chatbot to get more info on, like, what’s been happening on a month-to-month cadence, like, you know, outlining pain points and stuff like that. So, if it’s helpful for everyone, I think
182 00:20:34.830 ⇒ 00:20:41.419 Sheshu Chandrasekar: I can make a case for it to build, like, a Slack summary, like, bot of some sort, like a lightweight RAG tool.
183 00:20:41.930 ⇒ 00:20:50.360 Clarence Stone: Yeah, I mean, to be honest, for EPs and SLs, it… you guys tell me, right? Amber and Mustaf, like, what if you guys got it every day?
184 00:20:50.840 ⇒ 00:20:54.970 Clarence Stone: like, just a wrap-up of, like, what the Slack conversations were about.
185 00:20:55.680 ⇒ 00:21:00.030 Clarence Stone: like, two lines, right? Maybe some bullet points.
186 00:21:00.720 ⇒ 00:21:13.899 Amber Lin: I know we were trying to do that with different client hubs. We did that for a brief period of time, it just wasn’t accurate way back then, so if it was accurate, then it will be really helpful.
187 00:21:13.920 ⇒ 00:21:26.239 Amber Lin: But also, like, I also feel like most of us are on the projects that we’re working on, especially for EPs. For CSOs, also, they’re usually on the projects, so…
188 00:21:26.370 ⇒ 00:21:31.529 Amber Lin: I think the person that would help the most is the SLs, for them to run stand-up.
189 00:21:32.530 ⇒ 00:21:33.460 Clarence Stone: Okay.
190 00:21:33.460 ⇒ 00:21:33.890 Sheshu Chandrasekar: Gotcha.
191 00:21:35.540 ⇒ 00:21:37.900 Sheshu Chandrasekar: Yeah, and I didn’t mean to hijack this meeting, so I’m.
192 00:21:37.900 ⇒ 00:21:40.899 Amber Lin: No, okay, this is the… this is relevant discussion.
193 00:21:41.280 ⇒ 00:21:41.630 Sheshu Chandrasekar: Okay.
194 00:21:41.630 ⇒ 00:21:46.330 Amber Lin: So the next question we have here…
195 00:21:48.480 ⇒ 00:21:52.580 Amber Lin: So, we have risks and issues.
196 00:21:54.810 ⇒ 00:22:02.069 Amber Lin: I did just put a… I put, like, a table right here of what it is, who raised it.
197 00:22:02.210 ⇒ 00:22:14.360 Amber Lin: So, for, I guess, for example, like, we could say… Andy, Central Doc Issues… And the zip… Missing…
198 00:22:15.170 ⇒ 00:22:24.239 Amber Lin: assignments… like, I don’t know how detailed this should be, and probably I would archive issues that we’ve already resolved.
199 00:22:24.400 ⇒ 00:22:28.080 Amber Lin: But, like, that… that could be an easy…
200 00:22:28.300 ⇒ 00:22:32.109 Amber Lin: view of, okay, I see that these are the issues.
201 00:22:32.430 ⇒ 00:22:37.649 Amber Lin: I can go access the documents there, and then I can read it here.
202 00:22:37.780 ⇒ 00:22:38.410 Amber Lin: What do you think?
203 00:22:39.910 ⇒ 00:22:45.549 Mustafa Raja: So, for me, in my weekly deck that I… that I make to present.
204 00:22:45.920 ⇒ 00:22:51.170 Mustafa Raja: I mentioned the risks over there, so my presentations would all have
205 00:22:51.420 ⇒ 00:23:03.029 Mustafa Raja: risks for each week, but I guess there should be a centralized database to have that. Maybe in this one, the one that’s, you know, right up,
206 00:23:03.030 ⇒ 00:23:14.350 Mustafa Raja: in the document, we could, have risks and issues that are, currently ongoing, and, we should have another database of.
207 00:23:15.020 ⇒ 00:23:19.109 Mustafa Raja: a list of risks that, you know, are now…
208 00:23:19.110 ⇒ 00:23:36.569 Amber Lin: Makes sense, makes sense, yeah. And that, like, because what I’m… when I do these documents, I’m thinking if ultimately these get synced to Krisher, or synced to Git, so that we can access it in Krisher, so it would be nice if we can list out everything in one place.
209 00:23:36.700 ⇒ 00:23:37.230 Mustafa Raja: Yeah.
210 00:23:37.230 ⇒ 00:23:38.010 Amber Lin: Cool.
211 00:23:38.700 ⇒ 00:23:48.720 Amber Lin: Next thing we have here is the time tracking, which I also think is… will relate to the margin and the metrics later.
212 00:23:48.880 ⇒ 00:23:59.730 Amber Lin: I currently only have… I don’t even have the Clockify here, so… actually, let me put… Down here…
213 00:24:00.360 ⇒ 00:24:01.034 Amber Lin: Hmm…
214 00:24:03.970 ⇒ 00:24:08.840 Mustafa Raja: I guess I’m not actively tracking who’s spending how much on my projects.
215 00:24:09.270 ⇒ 00:24:12.210 Amber Lin: Yeah, I want to talk about that, so…
216 00:24:12.890 ⇒ 00:24:20.579 Amber Lin: What is a good cadence of checking how much time people are spending? Because we work on weekly sprints.
217 00:24:20.750 ⇒ 00:24:23.590 Amber Lin: What’s the cadence, do you think?
218 00:24:24.240 ⇒ 00:24:25.269 Clarence Stone: Is that one.
219 00:24:26.010 ⇒ 00:24:36.080 Clarence Stone: Yeah, from my personal experience, the way I like to do it when I’m, like, leading a project is I check in every month and at every milestone.
220 00:24:38.200 ⇒ 00:24:43.749 Clarence Stone: So, if we just, like, delivered a huge feature to the client, milestone 2, that’s, like.
221 00:24:44.160 ⇒ 00:25:00.049 Clarence Stone: one of my top, timelines to check, like, okay, how many hours did it take for us to finish this milestone, right? And then I just do a quick check on the SOW just to make sure that, you know, I’m not, burning through my projections.
222 00:25:00.810 ⇒ 00:25:02.100 Amber Lin: Hmm. Gosh.
223 00:25:02.100 ⇒ 00:25:07.350 Mustafa Raja: You could also group by, people in the Clockify to get the…
224 00:25:08.010 ⇒ 00:25:11.799 Mustafa Raja: time spent by each person is, so… Yeah.
225 00:25:13.080 ⇒ 00:25:13.529 Amber Lin: That’s nice.
226 00:25:13.530 ⇒ 00:25:14.230 Mustafa Raja: Indiana.
227 00:25:14.530 ⇒ 00:25:15.280 Mustafa Raja: This view.
228 00:25:15.280 ⇒ 00:25:18.499 Amber Lin: Cool. Yeah, that’s really nice. Let me update that.
229 00:25:22.450 ⇒ 00:25:29.459 Amber Lin: Ideally, I… I still want to use the OmniDash that we created, I just think it’s…
230 00:25:29.620 ⇒ 00:25:39.450 Amber Lin: I just think it’s better than the Clockify interface. I really don’t like toggling, like, oh, this week, last week, so… ideally, I want to use the Omni…
231 00:25:39.870 ⇒ 00:25:45.810 Amber Lin: Dashboard… And then…
232 00:25:48.190 ⇒ 00:26:03.709 Clarence Stone: And… sorry, Amber. Hey, Sashu, since you’re here, can you, make sure you take down some notes on this? Like, I think we should, just make a backlog for your ops team to continue the support, so, like, Amber would like that…
233 00:26:04.060 ⇒ 00:26:11.739 Clarence Stone: time tracking in Omni, and I will give you guys an even bigger challenge. It would be amazing if you just got a Slack pin.
234 00:26:12.400 ⇒ 00:26:18.319 Clarence Stone: At the end of the, like, week, or at the end of the month, to say, this is how much time you’ve used.
235 00:26:20.690 ⇒ 00:26:23.199 Sheshu Chandrasekar: Okay, yeah, most definitely. Writing that down right now.
236 00:26:23.200 ⇒ 00:26:29.089 Clarence Stone: That would be amazing for me. Man, if I had that, I would be over the moon, because…
237 00:26:29.350 ⇒ 00:26:35.970 Clarence Stone: Yeah, managing this and remembering to go to the dashboard, regardless of, you know, if it’s Clockify or Omni, is just another thing, right?
238 00:26:36.640 ⇒ 00:26:37.300 Sheshu Chandrasekar: Yeah.
239 00:26:38.490 ⇒ 00:26:44.010 Sheshu Chandrasekar: No, that makes a lot of sense. Like, and we’re working on Omni Dashboards, so this is a perfect use case for us.
240 00:26:44.970 ⇒ 00:26:45.750 Clarence Stone: Great.
241 00:26:45.750 ⇒ 00:26:59.230 Amber Lin: Monthly… Week, weekly review… Monthly check… Milestone.
242 00:26:59.700 ⇒ 00:27:02.359 Amber Lin: Check. Question mark.
243 00:27:03.060 ⇒ 00:27:21.910 Amber Lin: Okay, let’s look at the next one. So, on status reports, I guess there’s status reports and also status reports we send, like, stuff we send to clients. I currently send status reports with email, if that’s a
244 00:27:22.090 ⇒ 00:27:33.499 Amber Lin: That’s how Klein prefers we do a presentation and also send a Friday email. Let’s… let’s create a…
245 00:27:33.800 ⇒ 00:27:37.190 Amber Lin: Communication section.
246 00:27:38.000 ⇒ 00:27:52.280 Amber Lin: So… let’s… Let’s do here… Communication press… Communications, so I’ll say… Weekly presentation.
247 00:27:54.060 ⇒ 00:28:00.280 Amber Lin: Thursday, and then Friday, email… Project updates.
248 00:28:00.820 ⇒ 00:28:02.050 Mustafa Raja: Yep. And then…
249 00:28:02.260 ⇒ 00:28:05.680 Amber Lin: Yeah, I think I can link the drive…
250 00:28:06.270 ⇒ 00:28:09.970 Amber Lin: Have the drive of the presentation.
251 00:28:11.290 ⇒ 00:28:17.620 Amber Lin: And then I also have the email… thread.
252 00:28:18.600 ⇒ 00:28:20.490 Amber Lin: ABC project.
253 00:28:21.100 ⇒ 00:28:21.910 Amber Lin: Updates.
254 00:28:23.550 ⇒ 00:28:31.929 Mustafa Raja: Cool. For me, for me, it’s weekly presentations, plus my CSO sends a Friday, end of week.
255 00:28:32.220 ⇒ 00:28:33.730 Mustafa Raja: Summary to…
256 00:28:33.730 ⇒ 00:28:37.639 Amber Lin: Gotcha Yeah, is it on Slack or on email?
257 00:28:37.640 ⇒ 00:28:38.420 Mustafa Raja: on Slack.
258 00:28:38.940 ⇒ 00:28:41.370 Amber Lin: Gotcha. Could you note that down as well?
259 00:28:41.570 ⇒ 00:28:46.450 Amber Lin: Of who’s responsible, and then when it’s sent each week.
260 00:28:47.230 ⇒ 00:28:49.719 Mustafa Raja: Yeah, yeah. Yeah, it’s on Friday.
261 00:28:50.220 ⇒ 00:28:50.860 Amber Lin: Cool.
262 00:28:52.010 ⇒ 00:28:55.339 Amber Lin: Oh, so this is, like, the communication cadence.
263 00:28:55.510 ⇒ 00:28:59.450 Amber Lin: regular meeting cadence, I think we all have noted that.
264 00:28:59.670 ⇒ 00:29:01.220 Mustafa Raja: Hmm. Down…
265 00:29:01.750 ⇒ 00:29:09.240 Amber Lin: So this is, like, with client… internal…
266 00:29:12.170 ⇒ 00:29:20.329 Amber Lin: Oh, I also have a question. Do you have planning and grooming sessions, kind of like the Wednesday working session we have for ABC?
267 00:29:21.420 ⇒ 00:29:24.290 Mustafa Raja: Right now, there isn’t, but,
268 00:29:24.530 ⇒ 00:29:27.850 Mustafa Raja: I’m going to set up one for, Friday.
269 00:29:27.960 ⇒ 00:29:28.620 Mustafa Raja: So…
270 00:29:28.620 ⇒ 00:29:29.040 Amber Lin: I see.
271 00:29:29.040 ⇒ 00:29:38.359 Mustafa Raja: we’ll plan for fri- we’ll plan on Friday end of day. So, in the Monday meeting, Monday stand-up, we know what we are going to do for the week.
272 00:29:38.840 ⇒ 00:29:52.110 Amber Lin: Awesome, okay. So, I think we… for each project, I wanted to make sure everybody had, like, a weekly, at least bi-weekly grooming session to go through the Gantt,
273 00:29:52.110 ⇒ 00:29:52.610 Mustafa Raja: Yes.
274 00:29:52.610 ⇒ 00:29:54.259 Amber Lin: update the Gantt.
275 00:29:54.260 ⇒ 00:30:01.000 Mustafa Raja: I do go through the Gantt, and we do plan, but it’s not fixed cadence, but I want to make a fixed cadence.
276 00:30:01.000 ⇒ 00:30:12.540 Amber Lin: Awesome, okay, that’s great to hear. So, up to Gantt… Update, linear… Tickets… Yeah.
277 00:30:13.180 ⇒ 00:30:14.000 Amber Lin: Cool.
278 00:30:21.930 ⇒ 00:30:31.489 Amber Lin: Alright, so main client contact… Escalate issues, internal… Okay, let’s go through…
279 00:30:31.760 ⇒ 00:30:37.520 Amber Lin: Main client contact, and who’s the executive sponsor?
280 00:30:37.760 ⇒ 00:30:44.089 Clarence Stone: And just as a call-out here, you know, we don’t experience this too much right now, but we will soon.
281 00:30:44.240 ⇒ 00:30:50.280 Clarence Stone: We may have multiple projects with the same client, where you have different stakeholders for each.
282 00:30:50.800 ⇒ 00:30:51.880 Amber Lin: Project.
283 00:30:52.060 ⇒ 00:31:03.860 Clarence Stone: Right? Eden, I think, is a good example of one, where we’ve, you know, we’ve got Zaron working directly with one of the directors, and then, like, you guys do a…
284 00:31:04.100 ⇒ 00:31:14.909 Clarence Stone: a full presentation to everybody, right? And that’s really why I came over that question, is like, who… like, which exec is this project for, right? And, you know…
285 00:31:15.100 ⇒ 00:31:18.589 Clarence Stone: And is it different from others? So, it’s just important to…
286 00:31:19.810 ⇒ 00:31:26.420 Mustafa Raja: Yeah, it’s just with a default, so we have, we have this, data platform project.
287 00:31:26.540 ⇒ 00:31:36.440 Mustafa Raja: But, we have some streams, and, I guess we have about 3 different stakeholders for each of the streams.
288 00:31:37.280 ⇒ 00:31:43.020 Mustafa Raja: And we are, meeting with, with directly with the, stakeholders.
289 00:31:44.330 ⇒ 00:31:45.270 Amber Lin: Gotcha.
290 00:31:45.910 ⇒ 00:31:47.890 Amber Lin: Person to communicate.
291 00:31:49.360 ⇒ 00:31:53.139 Amber Lin: Like, I can say, for example, for Andy, I’ll say.
292 00:31:53.420 ⇒ 00:31:57.460 Amber Lin: Yvette is the main stakeholder.
293 00:31:58.300 ⇒ 00:32:00.100 Amber Lin: June.
294 00:32:00.100 ⇒ 00:32:04.780 Clarence Stone: Oh, yeah, you don’t have to do that if you have that table down there. That was perfect.
295 00:32:04.780 ⇒ 00:32:08.119 Amber Lin: That’s true, okay. Well, let’s say…
296 00:32:08.120 ⇒ 00:32:09.590 Clarence Stone: Like, that table was good.
297 00:32:09.730 ⇒ 00:32:12.560 Clarence Stone: Right. Like, did you guys want to say anything else in here?
298 00:32:13.070 ⇒ 00:32:15.990 Amber Lin: Person to communicate to.
299 00:32:16.970 ⇒ 00:32:17.580 Clarence Stone: Yeah.
300 00:32:18.040 ⇒ 00:32:18.740 Amber Lin: Cool.
301 00:32:22.840 ⇒ 00:32:29.089 Clarence Stone: Yeah, and then there’s Bo, and then Bobby, and Les, yeah, there we go, there’s so many more.
302 00:32:30.350 ⇒ 00:32:34.139 Amber Lin: Like, these are the main people on the Andy side.
303 00:32:34.630 ⇒ 00:32:44.279 Amber Lin: Alright, so next one, how do we escalate issues that need leadership attention? So I think there is one, is…
304 00:32:44.440 ⇒ 00:33:01.710 Amber Lin: how do we escalate, and two of what needs escalation. So let’s write down… say, internal… Processes…
305 00:33:09.370 ⇒ 00:33:28.069 Clarence Stone: And some more context for that one, is, you know, the one thing that is really challenging for Utama Robert is to just get a random email out of the blue from a client, right, saying, like, hey, I told somebody this over and over again, I don’t think they’re not… they’re understanding it.
306 00:33:29.010 ⇒ 00:33:29.890 Clarence Stone: Right.
307 00:33:32.280 ⇒ 00:33:41.919 Clarence Stone: And, you know, when they follow up, it was just like, oh, yeah, I misunderstood what the ask was, right? Like, so, at any point, if, like.
308 00:33:43.420 ⇒ 00:33:51.929 Clarence Stone: There is… if you’re unsure, and the client is, like, asking for something, and you’re not sure how to do it, you should definitely escalate those things, or at least, like.
309 00:33:52.330 ⇒ 00:33:59.349 Clarence Stone: bring your three team leaders in and talk about it, right? And just log that as an issue that was identified.
310 00:34:00.740 ⇒ 00:34:14.149 Amber Lin: Cool. So I’m making this into the same section, because these are the stuff that gets escalated. Also added a prevention section of, for example, like, the sentiment,
311 00:34:17.230 ⇒ 00:34:41.840 Amber Lin: and owner… So… Like, for example… For… EPs… Escalate… Architecture… Broad technical planning issues.
312 00:34:47.199 ⇒ 00:34:54.250 Amber Lin: Or client dissatisfaction… What else?
313 00:34:54.400 ⇒ 00:35:04.870 Amber Lin: Continued… Errors or complaints… Oh, jeez.
314 00:35:13.570 ⇒ 00:35:20.340 Amber Lin: Say, Lee… Weekly… grooming… Wow.
315 00:35:21.900 ⇒ 00:35:23.560 Amber Lin: Or an issue…
316 00:35:28.180 ⇒ 00:35:34.109 Amber Lin: Summarized. Sophia, what else do you think we should do, and what else should we escalate here?
317 00:35:43.320 ⇒ 00:35:48.730 Clarence Stone: I think that goes for CSOs too, because CSOs are also probably talking to the client a lot, right?
318 00:35:49.570 ⇒ 00:36:03.589 Amber Lin: Cool. Escalate… So, when we escalate, who are we escalating to? So, there’s issues that we can discuss
319 00:36:03.750 ⇒ 00:36:17.699 Amber Lin: as a group of EPCSSL, like, that’s a layer escalation, and then there’s another layer where we escalate to, the CEOs, or say, who tell them, Robert, hey, these are the main…
320 00:36:17.740 ⇒ 00:36:24.040 Amber Lin: like, account issues. So what are… what are the different layers, and what goes where?
321 00:36:24.430 ⇒ 00:36:40.660 Clarence Stone: So, so, here’s an example. You know, there, there… I know of a client that is very particular about the way the Excel spreadsheets are, formatted when they… when the team shares, right? And…
322 00:36:40.670 ⇒ 00:36:55.350 Clarence Stone: the person who’s typically sharing is not great at using Excel and doing pivots, or, like, doing VLOOGUPs, or things like that, so it comes off to the client that we really don’t understand how to, you know, work with data.
323 00:36:55.400 ⇒ 00:37:12.509 Clarence Stone: Right? So if that got escalated, you know, and let’s say I’m the CSO and I experience that, like, I would just pull the team in and say, hey guys, I am awful at using Excel. Would any of you two mind, like, driving while we do the presentation?
324 00:37:13.170 ⇒ 00:37:22.410 Clarence Stone: Right. And let’s say, Amber, like, the team is like, got it, the SL is, the SL’s really good at using Excel, right? Like, he’s gonna take over.
325 00:37:22.410 ⇒ 00:37:34.260 Clarence Stone: For just presenting that part. Okay, well, you guys already resolved it at your level, you can just mark it as a risk, and say it was raised, and then we talked about it, and we’re just gonna switch who presents the Excel.
326 00:37:35.090 ⇒ 00:37:36.040 Clarence Stone: Right?
327 00:37:37.350 ⇒ 00:37:56.900 Clarence Stone: So that’s, like, one that you can take care of at your layer, but maybe there’s another issue where it’s much bigger, where the client’s just like, this isn’t what I asked for at all, or something like that, right? Or this is the wrong technology, it’s not the right feature, and then you guys look back at the… you guys talk about it, and you’re like, no, this is exactly what they told us to do, right? I would…
328 00:37:56.900 ⇒ 00:38:04.999 Clarence Stone: then, formulate maybe some plans of action on how we might be able to get the client what they want, and then escalate it to, Utam or Robert.
329 00:38:06.490 ⇒ 00:38:18.340 Clarence Stone: the presentation to Otama Robert would be, like, hey, client said this, right? This… it did match what we were doing in this way, and I think this is one approach that we can do to… to solve that.
330 00:38:19.120 ⇒ 00:38:26.449 Amber Lin: Gotcha, okay. So this is… let’s say level 1 is that, and then let’s say level 2…
331 00:38:27.240 ⇒ 00:38:29.410 Amber Lin: Is to…
332 00:38:32.730 ⇒ 00:38:38.079 Clarence Stone: And here’s the thing, I think you guys are already doing this, but mostly over Slack, right? And we don’t…
333 00:38:38.080 ⇒ 00:38:39.020 Amber Lin: Yeah.
334 00:38:39.020 ⇒ 00:38:44.829 Clarence Stone: We don’t get to save those things, and I don’t get to show Utam and Robert, like, hey, these, like, teams were on it. They understand.
335 00:38:45.690 ⇒ 00:38:46.780 Amber Lin: Or…
336 00:38:47.040 ⇒ 00:38:56.700 Amber Lin: Gotcha. So let’s say if we were… we were to escalate… so we discussed… let’s do… okay. Well, issue comes, we do this process.
337 00:38:56.820 ⇒ 00:39:00.229 Amber Lin: Figure out, okay, that it’s a…
338 00:39:00.550 ⇒ 00:39:06.940 Amber Lin: it’s a key issue, we need further escalation, then I say, like, this spike…
339 00:39:07.570 ⇒ 00:39:13.779 Amber Lin: We need to also plus a recommended solution.
340 00:39:14.340 ⇒ 00:39:17.309 Amber Lin: Plus, say, like, wrist…
341 00:39:18.120 ⇒ 00:39:18.730 Clarence Stone: Yep.
342 00:39:19.420 ⇒ 00:39:20.260 Amber Lin: 2%.
343 00:39:20.260 ⇒ 00:39:26.589 Clarence Stone: You can say, hey, we can do this, but it’ll take us another 3 weeks, right? But it’ll get us there, you know, stuff like that.
344 00:39:29.310 ⇒ 00:39:30.060 Amber Lin: Boyd.
345 00:39:30.860 ⇒ 00:39:33.339 Amber Lin: Good, Robert. Cool.
346 00:39:33.970 ⇒ 00:39:40.390 Amber Lin: So… Jay… Let’s go here…
347 00:39:59.750 ⇒ 00:40:02.780 Amber Lin: So, for prevention, what should we do?
348 00:40:03.340 ⇒ 00:40:09.250 Amber Lin: Like, I know I like… The stand-up format that you guys came up with, if…
349 00:40:09.510 ⇒ 00:40:13.530 Amber Lin: Two sentence from each of the leaders.
350 00:40:13.740 ⇒ 00:40:24.639 Amber Lin: I think that was very helpful, especially to talk about the sentiment. I don’t think we’re completely adhering to that, because we all get distracted of it, like, this issue, that issue.
351 00:40:24.640 ⇒ 00:40:35.760 Amber Lin: So, like, I guess this is an ask if you can translate to SLs, like, can you force us to adhere to it? Because I get distracted, and I talk about specific stuff.
352 00:40:36.590 ⇒ 00:40:42.910 Clarence Stone: Yeah, I got you. I know that’s happening on one of the three stand-ups more than others, and we’re working on it.
353 00:40:47.560 ⇒ 00:40:56.750 Sheshu Chandrasekar: honestly, maybe… maybe during a retros, we can bring it up saying, like, hey, like, here are the risks and issues and problems we faced, right? Here is the context.
354 00:40:57.160 ⇒ 00:40:58.680 Sheshu Chandrasekar: That was occurring.
355 00:40:58.680 ⇒ 00:40:59.400 Amber Lin: Hmm.
356 00:40:59.400 ⇒ 00:41:00.699 Sheshu Chandrasekar: And then from there.
357 00:41:00.950 ⇒ 00:41:05.729 Sheshu Chandrasekar: this is how we solved it. Now, did we… now, in that context that you paint.
358 00:41:05.910 ⇒ 00:41:15.380 Sheshu Chandrasekar: you should paint it, like, okay, who did we solve it with? Did I solve it with EPs, CSOs, or did I escalate it to Robert and Utam? And kind of, like.
359 00:41:15.660 ⇒ 00:41:20.920 Sheshu Chandrasekar: discuss it amongst yourself, like, when the project is done, right? Because then that…
360 00:41:21.220 ⇒ 00:41:28.770 Sheshu Chandrasekar: that codifies that knowledge a little bit, a little bit more. And also, we have it on record, so if you were to face another problem on another project.
361 00:41:29.010 ⇒ 00:41:34.479 Sheshu Chandrasekar: And someone already faced a similar problem, they can always go back and platform and be like, hey.
362 00:41:34.700 ⇒ 00:41:38.840 Sheshu Chandrasekar: I’m facing this problem, how did this person solve it?
363 00:41:39.380 ⇒ 00:41:44.680 Sheshu Chandrasekar: before bringing it up to EPCS, or SL. And right now, I’m thinking out loud, but…
364 00:41:45.060 ⇒ 00:41:45.939 Sheshu Chandrasekar: I think that would be a.
365 00:41:45.940 ⇒ 00:42:00.099 Amber Lin: Gosh, I hear you. I think this is what we were trying to do when we had a PMO. It was more of a PMO documentation. Like, when we… when I was trying to set up the PMO, we had a…
366 00:42:00.100 ⇒ 00:42:06.959 Amber Lin: Project closing process, where we needed… we had to fill out forms, we had to do a closing
367 00:42:06.960 ⇒ 00:42:19.649 Amber Lin: discussion, closing retro, and then fill out a closing doc where you would document the project knowledge. Currently, you mentioned retros. I don’t think any of the projects have
368 00:42:19.650 ⇒ 00:42:37.719 Amber Lin: retros. I don’t know if the EP CSSLs have retros, or if maybe this meeting counts as a retro, but we also don’t have project closing processes, so if you’re writing stuff down, like, I think you guys can debate if that’s something that we need to do.
369 00:42:40.020 ⇒ 00:42:44.870 Clarence Stone: That is good info, Amber. I think we should do it, so we’ll add it to the list.
370 00:42:45.220 ⇒ 00:42:53.470 Amber Lin: It will just… it will just add a lot more meetings, and I think a big part of our move to this is… is to reduce the amount of time.
371 00:42:53.470 ⇒ 00:42:54.840 Sheshu Chandrasekar: Use it, yeah.
372 00:42:54.840 ⇒ 00:42:57.970 Amber Lin: Yeah, so there’s… let’s say there’s,
373 00:42:58.790 ⇒ 00:43:16.630 Amber Lin: I can’t write it out for you. So… There is… Project… Retro… Project closing process… And…
374 00:43:16.840 ⇒ 00:43:24.880 Amber Lin: Knowledge, documentation… Sprint Retro.
375 00:43:26.020 ⇒ 00:43:33.160 Amber Lin: And that… EPSL, CSO… True.
376 00:43:33.990 ⇒ 00:43:47.430 Clarence Stone: And Sesshu, like, I think what we need to do is take a look at those processes and see how much of it we can help automate, right? Because, like, for example, like, we can just literally send out an email survey for the retro and say, like.
377 00:43:48.320 ⇒ 00:43:50.869 Clarence Stone: What, like, what, what…
378 00:43:50.990 ⇒ 00:44:02.989 Clarence Stone: like, ask all the retro questions, like, what did you expect to happen? What did happen? What are the high points? What are some low points? What are some learnings, right? Just have, like, people fill it out, that way you don’t have to have a meeting for it.
379 00:44:05.170 ⇒ 00:44:12.809 Amber Lin: Yeah, I do find that meetings are the most, helpful for retros when I used to run…
380 00:44:12.960 ⇒ 00:44:16.950 Amber Lin: the retros for us. If you don’t…
381 00:44:17.160 ⇒ 00:44:33.389 Amber Lin: name someone, they were not gonna think about it. So, if you want a retro and to extract the things that people were thinking about, I do think a retro, like a meeting is necessary.
382 00:44:33.660 ⇒ 00:44:40.039 Amber Lin: here. Like, for example, these were the retros we were…
383 00:44:40.610 ⇒ 00:44:43.020 Amber Lin: I think we were… oh, what is this?
384 00:44:47.960 ⇒ 00:44:51.940 Amber Lin: Yeah, so I think, for example, when I used to run it, we would
385 00:44:52.670 ⇒ 00:44:56.839 Amber Lin: Put down the stickies, and then have a session where we vote.
386 00:44:56.980 ⇒ 00:44:59.810 Amber Lin: And then we will summarize…
387 00:45:00.300 ⇒ 00:45:06.549 Amber Lin: After voting, summarize the most important stuff, group it into improvements to be made.
388 00:45:07.350 ⇒ 00:45:16.449 Amber Lin: And then… Like, list out the improvements after each sprint, so this was a bi-weekly process.
389 00:45:16.550 ⇒ 00:45:24.389 Amber Lin: Like, I don’t… it did take up a lot of time, so it’s up to us to decide if the benefit is worth it.
390 00:45:25.940 ⇒ 00:45:29.899 Clarence Stone: Yeah, I think at the very least, Andrew, we should do it at the end of a project.
391 00:45:30.160 ⇒ 00:45:31.500 Amber Lin: I agree.
392 00:45:36.500 ⇒ 00:45:45.000 Amber Lin: Cool, we have 15 minutes left, I think we can cover another… Another one…
393 00:45:45.570 ⇒ 00:45:48.659 Clarence Stone: Mustafa, are these questions making sense now, or, like…
394 00:45:48.660 ⇒ 00:45:49.370 Mustafa Raja: Yep.
395 00:45:49.540 ⇒ 00:45:50.720 Mustafa Raja: these meetings.
396 00:45:51.120 ⇒ 00:45:58.120 Clarence Stone: Sweet, awesome, thank you. This is good. Okay, we’re getting to really hard ones, so fair warning. Go for it, Amber.
397 00:45:59.000 ⇒ 00:45:59.620 Amber Lin: Cool.
398 00:46:00.200 ⇒ 00:46:03.840 Amber Lin: Steffa, how does your team handle this right now?
399 00:46:07.450 ⇒ 00:46:09.170 Mustafa Raja: Okay.
400 00:46:10.360 ⇒ 00:46:13.129 Mustafa Raja: I think the CSOs are just directly handling it.
401 00:46:13.580 ⇒ 00:46:15.160 Mustafa Raja: Mmm.
402 00:46:15.160 ⇒ 00:46:18.240 Amber Lin: Is the CSOs handling it, or is the SLs handling it?
403 00:46:22.790 ⇒ 00:46:24.019 Mustafa Raja: the CSOs.
404 00:46:25.300 ⇒ 00:46:29.460 Mustafa Raja: And then the update is just given to the SL.
405 00:46:30.410 ⇒ 00:46:31.620 Amber Lin: I see.
406 00:46:34.500 ⇒ 00:46:46.660 Clarence Stone: Yeah, and this is the other bit of feedback I got from the SL meeting, is that, they’re having a hard time enforcing standards and getting details on tickets, like.
407 00:46:47.050 ⇒ 00:46:53.480 Clarence Stone: There’s not enough information in them, they’re asking for more details on, like.
408 00:46:54.050 ⇒ 00:46:59.199 Clarence Stone: What is the definition of done, of the ticket requests? What are, you know.
409 00:46:59.380 ⇒ 00:47:09.800 Clarence Stone: the ways to test the requirements, you know, things like that. So I asked them to come up with, like, absolute requirements for ticket formatting, so they’ll come back to me with that, but…
410 00:47:09.800 ⇒ 00:47:24.460 Clarence Stone: From the EP standpoint, it’d be helpful if you guys can help enforce those standards, because the difficulties with stand-up every morning is, like, they don’t have enough information sometimes, and then we just spiral into talking about one topic.
411 00:47:28.150 ⇒ 00:47:28.820 Mustafa Raja: Yeah.
412 00:47:29.420 ⇒ 00:47:30.110 Amber Lin: Okay.
413 00:47:30.370 ⇒ 00:47:38.240 Amber Lin: So… Ticket… Details meets standards.
414 00:47:41.720 ⇒ 00:47:43.399 Amber Lin: To be defined.
415 00:47:43.500 ⇒ 00:47:45.760 Mustafa Raja: This would be helpful, yeah.
416 00:47:46.410 ⇒ 00:47:59.420 Amber Lin: Yeah, cool, so… And checking against, checking quality… I guess the first check… But, hmm.
417 00:47:59.620 ⇒ 00:48:03.769 Amber Lin: So, would this be the SL or the CSO checking for quality?
418 00:48:05.530 ⇒ 00:48:08.440 Mustafa Raja: For my thing, I think it’s going to be SL.
419 00:48:09.710 ⇒ 00:48:15.730 Mustafa Raja: Since, for my team, CSOs and I am working, so SL would be the reviewer, no?
420 00:48:19.720 ⇒ 00:48:20.290 Sheshu Chandrasekar: Wouldn’t it be.
421 00:48:20.750 ⇒ 00:48:22.579 Sheshu Chandrasekar: A joint process between the two.
422 00:48:23.920 ⇒ 00:48:24.850 Mustafa Raja: Yeah.
423 00:48:25.100 ⇒ 00:48:26.020 Mustafa Raja: I guess.
424 00:48:26.410 ⇒ 00:48:42.690 Clarence Stone: Yeah, I mean, if we were to go through that entire workflow session, it would be like, maybe I built something, I committed the code, the SL came in, took a look, and approved my pull request, and said everything looks good. Gotcha. And then that same week, it gets presented to the client, and the client says.
425 00:48:42.860 ⇒ 00:48:52.560 Clarence Stone: yeah, this is great, except I’d also like an additional tab, right? And then the CSO comes back and says, client’s really happy, they just asked for this additional one, you know, tab.
426 00:48:54.680 ⇒ 00:48:55.560 Clarence Stone: Got it. Right.
427 00:48:57.030 ⇒ 00:49:02.469 Sheshu Chandrasekar: I think… the CSO should kind of anticipate, like, okay.
428 00:49:02.980 ⇒ 00:49:11.860 Sheshu Chandrasekar: And I don’t know how… I think this may be difficult, but, like, the CSO in this case should anticipate, oh yeah, the client may need another tab, like, before the client would say it, right?
429 00:49:12.770 ⇒ 00:49:15.999 Clarence Stone: At some point. Yeah, yeah. So, you know, if…
430 00:49:16.000 ⇒ 00:49:35.719 Clarence Stone: That should have really happened with the ticket descriptions, right? Like, the SLs only know what needs to be built based on those ticket details and what’s been talked about, you know, to them. So, like, if the CSO knows, like, specific details that need to be built out, they need to make sure that they work with the EP to make sure the ticket details are correct.
431 00:49:35.720 ⇒ 00:49:39.539 Clarence Stone: I think that’s our, like, biggest deficiency, aside from Slack these days.
432 00:49:40.520 ⇒ 00:49:47.790 Clarence Stone: Like, do we have, like… a ton of details in our linear tickets. I don’t feel like we do.
433 00:49:48.820 ⇒ 00:49:51.969 Mustafa Raja: Yeah, for me, that is the case.
434 00:49:52.200 ⇒ 00:50:01.050 Mustafa Raja: But… but that is the case because, maybe I’m meeting with… meeting directly with CSOs, a lot.
435 00:50:01.380 ⇒ 00:50:02.530 Mustafa Raja: So…
436 00:50:03.380 ⇒ 00:50:10.110 Mustafa Raja: Yeah, for my tickets, I feel they really don’t need much description, but they do need description for SL.
437 00:50:10.480 ⇒ 00:50:12.459 Mustafa Raja: So I’m going to work on that now.
438 00:50:12.970 ⇒ 00:50:21.620 Clarence Stone: Yeah, and Mustafa, think about it at an even higher level, like, let’s say, you know, Utam or Robert get that email, say, from the client saying they’re.
439 00:50:21.620 ⇒ 00:50:22.070 Mustafa Raja: Oh, yeah.
440 00:50:22.420 ⇒ 00:50:25.100 Clarence Stone: you know, like, they’re gonna look at linear, and they’re gonna be like.
441 00:50:25.100 ⇒ 00:50:25.450 Mustafa Raja: Oh, no.
442 00:50:25.450 ⇒ 00:50:27.600 Clarence Stone: Right?
443 00:50:28.080 ⇒ 00:50:29.910 Mustafa Raja: You saved my life there.
444 00:50:30.960 ⇒ 00:50:49.619 Clarence Stone: So, so, you know, it’s not a good look, and it makes it hard for somebody to drop in and help you guys out as well. So, yeah, please share that with your team. There’s other impacts, right? I think you guys work well together that, you know, a lot of this documentation becomes additional work, but, you know, we’re really building a system for when things go wrong.
445 00:50:49.680 ⇒ 00:50:51.560 Clarence Stone: Because we want to reduce those. Yeah, yeah.
446 00:50:53.320 ⇒ 00:51:01.329 Sheshu Chandrasekar: Would it be useful to have, like, a linear ticket writing 101, like, every quarter of some sort, to kind of reinforce those standards?
447 00:51:04.360 ⇒ 00:51:10.079 Clarence Stone: Yeah, I mean, go for it. I think we need to get people to commit to a standard first. That’s, like, the biggest challenge.
448 00:51:10.080 ⇒ 00:51:12.150 Sheshu Chandrasekar: That’s true, that’s very true.
449 00:51:12.150 ⇒ 00:51:14.060 Mustafa Raja: Yeah, as ET, I’m going to commit to it.
450 00:51:14.200 ⇒ 00:51:15.240 Mustafa Raja: That’s for sure.
451 00:51:16.080 ⇒ 00:51:17.369 Clarence Stone: What’s up, Mustafa?
452 00:51:17.590 ⇒ 00:51:24.379 Mustafa Raja: Yeah, I said as EP, I would commit to this, because I’m just, I’m the one creating tickets for my team, right? So I’ll commit.
453 00:51:24.380 ⇒ 00:51:24.710 Clarence Stone: Okay.
454 00:51:24.710 ⇒ 00:51:26.200 Mustafa Raja: Whatever standard we set.
455 00:51:27.050 ⇒ 00:51:32.799 Clarence Stone: Sweet! Okay, cool. Yeah, that’s good to know. Like, so we really need from the SLs, like.
456 00:51:33.120 ⇒ 00:51:35.560 Clarence Stone: What do they need to see, right?
457 00:51:35.560 ⇒ 00:51:36.120 Sheshu Chandrasekar: Yeah.
458 00:51:37.580 ⇒ 00:51:47.139 Amber Lin: Is there any way we can make it easier? Because right now, I don’t have too much time to create the tickets. When I was a PM, that took up the whole…
459 00:51:47.200 ⇒ 00:51:57.449 Amber Lin: essentially half of my time just making tickets and making sure they have details. From… so right now, my tickets kind of come from the Gantt.
460 00:51:57.450 ⇒ 00:52:08.970 Amber Lin: and some minor changes or sub-issues that comes with it. There’s really not that much time to add all the details there without, like, dedicating hours
461 00:52:08.970 ⇒ 00:52:18.320 Amber Lin: when we create that ticket. So, like, is there any way to distribute the work, or is there any way to get
462 00:52:18.450 ⇒ 00:52:23.259 Amber Lin: Like, automations or tools to help with that?
463 00:52:23.410 ⇒ 00:52:28.870 Amber Lin: I know the AI team was working on some linear agents, some linear grooming help.
464 00:52:28.990 ⇒ 00:52:32.379 Amber Lin: Way back when. But…
465 00:52:32.950 ⇒ 00:52:41.119 Amber Lin: like, I would prefer to have some help, because this is… I don’t know how sustainable this is when everybody’s still working on the project.
466 00:52:41.630 ⇒ 00:52:42.410 Mustafa Raja: Hmm.
467 00:52:43.790 ⇒ 00:52:51.979 Clarence Stone: Yeah, that’s a good point. Okay, let’s brainstorm it together, Amber. So, I presume, right, and just…
468 00:52:52.390 ⇒ 00:52:54.460 Clarence Stone: And check me on this, is that…
469 00:52:54.700 ⇒ 00:53:02.180 Clarence Stone: If there isn’t that much detail on the linear ticket, but you guys have already talked about it, this information is somewhere.
470 00:53:02.960 ⇒ 00:53:04.840 Clarence Stone: Right. Where is it?
471 00:53:08.510 ⇒ 00:53:22.249 Clarence Stone: That’s what I’m trying to figure out. Like, everyone’s, you know, doing work, and they’re delivering work on the tickets, right? And there’s not too many details on them. So, there must be… that detail must be somewhere else, right?
472 00:53:25.820 ⇒ 00:53:30.610 Mustafa Raja: We discussed those tickets, in the grooming… the grooming meeting the most, I believe.
473 00:53:31.680 ⇒ 00:53:32.760 Clarence Stone: Okay, yeah, so…
474 00:53:32.760 ⇒ 00:53:37.190 Amber Lin: The high level is in the Gantt, and the discussion is also.
475 00:53:37.190 ⇒ 00:53:38.510 Mustafa Raja: So, yeah.
476 00:53:38.820 ⇒ 00:53:48.680 Mustafa Raja: I feel once the ticket is assigned, whatever happens after that, the progress should be, should be taken care of by the one who the ticket is assigned to, right?
477 00:53:49.060 ⇒ 00:53:57.610 Clarence Stone: Yep, I agree with that for sure, right? Like, if you pause for the day and say, like, this is where I’m at, like, you should leave a note to say it’s being worked on, right?
478 00:53:57.610 ⇒ 00:53:58.910 Mustafa Raja: Yeah, yeah.
479 00:53:59.220 ⇒ 00:54:11.569 Clarence Stone: For sure. But Amber, you’re saying, and Mustafa, you guys were both saying that it’s on that weekly meeting, you pretty much go through all the tickets that you’re gonna do that week, right? And you collect, like, information about it?
480 00:54:12.610 ⇒ 00:54:15.150 Mustafa Raja: Yeah, that’s pretty much it, yeah.
481 00:54:16.070 ⇒ 00:54:21.259 Clarence Stone: okay, let’s try to get creative. Like, maybe, Mustafa, you can give,
482 00:54:21.510 ⇒ 00:54:30.939 Clarence Stone: You can give Sesshu one of your weekly meetings, like, as a recording, and then see if he can, like, create tickets for you from that.
483 00:54:31.470 ⇒ 00:54:31.920 Mustafa Raja: Yeah.
484 00:54:31.920 ⇒ 00:54:35.470 Clarence Stone: Or Amber, do you have one? Like, like, maybe we can try it.
485 00:54:38.300 ⇒ 00:54:49.189 Amber Lin: I… I can. My worry is that, okay, I have these tickets in the Gantt already. Like, I have the tasks we need to do, I have a rough timeline there.
486 00:54:49.750 ⇒ 00:54:57.159 Amber Lin: When we create it from the transcript, it’s either gonna be duplicative, or it, like, it might not have
487 00:54:58.340 ⇒ 00:55:07.329 Amber Lin: If we generate it from the transcript, it might not be as clear as what we entered in the GAND, and we have to enter it again.
488 00:55:07.740 ⇒ 00:55:13.529 Amber Lin: So, I can give you the meeting note of the most recent grooming session.
489 00:55:13.800 ⇒ 00:55:17.890 Amber Lin: Let’s… let me find it…
490 00:55:17.890 ⇒ 00:55:34.810 Clarence Stone: So this is what I talked to Utama about over and over again, is that I’m really starting to feel like Linear and the Gantt are, like, overlapping in what they provide, right? And I’m not sure how to handle that, so I’m open to thoughts and suggestions on that as well.
491 00:55:35.430 ⇒ 00:55:44.950 Mustafa Raja: So, for my team, the tickets are going to be directly coming from the Gantt, right? So, directly coming from the Gantt, and then there would be ad hoc requests from the clients.
492 00:55:45.580 ⇒ 00:55:49.659 Mustafa Raja: And that is pretty much it, I believe, so…
493 00:55:49.770 ⇒ 00:55:58.679 Mustafa Raja: I guess, Sheshu, were you going to create the tickets using the platform tool that we have for Linea?
494 00:55:59.970 ⇒ 00:56:06.169 Sheshu Chandrasekar: No, I was going… I mean, I was going to use a mix of both. I want to write it first, and then see how well the platform
495 00:56:06.330 ⇒ 00:56:07.830 Sheshu Chandrasekar: As well, on the.
496 00:56:07.830 ⇒ 00:56:24.289 Mustafa Raja: I guess the source of truth of what the task is going to be would be the Gantt itself, and then… Gotcha. …what the description of the ticket is would be coming more from the transcript. Let me know if I’m correct, Tambo.
497 00:56:24.740 ⇒ 00:56:28.310 Amber Lin: Yeah, that makes sense. But we also, like, skip over things, we don’t talk.
498 00:56:28.310 ⇒ 00:56:28.840 Mustafa Raja: Yeah, yeah.
499 00:56:28.840 ⇒ 00:56:29.660 Amber Lin: everything.
500 00:56:29.970 ⇒ 00:56:30.530 Mustafa Raja: Yeah.
501 00:56:34.730 ⇒ 00:56:36.669 Sheshu Chandrasekar: Got it, and that’s where the Gantt…
502 00:56:37.150 ⇒ 00:56:44.110 Sheshu Chandrasekar: And maybe the meeting notes will come into play, because it would provide additional context. So we need to figure out
503 00:56:44.740 ⇒ 00:56:46.479 Sheshu Chandrasekar: How to use those sources.
504 00:56:50.390 ⇒ 00:56:51.510 Mustafa Raja: Yeah.
505 00:57:04.590 ⇒ 00:57:14.199 Sheshu Chandrasekar: So, when… when you’re… when you mean by skipping over, why… why do you skip over? Is it because it’s already implied, like, by existing linear tickets? Like, I’m a little confused there now, I think about it.
506 00:57:14.200 ⇒ 00:57:25.640 Amber Lin: Yeah, we don’t talk about everything, because, some stuff we’re not doing now, we say, okay, let’s go on to the next one. We have limited time, so we will only pick the most important ones to talk about.
507 00:57:27.600 ⇒ 00:57:28.350 Sheshu Chandrasekar: Got it.
508 00:57:28.780 ⇒ 00:57:29.540 Mustafa Raja: Yeah.
509 00:57:32.170 ⇒ 00:57:40.350 Mustafa Raja: I believe, and correct me if I’m wrong, I believe, we do move the tickets around, right? So, for the current… Yeah.
510 00:57:40.480 ⇒ 00:57:46.399 Mustafa Raja: We would have, for the current week, we would have only the tickets that we want to work on, right?
511 00:57:49.880 ⇒ 00:57:50.830 Amber Lin: Yes.
512 00:57:50.830 ⇒ 00:57:51.340 Mustafa Raja: Easily guarantee.
513 00:57:51.340 ⇒ 00:58:00.249 Amber Lin: So, at least in linear, I only put in cycle the stuff that we’re working on this week to make it more clear for the SLs.
514 00:58:02.150 ⇒ 00:58:04.190 Mustafa Raja: Yes, that is correct.
515 00:58:10.660 ⇒ 00:58:17.819 Mustafa Raja: I guess we would want to make, the Gantt chart our source of truth for what we are going to work on then, right?
516 00:58:20.920 ⇒ 00:58:22.900 Amber Lin: Don’t use me, but.
517 00:58:25.670 ⇒ 00:58:32.859 Mustafa Raja: Like, for example, for my project, whatever is in the week, it would be translated to the tickets, right?
518 00:58:33.860 ⇒ 00:58:40.529 Mustafa Raja: And then, I could just grab, transcript from the grooming ticket, and add descriptions.
519 00:58:41.200 ⇒ 00:58:44.209 Amber Lin: That’s… that’s true, that’s true, yeah.
520 00:58:44.980 ⇒ 00:58:59.190 Amber Lin: I do know sometimes, say, Sam, where you guys would break it down linear a little bit further, but as, like, a high-level ticket, like, it does translate over. I just don’t know what the SLs need for those tickets.
521 00:58:59.630 ⇒ 00:59:00.310 Mustafa Raja: Okay.
522 00:59:07.120 ⇒ 00:59:10.409 Amber Lin: Cool. We’re out of time, I think we went through…
523 00:59:10.710 ⇒ 00:59:16.990 Amber Lin: meaningful chunks today. Next time, I think we can go over… we’ll take…
524 00:59:18.050 ⇒ 00:59:33.680 Amber Lin: like, a meaningful chunk to go over the financial stuff. And then, last… the last part is more, like, strategic, it’s more about renewal, which is, more overlapping with the CSOs.
525 00:59:33.820 ⇒ 00:59:43.639 Amber Lin: responsibilities, or helping support their work there, so I think now we can talk about last, and maybe we can invite some CSOs to talk about how they think.
526 00:59:45.040 ⇒ 00:59:46.650 Clarence Stone: Yeah, that’s a great idea, Amber.
527 00:59:47.040 ⇒ 00:59:58.199 Clarence Stone: I think it’s so topical because, there’s gonna be a lot of renewables coming up, so it would be good to team you how to, you know, react and, you know, adapt to it.
528 00:59:59.150 ⇒ 00:59:59.810 Amber Lin: Cool.
529 01:00:00.040 ⇒ 01:00:07.009 Amber Lin: Awesome, so let’s… next week we’ll talk about finances, and then after that, we’ll go on to talk about
530 01:00:07.850 ⇒ 01:00:10.189 Amber Lin: the renewal on Klan Health.
531 01:00:11.470 ⇒ 01:00:12.410 Clarence Stone: Boom, sounds good.
532 01:00:12.700 ⇒ 01:00:13.220 Sheshu Chandrasekar: Sweet.
533 01:00:13.220 ⇒ 01:00:13.900 Amber Lin: Alright.
534 01:00:14.490 ⇒ 01:00:15.130 Mustafa Raja: Everyone.
535 01:00:15.130 ⇒ 01:00:16.330 Clarence Stone: Thank you.
536 01:00:16.560 ⇒ 01:00:17.509 Amber Lin: Thank you. Bye.
537 01:00:17.510 ⇒ 01:00:18.160 Mustafa Raja: Bang.