Meeting Title: SL Leads Weekly Sync Date: 2026-01-26 Meeting participants: Clarence Stone, Sheshu Chandrasekar, Samuel Roberts, Awaish Kumar
WEBVTT
1 00:03:07.620 ⇒ 00:03:08.690 Samuel Roberts: A…
2 00:03:10.500 ⇒ 00:03:11.250 Clarence Stone: Hey!
3 00:03:12.890 ⇒ 00:03:15.600 Samuel Roberts: Did you connect through Zoom or through Google Calendar?
4 00:03:16.850 ⇒ 00:03:22.450 Clarence Stone: I have no idea. I just got it passed over to me.
5 00:03:22.450 ⇒ 00:03:26.569 Samuel Roberts: Oh, okay, okay. Yeah, I think what happens when the thing gets transferred,
6 00:03:26.680 ⇒ 00:03:31.559 Samuel Roberts: it. Sometimes just the links just disappear. I don’t really know.
7 00:03:31.560 ⇒ 00:03:38.389 Clarence Stone: Yeah, so I don’t understand the Zoom stuff, so I just want to make sure everyone’s set up. Where do I go to even search? Hang on.
8 00:03:57.080 ⇒ 00:04:04.230 Clarence Stone: I don’t know. It seems like it’s on my calendar. I, like, how am I supposed to fix this, guys? You tell me, I’ve never used this.
9 00:04:04.230 ⇒ 00:04:07.089 Samuel Roberts: You see, you see the event, you see the event on the calendar?
10 00:04:07.600 ⇒ 00:04:09.480 Clarence Stone: Yeah, it’s on my calendar.
11 00:04:09.690 ⇒ 00:04:12.860 Samuel Roberts: Okay, let me… maybe… maybe it was just mine was not loaded, right?
12 00:04:12.860 ⇒ 00:04:13.370 Sheshu Chandrasekar: Whoa.
13 00:04:14.540 ⇒ 00:04:23.310 Clarence Stone: Yeah, like… Y’all… y’all can see it right here. So…
14 00:04:26.820 ⇒ 00:04:28.139 Clarence Stone: This is the one.
15 00:04:28.140 ⇒ 00:04:31.970 Samuel Roberts: Yeah… Right, there’s no… I don’t see a…
16 00:04:34.090 ⇒ 00:04:36.830 Samuel Roberts: Usually there’s, like, a Zoom link at the top there.
17 00:04:37.350 ⇒ 00:04:38.210 Clarence Stone: Oh.
18 00:04:41.340 ⇒ 00:04:42.240 Clarence Stone: Oh, you’re right.
19 00:04:42.240 ⇒ 00:04:43.829 Samuel Roberts: Yeah, that’s…
20 00:04:44.120 ⇒ 00:04:55.189 Samuel Roberts: Yeah, I think that… that… this is not the first time I’ve seen this happen. I think it’s when events get transferred, because they’re… it’s, like, Utam’s room, now it’s your room, and it just, like, wipes the link, which is…
21 00:04:55.800 ⇒ 00:05:02.430 Samuel Roberts: you know, I get why it does it, because it’s, you know, everyone has a room, but it seems very inconvenient when stuff like this happens, because it’s not the.
22 00:05:02.430 ⇒ 00:05:03.240 Clarence Stone: Yeah.
23 00:05:04.860 ⇒ 00:05:05.440 Samuel Roberts: both.
24 00:05:05.880 ⇒ 00:05:11.979 Clarence Stone: Okay, cool. Alright, I’m gonna update this. Hopefully, like, Sam, can you tell me if the link shows up for you now?
25 00:05:11.980 ⇒ 00:05:12.599 Samuel Roberts: Yeah, I will…
26 00:05:12.600 ⇒ 00:05:13.190 Clarence Stone: Trick that immediately.
27 00:05:13.190 ⇒ 00:05:13.800 Samuel Roberts: Immediately.
28 00:05:13.800 ⇒ 00:05:14.840 Clarence Stone: invitees.
29 00:05:15.160 ⇒ 00:05:16.790 Clarence Stone: Yeah, that should solve it.
30 00:05:18.100 ⇒ 00:05:22.390 Samuel Roberts: Yeah… Of course, my computer’s being very slow right now, but…
31 00:05:25.760 ⇒ 00:05:29.150 Clarence Stone: Hello, hello, it was great seeing y’all. You guys found it.
32 00:05:30.080 ⇒ 00:05:30.700 Awaish Kumar: Hi.
33 00:05:32.920 ⇒ 00:05:35.890 Samuel Roberts: Yeah, let’s see… sorry, I’m just catching up with this.
34 00:05:37.070 ⇒ 00:05:41.670 Samuel Roberts: Huh. Yep, there it goes, just loaded. Okay, cool. My calendar’s playing catch-up.
35 00:05:53.510 ⇒ 00:05:57.250 Clarence Stone: Oh, man, Sesshu, this, this whole,
36 00:05:57.730 ⇒ 00:06:01.759 Clarence Stone: interview setup thing is brutal. Like, it’s…
37 00:06:02.420 ⇒ 00:06:08.230 Clarence Stone: So Rico asked me, like, when I’m generally available, which is after 3, and…
38 00:06:08.450 ⇒ 00:06:15.579 Clarence Stone: That does work, but as soon as we opened it, somebody scheduled a interview with me at 4 o’clock on the dock.
39 00:06:15.840 ⇒ 00:06:16.829 Sheshu Chandrasekar: Like, go away.
40 00:06:17.520 ⇒ 00:06:21.929 Clarence Stone: I was like, come on, can we not? That’s funny.
41 00:06:21.930 ⇒ 00:06:22.600 Samuel Roberts: honey?
42 00:06:24.790 ⇒ 00:06:31.050 Sheshu Chandrasekar: Wait, so, is the, do they use, like, a… what kind of software do they use to schedule the interview?
43 00:06:31.190 ⇒ 00:06:35.449 Clarence Stone: So, Rico set me up on this thing called Default, and…
44 00:06:35.450 ⇒ 00:06:35.940 Samuel Roberts: Yeah.
45 00:06:35.940 ⇒ 00:06:39.389 Clarence Stone: for a time block for availability, but, like.
46 00:06:40.710 ⇒ 00:06:48.290 Clarence Stone: Generally, I am free 3 to 5, but there are certain days I have meetings, and it would be good if it wasn’t scheduled on the day of.
47 00:06:49.380 ⇒ 00:06:50.110 Samuel Roberts: Yeah.
48 00:06:52.620 ⇒ 00:06:54.110 Sheshu Chandrasekar: Yeah, that is a little annoying.
49 00:06:54.280 ⇒ 00:07:00.159 Samuel Roberts: Yeah, and I’m living in a world with, like, 3 calendars, so it’s just absolutely brutal. That’s rough, yeah.
50 00:07:00.160 ⇒ 00:07:04.339 Sheshu Chandrasekar: Did it… did it get synced to your Google Calendar, or has it not been?
51 00:07:04.700 ⇒ 00:07:07.319 Clarence Stone: It’s on my Google Calendar now, the interview.
52 00:07:07.760 ⇒ 00:07:17.210 Sheshu Chandrasekar: No, I’m just saying, like, has Ricoh configured your Google Calendar to, default? So it gives you, like, options to block out times?
53 00:07:17.790 ⇒ 00:07:22.870 Clarence Stone: No. So the only options with the integration is to actually
54 00:07:23.420 ⇒ 00:07:26.010 Clarence Stone: Just pick time blocks, like that.
55 00:07:26.350 ⇒ 00:07:27.210 Sheshu Chandrasekar: Gotcha.
56 00:07:29.370 ⇒ 00:07:33.280 Samuel Roberts: Yeah, this is… this ain’t gonna work.
57 00:07:33.930 ⇒ 00:07:43.440 Clarence Stone: We’ll figure it out. Alright guys, this is about you. This is not about me and my scheduling problems and all that nonsense. How are you guys doing? How’s everything going?
58 00:07:44.500 ⇒ 00:07:46.290 Awaish Kumar: All good.
59 00:07:49.940 ⇒ 00:07:50.880 Clarence Stone: How about you, Sam?
60 00:07:50.880 ⇒ 00:07:55.200 Samuel Roberts: Oh, yes, I didn’t know if there was more of that. Yeah, I mean, things seem to be moving along, you know.
61 00:07:55.730 ⇒ 00:08:00.550 Samuel Roberts: ABC and Lilo, like, the guys are…
62 00:08:00.680 ⇒ 00:08:09.990 Samuel Roberts: pretty on top of everything, working with them has been good. We had a whole call today with, where we rearranged the Gantt and everything, and Casey kind of took the lead on that, which was nice.
63 00:08:10.130 ⇒ 00:08:13.009 Samuel Roberts: So I think things seem to be, like, people seem…
64 00:08:13.650 ⇒ 00:08:23.940 Samuel Roberts: invested in their… their roles and everything, and it’s nice to be like, yeah, can we… can we just update that? And it gets updated sometimes, which is good. But yeah, I mean, so far…
65 00:08:24.280 ⇒ 00:08:27.319 Samuel Roberts: I’ve been pretty happy. You know, things are…
66 00:08:28.540 ⇒ 00:08:30.090 Samuel Roberts: what’s the word I’m trying… like…
67 00:08:30.730 ⇒ 00:08:35.550 Samuel Roberts: doesn’t feel that different for the way I’m doing things right now, like, I’m just sort of still, like.
68 00:08:35.669 ⇒ 00:08:48.680 Samuel Roberts: helping everyone figure out what’s going on in the project, and, you know, technically sorting things out. But it does seem like other things are happening in terms of, like, the Gantz and linear, and things are up to date in a better way. Yeah, I think there’s still some room for improvement there.
69 00:08:48.860 ⇒ 00:08:51.199 Samuel Roberts: But I’m pretty…
70 00:08:52.120 ⇒ 00:08:58.540 Samuel Roberts: happy right now with the progress we’re making and the tracking of the progress we’re making and everything, so I think I’m feeling pretty good.
71 00:08:59.900 ⇒ 00:09:22.230 Clarence Stone: Yeah, Sam, I’m gonna give you a hats off for that. I was there on your meeting when you made that pivot to say, let’s just get it done right now, and that’s literally how you should take command of your time, like, message for both of you guys, right? Like, if documents are being updated, you know, just make sure you get through all your stand-ups, and then say, okay, let’s just take care of this now, because we have extra time, right? Yeah.
72 00:09:22.290 ⇒ 00:09:31.289 Clarence Stone: So, the key is, yeah, take command of that space and get things done as you need, but also, don’t let them bait you guys. Don’t let them bait you guys.
73 00:09:31.600 ⇒ 00:09:50.230 Clarence Stone: Right? There’s gonna be, like, certain questions that end up being, like, half an hour conversations, right? And if you feel that that’s coming on, you just say, hey, pause, let’s have a side meeting, right? Because stand-up is always stand-up, we have to make it through every single one. But if you do have extra time, you are in command of that time, so you made good use of it.
74 00:09:50.540 ⇒ 00:09:51.540 Samuel Roberts: Yeah, I think…
75 00:09:51.630 ⇒ 00:10:11.100 Samuel Roberts: there’s… that is a balance that I’m still kind of finding, where sometimes I’m like, okay, no, let’s dig in a little bit, and we can resolve this very quickly. Or, yeah, like, we had two calls that we set up right after that for both Andy and Lilo for certain things, and I was like, that is going to be way longer, and one of them took the whole hour, one of them took not the whole hour, but it was, like, not stand-up material, you know?
76 00:10:11.100 ⇒ 00:10:12.419 Samuel Roberts: San material, yeah.
77 00:10:12.420 ⇒ 00:10:21.740 Clarence Stone: That’s the challenge with taking the bait on checking under the bed. You don’t know if it’s a big monster or a little monster. You just go, oh, wait, I just used the rest of my stand-up time for this. Yep.
78 00:10:21.740 ⇒ 00:10:33.999 Clarence Stone: Yeah, cool. Awash, what about you? How’s everything going for you? Are documents up to date? Are, you know… let’s talk about the basics, right? Like, what I’m interested in is documents up-to-date, and do… are people showing up?
79 00:10:34.060 ⇒ 00:10:35.730 Clarence Stone: Like, that’s important, too.
80 00:10:35.730 ⇒ 00:10:38.060 Awaish Kumar: Yeah, people are showing up.
81 00:10:38.520 ⇒ 00:10:45.880 Awaish Kumar: I’m having issues with, Like, linear mode not being… Okay, dude?
82 00:10:47.590 ⇒ 00:10:55.099 Awaish Kumar: like, for some clients, like, what’s the plan for this week? And I do hear, like, we have to do this and that.
83 00:10:55.430 ⇒ 00:10:57.309 Awaish Kumar: But I can’t turn Geneva.
84 00:10:57.890 ⇒ 00:10:59.689 Awaish Kumar: See it on the board, right?
85 00:10:59.910 ⇒ 00:11:02.259 Awaish Kumar: Here are four tickets which we need to work.
86 00:11:02.420 ⇒ 00:11:03.200 Awaish Kumar: Sweet.
87 00:11:03.400 ⇒ 00:11:08.500 Awaish Kumar: And then it’s really hard for me to measure at the end of the day.
88 00:11:09.050 ⇒ 00:11:15.489 Awaish Kumar: Like, at the end of the week, like, what has been done, because… There’s… there’s nothing to see.
89 00:11:15.590 ⇒ 00:11:17.730 Awaish Kumar: I don’t know if they have done anything.
90 00:11:18.130 ⇒ 00:11:20.629 Awaish Kumar: No, like, I just hear it.
91 00:11:20.630 ⇒ 00:11:34.420 Clarence Stone: Your audio always comes in fuzzy, Oish, so, like, I’m trying to blast my audio here, too, because I can’t really… it’s not your quality, it’s, like, just… I think you might just have to crank your microphone or something, but,
92 00:11:34.780 ⇒ 00:11:41.720 Clarence Stone: Are you saying that people aren’t updating linear with tickets, and then you don’t have awareness for what’s done?
93 00:11:43.750 ⇒ 00:11:49.440 Awaish Kumar: I’m… what I’m trying to say is that the tickets are…
94 00:11:49.900 ⇒ 00:11:56.300 Awaish Kumar: There are no tickets, basically. Like, I don’t… on Mondays, I don’t see the plan for the week.
95 00:11:57.770 ⇒ 00:12:03.420 Awaish Kumar: Right? What leads should be done this week, right? Okay. There’s no ticket, like…
96 00:12:03.520 ⇒ 00:12:11.239 Awaish Kumar: I just hear that there are a few things I would be focusing on, but I don’t see… that don’t…
97 00:12:11.960 ⇒ 00:12:16.289 Awaish Kumar: What we are doing does not reflect… is not reflected in the linear board.
98 00:12:18.510 ⇒ 00:12:20.680 Clarence Stone: That’s a huge problem!
99 00:12:20.680 ⇒ 00:12:21.460 Awaish Kumar: Yeah.
100 00:12:21.460 ⇒ 00:12:26.780 Clarence Stone: Okay, what, what engagements is that happening on?
101 00:12:27.740 ⇒ 00:12:31.150 Awaish Kumar: For example, CTA, that’s,
102 00:12:31.880 ⇒ 00:12:39.170 Awaish Kumar: Yeah, like, I’m trying, like, for… it has been the case for Magic Spoons, this week it has been good.
103 00:12:39.320 ⇒ 00:12:42.230 Awaish Kumar: It has been a case for default, for example.
104 00:12:42.360 ⇒ 00:12:43.470 Awaish Kumar: So…
105 00:12:43.710 ⇒ 00:12:56.189 Awaish Kumar: it has improved for those clients. Like, for 2 weeks, I kept saying that. Now I’m seeing the tickets there. So, but for CTA, for example, I’m still not…
106 00:12:56.420 ⇒ 00:13:00.830 Awaish Kumar: Seeing that kind of, progress?
107 00:13:01.000 ⇒ 00:13:07.489 Awaish Kumar: Dr. Felina, And, yeah, so I didn’t, like, message that today.
108 00:13:07.680 ⇒ 00:13:12.079 Awaish Kumar: in the stand-up, like, Hotam is also the CEO, CSO there.
109 00:13:12.320 ⇒ 00:13:13.999 Awaish Kumar: So, I don’t know.
110 00:13:14.280 ⇒ 00:13:19.800 Awaish Kumar: I didn’t tell them that, like, I need more clarity here, what needs to be done.
111 00:13:23.680 ⇒ 00:13:31.709 Clarence Stone: Okay, so, so… What you’re telling me, Oish, is there are still…
112 00:13:31.920 ⇒ 00:13:35.389 Clarence Stone: Sorry, I just need to tell Rico not to…
113 00:13:35.590 ⇒ 00:13:43.550 Clarence Stone: Hang on. other meeting… to work.
114 00:13:52.410 ⇒ 00:14:03.140 Clarence Stone: Okay, cool. I was just telling Rico, I’m like, we can’t do same-day scheduling, man. Especially if it’s in an hour.
115 00:14:03.290 ⇒ 00:14:04.610 Clarence Stone: So,
116 00:14:05.590 ⇒ 00:14:18.160 Clarence Stone: A couple things. So, one, you’re giving me some good news, right? Hey, you’re saying, hey, linear’s not matching what you guys are telling me every week. Some teams are fixing it, other teams haven’t fixed it. Correct?
117 00:14:18.640 ⇒ 00:14:19.280 Awaish Kumar: Yep.
118 00:14:19.510 ⇒ 00:14:21.220 Clarence Stone: Okay,
119 00:14:21.800 ⇒ 00:14:35.020 Clarence Stone: I kind of want to give you guys a mechanism to prevent people from being able to actually even leverage resources without y’all’s approval. Deeper conversation I want to have with you, Sesshu. It’s like.
120 00:14:35.480 ⇒ 00:14:36.240 Awaish Kumar: Yeah, I’m…
121 00:14:36.240 ⇒ 00:14:43.849 Clarence Stone: It’s not fair to keep you guys accountable for, like, technical work if it’s not being… it’s not transparent and something that you can review and approve.
122 00:14:45.130 ⇒ 00:14:49.820 Clarence Stone: like, Awash, are you at least kept up to date on what they are doing?
123 00:14:50.170 ⇒ 00:14:52.300 Clarence Stone: Even though it doesn’t match linear?
124 00:14:53.010 ⇒ 00:14:56.049 Awaish Kumar: Yeah, tickets are not up to date.
125 00:14:58.790 ⇒ 00:14:59.500 Clarence Stone: Okay.
126 00:15:01.350 ⇒ 00:15:03.000 Awaish Kumar: Okay, sometimes they are.
127 00:15:03.160 ⇒ 00:15:05.130 Awaish Kumar: But not on the time, like…
128 00:15:06.140 ⇒ 00:15:09.580 Awaish Kumar: Not every time. So, I see one ticket
129 00:15:09.860 ⇒ 00:15:18.010 Awaish Kumar: his status is updated, there are some comments, but, like, there are still some tickets where I don’t see any…
130 00:15:18.670 ⇒ 00:15:24.499 Awaish Kumar: probably, like, any… anything, like, any update there, so I don’t know if it is done, if it…
131 00:15:24.610 ⇒ 00:15:28.439 Awaish Kumar: Is there… there’s any comment down there, or whatever?
132 00:15:29.540 ⇒ 00:15:39.470 Clarence Stone: Have you guys been planning? So, so how did stand-ups work prior to this? Like, did you guys talk about what you’re gonna do for the whole week, or was it just a day-to-day thing?
133 00:15:40.730 ⇒ 00:15:46.919 Awaish Kumar: But it’s, like, for the stand-ups, normally it is day-to-day thing, like, where we.
134 00:15:46.920 ⇒ 00:15:47.480 Clarence Stone: Yeah.
135 00:15:47.480 ⇒ 00:15:53.890 Awaish Kumar: see the progress of each ticket. On Mondays, we had a separate planning session where we planned for the week.
136 00:15:54.030 ⇒ 00:15:59.640 Awaish Kumar: But now that, like, our stand-ups are quite, like, the, you could say.
137 00:15:59.880 ⇒ 00:16:15.210 Awaish Kumar: slim, like, we don’t have to spend all the time. So, like, I have time to, like, ask for, like, okay, what’s the weekend? What’s the plan for this week? On Mondays, I normally ask. I don’t just ask for, like, what’s the plan for today? I normally ask, what’s the plan for week?
138 00:16:15.740 ⇒ 00:16:17.359 Awaish Kumar: I need to see, like…
139 00:16:18.900 ⇒ 00:16:21.309 Clarence Stone: Is this how both of you guys work?
140 00:16:23.190 ⇒ 00:16:38.369 Samuel Roberts: Yeah, we… it was similar. I think what I’ve been trying to adapt is more, like, keeping the stand-up stand-up, and then having, like, getting an update from everyone, especially, like, it’s Monday, let’s all check in, but trying to keep that, like, planning, the week.
141 00:16:38.550 ⇒ 00:16:41.619 Samuel Roberts: Like, a little more off… not offline, but just…
142 00:16:41.950 ⇒ 00:16:50.370 Samuel Roberts: not in the stand-up so much. So, like, we have our Gantt, we have our linear, like, kind of keep those up to date, and then stand-ups are more like, what are we doing today? Yeah.
143 00:16:51.200 ⇒ 00:16:53.470 Clarence Stone: Okay, and… Sarah.
144 00:16:53.470 ⇒ 00:16:54.129 Awaish Kumar: Follow me.
145 00:16:54.750 ⇒ 00:16:59.030 Awaish Kumar: Yeah, one thing to add, like, in the stand-up, I’m not going over
146 00:16:59.220 ⇒ 00:17:05.469 Awaish Kumar: The tickets and trying to, like, be with them to create tickets there and plan the session, or…
147 00:17:05.579 ⇒ 00:17:07.920 Awaish Kumar: I just want to hear from them, like.
148 00:17:08.770 ⇒ 00:17:20.660 Awaish Kumar: I, like, EP is the one who needs to create a ticket. I’m just asking on one day that, are you ready, like, for this week? Do you know what needs to be done? Are there any tickets there?
149 00:17:20.839 ⇒ 00:17:25.529 Awaish Kumar: If… even if not created yet, I would like to see all of them tomorrow.
150 00:17:26.290 ⇒ 00:17:28.250 Clarence Stone: Yeah, and you’re not getting them the next day.
151 00:17:28.250 ⇒ 00:17:29.370 Awaish Kumar: Yeah, yeah.
152 00:17:29.370 ⇒ 00:17:31.810 Clarence Stone: Dude, you gotta escalate that shit. You gotta… you gotta tell me.
153 00:17:32.250 ⇒ 00:17:51.140 Clarence Stone: Okay, so back to, like, when I keep telling you guys, this is your time box, it is for you to plan how you want to use that time. Awish, if people need to show up on Monday with their whole week planned out, with the list of all the linear tickets that they’re doing for that week, so that you can review and actually provide feedback, you can make that demand.
154 00:17:51.840 ⇒ 00:17:52.560 Awaish Kumar: Yep.
155 00:17:52.910 ⇒ 00:18:04.460 Clarence Stone: Right? So you can say, hey, starting from today, like, what I need to see on every Monday for every single project is, what are you doing, and what is the list of linear tickets you’re doing this week?
156 00:18:04.890 ⇒ 00:18:06.300 Clarence Stone: Right? And…
157 00:18:06.510 ⇒ 00:18:21.560 Clarence Stone: like, you can start Monday with, hey, I haven’t received it from this… this team, this team, this team. Tuesday, if you still haven’t received it, I still haven’t received it from this team, this team, this team, right? Say this out loud, say it in your call, because it’s all transcribed and saved.
158 00:18:21.750 ⇒ 00:18:26.409 Clarence Stone: So when we look back, hey, what went wrong? Hey, OSH has always been asking for this.
159 00:18:26.640 ⇒ 00:18:28.840 Clarence Stone: Right? So that’s one thing.
160 00:18:29.100 ⇒ 00:18:32.660 Clarence Stone: two, eyeing…
161 00:18:32.830 ⇒ 00:18:40.970 Clarence Stone: That’s alarming to me, because I’m wondering, like, how far apart is what’s actually happening between Like…
162 00:18:41.600 ⇒ 00:18:47.490 Clarence Stone: what you think… they’re doing, and what they’re actually doing, and what Linear says.
163 00:18:47.950 ⇒ 00:18:54.420 Clarence Stone: Like, what is the deltas that you guys are experiencing right now? Like, how wrong is linear?
164 00:18:55.530 ⇒ 00:19:03.910 Awaish Kumar: I would say… Yeah, like, I would say at least
165 00:19:04.730 ⇒ 00:19:10.480 Awaish Kumar: Like, we are only capable to measure 60% using Linear.
166 00:19:10.830 ⇒ 00:19:11.570 Clarence Stone: Okay.
167 00:19:11.710 ⇒ 00:19:17.460 Clarence Stone: Okay, this is a… this is a problem. Thank you for bubbling this up. So…
168 00:19:17.460 ⇒ 00:19:22.580 Sheshu Chandrasekar: So I think, Clarence, we may need to just create some sort of guidelines for the EPs to…
169 00:19:23.520 ⇒ 00:19:28.149 Sheshu Chandrasekar: to, like, help with the ticketing process, because I think that’s kind of the bottom line I’m hearing. I don’t think…
170 00:19:28.310 ⇒ 00:19:30.719 Sheshu Chandrasekar: They’re understanding how to submit it, or…
171 00:19:31.520 ⇒ 00:19:42.429 Sheshu Chandrasekar: Or they just don’t know, the importance of it, like, what’s classified as a ticket or whatnot. I think maybe that’s something we need to look into, tomorrow when we meet with the EP leads.
172 00:19:48.000 ⇒ 00:19:55.360 Clarence Stone: Yeah. What I wanted from these guys, though, is how do they want to see the information? That’s true. Did you tell them to do any process?
173 00:19:55.610 ⇒ 00:20:07.370 Clarence Stone: But, like, if they’re not getting the data fed to them in the way that they need to make, you know, good stand-up and have good decisions during stand-up, then it’s not going to be helpful either, right? So, like.
174 00:20:07.480 ⇒ 00:20:21.059 Clarence Stone: how would you guys want it done? Do you want an email on Monday morning with, hey, this is the project, this is all the tickets we want to do for this week, or is there a different cut, a different view? Do you just want a summary of, like, what the week’s objectives are? What’s good enough?
175 00:20:22.800 ⇒ 00:20:29.800 Awaish Kumar: Yeah, only two things which we already decided. The Gantt chart, And the linear tickets.
176 00:20:30.050 ⇒ 00:20:34.290 Awaish Kumar: Is more than enough to… To review, right?
177 00:20:34.790 ⇒ 00:20:35.480 Clarence Stone: Okay.
178 00:20:36.700 ⇒ 00:20:39.290 Samuel Roberts: So is this something that maybe we’d want to… oh, go ahead.
179 00:20:39.560 ⇒ 00:20:41.370 Sheshu Chandrasekar: Oh, I’m sorry, no, please go ahead.
180 00:20:41.370 ⇒ 00:20:44.850 Samuel Roberts: I was gonna say, is this something that maybe we want to start being, like, hey, Friday…
181 00:20:45.070 ⇒ 00:20:55.159 Samuel Roberts: afternoon, let’s get everything up to date for Monday kind of thing, and that way it’s… we’re pushing it a day early, it’s not Monday morning, and we’re saying, where is everything?
182 00:20:55.380 ⇒ 00:21:02.029 Samuel Roberts: at least, you know, making sure that we’re having conversations with the EPs, and the EPs and the CSOs are all, you know, making sure that that’s all kind of
183 00:21:02.490 ⇒ 00:21:05.159 Samuel Roberts: in progress before Monday, kind of.
184 00:21:05.470 ⇒ 00:21:07.060 Samuel Roberts: Morning, I guess.
185 00:21:07.780 ⇒ 00:21:13.429 Sheshu Chandrasekar: No, that’s awesome, yeah, that’s exactly where I was gonna ask, like, what’s the timeline, but that works, yeah.
186 00:21:15.580 ⇒ 00:21:16.200 Samuel Roberts: Yes.
187 00:21:20.770 ⇒ 00:21:24.630 Clarence Stone: Yeah, okay, we’ll work on this.
188 00:21:24.850 ⇒ 00:21:28.459 Clarence Stone: We do have an EP call tomorrow, so we’ll get it addressed.
189 00:21:29.210 ⇒ 00:21:32.010 Clarence Stone: What else?
190 00:21:33.440 ⇒ 00:21:36.710 Awaish Kumar: Yeah, like, I think I need more help here, Andre.
191 00:21:37.430 ⇒ 00:21:39.509 Awaish Kumar: It be signed, like.
192 00:21:39.650 ⇒ 00:21:50.150 Clarence Stone: In what ways? Like, in collecting information, getting direct answers, taking a look at, you know, information on what’s happening on a project. It’d be helpful to…
193 00:21:50.600 ⇒ 00:21:52.470 Clarence Stone: Like, what would help you?
194 00:21:53.300 ⇒ 00:21:54.450 Clarence Stone: Yeah, like…
195 00:21:54.450 ⇒ 00:21:55.130 Awaish Kumar: I.
196 00:21:55.130 ⇒ 00:22:04.920 Clarence Stone: I don’t want to be that corporate person that just goes, Awash said he needs help. Let’s just go hire somebody. Here you go, Awash, I hired somebody for you. And you’re gonna be like.
197 00:22:05.020 ⇒ 00:22:18.079 Clarence Stone: this dude knows nothing about what I need help with. This is not helpful! Right? And I would just go, well, I wish that he needed help, I hired somebody, right? But, like, so, like, that’s why I’m asking, like, really.
198 00:22:18.080 ⇒ 00:22:18.580 Awaish Kumar: Yeah.
199 00:22:18.580 ⇒ 00:22:20.169 Clarence Stone: like, how can I help?
200 00:22:20.170 ⇒ 00:22:26.410 Awaish Kumar: I… yeah. Yeah, what I need help with is, like, the… Yeah, that…
201 00:22:28.050 ⇒ 00:22:30.949 Awaish Kumar: I’m, like, what I’m getting from EP is…
202 00:22:31.290 ⇒ 00:22:34.560 Awaish Kumar: Like, the, the, like, the tickets?
203 00:22:35.220 ⇒ 00:22:42.340 Awaish Kumar: like, and, like, each person is kind of… Focusing on an individual ticket.
204 00:22:43.650 ⇒ 00:22:46.770 Awaish Kumar: Like, if… Somebody’s working on something.
205 00:22:47.170 ⇒ 00:22:51.890 Awaish Kumar: Like, there’s no, like, view of… the whole view of the…
206 00:22:52.670 ⇒ 00:22:55.909 Awaish Kumar: The work that is being done for the client.
207 00:22:56.070 ⇒ 00:22:59.230 Awaish Kumar: So, like, even if in… if in the call, like.
208 00:22:59.360 ⇒ 00:23:03.660 Awaish Kumar: And, like, here are a few tickets where I made progress.
209 00:23:03.840 ⇒ 00:23:12.969 Awaish Kumar: we are on a good track with what we are going to deliver for the client. I don’t hear that, like, I just hear, like, this is the ticket, I’m stuck there.
210 00:23:13.180 ⇒ 00:23:14.939 Awaish Kumar: Working on that.
211 00:23:15.970 ⇒ 00:23:18.160 Awaish Kumar: So, like, is it still,
212 00:23:18.440 ⇒ 00:23:23.930 Awaish Kumar: I think it’s still not in the format we want it to be, I guess. So, more like…
213 00:23:24.500 ⇒ 00:23:29.779 Awaish Kumar: Like, the way we were running it earlier, like, for individual tickets, everybody comes in.
214 00:23:30.230 ⇒ 00:23:38.150 Awaish Kumar: Says if it is done, or if it’s blocked, or where it’s, like, where it is blocked, and details about that ticket, but, like,
215 00:23:38.740 ⇒ 00:23:42.049 Awaish Kumar: Which, like, I don’t want to hear in the stand-up.
216 00:23:42.420 ⇒ 00:24:00.259 Clarence Stone: Okay, so let’s start from the basics to more precise, you know, needs that you guys have. And I just want to make sure I’m hearing each of these correctly. One, there’s activities happening at the client project level that is not being recorded by tickets.
217 00:24:00.760 ⇒ 00:24:02.050 Clarence Stone: Is that true?
218 00:24:02.590 ⇒ 00:24:03.290 Awaish Kumar: Yep.
219 00:24:05.570 ⇒ 00:24:06.800 Clarence Stone: Sam says maybe.
220 00:24:07.840 ⇒ 00:24:14.050 Samuel Roberts: I think… I think what I’m… the way I’m thinking about this is that our… our tickets may not be granular enough.
221 00:24:14.450 ⇒ 00:24:19.219 Samuel Roberts: But… seeing what the tickets are and seeing the updates, I’m kind of…
222 00:24:19.320 ⇒ 00:24:38.529 Samuel Roberts: plugged into what’s happening well enough, if that makes sense? Like, the… we kind of took the Gantt and said, okay, making linear tickets, but sometimes we’ve broken those down a little bit more, and sometimes we haven’t, and so I think some tickets are maybe not granular enough, and it’s spanning a little longer than it might be, but it’s just… in my mind, that’s just… we didn’t break them down enough this…
223 00:24:38.590 ⇒ 00:24:45.850 Samuel Roberts: cycle kind of thing. But yeah, overall, I think the work is being pretty well mapped to that. It might just not be as…
224 00:24:46.040 ⇒ 00:25:04.679 Samuel Roberts: if I weren’t in the projects as well as I was, I might not have as great a view of the linear, or as much insight into it, but the fact that I’m working with them about it, I’m less worried about that right now, and I’m kind of thinking as we’ll get better at that moving forward, but I think work is still being pretty well documented there.
225 00:25:05.120 ⇒ 00:25:08.030 Clarence Stone: Okay, cool. Awish, how about for you?
226 00:25:08.590 ⇒ 00:25:12.210 Awaish Kumar: Yeah, for me, I don’t… like, what…
227 00:25:13.630 ⇒ 00:25:26.280 Awaish Kumar: I agree with what Sam says, but that’s the problem, right? I have a ticket which says, engagement report, right, for one of the clients, and then it’s sitting there for 3 weeks, and…
228 00:25:26.280 ⇒ 00:25:30.540 Samuel Roberts: What I hear is still… we are still working on it, still working on that.
229 00:25:30.540 ⇒ 00:25:32.339 Awaish Kumar: They’ve asked for some updates.
230 00:25:33.330 ⇒ 00:25:42.059 Awaish Kumar: they asked… asked for some reviews. They asked for more work on that piece, I’m still on it. So, I don’t know, like, what’s… what’s going on?
231 00:25:42.060 ⇒ 00:25:48.989 Clarence Stone: Right. Just stop there real quick and say, okay, there is a ticket, it’s saying something like Client Analytics Dashboard, right?
232 00:25:48.990 ⇒ 00:25:49.360 Awaish Kumar: Yeah.
233 00:25:49.500 ⇒ 00:25:55.389 Clarence Stone: Am I right when you’re saying that there’s no description on it, on what the analytics for the dashboard is?
234 00:25:55.930 ⇒ 00:25:57.130 Clarence Stone: Is that correct?
235 00:25:57.530 ⇒ 00:25:58.580 Awaish Kumar: So, like…
236 00:25:58.810 ⇒ 00:26:12.579 Awaish Kumar: So, on the data side, like, these are the individual things, right? We started to get with some basic requirements, like, that’s what we are going to deliver, right? We have done that part.
237 00:26:12.770 ⇒ 00:26:17.670 Awaish Kumar: Right, and then it should be closed, but, like…
238 00:26:19.110 ⇒ 00:26:22.329 Awaish Kumar: But then, like, it goes for review.
239 00:26:22.550 ⇒ 00:26:31.320 Awaish Kumar: then maybe there are some… I’m doing… I’m reviewing it, I’m kind of queuing it, I need to add one more field, first client wanted to add it.
240 00:26:31.480 ⇒ 00:26:36.670 Awaish Kumar: Like, then, like, these all are, like, separate asks, right?
241 00:26:37.490 ⇒ 00:26:44.790 Awaish Kumar: which are, like, now, that is not part of the same ticket, right? That was not initially asked.
242 00:26:45.060 ⇒ 00:26:50.690 Awaish Kumar: So, that takes time, and that is, like, still sitting there, I’m not sure.
243 00:26:50.890 ⇒ 00:26:58.670 Awaish Kumar: If that ticket is done, or… It’s not done, because like… we didn’t…
244 00:26:58.950 ⇒ 00:27:09.379 Awaish Kumar: delivered it as it… as the client wanted. That’s why it is sitting there, or it is not moving because we are continuing to add the new requirements?
245 00:27:10.330 ⇒ 00:27:10.980 Samuel Roberts: Right.
246 00:27:11.490 ⇒ 00:27:12.160 Awaish Kumar: I hate it.
247 00:27:13.680 ⇒ 00:27:28.069 Clarence Stone: Okay, so… so… would you say we would rectify the situation if we came up with standards on what warrants a new ticket, and what is, what needs to be, like, written on the ticket if it’s still open by the end of the week?
248 00:27:28.660 ⇒ 00:27:40.900 Clarence Stone: Like, like, if I made a policy, Wish, that said, hey, if you have a long project, and it’s in a single ticket, and you’re still not done with it by the end of the week, you need to write an update on why that’s still open and assigned to you.
249 00:27:42.740 ⇒ 00:27:44.189 Clarence Stone: Would that solve your problem?
250 00:27:46.650 ⇒ 00:27:51.730 Awaish Kumar: I think having clear acceptance criteria, like, these are…
251 00:27:51.890 ⇒ 00:28:03.990 Awaish Kumar: This is a ticket, that’s what we need to deliver, like, in that, like, for example, if it’s an analytic dashboard, then, okay, having these… I need these four charts, which are going to show this
252 00:28:04.310 ⇒ 00:28:05.270 Awaish Kumar: data.
253 00:28:05.590 ⇒ 00:28:10.540 Awaish Kumar: That’s the scope of this ticket, right? Now, if they want to add one more chart.
254 00:28:10.880 ⇒ 00:28:12.499 Awaish Kumar: That’s not part of this single thing.
255 00:28:13.850 ⇒ 00:28:15.439 Awaish Kumar: There’s a separate ask for the dashboard.
256 00:28:15.440 ⇒ 00:28:22.940 Clarence Stone: That’s a pause right there, like, how do you want the project teams that you’re managing to handle that situation?
257 00:28:23.190 ⇒ 00:28:35.260 Clarence Stone: Because, like, if you don’t go out and say, hey, if you’re, if you have a, you know, additional feature in the ticket that wasn’t previously specified, you need to create a new ticket, or create a sibling ticket, or a child ticket, like.
258 00:28:35.300 ⇒ 00:28:41.129 Clarence Stone: If you don’t say that to them, then they’ll just leave it open and say, hey, we have a new requirement, we’re just gonna tack it onto this ticket.
259 00:28:41.130 ⇒ 00:28:58.959 Clarence Stone: Right? Like, water’s gonna flow the easiest way it’s gonna flow. So, like, if you want them to do something that you need to help keep operational oversight, then you have to say it. So, what is the behavior in tickets that we need to change, is the question I’m asking you guys.
260 00:28:59.030 ⇒ 00:29:16.900 Clarence Stone: Clearly, we’ve got to change the way, you know, tickets are updated and information’s provided. I’m getting that from you guys, but how do we change it? What is the process we want to change to get you that visibility? Is the decision I want you guys to make, because if I make it for you, like, it’s not going to be what you need.
261 00:29:17.230 ⇒ 00:29:27.839 Awaish Kumar: Yeah, that’s what I described, like, I want… for each individual ticket, we want some basic scope defined for the ticket, what needs to be delivered.
262 00:29:28.230 ⇒ 00:29:29.720 Awaish Kumar: As part of this ticket.
263 00:29:30.030 ⇒ 00:29:36.639 Awaish Kumar: When that is done, And… And delivered, then we are going to close that ticket.
264 00:29:36.990 ⇒ 00:29:39.620 Awaish Kumar: Anything after that is a new ticket.
265 00:29:40.240 ⇒ 00:29:41.900 Awaish Kumar: Even for the same dashboard.
266 00:29:42.210 ⇒ 00:29:42.950 Clarence Stone: Okay.
267 00:29:43.620 ⇒ 00:29:47.259 Sheshu Chandrasekar: Got it, so it doesn’t matter… Oh, sorry, go ahead, Clarence.
268 00:29:47.260 ⇒ 00:29:48.479 Clarence Stone: Yeah, go for it, Sashi.
269 00:29:48.480 ⇒ 00:30:00.209 Sheshu Chandrasekar: So, just to confirm here, it doesn’t even matter if, like, you finish one task, and based on… in your head, it’s… once it’s done, it’s done, and if we need to keep on working on the same exact
270 00:30:00.490 ⇒ 00:30:08.550 Sheshu Chandrasekar: Ticket, task, whatever you want to call it, like, you have to submit a new ticket and re-enter that information, basically.
271 00:30:12.210 ⇒ 00:30:12.670 Awaish Kumar: Yeah.
272 00:30:12.670 ⇒ 00:30:20.270 Sheshu Chandrasekar: So, for example, let’s say I need to build a car, right? And I say, okay, in order to build this car, I need to put 4 wheels.
273 00:30:20.560 ⇒ 00:30:28.140 Sheshu Chandrasekar: 4 silver wheels. I put 4 silver wheels, but then you come back, you say, you know what, I don’t like the silver wheels, I want black wheels.
274 00:30:28.450 ⇒ 00:30:38.550 Sheshu Chandrasekar: But in my head, I already finished my task, you’re just… I just need to submit a new ticket saying, add 5 black wheels to the car instead of the silver ones. Is that kind of what I’m understanding here?
275 00:30:39.370 ⇒ 00:30:40.440 Awaish Kumar: Yes.
276 00:30:41.110 ⇒ 00:30:43.839 Sheshu Chandrasekar: So, wouldn’t… would it be better…
277 00:30:44.200 ⇒ 00:30:56.730 Sheshu Chandrasekar: I’m just curious, like, would it make more sense if we don’t close that ticket, and then we just add, like, an amendment to that ticket? Just so we have, like, previous context? Or would you just want complete new context here?
278 00:30:57.250 ⇒ 00:30:59.220 Awaish Kumar: Yeah, we needed… we needed.
279 00:30:59.220 ⇒ 00:31:00.779 Samuel Roberts: You can reference other tickets.
280 00:31:00.920 ⇒ 00:31:01.370 Awaish Kumar: We…
281 00:31:01.370 ⇒ 00:31:02.000 Sheshu Chandrasekar: Okay, so…
282 00:31:02.000 ⇒ 00:31:11.350 Awaish Kumar: ticket, but we need a separate ticket, because the efforts it… if effort it takes to add… add, like, silver tires, and then black tires, and…
283 00:31:11.810 ⇒ 00:31:12.560 Awaish Kumar: like.
284 00:31:12.560 ⇒ 00:31:14.000 Sheshu Chandrasekar: Oh, okay, it changes a little.
285 00:31:14.670 ⇒ 00:31:15.730 Awaish Kumar: Got it.
286 00:31:15.730 ⇒ 00:31:34.480 Sheshu Chandrasekar: Okay, so then I guess the EPs need to have better context, right? They need to be like, okay, we worked on this ticket, referenced this, for future… okay. I’m just curious, because, like, you know, we don’t want to add a new ticket, and then it’s, like, something you already worked on. Like, let’s say someone else jumps in on a project, and it’s just good to have that traceability.
287 00:31:34.520 ⇒ 00:31:38.260 Samuel Roberts: Is what I’m thinking, and I don’t know how useful it would be for you guys as well, so…
288 00:31:38.350 ⇒ 00:31:39.980 Sheshu Chandrasekar: Please stop me if I’m wrong here.
289 00:31:40.210 ⇒ 00:31:47.430 Samuel Roberts: No, I think you’re on the right track. This is definitely something we’ve talked a lot about in the last several months, is just, like, ticket grooming in general, and, like, what…
290 00:31:47.590 ⇒ 00:31:53.559 Samuel Roberts: Because for a while, what was happening sometimes is, like, a meeting would happen, the linear ticket generator would…
291 00:31:53.870 ⇒ 00:32:06.220 Samuel Roberts: make some calls out of that, and then just tickets with titles would get made, and there’d be no descriptions, and there’d be no acceptance criteria, there’d be no stuff. So, grooming in general is something that I think, you know, ticket-wise, we need to get.
292 00:32:06.570 ⇒ 00:32:08.529 Samuel Roberts: kind of on the same page about. I think we’re.
293 00:32:08.530 ⇒ 00:32:08.930 Sheshu Chandrasekar: Gotcha.
294 00:32:08.930 ⇒ 00:32:18.559 Samuel Roberts: starting to get there a little bit, but, I think, which is right. Acceptance criteria is the biggest one, probably, so, like, what qualifies this ticket as done, if things change
295 00:32:18.650 ⇒ 00:32:32.000 Samuel Roberts: I think new tickets make sense. You know, there’s… there are… there’s tracking changes on tickets, but if we’re trying to use that as, like, a measurement of how things are going, I think new tickets make sense. I had another thought there that was
296 00:32:32.670 ⇒ 00:32:39.740 Samuel Roberts: on the tip of my tongue at the end there. The grooming, the tickets… the acceptance criteria.
297 00:32:39.910 ⇒ 00:32:43.670 Samuel Roberts: And oh, I think the other thing I mentioned is, like, just granularity of tickets in general.
298 00:32:43.670 ⇒ 00:33:00.690 Samuel Roberts: if it’s a big, like, build this car, like, that’s not a great ticket. That shouldn’t be, you know, either the ticket, or it shouldn’t be the only ticket, if that’s, like, if there’s child tickets or whatever, and that’s, like, rolled up into that, I think that makes sense, but I think, yeah, grooming and granularity.
299 00:33:00.750 ⇒ 00:33:03.269 Samuel Roberts: Is… is kind of the biggest,
300 00:33:03.900 ⇒ 00:33:07.840 Samuel Roberts: Things that we can probably work on in terms of linear tickets, in my mind.
301 00:33:08.420 ⇒ 00:33:12.479 Samuel Roberts: And I think some of that would solve OASIS’ problem with the acceptance criteria.
302 00:33:13.080 ⇒ 00:33:20.129 Samuel Roberts: keeping tickets. If they’re granular, then when something changes, a new ticket can, you know, supplant the old one, or come after the old one.
303 00:33:20.130 ⇒ 00:33:33.459 Samuel Roberts: So I think that’s kind of where I’m… I’m at. This is sort of what I mentioned earlier, where I think, like, if I weren’t plugged into the projects as well, and I was just looking at the linear board, I might not have a great sense, because some of the tickets aren’t granular enough, but, we’re working towards that in my mind, so…
304 00:33:34.590 ⇒ 00:33:41.269 Clarence Stone: And Waish has a, like, a bigger problem, because he’s got so many projects that he has to keep track of.
305 00:33:41.270 ⇒ 00:33:43.300 Samuel Roberts: That’s the other side of it, is I’m plugged into the.
306 00:33:43.300 ⇒ 00:34:02.520 Clarence Stone: He’s hitting his limit here. Yeah, exactly. And so, so here’s my, here’s my feedback for you guys. Here’s what I really need from you. Like, I… I… if I… I can’t make this decision on my own, right? Like, so I need from you guys, one, what should be a part of a ticket?
307 00:34:02.810 ⇒ 00:34:16.040 Clarence Stone: what is the essential things you expect in a ticket, the two of you, right? If, you know, if it doesn’t have this, then, like, I… like, this cannot be assigned, it cannot be work that goes through, kind of stuff, right?
308 00:34:16.230 ⇒ 00:34:28.209 Clarence Stone: And then, in what conditions, like, do you create a new ticket? In what conditions do you, you know, provide an update? Like, I need some insights into that.
309 00:34:28.350 ⇒ 00:34:38.400 Clarence Stone: Because everything else, right, like, the whole concept of, you know, a new ticket should have been started because the customer asked for a change order, like.
310 00:34:38.400 ⇒ 00:34:55.949 Clarence Stone: I don’t believe that it’s something the EP should just, like, you know how to really go out and do. It should be a conversation that happens at your stand-up, saying, hey, customer came back, wants black wheels, we put silver ones on, and, you know, Sam, you or Wish can go, okay, that’s a huge change order, we’re gonna add a new ticket.
311 00:34:56.770 ⇒ 00:35:01.920 Clarence Stone: Right? And, like, that should be a direct thing that, you know, gets discussed at standout.
312 00:35:01.920 ⇒ 00:35:18.859 Clarence Stone: So you, like, just, I guess, another reminder, right, that you’re in command of that time. You can say, hey, if the right way to keep good hygiene of all our documentation is that you spin up a new ticket for this, then you ask them to do that. And if they’re not complying there, then that, you know, that’s another level of enforcement that we can get towards.
313 00:35:19.000 ⇒ 00:35:31.610 Clarence Stone: Right. Okay. But what I will do to back you guys, once I get those two pieces of information, what does the perfect ticket look like? Plus, how do you handle changes on a ticket, right? I’m gonna write documentation for you.
314 00:35:31.620 ⇒ 00:35:49.460 Clarence Stone: I’m gonna write all of it together, and you can… you guys can tell me if that looks good, right? Because when you enforce it, you can just say, hey, look at the documentation that says this is how we handle tickets, right? So, based on that criteria, you know, black tires instead of the silver wheels, it requires us to create a new ticket.
315 00:35:49.460 ⇒ 00:35:51.749 Clarence Stone: I expect to see a new ticket tomorrow for this.
316 00:35:52.660 ⇒ 00:35:53.440 Clarence Stone: Right.
317 00:35:53.870 ⇒ 00:36:03.000 Clarence Stone: So, a way you should remember that you get to call the shots on, you know, slowing things down and making sure that all the information’s up to date.
318 00:36:03.270 ⇒ 00:36:08.499 Clarence Stone: And if that’s not happening, that really needs to get escalated to the Utah and Robert level.
319 00:36:12.850 ⇒ 00:36:15.960 Clarence Stone: Just so I can get an understanding of, like.
320 00:36:16.350 ⇒ 00:36:30.980 Clarence Stone: how far things are off the rails, like, how many of your projects are in this situation where you don’t have a good understanding of the progress? Like, is this one or two, or, like, all of them, or, like, how bad is this, guys?
321 00:36:33.730 ⇒ 00:36:40.990 Awaish Kumar: Yeah, it’s, it’s for the clients where I’m not work, like, I’m not directly involved. For example, like…
322 00:36:41.150 ⇒ 00:36:42.380 Awaish Kumar: And then…
323 00:36:43.080 ⇒ 00:36:50.309 Awaish Kumar: That’s why I have this issue on those clients, because I’m not directly involved, and I don’t have enough context.
324 00:36:50.800 ⇒ 00:36:51.670 Awaish Kumar: And,
325 00:36:52.110 ⇒ 00:36:59.689 Awaish Kumar: I don’t see the tickets, so… I don’t know what’s going on, and, like, I have a lot of work, like,
326 00:36:59.990 ⇒ 00:37:09.040 Awaish Kumar: Right now, like, development work as well, so I don’t get time to, like, go in the slack of other clients to see what’s going on here.
327 00:37:09.450 ⇒ 00:37:32.799 Clarence Stone: Right, yeah. So, I mean, that’s another thing that we need to write in our ticket policy, right? Like, conversations related to work that’s on a ticket needs to be updated at the ticket level. It doesn’t matter that you had a phone call with somebody, right? That doesn’t show progress. You need to show me exactly in that ticket where, you know, where the decisions are made, where the updates are, right? Like.
328 00:37:32.800 ⇒ 00:37:42.589 Clarence Stone: For example, like, OAS, let’s say, you know, a customer has a new dashboard requirement, I come and say, hey, like, I need another 2 days, this is a new requirement.
329 00:37:42.590 ⇒ 00:37:48.499 Clarence Stone: Awash, you tell me I have to create a new ticket. I go in and say, after speaking with Awash, this is.
330 00:37:48.500 ⇒ 00:37:49.260 Samuel Roberts: Right, right.
331 00:37:49.260 ⇒ 00:38:05.300 Clarence Stone: ticket, tacking on the feature required from the, you know, per business, right? That’s what needs to happen, right? But the enforcement level comes at that daily stand-up when I say, hey, there’s a new feature request from the client, a way she can automatically say, that triggers a new ticket.
332 00:38:05.300 ⇒ 00:38:10.949 Clarence Stone: And please write a description of, you know, the… how this ticket came to be and who made the decision.
333 00:38:11.150 ⇒ 00:38:27.669 Clarence Stone: Right. So it seems like the biggest problem that’s happening, and I think, Sam, this does echo with what you’re saying, is like, hey, like, I understand what’s going on, because I’m part of these projects. Exactly. It indicates to me massively that most of the conversations are happening in the client chat accounts.
334 00:38:27.670 ⇒ 00:38:30.759 Samuel Roberts: This is ex- yeah, I was gonna… I was just gonna say that, like, that’s been a problem
335 00:38:31.110 ⇒ 00:38:33.740 Samuel Roberts: for a while, is there’s Slack, there’s…
336 00:38:33.740 ⇒ 00:38:34.190 Awaish Kumar: Thank God.
337 00:38:34.190 ⇒ 00:38:51.399 Samuel Roberts: Zoom, there’s linear, there’s now Instagant, and, like, I think we probably need to start enforcing a little bit more, like, okay, that’s great, everything we just said is wonderful, I’m glad we talked about it, put it in the ticket. Like, you know, tag this linear, tag this, Slack in the ticket, or, you know, make sure to pull that reference, or whatever.
338 00:38:51.560 ⇒ 00:38:56.629 Samuel Roberts: But linear should be the source of truth for a lot of that stuff. That’s how we have to lean on it.
339 00:38:56.630 ⇒ 00:39:01.019 Clarence Stone: Yeah, that’d be absolutely right. And I don’t think that’s an EP job either, like, if I was.
340 00:39:01.020 ⇒ 00:39:02.360 Samuel Roberts: No, no, I agree, yes.
341 00:39:02.360 ⇒ 00:39:06.410 Clarence Stone: signed a ticket, right? There’s, like, business decisions that were made as part of that.
342 00:39:06.410 ⇒ 00:39:06.750 Samuel Roberts: Yep.
343 00:39:06.750 ⇒ 00:39:08.560 Clarence Stone: I go back into the ticket and said.
344 00:39:08.560 ⇒ 00:39:09.370 Samuel Roberts: Exactly.
345 00:39:09.370 ⇒ 00:39:14.699 Clarence Stone: Had a chat with Sam. He told me I should use this extension, or this service, or this capability.
346 00:39:14.700 ⇒ 00:39:17.450 Samuel Roberts: going to use this as the plugin, right?
347 00:39:17.550 ⇒ 00:39:18.420 Clarence Stone: Yep.
348 00:39:18.830 ⇒ 00:39:30.560 Clarence Stone: I would catalog that in the ticket, because that’s where, like, the whole life cycle of the project sits. So, I think we just need to communicate that more strongly, and also hold to it at stand-ups.
349 00:39:30.950 ⇒ 00:39:31.310 Samuel Roberts: Yes.
350 00:39:32.370 ⇒ 00:39:41.409 Clarence Stone: Yeah, like, I hate to give the two of you more work, because you two are probably some of the most busiest people in this organization, but I do need to know
351 00:39:41.630 ⇒ 00:39:54.810 Clarence Stone: what does a perfect ticket look like? Give me all the data points that goes into it, right? And then the criteria of acceptance on whether or not a ticket stays, or you have to create a new one based on conditions.
352 00:39:54.990 ⇒ 00:39:59.929 Clarence Stone: Right? Because, yeah, like, your team doesn’t have that formula in their head, and…
353 00:39:59.930 ⇒ 00:40:00.360 Samuel Roberts: I am.
354 00:40:00.360 ⇒ 00:40:06.669 Clarence Stone: The hygiene’s not gonna happen unless somebody’s, like, there saying, hey, you gotta follow the rules, right?
355 00:40:07.850 ⇒ 00:40:12.309 Clarence Stone: The funny thing is, a lot of what you guys are describing
356 00:40:12.540 ⇒ 00:40:14.839 Clarence Stone: it’s already in the playbook, but I doubt.
357 00:40:14.840 ⇒ 00:40:15.210 Samuel Roberts: Yeah.
358 00:40:15.210 ⇒ 00:40:16.580 Clarence Stone: aren’t actually…
359 00:40:17.020 ⇒ 00:40:21.570 Clarence Stone: are actually reading it. So this is why I don’t even want to create new documentation.
360 00:40:21.570 ⇒ 00:40:22.160 Samuel Roberts: Alright.
361 00:40:22.160 ⇒ 00:40:25.879 Clarence Stone: I would rather you guys, like, look back at, like.
362 00:40:26.060 ⇒ 00:40:32.220 Clarence Stone: The linear ticket agent, and the linear ticket transcripts, and the way, like.
363 00:40:33.000 ⇒ 00:40:35.720 Clarence Stone: We handle tickets as part of the vault.
364 00:40:35.850 ⇒ 00:40:40.040 Clarence Stone: And… and then come back to me on if that’s still wrong.
365 00:40:40.550 ⇒ 00:40:43.839 Clarence Stone: Because, like, the vault has instructions on how we handle this.
366 00:40:45.820 ⇒ 00:40:51.700 Clarence Stone: I don’t know what you guys think. Do you still think I should create documentation? If you want me to, I will.
367 00:40:53.170 ⇒ 00:40:55.649 Samuel Roberts: I would… hold off, let’s see what’s…
368 00:40:55.980 ⇒ 00:40:59.380 Samuel Roberts: Let’s see what’s there, we’ll see what we can point people to already.
369 00:41:00.830 ⇒ 00:41:03.799 Samuel Roberts: And then if we need to make more explicit.
370 00:41:04.390 ⇒ 00:41:04.920 Awaish Kumar: Hmm.
371 00:41:05.200 ⇒ 00:41:06.029 Samuel Roberts: Then we can.
372 00:41:06.850 ⇒ 00:41:16.210 Clarence Stone: Yeah, like, if it’s… if it’s there, we just have to start being more disciplined with pointing it out and saying, hey, per, you know, our ticket guidelines, we have to treat tickets this way, right?
373 00:41:16.210 ⇒ 00:41:16.780 Samuel Roberts: Yep.
374 00:41:17.830 ⇒ 00:41:23.150 Clarence Stone: Here are the, the, the three files.
375 00:41:23.870 ⇒ 00:41:28.980 Clarence Stone: in the playbook… I’m just gonna drop it in here.
376 00:41:33.180 ⇒ 00:41:35.060 Clarence Stone: I would check those and see.
377 00:41:35.670 ⇒ 00:41:40.820 Clarence Stone: If it’s covering everything, and if it’s not, if, yeah, if there’s a gap in our documentation, let’s… let’s write it.
378 00:41:41.180 ⇒ 00:41:41.950 Clarence Stone: Not a big deal.
379 00:41:42.130 ⇒ 00:41:42.940 Samuel Roberts: Right.
380 00:41:43.580 ⇒ 00:41:49.719 Clarence Stone: Yeah, but this seems to be a problem that’s compounding, so let’s, let’s keep a close eye on it.
381 00:41:50.000 ⇒ 00:42:03.419 Clarence Stone: Oasis, that makes sense? Like, I think, we just have to enforce the rules, and if any of those guides are missing information, we should update it with the right information.
382 00:42:05.450 ⇒ 00:42:12.020 Clarence Stone: Yeah, I have a sense that the biggest problem is all the conversations related to project work is just happening in the chat, and it’s not going to the ticket.
383 00:42:14.690 ⇒ 00:42:16.270 Samuel Roberts: Yeah, I think that’s a big problem.
384 00:42:16.750 ⇒ 00:42:19.970 Clarence Stone: Yeah, okay. We’ll bubble that up.
385 00:42:19.970 ⇒ 00:42:20.400 Samuel Roberts: Okay.
386 00:42:20.400 ⇒ 00:42:21.060 Clarence Stone: this.
387 00:42:23.690 ⇒ 00:42:32.399 Sheshu Chandrasekar: Yes, I am. I was just jotting down some notes, but I think my head, I’m realizing maybe the vault isn’t the most.
388 00:42:33.830 ⇒ 00:42:41.879 Sheshu Chandrasekar: optimal location, in a way, to read all the acceptance criteria, so maybe we’ll just create, like, a guide of some sort. But also for EPs, like.
389 00:42:42.410 ⇒ 00:42:49.730 Sheshu Chandrasekar: I’m thinking we create, like, templates, like, PowerPoint templates of some sort, and then at the end, we reference this, right? Like, as, like, a…
390 00:42:50.350 ⇒ 00:42:59.650 Sheshu Chandrasekar: what do you call them? Like, an archive or a footnote of some sort, so they can always go back and easily access this. I’m just seeing all these different ideas, but…
391 00:43:00.000 ⇒ 00:43:08.969 Sheshu Chandrasekar: Yeah, I mean, if it’s already written, I think it’s a problem of access now, and keeping up with those guidelines, so that’s what I’m thinking as well.
392 00:43:10.010 ⇒ 00:43:14.949 Clarence Stone: Yeah, I hate to say this, but water flow is where it’s ever easy.
393 00:43:15.400 ⇒ 00:43:26.089 Clarence Stone: even if we write down these, you know, SOPs and processes, guys, like, it never is real until, you know, there are leaders in the organization that.
394 00:43:26.090 ⇒ 00:43:42.580 Clarence Stone: enforce those standards, right? And I want to empower you guys with the ability to do all of that. So, one, before I can say, like, hey, put your foot down and demand that, you know, people update those tickets, let’s make sure that the documentation actually supports them. Right, right, right.
395 00:43:42.600 ⇒ 00:43:59.230 Clarence Stone: Before I go chasing people down, and then two, once it does say that, you have all the power to make sure that you’re using your time blocks to enforce it. So if it comes short, let me know. We’ll follow up and figure it out.
396 00:43:59.770 ⇒ 00:44:15.890 Sheshu Chandrasekar: If it even helps in the meeting invites, maybe you can even add, like, the agenda, right? Like, in the Google Calendar invite, saying, hey, I need to reference this ticket, I need certain information, or I’m missing this. Just write it down in the calendar, because sometimes
397 00:44:15.930 ⇒ 00:44:19.789 Sheshu Chandrasekar: People will look into that. People will open the meeting and be like, oh, shoot, I need to…
398 00:44:19.900 ⇒ 00:44:24.300 Sheshu Chandrasekar: bring this up, or I need to give an answer to Awash, or to you, Sam, like.
399 00:44:24.640 ⇒ 00:44:27.430 Sheshu Chandrasekar: They’ll see that, and maybe that could help as well, but…
400 00:44:27.830 ⇒ 00:44:32.290 Sheshu Chandrasekar: Again, that’s just an experiment that we’ll have to conduct and see if it works, but,
401 00:44:32.600 ⇒ 00:44:38.829 Sheshu Chandrasekar: Yeah, like Clarence is saying, I think it’s more of a discipline matter than it is an SOP matter, so… yeah.
402 00:44:40.100 ⇒ 00:44:52.050 Clarence Stone: Yeah, and remember that, like, in the stand-up protocol, the reason why I have you guys as a service leader start for every single project is so you can make that call out from the top.
403 00:44:52.920 ⇒ 00:45:00.850 Clarence Stone: to say, like, hey, I saw your week’s plan this week. Here’s some of the things that I need some more details on.
404 00:45:00.850 ⇒ 00:45:04.159 Samuel Roberts: Yeah. CSO, tell me about how things are going with your client.
405 00:45:04.160 ⇒ 00:45:16.810 Clarence Stone: Right, so you are at the top, opening it up for each of the projects. So, if there’s stuff that they owe you, you can make that call out from the top, and then reinforce it at the end. You also end it.
406 00:45:17.120 ⇒ 00:45:17.790 Samuel Roberts: Right.
407 00:45:17.790 ⇒ 00:45:18.520 Clarence Stone: Right?
408 00:45:18.780 ⇒ 00:45:26.999 Clarence Stone: So, when you end it, you can say, hey, the plan of attack is going to be that you update those tickets, or you create a new ticket for that change order.
409 00:45:27.730 ⇒ 00:45:35.300 Clarence Stone: Right? So that you can reinforce it at the top and the bottom. It’s really just designed like a meta-prompt for.
410 00:45:39.210 ⇒ 00:45:48.680 Clarence Stone: So, that’s my best advice. If you guys could just take a look at the documentation on that. Yeah. Let’s try to tackle this this week, guys. I think we can do it. We’re so close.
411 00:45:48.680 ⇒ 00:45:49.430 Samuel Roberts: Thanks, Al.
412 00:45:49.430 ⇒ 00:45:58.729 Clarence Stone: getting accurate information is something that, you know, we as devs should be doing. It’s good hygiene regardless of where you work. Totally.
413 00:45:59.690 ⇒ 00:46:00.230 Awaish Kumar: Okay.
414 00:46:00.230 ⇒ 00:46:09.070 Sheshu Chandrasekar: Yeah, and one last thing before I have to drop as well. If you could find, like, a really good ticket that you worked with in the past, and a bad one.
415 00:46:09.340 ⇒ 00:46:17.339 Sheshu Chandrasekar: And just, like, kind of outline why. Why is this ticket so good? What… what did it help you accomplish? And, like, not in terms of, like.
416 00:46:17.770 ⇒ 00:46:19.550 Sheshu Chandrasekar: the ask itself, but, like.
417 00:46:19.550 ⇒ 00:46:19.900 Samuel Roberts: Right.
418 00:46:19.900 ⇒ 00:46:35.740 Sheshu Chandrasekar: or, like, how granular the ticket was. Like, certain details on why this ticket was bad, right? Like, if you can give me, like, the pros and cons of each ticket, that’s a good example and a bad example, that’d be helpful, because maybe we can use that to help you guys, you know.
419 00:46:35.920 ⇒ 00:46:39.340 Sheshu Chandrasekar: enforce that with other… the EPs and stuff like that, so…
420 00:46:39.470 ⇒ 00:46:51.559 Sheshu Chandrasekar: Yeah, again, I’m so sorry, like Clarence said, like, I don’t want to add more… more work to your pile, but this could be very helpful for me, and, you know, we can… we can refine it a little better moving forward.
421 00:46:53.070 ⇒ 00:46:53.610 Samuel Roberts: Cool.
422 00:46:54.500 ⇒ 00:46:55.620 Awaish Kumar: Good. Thank you.
423 00:46:55.930 ⇒ 00:46:57.709 Clarence Stone: Great. Thanks, guys.
424 00:46:57.710 ⇒ 00:46:58.599 Sheshu Chandrasekar: Thank you so much.
425 00:46:58.600 ⇒ 00:47:01.820 Clarence Stone: Back as always. We’re just gonna keep refining this until it gets…
426 00:47:01.820 ⇒ 00:47:02.880 Samuel Roberts: Yeah, exactly.
427 00:47:03.560 ⇒ 00:47:05.690 Awaish Kumar: Cool. Thank you.
428 00:47:06.110 ⇒ 00:47:07.400 Sheshu Chandrasekar: Thank you, have a good one.
429 00:47:07.400 ⇒ 00:47:08.480 Samuel Roberts: Yeah, I guess too.
430 00:47:08.480 ⇒ 00:47:09.750 Awaish Kumar: Bye.
431 00:47:09.750 ⇒ 00:47:10.320 Sheshu Chandrasekar: Bye.