Marc Andreessen (93:05)
I'm not sure if it's that one, but it's one of those. I think it Might be that one. Yeah. And he actually went back and this is like, you know, this is. We're talking about like 1940s, 1950s, 1960s. And he went back and he got them at that time they had a secretary transcribing in real time all of the executive staff meetings every Monday morning. And he went back, back. And I actually got the archives of the transcripts of the executive staff meetings. And it's just literally Thomas Watson's just like cursing everybody out and just like, just like a complete tyrannical psychopath, just like screaming at people. And it's all, it's all in the records. And so it's like, you know, so how much of this stuff ever changes? You know, it's like, you know, whatever. I don't know, whatever Elon gets accused of or whatever Steve Jobs, it's like, oh, no, that guy was. Whatever it is, it's a pale version of what that guy was doing. But anyway, the point being is like, IBM. So by the time I got involved in IBM was like six years later, you know, anyway, yeah, 50 years later after that. And so they were kind of peaking in their power. But what happened was, I remember this because I was there as intern and I was trying to figure out whether should work there after college. And they had a. Their intranet was a mainframe app. And one of the functions was the org chart. And it calculated there were 12 layers of management between me and the CEO, which meant the following. It meant that my boss's boss's boss's boss's boss had a boss, boss, boss, boss before it got to the CEO. And then really what happened? The story of the thing, really what happened was. And I saw this happen. I saw this happen up close. What I saw this happened was each layer of management was lying to the one above it, right? Because each layer wants to look good and wants to whatever, put a little spin on the ball. And if one layer lies to the next layer above it, maybe that's okay. But when that happens two or three times, the lies compound. That happens six times, the lies really compound. If that happens 12 times, the CEO is idea what's happening? Like, absolutely no clue what's going on in the company. Which was the state of play that IBM had, they actually had a term. There's actually a term, they had a whole vocabulary. I mean, this company was like a nation state at the time. You could like live your whole life, like in Austin, Texas, and never meet anybody who didn't work for IBM. Like, it was just like this incredibly, this incredible thing. But they had this concept they called the big gray cloud. And it was literally the cloud of men and gray businesses who followed the CEO around and prevented him from ever talking to anybody who was ever actually doing the work. And so when he would come to visit, it was like a state visit. It was like a visit from the king. And it was like the king and the king and the traveling court. And so it was completely impervious. Mobile to get information through. But I tell that story because that's the polar opposite of the Elon approach, right? And by the way, being the CEO of IBM in 1989 was a great way to live, right? Because it's just like, wow, everybody's bringing me good news all the time. I wake up in the morning and everything is great. And I'm famous and I am rich and I am successful and I've got a chauffeur and I've got a jet and I've got these 80 guys in gray suits who are taking care of everything for me. And I don't have to ever talk to engineers. And this is great until, you know, it's like the turkey on Thanksgiving, you know, until things change and there's a problem and then you have no idea what to do about it, which, which is what happened to them. The Elon approach is the polar opposite of that. And the polar opposite of the approach is literally like, I'm only going to talk to engineers, right? And so when there's an issue, I am going to go straight to the source of truth. And the source of truth is the engineer who actually knows what's going on. And so what Elon, literally, and I've seen him do this, so he literally does, is he goes to whatever when, when there's an issue, one of his companies, he goes to whatever, is the engineer who's working on that problem, and he sits down to engineer and they solve that problem. And like, and I can just tell you, like, the number of CEOs in tech, even the great ones who do that. Like, I mean, almost nobody ever does that. Why does nobody ever do that? Well, first of all, it's just like a giant pain in the ass because, like, your life consists of, like, having to actually solve all these problems. Like, the whole point of being like, big and powerful and successful is you pay people to do that. And now you're doing it and you're in there at like two in the morning doing it, right? Like, it just. This sucks, right? And so, like, most people won't do it. And then the other is you have to. That means the CEO of the company has to have the skill set to be able to do that. So the CEO has to not just be a great CEO, they also have to be like a great technical technologist. Not just that, they have memories of having been a programmer at one point or whatever, a chip designer. Or they can actually sit down with the chip designer right on Thursday night at 2am in Austin and they can actually figure out what's wrong with the chip. And Elon has that ability and he's encyclopedic on every area of technology and is able to go hands on with rocket designers and AI designers and everything in between. And almost no CEO. CEO has that, but that's literally what he does. And then the way that he thinks, the way that he thinks about it, I think is basically he runs whatever six companies he wants or something. And it's like basically in any given week, he thinks about everything as a production, basic production line, production process. He's actually like an old school industrialist. So everything's like a production process. And then any given week, in any production process, there's always a bottleneck. So there's always the thing that is slowing down the process the most and that's always one thing. So what he does for each of his companies is he identifies what he charts. He literally maps out the production process. He literally has these monitors where he has the whole thing laid out. And then he basically says, okay, this is the issue that's holding up production this week. And then he goes and he works with and that's the thing that he goes to work with the engineer on is he goes to fix that bottleneck. And he does that every week for every company, right? And so think about what that this is why Tesla is smoking. The is like has been so much dramatically outperforming the rest of the auto industry is because Tesla, he's fixing the critical production bottleneck at Tesla 52 times a year himself. I can tell you what the CEO of the legacy automakers are doing. They're not doing that. That is not what's happening. In contrast, a normal company, it might take six months to solve these problems. And Elon's fixing it right now, tomorrow. Let's go fix it right now. And so he just runs this loop over and over again. He's just, just, he's absolutely indefatigable. I offered he famously, for a while he had sold all of his houses and he was literally cuff surfing. You know, it's one of the most successful people on the planet. And so I have a vacation house. And I offered him, I said if I take a week and use the vacation house and whatever, take the kids, feel free. And he'd sit back five minutes later, it's like, you know, whatever, 11 o' clock at night. Forward response. I don't take vacations. Right. Which again, it's like there's no CEO like this. The whole point of being a CEO is you get to go jet around. And so anyway, so he's doing that and then, and then, you know, and then he turns this into routine. And so, you know, when he does like he does like a day a week at each of his companies and he'll basically do like all day, he'll do like a 12, 14 hour stretch where he'll do design reviews with. But the way that he does it, he does with five minutes per engineer, right? And so he does 560 divided by five. It's been way too long in this podcast. How much is that? 12.