Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

🚀 What if the exact same 5-step algorithm Elon uses to build Starships and revolutionize manufacturing could completely transform how you approach challenges in your own life? In this powerful clip from @EverydayAstronaut’s unforgettable Starbase tour with Elon Musk, he walks through his legendary process in detail — question...

13,249 Aufrufe • vor 27 Tagen •via X (Twitter)

0 Kommentare

Keine Kommentare verfĂźgbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

Elon Musk explains his 5-step process for running companies: "First, make your requirements less dumb. Your requirements are definitely dumb. It does not matter who gave them to you. It's particularly dangerous if a smart person gave you the requirements because you might not question them enough. Everyone's wrong no matter who you are. Everyone's wrong some of the time. So make your requirements less dumb. Then try very hard to delete the part or process. This is actually very important. If you're not occasionally adding things back in, you are not deleting enough. The bias tends to be very strongly towards let's add this part or process step in case we need it. But you can basically make in-case arguments for so many things and for a rocket that is trying to be the first fully reusable rocket. There's never been a fully reusable rocket. People don't understand. This is like the holy grail of rocketry. So you've got to delete the part or process step. Super important. You can't hedge your bets. That's why the grid funds, for example, do not fall down because that's a whole extra mechanism that we don't need. Also, whatever requirement or constraint you have, it must come with a name, not a department. Because you can't ask the department. You have to ask a person. That person who's putting forward their requirement or constraint must agree that they must take responsibility for that requirement. Otherwise, you can have a requirement that basically an intern two years ago randomly came up with off the cuff and they're not even at the company anymore. These things are often just way more silly than you think. So step one, make your requirements less dumb. Step two, delete the part or process step. If you're not adding things back in 10% of the time, you're clearly not deleting enough. And then only the third step is simplify or optimize. The third step, not the first step. The reason it's the third step is because possibly the most common error of a smart engineer is to optimize a thing that should not exist. Everyone's been trained in high school and college that you've got to answer the question. Convergent logic. So you can't tell the professor your question is dumb. You'll get a bad grade. You have to answer the question. So everyone's basically, without knowing it, they've got a mental straitjacket on. They'll work on optimizing the thing that should simply not exist. And then finally, you get to step four, which is accelerate cycle time. You're moving too slowly, go faster. But don't go faster until you have worked on the other three things first. You can always make things go faster. And then the final step is automate. Now, I've personally made the mistake of going backwards on all five steps multiple times. Literally, I automated, accelerated, simplified, and then deleted. One example I've talked about before is there were these fiberglass mats on top of the Model 3 battery pack that were in between the floor pan and the battery. And it was at one point choking the battery pack production line. And I was basically living on the battery pack production line trying to fix the line. It was choking the entire Model 3 production program. So the first mistake was I tried to fix the automation, like make the robot better. So automating was a mistake. Then accelerating was a mistake. Then optimizing was a mistake. And finally, I said, what the hell are these mats for? And I asked the battery safety team, what are these mats for? Are they for fire protection or something? They said, no, they're for noise and vibration. Then I asked an NVH, a noise, vibration, harshness team, what's it for? They said fire safety. So literally, it was like being in a Dilbert cartoon. Actually, I feel like I'm in a Dilbert cartoon quite frequently. So then finally, OK, great, let's try a car with the fiberglass mats and without. And they put a microphone to both and see if you can tell the difference. In fact, I was like, which one is which? So we just deleted them and just bypassed this $2 million robot cell. It was just a complete pile of nonsense."

Founder Mode

73,366 Aufrufe • vor 4 Monaten

we all dream of those big wins in life the 100x, the multi-million dollar trade, or even just 10x of what you started with in 7 days i’ve been fortunate enough to experience a few of those over the past few years, and the reality is when you do win big, it doesn’t feel like it at all it hits for a split second, and then your brain just normalizes it it's a part of how to get there in the first place, but makes it a lot easier to lose it if you don't have the right guardrails in place and in that exact moment, you being even keeled doesn’t mean the number in front of you isn’t life changing it is this is where you have to slow down a bit, breathe, settle your mind don’t just roll it into some bullshit take some off the table, step away for a few days if you have to, funny enough, blowing let's say 10k of it on a beautiful trip to tokyo will save you so much because once you actually process what just happened, your future self will thank you for it the truth is, even if you think you’re going for a certain number, the moment you hit it, you’ll want more and more, and more anyone who's been in the same position will tell you the exact same thing ironically the people that win are addicted to winning and if you ask the same people in a year after that big win, what they regret and where are they proud of themselves? they will tell you they regretted rolling it over and giving some/all back or they are proud for switching back on the switch all of this is real, but it’s also exactly how i imagined it would feel years ago before it ever happened manifest your life, the feeling not just the number everything happens twice, first in your mind, then in reality

۟

23,017 Aufrufe • vor 2 Monaten

Q: Why is company culture important? In the clip below, a16z cofounder Ben Horowitz argues that culture drives how people in your company behave on a daily basis—and particularly, how they behave when you’re not looking. Is that phone call so important I need to return it today or can it wait until tomorrow? Can I ask for a raise before my annual review? Is the quality of this document good enough or should I keep working on it? Do I have to be on time for that meeting? Should I stay at the Four Seasons or the Red Roof Inn? Should I go home at 5 p.m. or 8 p.m.? Should we discuss the color of this new product for five minutes or thirty hours? If I know something is badly broken in the company, should I say something? Whom should I tell? Is winning more important than ethics? None of these things are in your mission statement or OKRs, but they determine many important things for your company, such as how people experience your company, what you’re like to do business with, what your company is like to work at, etc. And as Ben describes, what drives the culture is all of the little behaviors and cues people take on: “this is what I have to do to succeed in this company.” Culture can feel abstract and secondary when you pit it against a concrete result that’s right in front of you, but it’s a strategic investment in the company doing things the right way when you are not looking. It’s the set of assumptions your employees use to resolve the problems they face every day. It’s how they behave when no one is looking. If you don’t methodically set your culture, then two-thirds of it will end up being accidental, and the rest will be a mistake. If you’re looking for a more in-depth guide to culture and how to build a great one, I’d recommend Ben’s book: What You Do Is Who You Are.

Michael McGuiness

180,634 Aufrufe • vor 2 Jahren

Revel Founder & CEO Scott Morton spent 9 years working at SpaceX / Starship for Elon Musk: Biggest lesson? "Elon Musk is really good at is asking engineers to go further than they otherwise would have." i.e. Push past the first “no.” - Avoid incremental thinking. - Question every requirement & constraint. - Force one more round of thinking. - Breakthroughs often follow discomfort. Ref: Walter Isaacson's Biography on Elon: “1. Question every requirement. Each should come with the name of the person who made it. You should never accept that a requirement came from a department, such as from “the legal department” or “the safety department.” You need to know the name of the real person who made that requirement. Then you should question it, no matter how smart that person is. Requirements from smart people are the most dangerous, because people are less likely to question them. Always do so, even if the requirement came from me. Then make the requirements less dumb. 2. Delete any part or process you can. You may have to add them back later. In fact, if you do not end up adding back at least 10% of them, then you didn’t delete enough. 3. Simplify & optimize. This should come after step two. A common mistake is to simplify and optimize a part or a process that should not exist. 4. Accelerate cycle time. Every process can be speeded up. But only do this after you have followed the first three steps. In the Tesla factory, I mistakenly spent a lot of time accelerating processes that I later realized should have been deleted. 5. Automate. That comes last. The big mistake in Nevada and at Fremont was that I began by trying to automate every step. We should have waited until all the requirements had been questioned, parts and processes deleted, and the bugs were shaken out.” . . . Scott Morton (Scott Morton) Founder & CEO of Revel (Revel.io) "Oh man, I have so many stories. But actually, there’s a good one here. I think what Elon’s really good at is asking engineers to go further than they otherwise would have. One of the most interesting examples was the first orbital flight of Starship. We had this maneuver to separate the booster from the ship. We called it the “twig snap.” It essentially looked like a twig snapping in space, and it was a very inefficient way to do it. For the next flight, he was like, “We’re going to do hot staging,” which is where you literally start the Starship engines while it’s still connected to the booster and just blast off. Coming out of that, we all thought, “Okay, cool. We’re going to do the same exact conceptual operations for the next flight. Of course. We’re just going to go nail it this time, right?” And he was like, “No, we’re going to do hot staging on the next flight.” I was actually sitting outside. I wasn’t in the Elon meeting, but I was outside. I saw everyone walk out, and they were all just like, “Oh my God. How are we going to do this?” That week, screenshots started getting shot around. I’m sure everyone was thinking, “Oh, this is going to be really difficult.” But then, throughout the course of the week, some really awesome ideas started coming up. It started to look more and more feasible. Then it became, “How would you manufacture this? How would this all go together?” They ended up inventing, just out of nowhere, a new stage that would sit between the booster and the ship called the hot stage. It would take the blast, and then it would get ejected on reentry for the booster. It worked first shot. That’s insane. I just remember the vibes at SpaceX were like, “Oh my… how in the hell are we going to go do this?” But I think the big lesson there, and something I’ve pulled forward to Revel, is that when engineers come to you and say, “Hey, we just can’t get this to work. This is not possible,” you push them and say, “Well, why don’t you spend two more days thinking about it? Let’s see what comes up. And if nothing, we’ll think about it then.” Engineers really underestimate their ability to creatively problem-solve and come up with new ideas they otherwise never would have thought of when they’re presenting what they think is possible in the moment. I’ll say, “Okay.” They’ll say, “This just isn’t working. We don’t think this is a path.” And I’ll say, “Okay, let’s spend one more day thinking about it.” Oftentimes, there’ll be some breakthrough that no one saw coming. I don’t know how someone hasn’t made a movie about this. There are just so many stories. I mean, early Starship, back in the Hopper days, it was like…"

Molly O’Shea

90,303 Aufrufe • vor 5 Monaten