Transcript 0:00 Welcome, everyone, to a new episode of the FinOps Weekly Podcast, and today we have a FinOps legend, uh, with us. We have Ben Demora. How are you, Ben? A legend, wow. I wasn't expecting that. [laughs] Yeah, I'm good. 0:11 I'm all right, man. Good to, good to, good to catch up. Yeah, good to, good to catch up. Uh, we were discussing, like, how to present Ben because, you know, he has a lot of experience. 0:20 He have, uh, seen it of, of, you know, all the, all colors, as we say here in Spain, um, in, in FinOps, and we are going to talk about multiple, multiple topics, especially regarding, uh, the data and making FinOps actionable these days. 0:34 So, you know, I'm going to start with a, maybe a tough question that, you know, you have mentioned. We were discussing, like, uh, data, uh, in FinOps is not the solution that, you know, you think it is. 0:45 So maybe you can clarify the audience what do you mean by that and, you know, where you have seen this fail in, in FinOps. Yeah. So a good way to think about data in FinOps is the foundations of a building, okay? Mm. 1:00 If your foundations are poor, your building will not stand l- for very long. It will not look very good. It will probably fall apart, right? But if you pour the best foundations in the world and stop there, 1:15 you don't have a building. You've just got some flat, very solid, flat ground. It's great. You can go do stuff with it, but there's nothing standing on it yet, right? So you need data. 1:26 Data is critical, and it must be accurate, and trustworthy, and clear, and current, as per the principle of FinOps, right? It needs to be accessible, timely, and accurate, and relevant. 1:37 Um, but that's not enough, and a lot of businesses, a lot of people think that, that it is enough to make it happen. 1:43 You show somebody the world that they need to see, and suddenly they will somehow just take action and do the right things, right? Um, but actually, it's not the case. 1:55 What you need is context, and you need understanding, and you need sort of the reasons behind the data which often isn't there, right? You're never, ever in a million years gonna get context from your cloud bill. 2:07 It's not gonna happen, right? Yeah. Um, you need the business context of why things are where they are. Maybe things aren't optimal, but maybe there's a reason for that that you don't know, right? 2:18 Um, maybe focusing on optimizing something or trying to, trying to reduce waste on something actually might hurt you in the short term at that particular point in time. 2:27 So understanding the context behind the data is really important, and then beyond that, understanding, like, okay, who owns this data? What does good look like? Like, what does bad look like? 2:40 If I see my data, what is an acceptable threshold for what this should be looking like? Because, um, numbers on their own don't really... They tell some of the story, but you need a lot more than that. Yeah. 2:52 So it kind of... That's what I mean. I think, I think people over-rotate. I mean, okay, maybe they're not over-rotate 'cause data chall- data is a challenging f- space, right? It's hard to get right. 3:02 But a lot of people spend so much focus on that, that they forget what it's for, and they don't start to actually have the context and the, the, the sort of bigger business conversation around it. Yeah. No, that's true. 3:15 That, that's something that, you know, we of course discuss with, um, with Frank when, when we had this, uh, the podcast with, with him- Mm... 3:22 about, you know, the context, the important of the, of the business strategy and how it makes sense. Um, but, you know, how- Now, that's a FinOps legend right there. Yeah, yeah. That's right. 3:31 That's also another FinOps legend. That's... He des- he deserves that title more than I do. [laughs] I don't recall- Way more... 3:37 how, how I present him, but I [laughs] definitely, um, I don't recall, but you- The Red Gloves of FinOps. Yeah. It's... He's a legend. But, you know, I wanted to also, um... 3:48 So, uh, as mentioned, we discussed about it, like numbers on their own don't mean anything. It could be, you know- Yeah... apples or it could be- Yeah... you know, cloud cost, whatever. Um- Yeah... 3:56 but, and they need to, to build a business context. And, you know, apart from the business context, what do you think it also helps, you know, solve the problem in FinOps? Do you think there is- Mm... 4:06 another missing pint, missing piece about, uh, FinOps that we are seeing apart from, from this context? Yeah. So, um, as I g- kinda go back to my rubbish analogy about it being a, being foundations for building. 4:19 Um, what's missing is, is the organizational structure, right, a lot of the time, and I don't mean a FinOps team. That's kind of a solved thing now. 4:28 We know what a FinOps team looks like, what it should be doing, all that kind of stuff. I mean the wider structure. I mean, how do we create ownership, and what does ownership mean, right? 4:41 'Cause you need to provide data for ownership, but you also need to provide autonomy, and you need to provide engagement and like, you know, what, what's in it for them? Why do they care, right? 4:50 Um, and often people outside of finance or whatever don't really care about saving money, right? Um, so what do they care about? Figure out how to, how to sort of attach to that. So what solves the problem 5:05 is attaching not just the business context, but the human context as well, right? So how do you, how do you get people engaged? And there'll be different things that can be used for that conversation, right? 5:15 Could be, uh, do you want a bonus, right? [laughs] Here's, here's a KPI. Hit this KPI, and you, you get, I don't know, a steak dinner or something, whatever it is. Um, so, like, how do you incentivize things? 5:31 How do you create clarity and ownership around these things? How do you give people the safety to understand the information and go, "Hey, do you know what? 5:40 I know the context of this engineering environment, and I know that I can actually do this thing over here," right? Uh, how do you give them the time in their sprint for that and prioritize that kind of work as well? 5:51 So State, FinOps data that we saw recently, um, kind of reiterates that and shows that, um, autonomy is still a challenge. Executive sponsorship is still a challenge. 6:02 Um, creating the space in the project plans for not just building and deploying and shipping, butYou know, um, actually improving the efficiency and, and recognizing the value of it, right? So what's the missing piece? 6:17 Context and ownership, and just supporting the understanding that we're trying to drive value, not save money. Yeah. The different things. That's for... No, well, that's the... 6:28 I think that's one of the, of the basic points, and also, um, you know, try to give people, like, guidelines so, so, okay, like... 6:35 So I, I remember when I started in FinOps, like, one of the topics was, like, you know, engineering is not doing anything, blah, blah, blah, blah. Yeah. And I was like, "What are the guidelines that they have?" 6:45 Like, they, they have help. They have- Yeah... the, what they need to do. Is this a KPI that you're measuring? Uh- Yeah... are you doing something for, uh, incentivizing that? Exactly. If the answer is no [laughs] 6:59 And, and also, right, like, before I worked in FinOps, I was an engineer. I was a data center engineer for five years, and prior to that, like, operating systems engineering for Solaris and Linux and everything else. 7:08 And I've, I've run teams, and I've not known, and I've not known a single engineering team in my entire career that isn't up to its eyeballs in workload, right? 7:18 Like, every engineering team I've ever worked with has been like, "Okay, your capacity is this. You're gonna do this," right? Um, so it's not that they're not taking action. 7:31 It's like, okay, well, but what are we, what are we giving them to do? And, and how are we ranking those tasks in order of priority? What's the backlog look like? 7:40 Um, 'cause I guarantee you that if you balance that well, and you balance what the engineer t- in engineering groups and the other departments, procurement, product, everybody else, right? 7:51 If you balance out what their expectations are, and you say, "Right, I want you to build everything yesterday," or the, "I want you to build it, but I want you to build it sensibly and conscientiously. 8:01 I want you to do it with an eye to GreenOps. I want you to build it to an eye to, with an eye to maximizing flexibility and elasticity." It depends on what people are prioritized to do is what they will do. 8:14 'Cause otherwise, if they don't do what they're told, they don't have a job, right? Yeah. That's how that works. So- [laughs]... you know, they're gonna do what they're asked. So what are we asking them to do? Yeah. 8:24 That's important. Yeah, definitely. 8:26 And, you know, you, you mentioned the, before that, uh, you know, you need to make, uh, FinOps relevant for, for someone that is, you know, their job is not saving money, and we're talking about engineers- Yeah... 8:36 but there are other people involved- Yeah... such as product and... So how do we make it, apart from, you know, a steak dinner that, that you mentioned? Uh, how we, how we make it work for them? I mean, I, I'm, I'm easy. 8:47 I'll do anything for a steak dinner. Um... [laughs] Me too. Yeah. Um, yeah, right. So anyway, um, how do you make it relevant? So that c- that, that comes down to what, what are the, what does their world look like? 9:00 What are they trying to achieve in their profession, in their job, right? 9:05 Um, because FinOps, one of the in- one of the reasons I find this such an interesting and fascinating discipline is that it's so broad, and it sort of reaches into so many different specializations. You learn so much. 9:18 I've been doing this now for, what? Seven, nearly eight years really, if you d- count the time I was doing this at Oracle. Um, and I'm still learning things. 9:28 I'm still learning things about different parts of the organization, the way they operate, the way they, the, what they do, and what they need. So find out what they want. Find out what they want to achieve. 9:37 Don't make it about FinOps. Make it about them. What are you trying to get done? What's difficult in your world, right? 9:44 W- what did you wish you could know about this really crazy, mad thing called cloud that nobody really understands except the engineers? They don't understand it either a lot of the time, really. 9:55 [laughs] Let's be honest. Um, nobody really get... [laughs] It reaches a level of complexity, it just melts the brain. But, like, what are, what are they, what are they trying to achieve, and what would they... 10:06 What would help them? Yeah. Right? You always need to- What insights are useful to them? You always need to be, like, em- I think it's emphatic in English. Like, you need to be- Yeah... 10:15 po- position yourself in the- Emphatic, I think is emphatic. Emphatic. Okay. Yeah. My native English, uh, is not there. Um, but- Neither is mine. 10:23 [laughs] So, but, you know, you need to make it, you know, think about the other person and try to play around, um- Yeah... you know, what they care about. 10:30 Because it's like if you are always talking about, you know, what you want, it's like, that's fine. But the other person will say, yeah, that's not what they want. That's what you want to. Yeah. 10:37 Why I have to do it, right? It's the so what factor, right? Yeah. What's in it for me? What do I care? You know? Yeah. 10:42 Um, I think that's really import- that's a really important thing to be able to dig into is, like, um, whenever I'm speaking to somebody and I'm trying to get FinOps in place and, like, helping people to develop the practice and establish the connections, I don't start by telling them what I need them to do. 10:58 In fact, usually I don't tell them what I need them, need them to do at all. Um, I usually begin by saying, "Okay, well, what does your world look like? What do you, what do you struggle with every day? 11:09 Um, and what sorts of things are you busy doing, and what would make that easier?" Mm-hmm. That's it. Simple conversation, right? And if it's... And, and it, that sort of s- s- begins a whole load of... 11:25 They actually do then, then they care. They're like, they, then they'll spend half an hour explaining to you what their day job is like, what they do, what winds them up. 11:33 And if you get onto something that really winds them up, probably have a decent cup of coffee 'cause they'll be there a while. But, you know, like, find out, 11:41 find out f- from the, from people what it is that they wish they had. Because, 11:47 again, going back to the fact that FinOps are so interconnected and so broad, chances are what they wish they had exists somewhere else- Yeah... 11:54 in the business, and is actually something that the found- the FinOps team can conduit as part of the improved context that we work with, that we flow through, uh, and that we help them to develop. 12:07 So-I'll give you a for instance, right? Um, speaking to a finance team and they're like, "Man, I wish I could figure out why the bill is so completely unpredictable every single month. 12:18 I, I, I go to the engineering teams and I ask them what they're gonna spend and they don't know, or I ask them what they're gonna go do and they're like, 'Hey, here's a really complicated product plan or project plan that I don't understand,' 'cause it includes really useful phrases like Kinesis Firehose, right?" 12:34 [chuckles] "An elastic beanstalk. I'm a finance person, I don't know what that means. Help me out here," right? Um- Yeah... 12:41 and you can sit down and go, "Okay, well, look, this service is used for this and it usually behaves like this if it's working properly." 12:50 So based upon that context, and you can have this conversation, you don't need to become an... You don't need to turn them into an engineer, but, like, find out what it is that drives them crazy. Um, right? 13:00 Engineering teams, they're like, "We've got so much work to do, and we can't... We're being told save money." Like, what money, right? 13:08 You want me to do all of this stuff and build all of these things yesterday 'cause we've got aggressive business plans, we have got a competitive marketplace for our product, and we have to get our... We have to ship. 13:18 We have to ship it. That's the cri- you know, um, successful businesses ship. That's the way it goes. So I've got all this drive and demand from the organization to do stuff, and now you're saying to me save money, 13:31 um, or reduce costs. I'm like, "Okay, great, but, like, how? Where?" Uh, and also you're telling me to save costs. This thing is idle for a reason. Don't touch it. It's part of a SAP cluster or it is, right- Yeah... 13:45 an active-passive failover architecture. Whatever, yeah? So you need to try to help these people to, to understand how the wider picture can help, right? 13:59 Um, because historically people have done, just basically sort of done their job with their blinkers on. They've sort of kind of existed within their world, right? 14:08 And done a lot of belly button staring and just basically done their job, and now, um, cloud kind of forces you to step out of that- Mm... because of how quickly things evolve and change. 14:21 You, you can't hide behind the delay of six months to get a server and another two months to get it racked if you're working with somebody like I used to be at the data center. I shouldn't have said that. But [laughs] 14:32 um, but, like, you know, it's like it... 14:35 If you're working with something that happens at the speed of cloud, at the speed of decision-making, um, which is a phrase I've st- stolen from somebody else who used it recently, um, 14:49 you can't hide behind slow cycles anymore, and you have to be able to collaborate and, and in, and, and work together. 14:56 It's, it's the oldest principle in the foundation is, like, you know, you have to, you have to collaborate. It's one of the oldest principles. So yeah. 15:03 How do you, how do you get people to go beyond their, their job and care? Well, make... Don't get them to go beyond their job. 15:11 Find out about what their job needs, what they need, what they're struggling with as a result of the emergence of this, of this thing, and not, not really emergence. 15:19 This, this macroscopic growth of cloud, which is causing an enormous amount of friction wherever it starts to grow. That seems to be the one universal truth, actually. 15:29 It does seem to cause friction wherever it starts to grow exponentially. In any organization, it makes things harder. Yeah. And I think the reason it makes things harder is because 15:38 people don't talk to each other enough beyond the boundaries of their disciplines. Yeah. And they don't listen, they don't understand each other's situation. 15:45 So the FinOps team has a mandate unlike any other to go everywhere and ask these questions and understand what makes things hard now, what is difficult. And, you know, going to somebody saying, "I need X, Y, Z from you. 16:01 Give it to me in two weeks," forget that. Then you're not gonna get it, right? Espe- especially if you are not the, the ones measuring their performance or if they are not the ones- Yeah. You're not their boss. Yeah. 16:11 You're not their pal. You are not their boss, um, they say, "Yeah. Yeah. Why?" Be like, "Yeah." So in, in that, like, uh, so, you know, we discuss a lot about the, you know, being able to talk. 16:22 You need to talk to each other. I think that happens especially because it grows bigger. Normally means that the company's bigger and you know that communication sometimes in- Yeah... 16:30 large corporates, uh, it's difficult. Like, it's not that accessible. Knowledge sharing, all of that is fairly- Yeah... fairly difficult, right? 16:39 And, you know, communicating the business strategy and everyone is aligned on a, I don't know, a 200,000 people company [chuckles] is not easy, right? You need to align a lot of people. Yeah. Yeah. 16:53 Um, and, and business strategy can sometimes be a bit of a problem, too, right? FinOps is, FinOps is an interesting one because it operates both at the very, very detailed level, right? 17:05 We're talking about in- individual line items in the cloud bill- Yeah... single VMs, right? Single idle disks, all this kind of thing. Super, super detailed. Second-by-second, and events, and that kind of thing. 17:17 But it also operates at, at the board level. It operates at the, uh, the stakeholder, the, the shareholder level, the, the, the public company filing level, right? 17:27 It affects everything all the way up to the, the direction of the business. 17:33 If your organization is a heavily cloud aligned or heavily linked to cloud spending, and you der- that's where you derive your value, then your strategy should not only be informed by FinOps, but it should be shaped by it, right? 17:48 You should be shaping your strategy as a result of understanding what the heat map of spend versus value looks like, right? What areas of your cloud are earning you money? What areas are wasting you money? 18:03 What areas are necessary in order for your organization to exist, and therefore indirectly earning you money, right? Um, 18:09 but understanding that at a strategic level and also understanding, like, if you make-Mandates, business mandates about what your product is going to do, what your service is going to do, and you don't do that with an awareness of the way that cloud behaves or the way that your business interacts with itself around that, those decisions, 18:32 um, that strategy's going to struggle. Um, and I'll give you a for instance, right? Let's say, for example, um, your product is super bursty, super, super, like, you know- Yeah... 18:46 very, very h- high load and then nothing, then high load, and the, and the, the scale is very rapid. Mm-hmm. Right? 18:54 Very, very hard to architect something that can elastically scale that fast, um, unless you're starting to use something like serverless, yeah? Um, but then... So, okay, maybe, maybe you recognize that. 19:09 Maybe you understand that actually that's your strategy. You're going to say, "Right, we only use serverless here. We don't use any static resource. We only spin it up when we need it. Everything is serverless." 19:20 Cool, right? And then you come out with a new product, and your new product isn't bursty. Your new product is like a huge batch process work, right? 19:31 Um, and your new product actually behaves in a very, very different way, but the strategy is cloud native. It's all, like, you know, serverless and that sort of thing. So, fun fact for you. 19:44 If you were to take, I think this is still correct, if you were to take a, an AWS Lambda function with a certain amount of resource- Mm-hmm... 19:51 and you were to take an EC2 instance with roughly the same amount of resource available to it, and you run them full tilt 100% nonstop, full parallel, the Lambda function will cost you 16 times more money. 20:06 That's a lot [chuckles] of, uh- I-... of difference. Yeah. [chuckles] You know what I mean, so, like, that's, that's a dent, you know? It's not a small thing. So, 20:17 strategy needs to continually listen to the heartbeat of, of what FinOps is saying and what FinOps is giving you in terms of, like, look, this is what we're doing. This is what we could be doing. 20:30 Uh, are we still going in the right direction, right? Um, and I think that strategy historically has been a very long-term outlooky kind of thing, um, and it should probably not be because, um, 20:48 those sort of slow cycles, the long burn cycles of strategic direction, um, don't really vibe very well with, um, the rapid changing nature of, of not only cloud, but also everything associated with it, the, the flexing customer demand, all that kind of stuff. 21:04 So, um, strategy really should be really shaped by what FinOps is identifying, finding out, not just in terms of the way that the cloud providers are changing and evolving. 21:18 Um, also, I'm gonna, I'm gonna in- invoke the, the dreaded phrase, AI, or a- acronym, whatever. Uh, we, we managed to make it 20 minutes into this conversation before anybody mentioned that. Yeah. 21:29 And it's my fault, and I brought it up, and I hate talking about it. But, like, um, everybody's AI strategy right now seems to be turn it all on and see what it does, right? 21:39 Um, and- And they spend a lot of money in the way. [chuckles] And spend a lot of money, right? 21:45 And the, there just doesn't seem to be a whole lot of feedback going into, "Hey, so you know how we turned all this stuff on and people are using it like crazy, and they don't really know how to write prompts, so they're doing a really bad job of it and burning through loads of tokens, and everything's going terribly wrong, and we've chosen the wrong models, and they're really inaccurate and that doesn't help us?" 22:03 Whatever, right? Um, yeah. Being able to sort of react and flex to that and understand the, the changing and evolve. People are making three-year, five-year commitments to AI providers already. Yeah. 22:18 And they've been using the providers for like six months, or less, right? It's, blows my mind. Anyway- Yeah. 22:26 It's, it's- Um, the business strategy needs to sort of really be much more in step with what, what the cloud FinOps team is, is telling them. Um, and often that isn't the case at the moment. A lot of the time I'm seeing, 22:40 um, FinOps teams kind of at the level of the engineering department, right? 22:47 And they're, they're kind of like the, the, the, the, they're quite low down in the, in, in the order of things, and their voices are just not reaching the altitudes they need to reach in some cases. When they do, 22:59 things are really good. 23:00 When they actually reach the altitudes they need to reach, and the, the, not just the data and the, the, the sort of dry, the dry graphs that have been copy-pasted out of insert cloud cost management platform here, 23:13 webpage, and stuck on a PowerPoint and, like, you know, that sits there for a month while people talk about it. Not like that, right? 23:21 But actually being a live part of the conversation when people are having strategic conversations. Yeah. That's true. And you also need, like, the... 23:31 It's, it's difficult to, you know, to, to push it forward, but maybe for- Mm... for helping Pino- FinOps people, like, um, push it forward, what do you think, like, 23:41 FinOps in a more strategic way looks like compared to, like, the, you know, uh, right sizing or, uh, cost cutting that we are, you know, maybe engineers are more used to, like, they are, and they pretty understand, like, to adapt the, the, the resource, but they are not... 23:58 That message is not going to be transmitted upwards because the upward- Mm... people are not going to understand it. What's your recommendation in, in that term? Yeah. So 24:10 cost cutting, waste reduction, whatever it is, right? This is housekeeping. Yep. Okay? You're either good at it or you're not.You know what I mean? Um, I'm, I'm good at it sometimes, right? 24:21 I make sure the background of my camera looks good. [laughs] But, but, you know what I mean? This is so... It, it is basically, it's housekeeping, right? It's keeping things tidy. That's just being a good citizen, right? 24:33 Um, but also if you, if, if you over-rotate on focusing on cost cutting, um, you'll do massive damage to your organization. Because a business is three... I, I talk about this a lot. 24:47 A business is three things, and I've stolen this from a Harvard professor who did a talk on this. It's, it's three things: money in, money out, what's left over. Okay? Yep. Um, a strategy needs to encompass that. 24:59 And it nee- any FinOps conversation needs to encompass all three of those things at all times, right? Um, one of the things that we do when we talk about FinOps, um, is we talk about these mini business cases. 25:13 We've been talk- talking about these for years, right? And what should be in a mini business case isn't we will save X by doing Y. That's not what should be there. 25:23 What should be there is, okay, so we've identified an opportunity that potentially could reduce our waste, iden- or potentially could, could be waste, could, might not be. 25:33 We could reduce our spending by X, right, by taking actions Y and Z. The cost of taking actions Y and Z is this, right? I ran out of letters. Um, and that cost could be borne over a period of however long. 25:51 Our breakeven point is this. Our risk of not succeeding is that, right? We need these resources. 25:57 The potential, um, opportunity cost for diverting resour- resources away from what they were doing is this, that, and the other. I, yeah, so 26:08 in terms of, like, bringing it all together, it isn't about just sort of feeding up cost cutting and, and saying, "Yeah, we, we, we turned off all these VMs and reduced our spend," and yada yada. I mean, if, if... 26:19 I mean, one of the other things I say far too much is, is like: Look, I'll tell you what. I'll make your cloud spend zero real fast. 26:27 If that's all you care about- Yeah, there is a, there is a hanging carrot that can do that, yeah... all you worry about is what's on the bill, I can fix that for you dead easy. Yeah. That's not a problem, right? 26:37 Um, unless you've committed to an am- amount of spend with your cloud provider of a few years, in which case you're paying it anyway. [laughs] Sorry. 26:44 Um, but, like, you know, focusing on, okay, well, but what are we getting for our money? And are we able to understand if a opti- optimization step is necessary? Yeah. True. 26:58 And wanted to add, like, when, when you were discussing, like, the whole, like, the step by step about, you know, you start from there, this is the opportunity, and this is the real cost. 27:09 Um, sometimes that, especially people maybe that are not, let's say from the finance or from the business perspective, but I, I, I don't say that they work on that, but they do, um, have some background. 27:21 I'm, I tell because of this story. Like, if you are probably investing in companies, in individual, individual companies, you probably watch or read the reports, 27:32 and then you probably see things like, you know, net margin, m-more of a financial thing. Like, you see net margin, operating margin, co- uh, cost of- Yeah... goods sold, blah, blah, blah. 27:41 It all goes down to that in business. Like, it's fairly simple. Like- It is. It's all about margin. Yeah, yeah, yeah. Yeah. It's all about the, like, why are some business are called better than others? 27:53 Because, for example- Mm... a business like Visa has margins that, uh, you know, are over 50% because their b- Yeah... their business model is just, you know, it's a great business model. 28:02 But if you are talking to Walmart, um, they need to have, like, a business model that it needs to be huge because their margin- Mm... 28:09 is going to be 5% and it's going to not to be more than that, because then other, uh, chain will be better than them. Um, so you need to, like, 28:19 uh, inde- independently of the level that you are, like in your career, if you are a junior or if you are, you know, more senior, you need to understand that because that's what business is about. 28:29 And that's the good thing about FinOps, and that's one of the things that kind of, you know, made me, uh, go all in into it, is because it, that much, like, it goes to the business level. 28:40 And as much IT or cloud cost you have in a business, the more important it's going to be FinOps. So- Mm... this is going to be embedded into the, the root of the business, and it's not going to be going away. 28:52 So that's when I understood, and I was, that's something that I try to transmit everyone. It's like, think about if you were reading the, you know, the results of your company. Do you... 29:01 I recommend you to everyone to take a look at that, even though the first time you read those, you won't understand nothing. Uh, you can ask your, you know, Jamie and I to explain to you. 29:10 Everybody- [laughs] And, and- If you work for a publicly filed company, you should know what your company filed company, co- company's balance sheet looks like. You should know. 29:18 And you need to understand- If, if nothing else, right, you should know whether where you work is a healthy business. You know what I mean? Because if it's super unhealthy, we've seen... I mean, it breaks my heart. 29:29 We've seen some businesses close their doors not long ago that were working in FinOps that were not health- that, that, you know, didn't succeed, and it's really sad. Um, friends of mine were affected. 29:40 And, like, you should know what your balance sheet looks like. Mm-hmm. Yeah? 29:45 And if your organization is, is, like, hugely invested in cloud, um, then FinOps is probably the m- one of the most important parts of that balance sheet, right? 29:56 FinOps is gonna have more impact on that balance sheet potentially than anything else, other than market forces for your product, right? Yep. That's true. 30:05 And that's, uh, something that I try to, you know, we need to try and, and make people understand. And, you know, now with especially- Yeah... the good, umLet's say the forbidden word, AI. Uh, it, it- Yeah... 30:16 could really help you. [laughs] That's a- A really good use of AI, like understanding about it- It is... and then it's like, "Okay, explain to me." And it's like, "Okay." Yeah, yeah. Um, actually it is quite useful. 30:26 Um, I've done that myself, is like taking... And I'll, I'll, I'll admit to this, right? 30:31 Like I'll, I'll take some company's huge balance sheet that just is full of stuff, um, and I'll, I'll drop it into, it- some AI vendor, right? I won't, won't name one. Mm-hmm. 30:42 Um, and I'll be like, uh, and it's public knowledge anyway, right? So the, but it's not like- Yeah... you're giving it sec- it, it's publicly filed data. Uh, don't ever put anything private into AI ever. Don't do it. 30:53 Uh- Yeah... even if it, if they, even if they say they're not gonna train on it, don't do it. [laughs] Um, but yeah, like the, um... Just put the balance sheet in and say, uh, "Tell me about this company. 31:04 How's it going?" Right? Like, "How are we doing?" And maybe even a couple of balance sheets. You go and get the last five years of filings and say, "There's the last five years of, uh- Post evolution. Yeah, yeah, yeah... 31:14 right. Acme, how's it, how's it, how's it going, right? Um, and is this a good place to be? And, you know, all that kind of stuff. Is it, should I invest or not?" Don't ever ask that question. But, um- No... 31:26 you know, like i- is this a, you know, is, is this a healthy company is the fundamental question. Yeah. Um, and going back to the kind of point of that, um, 31:37 you'll s- in s- in quite a lot of balance sheets now, you're starting to see cloud being broken out as a separate sp- spend item- Mm-hmm... in their balance sheet, right? 31:45 And if we take the, take the view that like on average, I think there's still today about 30% of cloud spend is waste. Yeah. Still today, which is, just blows my mind 'cause that's not far off of what it was in 2019. 32:00 Um, right? So I'm like, like I, I view that as being the fact that not that FinOps is failing, but that more and more people are sp- are building into cloud and they're starting their journey, you know? 32:12 I spoke to somebody six months ago who was starting their journey in cloud, and they'd, um, just, had just discovered the FinOps Foundation 'cause they'd never needed to look before. Yeah. Right? 32:23 Basically that's it, yeah. So- There, there is a lot of evolution in the, in the ecosystem, and you, we always think like it's been there forever and everyone is in the cloud and blah, blah, blah. 32:32 Whenever you have an IT ecosystem, it's... Like especially, you know, there are new companies, there are new ways of doing business, and there is- Mm... all, all good brick and mortar business. Uh, maybe they- Yeah... 32:44 now need cloud because whatever business reason or whatever it will- They've got their DC renewal quote through the door, and after they've picked them up off the floor, um, and they've like, they've had a brandy and recovered from seeing the price, price change, and they're like, "Wow. 32:57 Uh, okay." Yeah, we need to- "All that tech I haven't refreshed for seven years. I need to do something about this." Definitely. Definitely. 33:06 So, um, you know, wanted to, apart from, from, you know, all this business, and we, we talked about the strategic and how to incentivize people. So apart from all- Yeah... 33:15 we have discussed about the data and being, how we can make, you know, FinOps more actionable for people. Mm. 33:22 So like if they are someone that is struggling to make adoption, uh, what's the first thing that you will tell people to- Mm... to do differently that they are doing? So, um, 33:35 I'm one of these people who believe deeply in the fact that this practice is extremely important, valuable, and makes sense. And I understand... 33:43 I, I, I won't say I understand it 'cause I, you know, I don't think anybody fully does. But like I recognize its value. Yeah. Okay? I don't need to be sold to, however... You know what I mean? 33:56 In terms of like convincing this is a good idea. But there are people out there who have... Many, many organ- pe- people in organizations who've never heard of it before or per- peripherally heard of it. 34:07 It's not their job. They don't know about it. It sound, sounds like something complicated and technical, not my problem, or financial, not my problem. Um, 34:15 so I think one of the most underrepresented parts of any FinOps team is marketing and internal marketing, right? 34:26 And something that marketing people do very, very well, I have, um, friends who do this very, very well, is they simplify the complicated. Right? Some of them maybe simplify a bit too much, 34:39 but um, you know, don't, I won't start. But, um, yeah, like you have to simplify it. You have to translate it to make it relevant. Going back to what we were saying before, like so what? What's in it for them? 34:53 Why do they care? Okay? 34:55 If you can figure that out for your business holistically, if you can figure that out by department, then you can start to tailor your messaging, your outreach so that it isn't, "This is FinOps and we need X, Y, Z, and we are gonna do blah." 35:12 No one cares, right? Um, pe- well, a few people do. But- [laughs]... like how do you connect with your organization? How do you connect with your people and un- understand why they should care, right? Yeah. 35:26 Um, don't tell them why they should care, ask them why they should care, right? And ask them what, what, what matters to them. So the first thing... 35:34 S- so I've seen a lot of practices with great data, with really good reporting, really good tools, right? Like got a top right quadrant, best in class sort of solutions in place. It's all good. Works perfectly. 35:47 They've got exquisite graphs and dashboards with really great information, really actionable, really good, and yet no one does anything. 35:56 And they are constantly going and banging on doors and shouting from the rooftops like, "Look, look at the graphs." 36:01 And you go look at the login stats for their solution, and there's like three people have looked at it twice last month, and no one cares, right? 36:10 Um, and it's because we make the, we make the, we, we, we suffer from the assumption that because we think it's important, everybody does. Yeah. And they just don't. I promise you they don'tThey have- So-... 36:23 way more, for them, they have way more important things in their plate than, than FinOps, right? [laughs] They, they have a job to do that isn't- Yeah... FinOps, funnily enough. Um, so like wh- 36:35 wh- what's the first thing you'd do differently if, if the data's great and the reporting is great, and you're getting no traction? They don't care. Why don't they care? 36:46 Um, don't ask them why they don't, they don't care about FinOps 'cause they don't care. They just, they just won't. So how do, how do you make it relevant to them? Mm-hmm. What problems can you solve that they have? Yep. 36:59 Um, and as soon as you can... As soon as they start to realize that they can come to you and get value from you as a practice, as a FinOps practice, and actually they get 37:09 not just value, but they get a conduit to the rest of the business, their problems are no longer just their problems. 37:15 You can support them with connections and with that fabric of, of context across the whole organization. And then you'll have a job keeping them away from your door 'cause it'll be busy, right? [laughs] Yeah. 37:29 But, um, which is what we want, right? We want lots of people bu- knocking on the door and, and asking to talk to us and, and engaging with us. That's what you want. It's brilliant. But, um, 37:37 you have to sort of, you have to find out why they care and, and then appeal to that. And your, your marketing team does that like, like breathing. That's basically, that's what marketing is, right? 37:49 Is find out why they care. So if you don't have a marketing person on your FinOps team or w- or working closely with it, and you're struggling to gain traction, that might be why. Yeah. 38:01 So, you know, be friends with your marketing people. They're usually lovely people. Um- I, I-... get them involved... 38:06 wouldn't have, uh, thought that we could bring like to that point that we need marketing, uh, people- Internally... in the FinOps team. [laughs] Yeah. I think it'd be great. Yeah. Um- That would be fun. Yeah. 38:17 I think it'd be great. Like, I've, I've actually seen a FinOps practice that had somebody who, um, they were like dotted line from the marketing team, like internal marketing team, large organization, 38:30 and the comms were amazing. The comms were great, and as a result, people were engaged, right? Yeah. It actually worked really well. 38:38 Um, even to the extent that I think they were actually, the marketing team, marketing person was actually involved in, um, refining the report visibility so that it was more attract- more in- you know, more engaging to read and, like, added extra stuff in it, just not just graphs and tables. 38:53 It was, it was useful. So there was some context in there and... But the comms were brilliant. So if your data's good and your engagement sucks, your comms are probably the problem. That's, that's a wonderful... 39:08 I think that's a wonderful advice. And with that, I think it's a, it's a great, uh, way to, to finish the, the chat today. Um, thanks, Ben, for, for your knowledge. 39:18 It's always a pleasure to, you know, to have a chat with you. And, you know, thanks, uh, for, for taking the time today. Amazing. Well, it's always lovely to catch up with you, Victor. It's nice to see you. 39:29 Let's make it, uh, not too long next time, man. Yeah, for sure. Uh, let's hopefully see each other soon, and if it could be, you know, on site and meet each other, would be- Yeah... would be amazing, man. 39:40 I will be in London for FinOps X London on the 24th of March, so, uh, if you're about, uh, let's get a coffee. Yeah. And if anybody else is about, if, in the future, uh, uh, yeah, say hi. [laughs] Definitely. 39:56 So, and to everyone, uh, that are watching, uh, today, I'll see you in the next episode. Bye-bye. [upbeat music]