Transcript 0:00 What kind of formats for, you know, educating have worked the best? Like workshops or the office hours or maybe some guidelines. What, what's your experience on the formats? 0:11 Uh, we had a lot of different formats and, uh, for example, we had regular office hours, we had, uh, lectures, we had workshops. 0:22 But, um, with the workshop, for example, I didn't guide them, them myself, so here I don't have a lot of experience. But speaking about lectures, it was a different format again. It was like, uh, pure vendor sessions. 0:37 It was, uh, sessions with, um... for example, somebody speak about, uh, the, the vendor speak, and plus it could be a case from the inside from the company. 0:47 And, um, it could be the third format when we started making the dashboard to understand if you need the session or not. And, um, this dashboard thing we just started doing the last year, and, um, 1:05 it was kind of interesting experience because y- the person can understand directly if he need to come. And most of the times they coming because they see that, for example, exactly this optimization we need right now. 1:18 We see this m- main metrics, we see this main KPIs, which is influenced by this metric, by this optimization, and they are coming. 1:25 And for me, this, uh, format of the lectures, uh, and internal case was one of the most, um, of the f- w- one of the favorites, most of the people joined it because they saw that somebody already did it, and maybe they can apply it too. 1:43 Because they see that this case is alive. This is not something, uh, like artificial. This is something real. 1:50 And we explaining them, like, how they can do it, how another team did it, how they find out it, and then one of the vendors explain more into details, like what else you can do, how you can understand how to do it, and what is suitable for you. 2:06 And, uh, most of the times people joining this. But speaking about, for example, uh, FinOps, um, office hours and just office hours in general, I did it kind of weekly, but it was not the best... 2:22 For me, it wasn't work as the best format because teams still continue, um, texting me and continue asking me. 2:31 And sometimes, of course, I send them to this, uh, office hours, like, "Come join me on Monday, and I will explain you everything." But 2:41 at the end, it's better to leave something like a channel for them to communicate with you than just saying like, "Join exactly this day. Only this time I am available." 2:52 I think it's, it's, it's not, [chuckles] it's not the type which I think is working very well. But yeah, lectures was one of the best things. No, that's cool. 3:01 I, I totally agree that, like, case studies and, you know, seeing people already doing that is one of the best, like, resources in FinOps. 3:08 I tend to, like, focus on that, on, on the newsletter itself, and I, I think it's more realistic when I see, you know, the different company like Adidas, Zalando, all these big companies, like, doing, like, a major, uh, thing. 3:21 It's like, yeah, they did it, so maybe you can do it, and they posted like GitHub code even or things like that. So examples. 3:28 And then office hours, like, I, yeah, I think, [mouse clicking] you know, it's better to have [bell ringing] like a Slack channel or a Teams channel and, you know, drop questions over there. 3:35 And then from those questions, like, you can maybe leverage and do a guideline or maybe do something that can be shared to, or an FAQ section maybe. 3:44 Um, so I think those are very good, good, uh, formats that, that you mentioned. And, 3:49 you know, um, starting from, you know, the formats, so have you been able to, like, uh, onboard or embed, sorry, um, this education into, like, processes of the company? 4:01 So for example, when you are doing the onboard or when you are doing, uh, you know, certain updates, have, have you been able to, to do th- things like that? 4:13 We decided that we don't want to put and to push our FinOps education everywhere. Mm-hmm. And, uh, we just focus on the few key processes where it can be suitable. 4:24 And, uh, I tried to keep it, like, inside the central team. And, uh, of course, we had some processes where we did these meetings, uh, like every time. For example, budgeting. 4:38 Every time before budge star- budgeting started, I always did a session where I explained what to do, how to do, who have to participate, like all this information. I teach them how to... 4:49 how they can forecast themself, and, uh, it was something what, uh, take part with the process. Uh, sometimes it was, um... but mostly we try to do our own schedule. 5:01 And for example, we try to do this education session once in two months, one in three months, like gathering this data, this optimization ideas about which we can tell to the teams. But we had, uh, this FinOps, um, 5:18 uh, we had this meeting for the practitioners and, uh, which was something like an onboarding, and it was my, uh, main onboarding process. 5:29 And when sometimes it's a lot of changes in the company when you need to onboard a lot of people, but not just the people who is just, who was just hired, but people who, uh, take a part in, on this FinOps practitioners activity. 5:42 For example, somebody left, and they find a new person who will replace it in the FinOps activity. And when it's a lot of people, I did this onboarding. 5:50 Yeah, but, uh, of course, all the-FinOps process was very supported with the documentation. And, um, yeah. So long story short, um, we try to keep this education activity based on our FinOps, uh, processes. 6:08 Uh, and, uh, that's, that's the main thing here. Because sometimes you can, you can try to put it somewhere, but, um... And to draw in any activity from other teams, but we still was afraid that it could be a blocker. 6:23 It could be a blocker for something, because when you put a lot of, um, activities into one process, it's becoming longer. You can try, you can do your best, you can do everything, but it always will be longer. 6:34 So that's why, yeah, FinOps practitioners and education bec- uh, is, uh, became mandatory, and I think it have to be mandatory if you want to grow the maturity of the FinOps in your company. 6:46 But it's still, uh, the thing which, uh, FinOps central team decide when you have to, uh, do this education meeting and, uh, which pro- before which process you have to educate your people more. 6:59 I think here it's like this. Okay. No, that's, that's an interesting approach. Um, I've seen, like, like, mandatory everyone do- does it to, like, nobody does anything. 7:10 So I think that, uh, as a, as a hybrid approach, it, it's a good stuff. And, you know, um, what have you seen, like, um, as a motivation, um, for people to, to learn FinOps? 7:21 So, you know, you have the, the mandatory things, but, you know, for people that, you know, want to learn more about it, what, what are having, you know, the incentives or, or tips that you have seen on, on your side? 7:33 It's so different because people is so different [chuckles] too. Yeah. It's everybody's motivated with so different thing. For ex- for example, somebody is crazy self-motivated. 7:45 Somebody is motivated by the manager, and when the manager is pushing, he will start doing something. 7:52 Somebody is crazy about the process, and they like the process so much, and they like to edu- uh, to learn, to educate, and, uh, to, to all the stuff. And, um, but the thing is [chuckles] that, um, 8:11 um, people like to see the result, and people like to see, uh, how they influence something. Like, um, one person came to me and say once that, like, "I want to do FinOps because I want to see the result of something. 8:27 Because I want to see how my, um... Which... All, all the power which I spend influence the money, influence something, influence the product." And, uh, I think this is the thing which can motivate most of the people. 8:42 But, uh, to be fair, uh, things goes much faster when all these KPIs becoming mandatory. And, um, after that, people splitting for two types. 8:57 First, people who is doing a bare minimum, and they will continue doing bare minimum. If you will show them the results, they don't care. But... 9:04 And another part of the people who, whose, w-who you can mot- whom you can motivate and who want to do more. And both of them, again, you have to show them, you have to visua- visualize their results. 9:18 They have to show them the KPIs which can motivate them. For example, how they're decreasing the waste, how they're decreasing the cost, and, uh, how much they save. This is what can motivate them. 9:31 And the very good sign which I saw once, but not once, I think more, some people, uh, started setting their year goals with the FinOps goals. 9:42 And, uh, so this is like this year goals which you s-set up for HR with your manager. They started putting FinOps there. And of course, it's motivate them too. So people see... 9:54 People can be motivated when they see that it's something valuable for them, that their actions make a value for them and for the, for the, for the company it's much less, to be honest, because it's always about us. 10:08 And, uh, so yeah, from my point of view, it's something like this. Yeah. That's, that's interesting. 10:15 I think what you mentioned about the goals, like, I, I haven't thought about it because I do, like, have a similar goal system on, on my company and, and I think that would be interesting, like, especially, well, of course, for the FinOps, uh, people, but also for, for engineering, like, uh, you know, reducing cost or making cost more efficient, um, for, for existing deployments, I think it would be a very interesting goal. 10:37 Um, and also for development, like, you know, I'm able to do... Try to do the same architectures in a more efficient approach. Yeah. So that would be, um, super, super interesting. 10:48 And, you know, okay, so we've talked about, like, how you explain to FinOps and how you make people learn it and how you can educate. 10:55 But, so let's say that someone, like, from the different personas, let's say, like, "Okay, I get it now. I passed the education that, that you have gave me," and they want to do, um, to, to start applying FinOps. 11:06 So what do you think are the, the first steps that they need to, to do, uh, and, and start with? Um, I want to think about this question from the two points of view. What will do my 11:25 engineer, engine- uh, when I will talk to him and when he will go through the education process and through this FinOps champions process or whatever, and what the manager will do? 11:37 I think from this part, because I think that we everybody know what the FinOps practitioner, like professional FinOps practitioner will do. 11:44 Because it's much more difficult, I don't think that we will not have time today to [chuckles] say all the steps which, which, uh, the person have to do when they want to start the FinOps. It's a lot. 11:57 But if we speak about-When you educate somebody and when you want to see that they achieve the result, in my, um, in, with my engineers, first he have to go and check the tagging, like if everything is tagged. 12:14 And the second thing, he have to check his waste dashboard. This is, like, in my experience, uh, what my engineers have to do. 12:23 But again, of course, it's like your, um, way how you will set up your FinOps processes, your communication with engineers and whatever. 12:32 But I think here is the few things which you can make more self-sufficient for them, for the engineers, which engineers can do, and this is everything what they can touch with their arms area. 12:47 And most of the time, this is simple way, s-simple optimization. This is a structured optimization, which is tuning for everything. This is right sizing. This is waste. 12:57 This is, um, for example, checking out which is tree type you can use, et cetera. Uh, gravitons for RDS, uh, and so on. This is simple activity with the budgeting. And, um, 13:13 yeah, this is like an examples which, which, which can be done. And for my engineer, he will go, and he will check the tagging and the waste dashboard. 13:21 Like how much, uh, waste, because he already will understand that waste is super bad, and this is simple, applicable thing which you can do first. 13:30 And that the tagging that is, is like our strategy, is a slow, long-term activity, and he is responsible for that because not we are doing te- not, not FinOps team doing Terraform, uh, script. 13:42 And this is something what the team is doing, and this is their area. And speaking about the manager, if we sp- if we talk to the manager or to the owner of the, 13:54 uh, branch or whatever, from my point of view, but this is only my point of view, that he have to go and set up, um, his, um, um, alerting system. 14:07 Like, he have to set up how much he have to spend daily based on the average or based on the maximum, for example, and his monthly, um, monthly aler- alerting system. 14:18 I think this is like first steps for people whom you educate and who talk to you, um, as a FinOps, uh, central team. Oh, that's, that... I think that you... 14:30 I, I was, you know, curious about, like, the different persona approach and, you know, how do you do it with, with engineering? What, one is one thing, and I think I started with tagging and, and, you know, the waste. 14:40 Like, yeah, I think waste and tagging are one of the concept that I have seen, like, more people involve into and more people wanting to learn and, and, you know, the budgeting is also, of course. 14:50 And it's more like a managerial kind of thingy, and it's fairly, you know, easy to, to start with. And, you know, we have started with, uh, we have talked about the, the things to start and the first steps. 14:59 What have you seen are the first mistakes that people do? Like when they are starting, and they, they do the best approach, uh, and but still make some mistakes when, when they are starting doing FinOps on their own. 15:11 I think that people want to achieve a quick wins, and it's not always a thing. Like, um, again, if we'll go back to check your tagging, tagging is not a quick win at all. 15:24 But it is a thing which you have to take care about it first. 15:27 And when you're starting, like, doing these quick wins, quick optimizations without understanding what your business want to do, and if you really need to do this exact optimization right now, this is, this is the mistake from my point of view, which you can make, and you have to be aware of it. 15:44 Because quick wins is not always win-win. This is just quick and not quick is... Not all the quick things is good. 15:50 But sometimes, of course, sometimes it can be exactly in the eye, but sometimes it can be directly wrong thing. That's, that's, uh, that's a good quote. 16:00 Like, uh, I, I think that sometimes, like, we think about the quick wins, and yeah, this is fairly easy, and this is what, what I need to learn. 16:09 But sometimes it probably generates, like, an issue in the long term, or it's something that you need to make a quick win, like, every week, and it's not sustainable, and maybe you need to automate it or, or things like that. 16:20 Um, so yeah, that's interesting. 16:22 I, I can tell, like, one of my, my managers when I started doing FinOps and, and all of this, one of the advices was, like, if your hourly rate is more than the cost that you are saving, you probably better [chuckles] use your hourly rate to develop the business and not, uh, save money. 16:39 With, what I mean by that is, you know, if you are doing, like, uh, experiments and you are in a small project and, you know, the time that you are, uh, thinking about doing an opti- a quick win optimization that is not, let's say, replicable or automated- Mm-hmm... 16:54 um, uh, then if your hourly rate is more, then you are wasting, uh, company's money, uh, instead of doing development. Yeah. Um, so you need to think about that, uh, right? 17:03 So, uh, it's something also to deliver to, to engineers because we... 17:08 Like, I come from the engineering side, and it's like we think a lot about, you know, testing and doing the latest thing and the latest, you know, uh, trendy thing, and we forget about, like, the cost to the company, like in the hourly rate, right? 17:21 So- Absolutely... it's like you, you need to think about what you are doing, and, and you need to think about, you know, is this worth for the, for the company. 17:29 Yeah, because it's always about the collaboration, and I think that any FinOps, most of the FinOps activity have to be done with the collaboration. 17:37 And so if you are this, like, when you're doing these first steps, you cannot do these first steps without support. 17:44 Even if you are a FinOps, even if you are first FinOps practitioner in the company, if you just was hired, you still need to start with the communication. You need to talk to the stakeholders. 17:53 You need to understand what is your, um... 17:56 You have to have this list, what is your perfect first steps, and, uh-Quick wins have to be there, of course, but you have to communicate with people because not all these optimizations applicable directly everywhere. 18:12 And yeah. No, I, I think you, you say right. 18:16 And, and you were, uh, now that you're talking about communication, like, what had been the main problem or problems that you have seen in the communication from, from the FinOps team when you're trying to, you know, build awareness and communicate about the practice? 18:32 Um, you know, I don't know a lot of mistakes because people like to speak about success. They don't like to speak about mistakes. 18:41 And when you are search for something, or when you are listening to the podcast, or when you are watching this, uh, I don't know, uh, FinOps sessions or presentations, people saying you like, "Feel free to speak about the problems." 18:56 I remember once they told me like, "If you're doing a presentation, speak about the problems, it's okay." But at the end, you don't want to. You don't want to speak about that. 19:05 And that's why I don't know a lot of mistake from other people, but I know the mistake which I did once at the beginning of all this, uh, FinOps communication stuff and, um, trying to onboard people on FinOps boards. 19:23 [chuckles] And it was not to focus on the people who is not interested from your point of view, who is, like, not suiting or something. 19:34 And I remember I started going to the managers and saying them like, "Give me one practitioner. I will educate him. Just choose this one person, not more. I need only one." 19:47 And people started providing me two person, three person, and I'm like, "No, I'm not gonna onboard them. I need only one." And this... 19:53 And at, at the end, uh, it shows that, uh, these people, they want to learn because the manager choose them because they want to educate themselves, and they want to participate in something, and they're crazy interested. 20:08 But at the e- at the beginning, I said that I don't need them. But at the end, this is like extra brain in your FinOps group. 20:15 This is extra person who can, uh, even teach you something, who even can find something interesting for your company, for your, uh, FinOps activity. And at the end, I onboard them all. 20:28 It was a scheme that, um, like, it was one main FinOps practitioner and two, like, sub-FinOps practitioners, and the first person was responsible, and others was just go s- uh, went to the education sessions. 20:43 They participate, uh, they ask the questions, like, they were there. They were there all the time. 20:49 And I think, yeah, it's a mistake when you think that you know exactly, um, which people you want and you not, um, involve others. But you always have to be open. Well, that's, that's very interesting. 21:07 Like, I think, like, not, you know, uh, you don't have enough resources anytime in FinOps, like, especially in the human side. 21:14 Like, as more, uh, people that you can get involved, the better, even though, uh, you know, it may be trickier for you that you can feel like a, a bit of a bottleneck, like I have to teach too many people at the same time and all of that. 21:25 I think that, um, you know, having as much as you can and having as many people involved of, as you can. You know why it was like this? Because it was a mature process. 21:35 It wasn't fo- it was not like only just join us, and that's it. It was the, my responsibility how much people I onboard, how they, um, [lips smack] meet their KPIs, 21:51 because I need this list of the responsible person. I just needed to be sure that they're gonna do something because it was my annual KPIs. It was, uh, m-my activity. I have to be sure about these people. 22:07 And, uh, at that time, I didn't even think that maybe I have to onboard somebody else. I think it was, uh, about the mandatory, about the mandatory of the process. Yeah, I said wrong at the beginning. 22:20 That's because it was a mandatory, because it was necessary. These people have real responsibility, not just like something in the air. No, for real, you have to track your KPIs. You have to track your budget. 22:32 You have to track your waste. You have to do all of that, and I'm tracking how you track it, and I'm tracking how you're good in it and how you perform. And that's why I decided that it have to be strict. But at the end, 22:43 um, we still found these responsible persons. But I was able, I created another group, which I called, like, education group, and they just joined us and, um, took part in the processes and education. 22:57 That's, that's definitely, like, a, a, an interesting approach. 23:00 And you, you know, I think, like, what you, what you mentioned is very interesting from, from the FinOps side because I, I remember, like, reading a, a blog post from, I think, Ellie Rau. 23:11 Uh, she was in Disney, and now I think, uh, she's working in, in FinOps. And she mentioned about the, the burnout of, of FinOps, right? 23:20 So because sometimes, like, FinOps are involving too many things, they have too many tasks, and it's, you know, since it's a bit, uh, it's a process that is involving in too many factors. 23:30 Um, I don't know if you have suffered, like, uh, not FinOps burnout, but, you know, you have feel like a bottleneck and how you've been able to solve, like, if that happened, like, how you've been able to solve to, you know, try and delegate or try to, uh, leave these tasks to, to more people. 23:44 We delegated, um, yeah, it was delegated. 23:49 And, uh, what I said about this mandatory thing, about this mandatory FinOps practitioners, the more teams you have, the more difficult for you to be, be customized central team because you need to support everyone. 24:03 And, uh, like, at the end, it was-120 teams or something, and, um, FinOps team was overwhelmed. It was a lot to do, and, um, 24:21 the self-sufficiency helped, helps you a lot. And, uh, this is how to not to be a bottleneck. 24:29 Again, at the topic of the discussion, educate them, provide them tool set, provide them documentation, support them, and just let them do their stuff. Because they... 24:41 In, in s-some things they're so close to their numbers, they're so close to their resources. 24:47 Sometimes when we speak about budgeting, I don't remember if I talk about it or not, but how it works right now and how it, I think, have to work. 24:57 Like, you are, as a FinOps central team, you are doing main canvas, like, your main forecast, and the team can put their details, they add their details exactly in their forecast, and that's how you can achieve the best, um, detailed and the most right forecast. 25:18 After, um, m-m, providing opportunity for our teams to budget themselves, of course w- of course I control it, of course I do analysis of their n-numbers, of course we had our KPIs. 25:32 Uh, for example, is it how much is bigger than our forecast? How much it lower than our forecast? It was a few KPIs. 25:39 At the end, we get, like, if the prev- the year before it was, um, only 75% of the teams was inside our forecast, inside the budget at the end of the year. 25:52 Next year, when teams becomes more s- become more self-sufficient, when s- team started, um, budgeting themself, it was already 95. So it plus 20 years of, uh, t- 20% of the, um, 26:11 budgeting accuracy, and I think it's a great... It's, it just... And, um, we achieve, we started spending three times less time as a central FinOps team for this budgeting process, and plus we get it 20% better. 26:28 I think it's real numbers and, uh, this is, like, we avoid this bottleneck, and we make the process better because we just did the clear processes, documentation tools, et cetera. Yeah. 26:40 I think what, what you mentioned is, is key, right? 26:43 So, you know, being able to create, like, a self-sufficient, uh, thing, self-serving, like, being able to define, like, uh, the process so people can follow it, try to, you know, optimize this as much as you can. 26:54 I think, like, in general, like, busin- good businesses are, are built upon, uh, good processes, and once you, you do, like, a good process that impact, like, a lot of the, of the company, what you mentioned, you know, uh, three times, uh, less and 20, like, uh, an accuracy of 90, [laughs] like, 95% is, uh, is key. 27:14 Like, uh, you probably cannot have, like, an AI doing even, uh, better than, than that. 27:19 So, um, that are great numbers especially for budgeting and forecasting, which are, like, probably the most difficult things that you can do in, in FinOps, you know, knowing how much are you [laughs] going to, to spend, right? 27:32 Yeah. It is. It's... Yeah, it is. But yeah, I, I'm really proud of that what we did, and, uh, yeah. Of course, we did very good forecasting. It was, uh, my colleagues who, my colleague who did it very crazy good. 27:45 But anyway, I think that it's forecasting plus teams plus process plus tools. It's not, it's, um, it's in the connection with- No, that's, that's great. Yeah, I think it's, it's a wonderful result what, what you share. 27:59 And, you know, looking at the, a bit about more the, the human part, um, I don't know how you have seen, like, the, the evolution of the culture in the, in the company around FinOps, and how you have seen, like, from when you started in the, in the practice, like maybe in your early experiences, until now that you may have, like, seen, like, a lot of situations and a lot of changes. 28:21 How you have seen the culture evolving, like, in the different companies and how you have seen it growing maybe in, in your case? Um, I can say how I see how the culture growing in my case. Mm-hmm. 28:35 I think that this is about how people doing FinOps [laughs] and when and why, what is their reasoning, and it's always changing, and, um, 28:48 then more mature it's becoming, then, um, higher the ownership that, uh, for example, I can count it on the amount on, uh, teams with the FinOps practitioners. 29:02 I can, uh, understand it on how many, again, how many teams, uh, was able to do their budget without my support. I can, um, measure it on the, for example, um, tools usage. 29:18 How many people start, uh, using the tools, checking the dashboards, how often, uh, who is joining the meetings? Like, this is the level of the interest in the company, and when the interest is growing, 29:32 then, m- you can understand that the culture is growing. Of course, it could be sometimes a toxic culture or whatever. Yeah. 29:40 [laughs] But, but yeah, like, people just saying FinOps without understanding what is it, but I think when then, then you start showing them, uh, KPIs or where to pay attention on, uh, it's becoming more, um, more, um, it's m- better. 29:57 For example, this yearUh, I saw how much more directors, uh, joined the process and how they joined it. That their vocabulary become more professional. Uh, they started understanding what exactly to do. 30:14 They started providing the ideas how to make it better. 30:17 For example, when I did my products research, products researches inside, uh, the company, they already came with the ideas because they started understand the framework. 30:27 And this is for me how the culture change without the saving, because everybody understands how to measure it with the saving, but this is more about the human communication. 30:37 Because when people, when people join, when you see that people speak about FinOps already more professional, when you see the people without you pushing them to check the dashboards, they're checking the dashboards, 30:50 and when they're coming with ideas, I think for me it's a good sign of growing. Oh, definitely. And, and I think you brought, like, a point that I haven't thought about or seen, is that to measure it, right? 31:04 So because the culture- Yeah... 31:05 sometimes is more, let's say, more human, more abstract, more things like, yeah, it's growing or it's not growing, or we are in that situation, we have a better or worse culture, and it's like, what is a better or worse culture? 31:18 But what you mentioned about measuring it and seeing, like, how many people join, how many people are talking in the events, how many people are, uh, you know, proposing ideas, checking the dashboards, all of that. 31:29 Like, having KPIs for the FinOps culture, I think it's something that I have never thought, and it's a wonderful, a wonderful idea. 31:36 We, we'll probably need to think about defining the best practice about, like, what are the KPIs that are, um, useful over there, and you already, like, shared a lot of them, so thanks. Yeah. 31:46 To, to be honest, everything what I said right now, part of it can be counted. And, uh- Yeah... it can be, uh, yeah, it can be a quanti- quantity. 31:55 And for example, you can count how much people check a dashboard, and it was one of my KPIs which I check all the time, and when I make the changes. 32:01 And for example, when I do the education sessions, when I speak about, uh, something what you can't, can find on the dashboard, I checked after if people started searching it, if I explain it right, if I show them where to check, and if they go and check. 32:15 So yeah, a lot of the things you, you can, you can count. You can set up this, uh, um, logging and monitoring, and, uh, it will work for you. You can just do it in a good technical way. So yeah. Yeah, definitely. 32:29 It's just another KPI, and you can, uh, set it up the same that you do, you know, with the cost per user or things like that. Yeah. 32:35 You can do it for, you know, how many clicks, uh, how many visits a, a dashboard has instead of, you know, a, a website or the, or the checkout cart or whatsoever. You can do it for the, for the dashboard. Yeah. 32:47 So yeah, uh, I think that's, that's a wonderful thing to, to end up the, the conversation. 32:53 I think it was very, uh, you know, insightful and a lot of tips and tricks about how to build, like, a FinOps practice and, uh, culture in your company from scratch. 33:02 Uh, so thanks a lot for, for being here today with, with me, and looking forward to, to having you next time. Yeah. Thank you for inviting me. It was great to talk. Yeah. 33:13 Pleasure to talk, and see you in the next episode. Bye-bye. Bye-bye. [outro music]