Transcript 0:00 Different people doing FinOps come from different backgrounds, right? Your, yours is a DevOps background, I'm a cloud solution architect. 0:07 Um, but lots of people I meet don't necessarily have the, the technical experience, right? 0:11 For me, it's more about almost a, uh, a stakeholder management exercise in terms of developing trust, a level of understanding, a common understanding between those teams. 0:21 Partnerships, collaboration, developing trust in, in the first instance before then getting to the actual... 0:27 The incentive for engineers to reduce cost was that that cost saving could be used to, uh, bring in more engineers. The one thing for me is, is the common language, the, the common taxonomy, right? 0:40 So if I go to an engineer and I'm talking about reservations and commitments and NFUs, right? 0:45 [chuckles] And they don't know what I'm talking about, it's almost one of the bigger kinda change management, stakeholder manager communication projects that you might undertake to bring together such a broad community of people, and to get them up to the same level so that they can communi- comm- communicate efficiently. 1:04 So, uh, welcome everyone to a new episode of, uh, FinOps Weekly Podcast. 1:09 Uh, today we have a very, you know, special guest that has been recommended by a lot of people from, from the community, that has been featured, uh, in Professional Spotlight of FinOps Weekly, and I think it's a very well-known figure of, of the community. 1:24 Uh, we have today Jeremy Chaplin from Flexera. How are you, Jeremy? I'm very good, thank you Victor, thank you Damian for the opportunity to come and join you today. 1:33 Excited to have a, have a good conversation with you, so great to be here. Yeah. Yeah. Thanks, thanks for, for having the call. 1:39 I think, uh, it's, it's very special to, to have you today, and of course I want to, to greet my, my partner Damian. Damian, how are you doing today? Doing well. Very excited. 1:52 Um, doing a lot of stuff lately and, um, again, always willing to talk about FinOps and, uh, especially with, uh, a good guest like, uh, Jeremy. Yeah. So it's, it's been a, a pleasure to have you on today. 2:07 I think we have a very interesting discussion because as, uh, you know, several part of the, of the FinOps audience, some people come from the finance world, but a lot of people come from the engineer perspective, such as, for example, me, I come from, from the DevOps background. 2:23 Uh, so we want to know a bit about the integration, let's say, about this engineering into the FinOps world. 2:29 So, uh, in your perspective and in your experience, uh, you know, how do you find, uh, the role of the engineering side into, uh, the FinOps ecosystem? 2:40 How do you think it develops, and what are the key factors so it's effective for, for the FinOps practice? 2:47 Yeah, no, it's a great question and, uh, you know, it touches on the fact that different people doing FinOps come from different backgrounds, right? Your, yours is a DevOps background, I'm a cloud solution architect. 2:59 Um, but lots of people I meet don't necessarily have the, the technical experience, right? 3:03 They might be coming from a finance background, even a procurement background or, or whatever it might be, uh, e- even kind of licensing and, and other areas. Um, and so for me, you know, I've... 3:15 I wouldn't say I'm, you know, I've got the DevOps experience, but I've certainly had the experience of trying to take recommendations and look to engineers to act on things. 3:24 It becomes a, uh, a trust issue, and that typically is do you understand that, you know, the challenges around provisioning up, you know, infrastructure to support applications? 3:34 Do you understand the process that has resulted in, um, the decisions that we've ultimately made? 3:40 Because you're challenging an engineer to say, "Well, we think maybe the decision was, was ultimately wrong, or that there's a, a more optimal way that, that you can do that." Um, so the, the... 3:50 for me it's more about almost a, 3:53 uh, a stakeholder management exercise in terms of developing trust, a level of understanding, a common understanding between those teams before even then getting into the, the nitty-gritty about, well, how did I come up with this recommendation in the first place? 4:06 What tooling, you know, might, might I have used, uh, in order to, to make those recommendations. 4:12 So partnerships, collaboration, developing trust in, in the first instance before then getting to the actual, "Hey, let's have a conversation about why this instance type or, you know, why, why this particular node type for a cluster," or whatever the, the, the kind of change may be. 4:28 Um, how does that r- you know, reflect on your own experience, Victor? Yeah. So I mean, from, from my experience as something similar. 4:37 Um, so basically after all, uh, what I've seen engineers do is basically start from building internal tools from, from end users, so in this case if you are a, a vendor provider, basically building the actual tool that your, your service is doing. 4:51 But for an end user perspective, it's actually working on applications whose target is reduce cost or cost allocate or doing some stuff, and that's the way you introduce yourself to the ecosystem and start understanding showback, chargeback, all these terms, all this language from building the application. 5:11 So that's kind of the way that I'm seeing it's introducing themselves. And from there, this, this, let's say tier or this group of engineers can then expand or help, uh, the rest of the engi- organization to- Mm-hmm... 5:26 adopt the, the practices and to install, let's say, the FinOps culture from the engineering perspective because they already have worked in something that is, you know, FinOps related- Yeah... 5:37 but from a application perspective. So that's how I think it's, is the way I'm... I think it relates. Meeting in the middle, right? 5:44 So the, the, the FinOps persona kinda leaning in a little bit on the engineering side and getting some engineering, you know, understanding at a high level, and then the engineer leaning towards the FinOps persona and understanding the chargeback, showback use cases and, and the, the other terminology around FinOps. 6:00 Uh- Yeah... I guess hence the, uh, hence the training for FinOps for engineers, right? So [chuckles] Yeah. 6:05 Makes sense.And, and, and also it's because, you know, after all, in, in companies you get a point where, uh, you know, the, the management, uh, asks about cost, not exact- not necessarily because of FinOps, but just because of, you know, uh, finance perspectives. 6:22 So that way, um, you need to estimate like what's the, what's the unit cost or what's the business cost or business area cost. 6:31 And from there, I think it starts, you know, okay, now we will take the cost one time a year, and then we say, "Okay, we are spending a lot on this, this, and that." 6:39 And then from there, let's say, "Yeah, we can reduce from here to here." And then they need to start, you know, evolve, uh, evolving. 6:46 And then now I think it's more expanded, the FinOps culture, and it's more, let's say, professional and constant rather than one time, uh, budget in year. Yeah. 6:57 You, you touched on a point there, I think that's particularly interesting in, in the unit cost space, right? Unit economics measures. 7:02 Because we're talking about eliminating cost or we're talking about reducing waste, but actually we should be having a conversation about value. [chuckles] Yeah. 7:10 And, you know, it may well be that actually I include, increase the workload size, I process far more transactions or, or whatever the unit is, and therefore, you know, the, the, the value increases and the, and the unit cost decreases. 7:23 Um, so it doesn't necessarily have, have to be spend less. Yeah. It could be spend more [chuckles] and drive more, drive more revenue, right? So, 7:32 um, I think that that's common, you know, common in the, uh, the, the practitioners that I see and in the management focus, of course, in that it's always misconstrued to be a, a cost reduction exercise rather than a value realization exercise. 7:46 So- Well done... and I think that has different, you know, uh, implications to people taking action as well, because they're always, you know, make it cheaper. [chuckles] Cheaper and faster, quicker, right? So- Yeah. 7:59 Yeah. Competitive things. I, I'm also interested as well, so you know, given the recent direction of the foundation, um, you know, take- taking action on recommendations continues to be challenging. 8:09 And the things that I'm seeing that are barriers, you know, potentially to, to doing that would be, um, you know, obviously shift left would be great to kind of bake those things in at the point of design anyway, right? 8:21 And that then becomes, well, FinOps as a solution architect or FinOps as a, an application designer or whatever the role might be. 8:29 But then the other pie- piece is of course, um, you know, the proliferation of infrastructure as code platforms, um, changing the size of an instance in a cloud console is no longer the right thing to do. 8:42 What are, what are the solutions that are more tightly coupled to the pipeline that you're using to build that infrastructure? 8:49 Um, and I think that there's, there's, you know, challenges in terms of tooling a- and how we go about that, um, right now, but that, that makes it difficult. 8:57 It nee- you know, it really sits still with the engineer to actually make those, those changes rather than bringing any au- automation to bear at, at this point in time. Yeah. Yeah, indeed. 9:07 And also, uh, coming from, from that perspective, I think, for example, uh, the, the recent acquisition of HashiCorp, which is, you know, the company building Terraform [bell dinging] and all the Terraform movement that was I think a year or a year and a half ago. 9:21 But the change of licensing, uh, that it happened and all the, you know, OpenTofu initiative, all these details that now affects a lot about infrastructure as code because after all, apart from Terraform, there is, uh, Pulumi and there is OpenTofu as an alternative for Terraform. 9:36 But all- everything is super, you know, uh, concrete, super specific to the, these providers apart from, you know, cloud formation as advisor. But for the generic like multi-cloud perspective, it's only that. 9:51 Um, so that changed a lot. The, I think like now I think the, the FinOps is integrating more dev practices like infrastructure as code and all of these, so I, I assume that would come to, 10:03 to- It's gonna be interesting to see. I think IBM just closed on HashiCorp, right? Yeah. So I think that, that has been tweeted and announced this week. 10:11 So, um, it'll be interesting what direction they, they take that, that product in. [chuckles] I think there's some- Yeah.... there's some nervousness in the DevOps community that I speak to about that. [chuckles] Yeah. 10:21 I think the, the change, like, like the first thing was the, the, the t- license change that I think was part, or let's say part of the agreement to happen beforehand. Uh, let's call it that way. 10:33 So I think that was related. Uh, and that was a bit of a, you know, movement, it caused OpenTofu to appear. Uh, so I'm not sure whether or not like now there's going to be changes. 10:44 Probably there will be, uh, but we'll have to expect and what's going on because Terraform is a very core element into infrastructure as code, and it would change anything because providers have spent a lot of time making, uh, resources, modules. 11:00 So if you go to the code of Azure or AWS modules and you see like all the business logic there, [chuckles] I don't know, I think there are 2,000 modules from AWS on, or resources alone, which is like a lot of engineering effort. 11:17 Yeah. Do, do you know how, uh, what the kind of market penetration is of like HashiCorp versus the native, uh, the native tools, the cloud formations and others? Uh, I don't think I have the numbers, but for... 11:29 I think it's, I don't know, like everyone is doing pr- uh, Terraform. Yeah. Unless you are, uh, let's say super into one provider, uh, like for example, CloudFormation. 11:42 Uh, if you have more than one, for sure you are do- using either or Terraform or Pulumi, I think, or OpenTofu. No. Uh, I'm not sure. 11:49 I would like to see what's the penetration of the market of OpenTofu and Pulumi versus, uh, Terraform now. I would like to see if that trend has changed. 11:58 That's a, that's a very interesting question and I will try to, to find that info. Yeah. That'd be worth, worth digging into. 12:04 But nonetheless, the challenge remains in that, you know, everybody is kind of focused on-Particularly when we think about automating those actions, taking action on the result itself, and really that's, you know, a little bit, um, misinformed in that, you know, most, most people have got, you know, programmatic code pipelines, and it's just gonna replace the change that you made, um, you know- Yeah... 12:25 with something in a script. So, yeah. So, and, and so coming from, from the take action, uh, thing, we were... 12:33 The other day we were making a, a webinar, um, about FinOps in the DevOps cycle, so very related to what we're talking here today. And the, the topic come about incentives, you know. 12:46 Because, uh, engineers, uh, may or may not have, you know, have some features or they have to, you know, have the application working, have the, the reliability, the security, et cetera, et cetera. 13:00 But they may or may not have, uh, the cost part, uh, into, into account if it's not super, let's say, relevant or there are not big applications. 13:09 But what was the discussion point of, of that day was that, okay, maybe if we put incentive programs on the end users, we will get better, uh, information. 13:22 And so in your case, what do you think an incentive program for, you know, uh, improving business value metrics or improving, uh, the cost relations would affect the end users engineers? 13:34 How do you think that would play around? Yeah. What, what a great question. I mean, it's really challenging. In fact, measuring the outcome of usage reduction in itself is challenging, right? 13:45 So, um, you know, rate reduction savings, easy to understand what you might save with a reservation or a savings plan or a committed use discount. 13:54 But when you produce a recommendation that says, "Hey, rightsize this or delete this or terminate whatever," how do you know A, that the action is taken, B, that it's the action that you recommended and, and C, actually what the material value of it was, right? 14:08 So incentivization i- is about, I think, uh, well, there's several aspects to it. 14:13 If you're gonna do it after the fact, right, and you're not going to build cost into the, um, criteria that an engineer is considering, which one would argue is gonna be the most successful way to do it because, you know, they should be doing that at the point of design. 14:29 If you're looking at it after the fact, it's about efficiency metrics, right? And, you know, let's take a simple one, which would be recommendations as a percentage of the overall spend of the application, right? 14:39 A, a quite a blunt metric. Um, but, but I think, you know, those things are extremely difficult to drive, you know, through the business, um, you know, i- in... 14:51 compared to, to doing it first and doing it right and have an ex-executive level kind of decision that cost is a, a factor of consideration because they're up against competing priorities of the business. 15:03 So, so anybody we're pushing into, you know, a Jira backlog to prioritize, is it a case, case of, you know, okay, I'm incentivized to save cost on this, but actually the business needs me to build, you know, a new feature or a new application or whatever it is. 15:18 And so those things can be very hard to get relative prioritization from the business. 15:24 Um, a- a- and therefore, the incentives would have to be pretty strong and maybe in opposition to other outcomes that, that you're looking to achieve. Um, so I, I don't think I know the solution. 15:34 I know that it's a complex problem and o- one that we, we spend a lot of time kinda, you know, chewing over with customers around what KPIs are gonna deliver the right outcomes. 15:43 Um, but it again goes back to the shift left, right? Yeah. 15:45 If we can get that baked in, it's, you know, alongside the functional requirements, um, then we're more likely to be successful at the point of build, uh, and design rather than the, you know, after the fact. Yeah. Yeah. 15:58 Definitely the, the incentive is a key part, you know, because I, always when we talk about FinOps and DevOps, [chuckles] 16:07 I first think, you know, if I was doing, uh, my job, you don't want to become someone external, come and tell you what to do. [chuckles] So, so I think the problem starts in there and, and, and incentives are, are... 16:21 I think it's a must in, in, in, in order to, you know, make them engage-- people to engage people. So it must be on the, whether it's, um, 16:31 a yearly, you know, when you, you do an overall, uh, you know, um, uh, an overall, um, uh, I forgot the word. An overall- Performance review. Yeah... performance review. Exactly. 16:44 The performance review of the person, it should be there, right? Uh, that could be- Yeah... a, a, a good metric KPI for... 16:51 I- if you can bake it in, but it's also a retrospective thing then and, and against comp-- you know, other competing priorities, isn't it? 16:58 So it becomes, it becomes difficult to achieve both of those outcomes potentially and which one, you know, delivers more, more value for the business. Yeah. But yeah, i- interesting challenge. 17:09 I think what, what you said is, is pretty interesting, like the reactive v- versus the proactive, uh, approach. Let's, uh, I think now mostly everyone is on the reactive approach. Like, okay, we're spending a lot. 17:20 We already have the architecture design. Everything is designed. Uh, so the main issue or the main, you know, point of, of conflict that was, uh, said with the incentive programs is that, okay, if we reduce... 17:33 Let's say we, uh, let's put it the case that we reduce and maintain the same value. 17:37 So if we maintain the same value and reduce the cost, then how we can prevent, you know, uh, because in companies th- this tends to happen. Like you reduce the cost, then your budget for next year is lower. 17:49 [chuckles] So the idea is that, uh, that's very problematic and you need to prevent like how do you, uh, tell, you know, the executives or the people that are above that, that, yeah, we have reduced because we made a re-architecture, we make an effort, and we need now with this budget, uh, the application was good. 18:06 So the only thing that we need is instead of reducing our budget, keep the budget and, you know, uh, have more people or have more feature or have more tools. How do you translate that-... to the executive above you? 18:19 How do you get executive buy-in to, not to cut your budget when you have done FinOps, uh, let's say savings in th- in this case? Yeah. It reminds me actually of a great incentive that I heard. 18:32 I can't remember where I, where I picked this one up from, but, um, there was one organization that the incentive for engineers to reduce cost was that that cost saving could be used to, uh, bring in more engineers. 18:46 Okay? [chuckles] And so the, the savings were effectively retained and invested in growing the, the team. Um, and of course then your velocity increases and the business value ultimately increases as well. 18:59 So I think, you know, it, it's twofold. Using that as an incentive to [chuckles] you know, bring more, bring more engineers in, grow your team, uh, you know, share the, share the workload. 19:09 But also talking at an executive level about not driving cost out, but driving value in, right? 19:15 So if I can save money here, but I can make the team go faster and deliver your business outcomes, then it's a win-win for, for all involved. 19:23 So I think it's, it's again, not just thinking about it, you know, driving cost out, but actually driving value in and, and growing your business and, and using FinOps to make money, not necessarily to save money. 19:35 Another option would be invest in innovation. 19:37 So technical people like to, you know, uh, uh, like technology, like to test new things, learn new things, and, and that can be also a very good incentive, uh, that I also see- Yeah... a very valuable one. Mm. 19:53 Put, put the money in, I don't know, an ML pot or an AI pot that- Yeah. [laughs]... you know, can go like automated outcomes or, or whatever it might be. But, um, reinvest I think is, is the key there as an incentive. 20:03 Yeah. Yeah, we maintain the value and we try to improve the margins while trying to, you know, reallocate the, the, the input to a different, let's say, area that can bring more value in the future. 20:16 That's super, super interesting. So yeah, I mean, we've been talking about, you know, a lot of, uh, you know, advices and goes about engineers, but what we... Maybe the audience want to know more about, like you, no? 20:26 Because I think people are super, uh, you know, interested and they have doubts about how, you know, they become FinOps, uh, either engineers or leads, et cetera. 20:37 So, uh, for someone that is, you know, trying to transition, I, I, I have a lot of question about transitions about to, to FinOps. 20:44 So, uh, tell us about, you know, your story and how it's been your, your road till, till this point. Oh, that's a great question. [laughs] Interesting one. So, uh, uh, IT background all my life. 20:56 Um, you know, even as a kid, I knew I wanted to do computing despite my, um, uh, inability to do maths very well. So [laughs] I persisted, uh, I persisted at that. 21:05 But, um, yeah, spent, spent a lifetime in IT, originally in kind of desktop, um, you know, and networking, uh, and then, you know, into a kind of change management and ITEL space. 21:17 I spent time in the CRM industry with doing Siebel and, and that was my kind of first exposure to SaaS and other applications. 21:25 Um, but the journey really to FinOps was as I be- you know, started to lean into the cloud architect role. Um, so I was a solution architect in the, um, insurance tech space. 21:37 Uh, originally on-premise, the insurance industry were typically kind of a little bit laggards in, in [laughs] kind of modernization and adoption of cloud. 21:46 Um, but yeah, that was a great opportunity for me to sort of learn, you know, initially on, on AWS, um, you know, a, a, a bit about cloud and get, get educated. 21:55 And then I was involved in a data center, um, you know, migration program. 21:59 So, um, that, that was really informative for me, you know, and of course, a lot of that was driven by cost-based decisions, the cost of a data center, the cost of refreshing a data center, uh, you know, and modernization was, um, you know, one of the reasons for, for the, the adoption of cloud amongst, uh, others. 22:19 Um, and at that point actually, um, you know, I, I changed roles and went, uh, uh, contracting as a consultant for a, a UK-based, um, uh, MSP, um, a re-reseller of cloud. Uh, and they had a practice for FinOps. 22:35 It wasn't called FinOps at the time, it was cloud financial management, and they had a partnership with, you know, a, a well-known vendor of, of FinOps tooling. 22:43 Um, but, uh, hadn't been too successful in kind of getting leverage and getting the traction there. So I went and, and, and worked with them on all things FinOps. 22:51 Uh, you know, the go-to-market, the consultancy, the delivery, [chuckles] you know, the, the outcomes and value realization. 22:57 So it was really a kind of a, a baptism of fire, I guess, at the time because it wasn't called FinOps and I didn't know really what it was at the, at the time, but, um, you know, was, was super exciting. 23:08 Um, and then from there I've been in the vendor space since, um, which is, you know, looking at it from, from both sides of the fence. 23:15 So, so that was my journey, but I come across people that have come in from, you know, all different angles, um, you know, consultancy of course in, in the IBMs of the world. 23:25 Uh, but, uh, you know, Linux engineers and, uh, finance perso- you know, personas and people that have come in, you know, and, and have been given control of FinOps from a, an ITAM or a license management background as well. 23:37 So, um, I don't think that the background necessarily, other than it being, you know, having a little bit of a, an IT background is, is necessarily important. 23:46 Um, but you know, my keys, I guess, to success would be that, you know, the willingness to learn, uh, get hands-on, get involved. I mean, there's just so much learning. Every day is a learning day, [chuckles] you know. 23:58 And, uh, so embracing that and enjoying that, uh, you know, the passion for FinOps comes from a passion for, from learning things really, and it's such a, a deep and broad, uh, you know, area that there, there's always something new to, to embrace.That's, that's quite an interesting story. 24:14 I think that, uh, for whatever reason, you know, all the finance, insurance perspective come to, uh, get related to, to FinOps after all [chuckles], like, it's like kind of the source of all the, of all the practice plus, you know, all the freelance and consulting. 24:29 I think it, uh, all these, you know, uh, consulting/tooling side has a very powerful role about making, I don't know, what you said, you know, the baptisms of fire. 24:39 Like, uh, I don't know, if you are a freelance and then you get to... 24:42 You have to make a cost reduction because you are a cloud architect or whatsoever, then, uh, you start, you know, learning a lot of things, and that's what happened, for example, to me, that I was helping someone, uh, on their, on their cloud architecture, and there was some objective to reduce the cost. 24:57 From there, I discovered like, okay, cloud cost reduction, and then I s- uh, searched about the keyword FinOps, and then I researched everything and, you know, we are here now. 25:06 Uh, so it's, it's, uh, super interesting to see, like, how this baptism of fire happens. So in nowadays, 25:14 for someone that is, you know, maybe an engineer that has some, I don't know, inclination to finance or likes numbers or, I don't know, uh, all these FinOps-related practice, what would be your advice or your, uh, considerations now that you have experience on the field to become someone that is, uh, you know, FinOps-oriented or a FinOps engineer? 25:36 What do you think are the, the steps to be able to become a good FinOps, uh, practitioner from the IT perspective? Yeah. I mean, I don't think it's a difficult transition. 25:47 Most engineers that I've met, uh, you know, are very interested in efficiency generally, right? Yep. So, um, you know, uh, it, it's just another metric that one would consider to, to be successful. 25:58 If I can make it run, you know, efficiently, then I'm, I'm typically reducing, you know, the cost. So, um, yeah, obviously- Yeah... 26:06 you, you need to be interested and want to deliver the best outcomes against the requirements that you have. 26:12 Um, but an interest, you know, whether it's from a finance perspective in the levers that you can pull, um, you know, an interest in, in the business side of it in terms of, you know, how an organization is committing to use cloud, what the cloud strategy is, and, and those kind of things are important because, you know, commitments, RI savings plans, all of those kind of financial instruments, if you will, you know, become part of the puzzle and, and there's a lot of depth, uh, and complexity in there for, for kind of reaching out to it. 26:41 But, you know, start small. Go and go read the docs, look at, you know, the finops.org, get involved, look at the KPIs. 26:49 Um, you know, the, the fact that it's effectively, you know, o-open source at the end of the day and, and open for p-people to participate and share their thoughts, um, I think resonates well with the engineering community as well. 27:02 Um, you know, so everybody's welcome to, to participate. Um, so I would just see it, for me, as kind of a natural career expansion. You know, there's another requirement that I need to consider in the build. 27:13 There's a whole framework that gives me a bit of structure about how to think about that. There's a massive community now, of course, of people, you know, like-minded that, that, uh, are willing to support. 27:23 And I think now the time is, is right to, you know, to get involved, particularly with the kind of shift left momentum that we're, we're seeing, um, from the foundation and the community, um, because those engineers are, are gonna be the ones that are needing to, to think about that and do that early on in, in the design life cycle. 27:40 So now's the time to go [chuckles] and get involved, I would say. Um, but, you know, start small, uh, learn, learn lots, and, and, and contribute a-as you learn. 27:50 Uh, and that's how, how the, the framework and the foundation ultimately have been successful in, in, in the rapid growth that we've seen, uh, you know, in terms of membership and, and participation. Yeah. Yeah, I agree. 28:02 And also I think the, the target that, you know, it's super business impactful, um, I think that also contributed to, to the expansion of, of the whole ecosystem plus, you know, all the community work that everyone is doing. 28:15 I think it, it's, it's very good. And do you... 28:18 So now, so continuing on that, like, for example now, uh, this, this per-person or these people have become FinOps engineers, or they have like a clear, let's say, role now they attach to that, or they have like partially attached to that. 28:30 What are your considerations in terms of the collaboration or the communication perspective? 28:35 Because we've seen that this role is super collaborative, super oriented to communication because you have to deal with the finance, uh, perspective, with the executive perspective a lot to get buy-in of the initiative. 28:47 So what are your, uh, indications for, for these people in terms of like how to communicate, how to learn, how to get buy-in from, from the executive fancy to, to progress the, the practice? Yeah. 29:01 It, it becomes a question of organizational wide change, and I think anybody that's done the kind of FinOps Professional course, it's, uh, you know, almost less about going deeper on the, the FinOps aspects of it and the actual optimization, you know, side of things, and it's more around the organizational change, the stakeholder management, uh, the communication, common taxonomy, education. 29:23 You know, tho-those that I've seen being, um, successful, a-and a few organizations come to mind, but have fantastic training programs, um, mandating engineers go and get FinOps certified for a, for a start, but also, um, you know, educating from an executive level all the way down, uh, you know, around FinOps, around the, the why and, and around the value proposition o-of it ultimately. 29:49 Um, but the, the one thing for me is, is the common language, the, the common taxonomy, right? So if I go to an engineer and I'm talking about reservations and commitments and NFUs, right? 30:00 [chuckles] And they don't know what I'm talking about, we're off to a bad start, and, and similarly, you know, I should learn a little bit about, you know, the engineering disciplines and, and understand some of the challenges and competing requirements that, that an engineer needs to consider on a daily basis as well. 30:14 So, um, getting people in a room, you know, getting onto the same page, uh, whatever that might take in terms, in terms of education. 30:23 Um, of course an executive mandate is gonna help with that, but doesn't have to, right? Cloud center of excellence or whoever, whoever's gonna kind of lead that. 30:31 Uh, and just being mindful, I guess at the end of the day, everybody's, uh, you know, uh, actually focused on the same outcome, which is driving business value. We're just coming at it from sl-slightly different angles. 30:41 Um, so common goals, common taxonomy, uh, and an open mind I think are, are keys to success there.Yeah, I think you have, you have highlighted, uh, very, very good things. 30:52 And also the, the language part is crucial, I think, for-- because especially in this, in this practice which has a lot of terminology and very specific, you know, terms, 31:03 I think being able to understand everything, being able to digest everything. 31:07 Since it also impacts like a lot of areas, uh, we need like a single point of, of trust to, to be able to, you know, to communicate and, and learn. Yeah. That's another key point, isn't it? 31:20 The, the broad range of stakeholders impacted by cloud, you know, should- shouldn't be underestimated. 31:26 And so when I'm talking about having the right people around the table, it's likely finance, it's likely engineering, it's likely, uh, you know, the, the architects, it's likely security people, right? 31:37 I mean, the, the impact... And the business themselves, uh, ultimately that are looking for the outcomes. 31:43 Um, so it- it's almost one of the bigger kind of change management, stakeholder manager communication projects that you might undertake to bring together such a broad community of people and to get them up to the same level so that they can communi- comm- communicate efficiently. 31:59 Um, so yeah, it, it is an interesting challenge. It was one that we undertook in, in the kind of, uh, fintech and insurance space that, that I was operating in initially as we looked at the early adoption of cloud. 32:10 Uh, but, but always a challenge, and we see organizations, of course, [chuckles] at all sorts of different levels of maturity, uh, as they go on that journey. Yeah. 32:18 I think it's, it's built on the, on the cloud journey, especially now it's expanding to the whole, uh, let's say on-prem hybrid cloud everything. 32:27 Uh, but it's going to be like an ongoing practice, and as you've mentioned, it's, it's a organizational wide impact to, to the others. Um, so yeah, uh, I think we covered a lot of, uh, interesting topics. 32:39 I think engineers and executives and finance will have a lot of information here to, to take action. So Jeremy, uh, thanks a lot for, for giving all those insights. It's been a pleasure to, to have you here today, man. 32:53 Oh, likewise. Thank you both, Victor, uh, Damian, for, for again, the opportunity to come and talk to you. 32:58 And, uh, I will keep listening and, uh, look forward to hearing more from, uh, more guests as, as you, uh, continue with the pod- podcast here. So wishing you every success. Yeah. Thanks. Thanks a lot, Jeremy. 33:09 It's been a pleasure. Thank you very much. See you in the next episode. Bye bye. Will do. Bye-bye. [outro jingle]