Transcript 0:00 Welcome everyone to a new episode of the FinOps Weekly Podcast, and today we have a very special guest. We have Franck Entrepot from, uh, Coblam. Franck, it's a pleasure to, to have you here. How are you doing? 0:12 I'm doing great, and it's my honor to be there. 0:15 It's, it's great to have some experienced, uh, podcaster host, [chuckles] in the, in the, in the podcast, a fellow, uh, podcaster that I've been following since I, you know, introduced in FinOps and much more than a podcaster for, uh, for sure. 0:29 And you already, like, uh, been doing some, some great work in, in FinOps. 0:33 So maybe we can start with, uh, you know, some introduction for people that don't know you before we start with the big guns, uh, top-down FinOps. That is your, you know, the topic of today. Okay. 0:44 Uh, so yeah, I'm Franck Entrepot. You can guess from the accent that I'm not British native, even if I'm based in London. Uh, overall, what I've been trying to do over my career is to be a full stack person. 0:57 And so, for example, what I mean by full stack person is that I started as a developer in my garage, not wanting to talk to human beings, then discovering talking with human beings, that it was useful. 1:09 I became an exec in a company in a startup that got sold for a billion, so that was quite a stressful environment. 1:16 I've done something to learn about how the board reacts, so a non-executive director diploma it's called, and it's quite cool too. 1:23 So the idea is I want to understand finance, I want to understand the board, I want to understand the executive, and I want to understand the, uh, developers and the engineering team, all of this together. 1:34 I have to admit, it's slightly hard to keep track of all of this, but it's fine. It's doable. Uh, from your perspective, I've been FinOps has been now from the beginning, really. I was at FinOpsX, the first one. 1:46 I had a, I had a short talk about forecasts that day that was really funny. 1:51 And yeah, with Steven Old, we used to work for the same company, which was very, uh, FinOps company, but thinking from the banking perspective, which was really cool. 2:00 We, we, for five years now, more than five years, we've been doing a podcast once or twice a month. So yeah, that's me in a nutshell. Yeah. 2:09 No, well, now I have my own franckentrepot.com where I share my ideas, analysis, and yeah, I think too much, uh, some people say, so it's fine. [chuckles] No, thinking, thinking is good. 2:20 Um, so yeah, I, I definitely recommend everyone to, to go take a look at, at your website because you could find very interesting articles that have been featured, uh, a couple, uh, more times in the, in the newsletter. 2:32 So, uh, definitely quality, quality stuff. So, um, let's start with, with the main topic of today, which is like top-down FinOps, a topic that you have been, uh, developing for, for a long time. 2:43 And, you know, for the audience to, to know, like, when you say top-down FinOps, what exactly, like, do you mean? How is this di-- is, is it different, sorry, for another approaches that we have in, in FinOps? Okay. 2:55 So think of it this way. Until now, we almost, and I, I think I wrote about this, yeah, bottom-up FinOps, so the opposite of top-down, is ask engineers to fix things with no connection to the strategy. 3:10 So it is when you go into... When you start with... 3:13 Most of the documentation you have [clears throat] in FinOps is about, and the complaints also, is about engineer not taking actions, or I have a list of lots of recommendation they should be doing, all these kind of things. 3:26 This is what I call bottom-up FinOps, 'cause yes, it comes from the data, but it doesn't have any real connection with what at the exec level they might need or even just at the VP level, who pays the bill. 3:38 Yes, you might reduce my cost by thing, by a certain amount, but if you are reducing the speed of delivery, I might not be that interested in the savings. 3:46 Or there are lots of things like this that, uh, we, the default-- Let's put it this way. 3:52 The default FinOps approach is bottom-up until now, most of the time, and we're trying to get access to, I would say, top management and executive and C-suite mostly for sponsorship. 4:06 This is slightly changing, but until now, they were just a participant, someone to inform. Uh, the executive were here to sponsor you. You were to inform them, and they would be here to sponsor you. 4:18 While on the other side, what I do believe is their job is to make decisions, take the responsibility when these decisions go well or bad, and then depending on this, so they make bets, depending on these bets, you want them to be implemented, and we are completely missing that bit. 4:36 So for me, top-down FinOps is to give back sixty to seventy percent of the data, which usually is enough for, to make a [audio cuts out] executive to decide what they want to do. Is this the risk they wanna go? 4:50 Do they want to go all in on, obviously, the AI? I need to say AI in any conference or, uh, do they want to go full speed onto, onto AI? Do they want to deliver much faster? Do they want to increase their margin? You... 5:03 Depending on that, they might choose different option of implementation, and that needs to go then down, and that's what you need to implement as a FinOps team. That's your priority. 5:14 Your priority should not come from a tool. Your priority should come from your boss. [chuckles] And that's what I call top-down FinOps, is we give back the decision-making, the risk also. We save ourself. 5:26 We are more secured because the risk is handled by people who are paid and trained to do, make decisions and risk. Yeah. That's, that's a very interesting approach because, you know, FinOps is such a, a... 5:42 I believe that it's such an important, you know, uh, practice and such an important, uh, thing to, to the company that it was weird or strange that the, the thing was bo- coming bottom up. 5:53 Like, you are implementing changes that are super important and super relevant to the company, but going from the bottom, which is fine, like to get, you know, a promotion or whatsoever, but then, uh, the strategy and the-You know, they, that kind of important changes need to come from, from the, from the top down because, you know, uh, and correct me if I'm wrong, but, you know, it's such an, uh, an important strategic decision that the ones that need to decide are in the top and not in the bottom, right? 6:21 [chuckles] The, the... Yes. And, uh, you've, you've highlighted also there is an, a very interesting thing about top-down FinOps is vastly different de- depending on the company. 6:31 You say that cloud, in this case of FinOps, is very important. It will depend on the companies. 6:36 So my short version is that if the company is on a very thin margin, so very small margin, the CFO has more power than the CTO, and cloud is probably if I do glasses or if I create that stuff for my house, 6:53 I-- cloud is yes, it's a necessary evil for some things, but it's not my business. So at that point, as you say, FinOps is less relevant or cloud is less relevant, IT also. 7:06 On the other side, if you're on a fat margin, you're probably a startup, you're probably in tech, and at that point the CTO will have more power 'cause they have more capability of spending because there is money in theory. 7:17 Mm-hmm. So the, the strategy, the top-down FinOps, that's part of what I'm saying is, do you know what your company is really targeting? Do you know in which a... what really would make an impact? 7:32 There was an interesting discussion recently about, uh, what can go into the balance sheet, so for those, uh, and what can go into CapEx, OpEx. It's the usual, uh, something. You need not to talk. 7:43 It's, it's a hell of complications. Yeah. [chuckles] But overall, what we are talking about in here, it has, uh, tax implication. 7:52 It has assignment, it has investor relationship implication, which is why it's not as simple as, "Oh yeah, OpEx is best." The other point that came to my, uh, to my thinking is how we see we live in a bubble, okay? 8:08 We live in a bubble of cloud, and it was... And we, in that bubble of cloud, we've been shaped by the marketing of cloud vendors, okay? Let's put it this way. By default, if you... No CFO 8:23 would say yes to cloud if they're in their right mind because you ask and you say, "How much is it gonna cost?" "I don't know." "Can we put a cap on it?" "No." 8:37 Or, or, "Is it gonna cost us another I don't know how much in technical setup?" "I can put alarms." You say, "Yeah, but that's too late." You... [chuckles] "I don't care about alarms." Uh, how do I... 8:47 And so the, the point being that you can see that the reality is me, for example, the big cloud vendors started from shadow IT. 8:57 It was someone in the dev team that bought with their credit card something to do a project, and that was cool because cloud is brilliant. And so it was really cool. 9:07 It was working, and it grew, and it grew, and it grew, and now it's reaching the CFO, which starts saying, "What, what's that stuff? What, what is the margin out of it? How much does it impact my tax?" 9:18 And you say, "Well, my EBITDA? Where's my..." I'd say, "Oh yeah, but that reduces your EBITDA. It makes it worse." Say, "Well, I'm not interested in that stuff." 9:26 [chuckles] And so we have that conflict at the moment, and the people in the bubble that we are, are fighting back saying, "No, no, our way is good." And you're there, "No, cool down two seconds." 9:36 Part of top-down FinOps is starting to put yourself in their shoes, okay? We've been managing money for more than five thousand years, okay? So they probably know something. We've been managing cloud for the last twenty? 9:50 [chuckles] Computers for the last fifty. So fifty to five thousand [clears throat] mean that- Yeah... they probably already have a name for it. They probably have seen it. 10:00 They probably have tried it, and it might not be in IT. It might have been in trains, might have been in oil, [chuckles] it might have been agriculture. I don't care. 10:08 The point is, it's been already standardized in lots of things. And so part of the top-down FinOps I'm saying, 10:15 the impact is for us in that cloud and FinOps bubble in particular, is a good dose of hu-humility and starting back, coming back, assu- accepting that we are biased in our decision, in particular from the marketing. 10:31 And last but not least, I'm talking about reserved instances. I'd like to talk to people that they are neither reserved nor instances. 10:40 And they are, they are the, the word I hate the most in, uh, in, in the cloud world, by the way. But it's, uh, at a... And, uh, and the small fun story, it's o-one day we went to, uh, with my boss, uh, Dr. 10:54 James, we went to talk with the CFO, and, uh, the CFO would say, "I don't understand that stuff." 11:00 And James was very kind to explain what in financial term, what an ROI is and how you can sell it on the ROI marketplace for twelve percent. 11:10 And the answer was, it's a forward buying contract with an embedded put option at twelve percent out of the money, okay? Yeah. That's- That is done. 11:20 The CFO knows how to account for it, how to manage it, the risk implied, but they never use that in AWS 'cause they talk with the tech people, 11:29 and they don't want it to spread 'cause as I say, CFO might not see that uncertainty and unlimited spend positively. [chuckles] Yeah, definitely. 11:39 And, you know, if you, if you have dealt with, you know, finance people and accounting people, they want to have things, like, very under control. Yes. 11:47 And, you know, as, uh, also, uh, reserved instances is something that is super, uh... I, I think it's one of the most trickiest thing to, to think about because they are very similar to what a CapEx buy would be. Yes. 12:02 But they are not. Uh- No, they're not. And, and that's, uh, I, I think, uh, that's deserve, like, a whole podcast on, on the reserved instance- Yes... 12:09 like saving plan thing on, on how to account for it because it's- Uh, yeah, no, I think you can't. So the point is we did some research. 12:16 You can'tYou cannot really account-- Oh, but the accounting is obviously gonna be extremely complicated. 12:23 And by the way, just say that was one of the thing we used to do is to help people, because every time you buy a, let's say, a thirty-six months RI, so three RI, 12:33 every month the accounting team need to count it how it is, 'cause if you spend one dollar today, it's not one dollar in three years' time. There is inflation in the middle. 12:43 So you need to start accounting that on a monthly basis in advance. 12:47 There is ton of accounting work for anything partial or full up front, which is why I think on the new RIs for DB or savings plans for DB, they just remove any other up. It's, it's nothing up front. [chuckles] Yeah. 13:01 It's like i-if you are into... Like, that's one of the things that I like about FinOps because I come, uh, you know, from the tech side, but I also like the finance. Yes. 13:09 And when I see, like, uh, finance stuff and it's super, uh, super interesting and, you know, uh, it's very tricky. It's very tricky. But, you know, moving on to, uh, the, the top-down. 13:19 So we have thought about, you know, how the responsibility has swapped from, you know, swaps to the bottom, uh, to the people to, uh, the top-down. 13:26 But some of these things, like those, uh, cascade of, of tools and some, some practices, it's like, how do you cascade, like from the different teams from the top-down without feeling like this is super mandatory, this is a, a policy? 13:42 Like, you know, how, how do you do that so it's embedded into the whole org? That, that's interesting. So there is a, there is a say that your creativity comes from constraints, okay? Mm-hmm. When I used to... 13:57 I- I have a beautiful book on programming, which is called Programming Pearls, and it is from the very beginning days when you had six hundred and sixty-four K of memory, okay? 14:06 And your problem was bigger than sixty-four K. How would you solve that? And so you had that constraint that was forcing you to think through and find new ways and innovative way. 14:17 So what I see is that for me, top-down FinOps as policies, and it is mandatory, but it's set. But the way you need to do it, and that's why you have multiple layers. 14:27 I think on one of my article, I've highlighted seven layers. I-I-- They are theoretical layers, but the idea is that if the CEO says, "We're gonna be, uh, 14:38 we're gonna be a lean company," for HR, that means that, yeah, you don't fly business. 14:44 But for the cloud, it might be that, hey, you do not use the latest generation 'cause prices are going up, and you're just gonna stick to... But by defining some constraints, you create what I call the sandbox. 14:57 You create a perimeter where the developers or the engineers, they don't have to think if they are doing right or wrong or going back to the architecture. It's, "No, that's fine. That's covered. 15:10 I can focus on the real problem I have." And, and so if we were to say, "Look, we're gonna be old style, we're just gonna do three-tier architecture. The database we're gonna use is Postgres. 15:21 The intermediate, we're gonna use network load balancers, EC2 instances, only spot, eighty percent spot, twenty percent non-spot. The, and, I don't know, application server in the middle, whatever." 15:33 And you just say, "Hey, that's, that's what we're gonna use for the next year or three years." It frees you as a developer to say, "Okay, how can I optimize that?" 15:44 How I can go deep dive into Postgres optimization instead of thinking, [gasps] "I should use DynamoDB for this, and key values should be in the other store, and that there, and then it's gonna be hell on earth." 15:56 So the way I see it, yes, it is mandatory. Yes, it comes with policies, but those policies, if well done, and the hierarchy is right, are gonna be freeing you from... 16:06 They're gonna give you play, a, a pitch in which to really play freely without having to be responsible for stuff that were totally out of your control or- Yeah. I, I... 16:19 And definitely you, you, you highlighted something very interesting that I totally agree on that. 16:24 It's like you need to, you know, constrain a bit the, the development, uh, cycle, even though, like, for certain cases, like, I don't know, AI things or all of that, you need to like, "Okay, let's frame this and let's see what's the new thing." 16:36 But for the general, like, software development, you can constrain what is best for your company because you can then, like, optimize more, like, on the performance side, on the technical side, on the price side. 16:47 You can then- Exactly. Like, if you have a stack, like, that's something that, you know, a lot of, uh, SaaS builders say that, you know, you, you stick with your stack, and then, like, you will be much more productive. 16:58 So innovation is great, like in, in tools, and there is always new tools and all of that. But then- Yes... if you constrain it, you become the best at, at your stack. E-exactly, and that's value, I think, though, so yes. 17:10 And, uh, and there are, there are software, it's interesting to say, and you work for one of these companies, which are enterprise type of company, and the enterprise type co- of company, they are here to stay for years because they manage things that you cannot change easily. 17:23 If you have a supply chain, you produce a product, and you have a supply chain that goes through China to India to the US to Europe to whatever, you need a software that holds it up together, and it needs to have a strong base. 17:35 That's what I've noticed. Enterprise software have a very strong base, and then you can adapt on top. And [clears throat] almost every, so let's say the Oracle, the SAP, the Salesforce, they're all based on that model. 17:48 And that's something maybe we don't have yet matured in, in FinOps. We have tools that try to tell you, "Oh, those are the best practices." And you say, "Well, cool down. Maybe not for me." Yeah. 18:00 [chuckles] And I think- And- Yeah, that's it. 18:03 Uh, and, and, you know, talking about, you know, best practices and, and saying that what you just said about, you know, that's not for me, maybe it's for, for another company. 18:11 So that, uh, relates to, to one of the topics that I wanted to discuss today, which is context, right? So you have said in, in multiple times that, you know- Yes... context is, is, is everything. 18:20 So, you know-Why context can be sometimes more important than the actual numbers that you can see. Yes. So I think it's, it's the-- So I will, I will... 18:33 Yes, and then I will tell a longer story later on, I think they will, when we talk again about context is everything. But to start with, uh, context is-- think of it in a very simple way. 18:44 We all have brilliant dashboards now out of fashion because now we decide that it's not enough, and we all need a chatbot. 18:51 But overall, when you look at any graph, okay, if I tell you forty-six percent, you have no clue what I'm talking about. There is no context attached to it. 19:02 And that's what-- If, if you look at the, if-- I will say the Kudos dashboard because I had the pleasure to working a lot with it. Pleasure. It's a ton of information without context most of the time. And you just... 19:16 So I've-- We, with Steven, we did a talk about this, that there are five things you need to have in every graph to make it useful. You need to, and to add that context. And the first one is the data. Yeah, thanks. 19:27 Got it. Second one is some text. Explain to me. If I were to tell you that those forty-six percent is the intake of fruit and vegetable in my diet every day, that would already make you more understandable. 19:39 But then what you need to have, and which almost everyone misses, is what is good, what am I targeting? Because I don't know if forty-six is good or bad. Mm-hmm. 19:50 And the same way, I, I need to have a good, which can be a value or, or, um, or a range. And then you need to have also what is bad. What is the bad range? 20:00 So you need to have the number, you need to have some context with text, you need to have a good, you need to have a bad, and the last thing you need to is to explain what good is good and bad is bad. 20:11 So for that example, and it is the one we've used in a, I think in a, in a keynote we, we delivered at one point, it is-- Imagine if I tell you that the goal is to get to between twenty-five and thirty-eight, and you say, "Why is that?" 20:27 Well, because if, if I have less than twenty-five percent vegetables, I'm probably ingesting too much fat and too many sugars, and so it's gonna be bad for my health and cardiovascular thing. 20:37 If I am above forty-six percent, I'm probably not taking enough protein in, and I will need to di... 20:42 And so at that point, if I tell you forty-six percent, showing you the ranges and all the stuff, I give you full context, you will understand that graph without me having to tell you anything. 20:53 And that's why-- And I am a data guy. I love dashboards and stuff, and I think we are just throwing numbers at people and telling them, "You should learn my stuff to understand these numbers." 21:05 And I totally disagree with that because I'm very opinionated. And, and I, I also agree. Like, I also deal with, with a lot of data and, like, a lot of data can be useful- Yes... um, but with the proper insights. 21:20 Like, I can have, I, I don't know, we can see like bills and, you know, all these excess, and you can have like, okay, I have a lot of data and a lot of visualization and all of that. 21:29 But, uh, one thing is like, okay, what do you do with that data? What does it mean? Uh- Yes. Why is it relevant for you, for your clients, for whatever? 21:38 So, you know, um, talking about this and adding more about like, uh, how does adding this context change to what decision, uh, people make when, when they have, like, this data and then you have context, and then how does it change for, for the decision? 21:55 Well, I, I think it put into, as we say, into context in this case, but it's... Think about it. 22:00 When you have a-- When people an engineer, they'll have a certain salary, and f- we all have a sensibility, for example, to money, which is different, okay? 22:08 We say, "Oh, if I'm earning tons of money, I can say, oh, a hundred dollars, that's irrelevant. That's a small amount of money." But a million dollars is always gonna be big. 22:18 But if you are a Fortune five hundred or even two thousand really, and you say a million dollar is irrelevant, it's just, it's peanuts. 22:28 But if I am the person in the FinOps place or the developer, I might find it very important. I hear continuously, you can see people telling you, "[gasps] You could save three hundred thousand dollars." 22:38 And you say, "Yes, and I don't know if that's important," because three hundred thousand dollars is just the price, potentially... 22:48 I, I used to manage forty-- I had a, a team of forty developers working for me, and you end up and say, "Yeah, I can tell you that their salary, okay, they are all earning quite a good amount, is way more than, uh, uh, per month." 23:02 So no, I'm not stopping, I'm not distracting them even two days, all these people, to do a hackathon for that amount of money. It's just no go. 23:12 And these kind of things, I think, is, is what the context bring is when you bring the context, it brings clarity with those constraint that we talk about to every individual. 23:24 So I know that in my company, any savings that is less than ten thousand needs-- Or better, for every ten thousand saving, it needs not to take more than an hour of time, engineering time. Does it take more than that? 23:40 Yeah. It's not worth it. That's a context that is really useful for me because all of a sudden, I don't need to make decision based on my biases. 23:48 It's been decided top-down that this is a number that match, and that number is communicated to me through context. Yeah. That's, that's something that, uh, it's very interesting, and I can totally relate on that. 24:02 I recall when I was... 24:03 And probably that's ha-happened to, to some people as well, that when I was starting to doing FinOps in, in, in my company and some others as well, like, um, if you are doing like a hundred dollars in savings a month and your salary is more than that an hour, uh, then you need to do it in like five minutes or something. 24:21 Exactly. Um, [chuckles] because they, they, like, the human, let's say, the human cost, uh, that you have for, for, let's say, for, for the human resource that you are for your company, um, is not worth it. 24:33 Like, that's... It's not worth it. So you need to take that... 24:36 You need to, as you, as you just said, define a decision processSo that, eh, you know, people can, can make a, um, uh, their right decision so that, eh- Yes... 24:46 they define, like, "Okay, let's do this," or, "Let's not do this." You define your, your decision, like, process so that we can apply it to, to Finos, right? Yeah. Context is transfer of information. 24:58 It is, and sometimes slim, but yeah, it is transfer of information, and it works very well with the top-down thing is this is the context of our company, this is the strategy, and that goes down through the right channels, through the right people whose job it is to make this. 25:11 So yes. And, you know, you mentioned before, like, you had a story- Yes... uh, to tell us about the, the context, so can you, can you tell us more about that? Yes. 25:20 [chuckles] Uh, this is a story that come from o-one of the best book that I invite everyone to read, by the way, which is the, uh, "Seven Habits of Highly Effective People." I don't know if you've, have got that one. 25:29 Yeah. But there is the story that is the story in the tube, and so it is... 25:33 Imagine yourself, so this isn't imagining, but imagine yourself, you are in the subway, whatever city you want, and you've just finished a hard day job, okay? 25:42 You're tired, you're exhausted, you're reading your Kindle there, and you want some time. All of a sudden, it's chaos. 25:49 Absolute chaos because you have two kids that are jumping around, smashing things, kicking poor-- touching people. They slap your Kindle. You get so upset, and they are, 26:00 they are old enough to be-- to do a chaos, but not old enough to be on their own. So you look for the parents, you know, uh, someone to blame on to. 26:10 And you go, and you find the father who is completely lost and seems to ignore all of that, and you get very upset, okay? So you are very upset, and you look at that person, and you say, "Get a grip on these kids. 26:21 They are doing chaos." And that person tells you, so the father tells you, "They've-- We come back from the hospital. They've lost their mother. I don't know what to do. They don't know what to do. 26:34 I don't know what to do." Okay? At that point, m- the chaos is there. The facts are there. The num-- If you were to measure things, nothing has changed. 26:44 I just want to hug that person and make sure these kids are gonna have all the emotional support they can get. The only thing that changed is the context. 26:54 And so when you read a number and it doesn't have context, it's useless because we are emotionally driven fa-by people. 27:01 So that story for me shows, and I have shivers every time I tell it because I think of myself, if you want, and you're there. It's, it's enormous. And the onl-- I, I would completely change my behavior, 27:15 and it's, it's not that. And so I invite other people, not in an extreme as this way, for example- Yeah... but to put yourself into someone else's shoes. 27:23 Put your-- Learn that finance bit to understand why are they being so painful with some aspects. 27:30 It's assume given A, that's, uh, another, from another thing, but given A, start by assuming that people are doing their best and they are smart, and that's you are missing something- Mm-hmm... 27:43 and ask for that something. Yeah, that's like, that was, uh, I recall about that story from, from the book, and it was very powerful to, you know, to, to, to showcase as an example. It was like... 27:55 And the way that it was written, it was very, very good to, a very good read. So I definitely recommend people to do so. And I totally agree. I think that can be applied also in, in, in Finos, but in general business. 28:06 Yes. Like, if someone is pinging you or someone is, you know, you're not understanding why they are acting some way, 28:14 you probably need to ask, like, why, uh, you know, the, the, the, the reason behind it, and they'll probably, like, dive deeper, and then you will know, like, what's behind. 28:26 And that can apply especially when you are, like, um, getting into more m- more management, more business style. You deal with more people. Yes. 28:35 And we get with more emotional and, you know, decision-making is something that you need to dive deep into, like, okay, what's the whole thing behind this so we can reframe, as you mentioned, ourselves- Yes... 28:46 uh, so that, uh, you know, we get to the right point or we get to the right solution. Everyone wants to have, like, a win-win solution, and that's it. 28:54 If not, then, you know, uh, that's someone you shouldn't be doing business with. Um, but that's, like, that's a super powerful, uh, example. 29:03 And, you know, so we have talked about, uh, the context and how it affects us, but, you know, most of, uh, or several people that are listening to us may be working in a, like, in a big company, in an enterprise. 29:15 So how people can implement cox-- context at scale, so, like, for a, for a big company? Like, where do you start, like, on the, on the first place? Well, you, you start... 29:27 So it goes, as we say, probably with, um, with the top-down thing. 29:31 So the, the f- the first thing I would invite people to do, even today, and I think that's, uh, is if you are in a big company, you're probably public company, or even if you're not a public company, you have investor report, you have strategy report. 29:48 Have a look at your quarterly report, okay? Have a look at how, uh, the company define themself. 29:55 What are the risks that the company as a whole is thinking about, that they are presenting back to investors, that the board are looking? 'Cause we talk about the board as if they should care, like, all this stuff. 30:06 Have a read at these documents, and you will discover they read. There is a big bank that is a lot in the cloud, and oh, and we were all use cases and success stories, all the stuff behind it. 30:19 And then you go into their report, and you search cloud, and there are three reference to cloud, and they're all in the same paragraph, and they talk about weather. And it has nothing to do with IT. 30:32 So you look into the IT thing, and you find that some of the cloud in IT or the IT vendor was named more in the risk side of things as we have a single vendor. And you're like, "Okay." 30:44 So these kind of things will-- E-even just reading this shall help you understand what is the board really f-... thing, and there is a really, really, really good chance that they don't give a monkey about cloud or IT. 31:00 IT, for most companies, is a necessary evil. 31:05 The only one it's not a necessary evil are usually startups because even when you-- because when you get to a certain size, even let's say Microsoft, Microsoft is a tech company, we all agree with that. 31:17 How much are server important compared to programming li- and creating license or managing your licenses or other people around? 31:27 It is, IT is vital, but still it's not the main dri- um, value dri-driver. Yeah. 31:38 I, I, I think that what you said about the necessary evil is like some-something that we, like coming, especially from coming from, from the technical side, we need to reframe ourselves because we think, you know, uh, the development, the applications that we do is the most important thing of the business, and we are doing a critical thing, and, you know, we are super important. 31:57 And that's fine. It's like, uh, self, uh, esteem, and that's super [chuckles] great. But sometimes, like, if you are working for a, a, I don't know, a supermarket or something like that, the good... 32:08 the, the thing that brings the business is to sell on the supermarket the products that you have. Exactly. Not the IT infrastructure that goes behind it and monitors everything and whatsoever. 32:19 If they could avoid it, they would do it because the only thing that matters is to sell- Yes... uh, the products and have quality products that people would buy with a good margin. Yes. 32:27 That's business, and all that comes behind [chuckles] is just a, a necessary evil. Like mostly like you can think with legal, you can think with, you know- Yes... uh, uh, IT. 32:38 It's all necessary things that, that you need to- Certainly... to make it happen, right. 32:42 A-and let me be a little more positive on this again with some sort of story, but, uh, uh, 'cause I, I want to highlight the good thing of cloud. 32:48 But s- the way I express it to company, I say, "Hey, if you're doing-- e-every company big enough has employees, and so they're doing payroll, okay?" Mm-hmm. 32:57 So you do payroll, and in the past, I used to have to manage some payrolls, and you, you would have a payroll, and it would... 33:04 you'd have a cutoff date, which usually was ten day before the pay, so that you would stop and say, at that date, we cannot approve holiday expenses, all this kind of stuff. It's gonna be back-ported to next month. 33:19 So sometime you would have to wait a month for something done, I don't know, a week before payday because they had that cutoff, and that was normal, and that was because you were limited by the amount of power it would take to build. 33:32 You had four, four servers to do all the, uh, accounting, monthly accounting, and but cloud changed that. All of a sudden you can ask, "How much do I-- how long do I want that cutoff?" 33:46 And if you were to say, "Hey, I want it to be one hour." Say, "Okay, to one hour you need two thousand servers." Say, "Well, let's get two thousand servers one hour before." 33:57 And all of a sudden, all the admin work of the cutoff, all the backlog, all the 34:03 bad cr- complexity of, oh, let-- pass my expenses that day because it's gonna be before the cutoff, and all this kind of stuff, they just disappear, 34:13 and, and that is, for example, the power of cloud is if, if you have some problem which can be solved with quantity 34:20 or things which are one-off [clears throat] and that you, you need that are one-off, you need massive, just do it. When I was at Strategic Blue, we had a guy, it was before the, all the AI, uh, craziness. It's a... 34:34 He's a researcher at University of California, San Diego, and he told us, he said, "I wanna buy every spot GPU available of all three cloud vendors in all regions in the world for one hour, all of it." 34:47 And he had, I think it was half a million dollar for that hour budget. And at, at the first time I was calling data centers, and were there, "I don't care about the marketing. Don't tell me infinite. 34:59 How many GPUs do you really have?" [chuckles] It was a really interesting thing, and he'd never managed to spend all that money. 35:06 Now it would be very easy, but at the time, he had-- he co- he had with that same budget, he, he did a couple, I think, of rounds to get it all. 35:14 What it showed on the other side is that we were able to bring up, I don't know if it was, I'm gonna say a number, but it might be slightly, but it was twenty thousand VMs up 35:24 cloud vendors in all region in the world in fifteen minutes. So in fifteen minutes, you were-- we were able to have twenty thousand VMs up and running, synchronized and working, and same thing for turning them off. 35:37 You say, turning off twenty thousand VM went down in five minutes, and you're like- Yeah... wow, that is a scalability which is mind-blowing. Oh, so well done guys managing infrastructure because that is huge. 35:50 At the same time, that was a problem he had for s-scientific research. Volume really is available for cloud vendors, and it-- they are doing it exceptionally well. So if you need that, brilliant. Yeah. 36:06 It's, it's crazy the things that we can achieve, like you mentioned, you know, having all the GPUs or all the spot GPUs [chuckles] that you can have in the world- Yes... 36:14 uh, at the accessible of, like, clicks, um, that's crazy. Yes. 36:18 And, you know, talking about these experiences, what, what do you think are the, the mistakes, you know, that, that we can have on, on context and, and in context to the cloud financial data? 36:29 Like we have, we have seen, like, you know, you share case studies that look awesome- Yeah... but what are the mistakes that people normally do with that? Well, well, I would say y-you go, it's as usual, it's the... 36:40 there is a saying in French which is, "Le trop est l'ennemi du bien." The too much is the enemy of the good, okay? Which means that y- when you start expanding, when... Let's go back to the top-down. 36:52 When you start with the top-down and you start enforcing thingsTo a level that is not your competence anymore. 36:59 So if I, as the CTO, I decide we are just gonna use these type of instances, that is so totally out of your depth in theory. You should not make these decisions. I'm still talking about a big enough company. 37:14 Your job is to make sure that IT get the budget and that it is allocated correctly. That's it. VP of engineering will start working and, and et cetera, and so you go down. 37:24 So one thing is to be too prescriptive, so that at that point you kill creativity. 37:29 Uh, you need to-- you always need to assume that the engineers and the tech people are still very creative because it's still a job that is not standardized enough to be non-creative. 37:40 Uh, by the way, there is the Pixar book on managing creative people, which is an absolutely must, uh, which is genius. But they, they are... So that's a mistake. 37:53 The o-the other mistake is just, uh, again, is to throw data at people expecting them to understand your context, is to not put yourself in others people's shoes and assume that they are stupid or that they don't know their stuff, and they should learn my stuff. 38:10 Always assume that it is you. So the, the mistakes are, are gonna be there for, for context, yeah, not enough or too much. That's why I'm trying to figure out those five things. 38:21 Say, look, you have five things you should say, and they should stand in a graph, okay? It's... We're not talking about trying to explain the world to everyone. 38:32 Uh, but yeah, th-those are the things, and last but not least that comes to mind, and we've t-talked about before, is assuming that, yeah, people, they should know they're stupid or they're doing it on purpose against you, and you say, look, in a company, it's extremely rare. 38:48 It's usually of incentives, and eventually these incentives are badly designed. And yes, you're trying to game the system. Is that a bad thing? It's, it's the system that is wrong. 39:02 Don't change the people, change the system, and that is the thing, uh, that comes from, from good leadership, in my opinion, and that's, uh, that's the thing you need to, to go for. Um, yep. 39:15 So I hope that kind of answers your question. [laughs] No, no, no, it, it does. 39:19 It do- it definitely does, and when you said it's, you know, uh, perfectly because, um, you need to put things, uh, as mentioned in context, and what you said about the system is like you have to in like in FinOps in general, like incentives is one of the, you know- Yeah... 39:34 uh, things that, that one of the leverages that you can have that are- Yes... more powerful in, in the practice, right? Yes, but, uh, a-and you always need to think about that it's gonna be in some form way gamed, okay? 39:48 And you need also to remember that the extremes are, are usually-- If you were to say, "Hey, you get a bonus if you reduce by twenty-five percent," say, "Oh, it's proportionate." And you say, "Well, perfect. 40:00 I'm just gonna turn everything off. I'm done. Oh, ma-massive bonus for me, absolute horrible for the company." They'll come by and say, "Oh, that's not what we intended." 40:10 Well, yeah, but that's what you intended by putting that, uh, not requirement, but that incentive. Yeah. 40:19 So i-i-it's very important to when you set incentive gamification or this kind of stuff, I highly recommend you to have a sh- a time period, an end to that, so you can review, is it doing what we are expecting? Yeah. 40:36 Uh, and, and don't put extremes or unlimited boundaries 'cause you're gonna end up in a mess 'cause, uh, yeah, the developers or we are all techies, we know the math usually. 40:48 That's why we don't play at reinventing casinos most of the time. [laughs] But on the other side, if there is a way that math is involved, how we can trick and tips and change, then we'll probably do it. 41:01 [laughs] Yeah, definitely. And what you said is like, uh, the most, uh, representative case, I think, in, in FinOps especially to illustrate, like to, to work on the business value and not on the cost, right? 41:12 And one of the most used e-examples. And you know, one thing that you said about we are from, from the techie side, we always like, you know, tools and, and technology. 41:20 So what do you think, like what tools or what tech can be used to make top-down FinOps or make context, uh, possible in, in a company? What do you have in mind? 41:31 So I think, so in FinOps, we still have a set of tools, and they're trying to do lots of things, but they're trying to be everything for everyone, and, uh, and as I said, I see enterprise, so the next level of software development, which we are not there yet, to be a very strong, stable thing for everything that is standard, and yeah, the SAP, for example, or C-- or Oracle is one like this, is you have a database, all styled, very strong. 42:02 There is a strong base on performance, quality, et cetera, and you have a very simple interface, which is SQL in the, in the case of databases, and on top you do whatever you want with it 'cause you need to adapt the tables to your need, to your data, to your queries, to all this kind of stuff. 42:20 That's what I see an enterprise thing is, but it all start from there is a strong base that you can solidify. Salesforce does that. It was able to do that because the CRM was quite clear. 42:31 Oh, there is a lead, there is a prospect, there is an opportunity, there is a company, all this kind of stuff. We are not there yet, I think, with FinOps. So at the moment with FinOps, 42:41 I would say you probably will need to... That's why people are using four or five of them. There is this aggregation that's happening at the moment. It's probably gonna go t-into that direction. 42:52 But to answer really your question, it is so-I see, and I think of putting the notes out from our, our thing. So the first thing is you start the... Where is it? Where is it? 43:05 Anyway, you start with decisions, and decisions are usually on pen and paper or on... So you start with a pen and paper, and then that's the first tool. 43:14 The tool, technologically tool that can work, and I've been working with them, uh, quite a lot, is the, is the policy, is to be able to transform high-level mandates into policies that are overarching, okay? 43:30 I don't-- I'm not gonna force you to use a tool or another, but I want to make sure that if I'm in a bank, you're encrypting everything. Mm-hmm. 43:38 I need to validate that because, yeah, my mandate is to be secure because otherwise I lose customers. So I think y-you have policy engines are really powerful. 43:49 Uh, there are potentially also orchestration systems that will help you with that, that will glue things together because you need to glue things together today. 43:58 A-and then you need to ask and be a pain with your vendors to say, "Yeah, but my whatever do not understand what this graph is about, or how does that relate to my thing?" 44:12 Remember that the more data, we have tons of data, and that's why we, we want FinOps to expand horizontally with scopes and go all over the place, which I like. At the same time, I see it as a dependencies. 44:23 We are curious animals. I think the National History Museum was showing in London, was showing that curiosity is an instinct. So if I can have more, I will always ask for more. Do I know what to do with that more? 44:36 Probably not. [chuckles] And so the point is, what I'm saying is from the tools is 44:44 start by your questions and then go and see if the tool answer those question or ask them to answer the question, which is why we do custom things lots of the time. That's why Excel still exists. 44:54 That's why every data goes through Excel, because Excel is the most cons- contextualized thing that you have. And by the way, AI is the same. We love AI. That's the superpower of AI. I wrote an article on this. 45:05 It's because it's contextualized. I can say, "Hey, tell me as I PhD in FinOps" or, "Oh, I know nothing about FinOps." I change my context, I change everything. I change all my answer. 45:18 So tools at the moment, I don't think we have the maturity in cloud, and the cloud vendors do not want that maturity completely to get through with. They don't want to be a commodity or commoditized. Mm-hmm. 45:30 Because let's be clear, the relational databases is a commodity. That's why you have tons of them. It's just, it's a mathematical problem, and now there are best people doing it in certain way or others, but 45:44 you need that level of commodity that we do not have in cloud. So the tools I would say, 45:50 pen and paper, communication, fortunately Excel for you, uh, probably policy engine would help if you're in a big company, really helps to make sure that everyone's following at least the, that minimum baseline that we can agree on. 46:03 And then underneath, yeah, you'll have multiple tools and use each tool for the niche they're trying to cover. 46:08 And don't believe the hype of, uh, oh, we do everything for everyone because everyone, every vendor is correctly following their customers. Not all their customer, their biggest customers. Cloud vendor is the same. 46:20 When they tell you, "We follow the customers," I say, "Yes, but Netflix is more important than me, I guess." [chuckles] Yeah. 46:30 I guess the, the big ones are, you know, it's what drives the, the priority of the, of the business and, and you said it right. 46:37 I, I totally agree on policies like independently of the, the tool or the native one integration that you have, uh, they are mandatory, I think, for, for any big company because otherwise, like policies and automation, um, that's where you are going to, to ingest things and- Yep. 46:53 Yeah. But, but build them from the top down. So build your policies- Yeah... based on what your boss's bosses-- wherever you can go at the top, and if you can justify it going down on... 47:06 The way I see it is take the big guess- the big yearly guess that every company will have. That is called the business plan for the year. When they tell you we're gonna grow by twenty percent, we're gonna... 47:18 If you attach anything you do to this kind of the business plan for the year, the objective of the year, the strategy of the year, you're gonna be able to justify almost anything you do in an extremely easy way. 47:32 I'm gonna ask for more budget, for twenty percent more budget because the boss says we're gonna have twenty percent more customers. Yay. Yeah. And it makes it way more, you know, let's say sellable or way more- Yes... 47:45 easy to achieve because you have a goal, so you can have a focus, and by having a focus, you can have more like you can have infinite request or infinite- Yes... actions that you can take. 47:55 But if you focus on the goal, then that's that thing. 47:58 So talking about action and talking about goals is, you know, if someone, uh, wants to do, uh, all the, all the advice that has been provided today, uh, this week, like what is the one thing that they should do to, you know, give context and make top-down, uh, happen? 48:16 I think it's, it's start r-read your company strategy. 48:21 I would say that's the first thing you should do because with that conversation, if you've got some aspect of it, which is we should, uh, th-the top-down decisions have been made already, okay? 48:33 And they are written somewhere. Yeah. To get to that and start from that and say, "How does it apply to me?" 48:40 It's gonna make it much simpler to sell whatever initiative you have, but it also gonna make it much simpler for you to understand what is relevant and non-relevant for your business, um, because that is the thing. 48:52 Another thing is if you, if you are one of these that feel that, uh, you have problem engineer- having engineers to do stuff- Mm-hmm... 49:02 the FinOps things-Uh, again, a-another article, but it's, uh, y- there is this thing if-- from the developer's perspective, for example, if it's not in the backlog, it does not exist. 49:13 So instead of bombarding the poor engineers, go to the product owner. How do they get requirements? Can you have FinOps requirement to fit? Can you have some sprint points to be assigned to you so that they are rewarded? 49:28 'Cause engineers doing the job you're asking them for FinOps are probably gonna be slapped on the hand because they are wasting time on stuff which is not what been requested. 49:39 And so go to your product owner, have a chat with them. How does it work for me to be on your backlog so that I, I become... I exist? 49:51 And I think that would solve the problem that been plaguing people for four years, and you're there, h-how can that be happening? So that would be my two things. 50:02 Read your company strategy and underst- apply it to yourself, and the other one is, uh, if you want engineers to do stuff, have a chat with their product owner. 50:12 So again, top-down FinOps, because that's the person that has the power to create a slot for your activities and will tell you why they can't do it this month because the release is in a week, so just get out of my way, [laughs] 50:26 is a really good answer for them. Yeah. I, I, I totally... 50:30 Like, uh, I haven't thought about the product owner thing, but, uh, now that I am, uh, especially, like, I'm working more of on that role than on the, on the developer role, I totally agree. 50:40 Like, I am the one, uh, let's say, making the calls and redirecting people to what they need to do and what they don't need to do. 50:48 Um, and that's like, if it doesn't come through, let's say, me or through anyone, then it's very difficult that, uh, it's going to be made by, by the compa- or by, by the team. So- Yeah... I totally agree. 51:01 That's a wonderful advice for, for getting people involved. It's like, you know, you make it top-down. You- Yes... achieve the product owner, and then, uh, the engineers will- Yeah... will do the work. 51:11 Especially you would be upset if, uh, you discover that one day of one engineer was lost trying to optimize a database that, yeah, was totally unplanned, and they've, they've not delivered a, a feature, and you're there, "No, no, no, no, no, no, no. 51:25 Go back." [laughs] Not a- Yeah. Yeah. Uh, that's, that's great, great advice. And, you know, I think with that, uh, we have more than, than enough that to, to cover today, so it's, it's [laughs] what? A pleasure to... 51:37 It has been a pleasure to, to have you here, Franck. I think you provided a lot of wonderful advice. Uh, so, uh, thanks for being here today. Um, but my pleasure, and I will be slightly selfish promotion. 51:49 I just published a book for managers, so please have a look at Protect the Doer. Let me know what you think about it. [laughs] Yeah, we'll put the, the links in the, in the description- Yeah... 52:00 below to all your, uh, all your stuff and definitely for, for the book because we love books, uh, here to, to be honest. And, you know, pleasure to have you, and see you all in the next episode. Bye-bye. 52:11 Well, thank you, Victor. Bye, everyone. Thank you, listeners. [outro music]