#414 How SpaceX Works

A few years ago, I started working on a book called SpaceX Foundation. A historical account of SpaceX's first decade told through firsthand sources, firsthand sources like Elon's company updates, launch dispatches, internal memos. This is the real-time record of a company that almost died three times and then became the most dominant launch provider on Earth. The gap between SpaceX and everyone else is enormous and widening. Yet most of what's been written focuses on Elon himself, not on the specific methods, cultures and decisions that actually built the company. That is what the book is about. While the book is still in progress, I've been writing an introduction essay as a way to work through the central question, why did SpaceX succeed in ways no one else has been able to replicate? And more importantly, is any of it learnable? The practices that made SpaceX dominant aren't unique to rockets. They're blueprint for building anything hard. That's the introduction to this introduction essay of this book. So the introduction essay is called Adams or Cheap. Process is pricey. What SpaceX teaches us about building hard things. It is written by Max Olson, who is writing that book called SpaceX Foundation. I've read this essay three times. I think it's really good, so I want to go through some of the main ideas with you. And so the essay starts like this. SpaceX has been remarkably open about how they operate. They've been succeeding in public for more than 15 years now, and yet no one has replicated the results. Competitors know their strategy. The engineering philosophy gets explained in interviews, tweets, and factory tours. Many of the ideas aren't even new. Lockheed Skunkworks ran similar approaches 60 years ago. Founder Kelly Johnson's 14 rules read like a SpaceX Operations Manual. The performance gap just keeps getting bigger. In 2025, SpaceX launched more mass to orbit than every other provider on Earth combined. Much more, this is crazy. Every payload from China, Russia, Europe, and all American launchers wasn't even a fifth of what SpaceX put into orbit. They're the only company producing rockets at an industrial scale. A Falcon 9 goes up every two to three days. Competitors manage single digit launches per year. The same boosters have been reused 20 times each. The company has sent astronauts to the International Space Station, the first private company to do so. Starlink, their satellite internet constellation, now has over 9,000 satellites in orbit, the largest in history. Both built and launched by the same company. SpaceX is now the most valuable private company on the planet. Yet the skeptics were confident it couldn't happen. Apollo astronauts Neil Armstrong and Gene Kernen testified for Congress against commercial spaceflight. They said that they thought re-usability is a dream and even if it did work, the market was too small to support the hundreds of launches needed to make re-usability worth it. Elon was described as a software guy playing with expensive toys. The early failures seemed to confirm them. Three Falcon 1 explosions between 2006 and 2008. By September 2008, SpaceX had funds for exactly one more attempt and Tesla was weeks away from bankruptcy. Elon was borrowing money for rent. Then it worked. Flight 4 succeeded and NASA's $1.6 billion cargo contract followed six weeks later. Then came Falcon 9, Dragon, ISS docking, boosters exploding on the pad, boosters landing, crude flights and eventually starship. So is any of this outlier performance repeatable? This is the puzzle. If the strategy is known and the principles are public, what's actually hard to copy? Obvious factors explained some of this, but not enough. And so he goes over some of the factors. The space shuttle retired, creating a gap. This was really good timing for NASA to become SpaceX's biggest customer. But Blue Origin was founded two years earlier and Boeing and Lockheed saw the same opportunity. The grand vision of Boots on Mars attracted missionaries, but ambitious visions are cheap and plenty of founders have them. Elon putting in $100 million bought early runway, but Basel's poured much more into Blue Origin and legacy primes had multiples of this amount. Technology was also getting better, 3D printing, simulation, advanced materials, all commercially available to competitors. These factors are real and none are sufficient. If they explained it, others could have caught up easily, but they're not even close. SpaceX is a hot bed of case study material, engineering, product, finance, strategy, manufacturing, product management, etc. If you're interested in the company, these are all important, but I'm more curious about which are repeatable. The question isn't why did SpaceX succeed? That's too vague to be useful. The sharper question, what can someone building hard things actually take away? And so then Max breaks it down into a bunch of subheadings. The first one is the strategy. What SpaceX has done more than anything is minimize the cost of getting things to space. The vision is humanity expanding across our solar system, but the lever is the cost of moving mass from Earth's surface to orbit and beyond. Everything else, the launches, the landings, the reuse serves that goal. When you study how companies hold advantages over time, consistently being the low cost provider might be the hardest to maintain. The reason is that it has to be baked into everything you do. It cannot be an initiative or an afterthought. It has to shape how you design products, structure the company, and choose what to build. And as you'll see in the book, it all started from the earliest days. Before starting SpaceX, Elon wanted to get to Mars, but he didn't set out to build a rocket manufacturer. In 2001, he tried buying Russian ICBMs to get there, but the Russians quoted him ridiculous prices. So he famously reframed the question from first principles. What is a rocket made of? Aerospace grade aluminum alloys, plus some titanium, copper, and carbon fiber. And then I asked, what is the value of those materials on the commodity market? It turned out that the materials cost of a rocket was around 2% of the typical price, which is a crazy ratio for a large mechanical product. 2%. Your car's raw materials are maybe 20% to 30% of the sticker price. Consumer electronics are similar, but rockets, 98 cents of every dollar, was going somewhere other than what it was made of. Where was it going? Three places it seems. Supplier markups stacking through contract layers, each tier adding 15 to 30% margin. Custom designs that couldn't achieve manufacturing scale, and expendable hardware thrown away after every flight. None of these are the laws of physics. Traditional aerospace treated high costs as fixed constraints. But what if you treated them as variables? How do you actually capture that 98%? I'm reading an early copy of this book called The Book of Elon. It's written by my friend Eric Jorgensen. It would be out in a few weeks. It's about 200 pages of just Elon in his own words, and he was actually talking about another way to think about this, this is what Elon says from this book. How could the Russians build low-cost rockets? It's not like we drive Russian cars, fly Russian planes, or have Russian kitchen appliances. The US is a pretty competitive place, and we should be able to build a cost-efficient launch vehicle. So back to the essay, another subheading, "Rething from First Principles." Start with the actual product. If you accept existing solutions, you accept their cost structure, so rebuild from physics instead. Don't ask what do rockets cost, ask what should rockets cost. Elon eventually named this the "idiot index," the ratio of the actual cost of a part to the cost of its raw materials. If the ratio is high, he says, you're an idiot. Consider the Falcon 1 actuator, a vendor quoted $120,000 in 18 months of development. SpaceX's engineers built it for $3,900. When founding engineer Tom Mueller's team asked about a critical engine valve, the supplier kind of smirked and left, after hearing SpaceX's timeline and budget. Mueller's team made the valve themselves. This pattern repeated across the vehicle. The dragon's capsule docking mechanism was reinvented from off-the-shelf bike shocks and catalog parts instead of adopting NASA's existing design. There are probably a hundred examples like this, most not discussed in public. The philosophy extended to fundamental architecture, SpaceX uses one propellant pair, liquid oxygen, and RP-1 kerosene, across all stages. The Vacuum Merlin engine uses a fixed nozzle extension instead of a deployable one. This is the main point. Fewer moving parts means fewer failure modes means lower cost. Compare this to the Atlas V rocket which uses up to three different rocket types in a single vehicle, each optimized for its flight phase. Elon's response to this was, you've just tripled your factory cost and all your operational costs. And so he continues to give examples of how they think in all these little decisions they're making. The Merlin engine family embodies his trade-off. Russian RD-180 engines cost 20 to 25 million each, while the Merlin 1D production runs around a million. How? SpaceX eliminated Hydrogen's complexity by using kerosene, used regenerative cooling with to fuel itself and optimized for manufacturability over maximum performance. The result was 95% of theoretical efficiency for 80% cost reduction. Merlin's performance is slightly lower but good enough at 120th the cost. But identifying where to cut costs doesn't mean you can actually cut them. You still have to build the parts. Once SpaceX concluded that atoms were cheap and process was expensive, vertical integration followed almost inevitably. That's a great line. SpaceX included that atoms were cheap and process was expensive and so therefore vertical integration followed almost inevitably the next subheading talks about this, becoming your own supplier. If materials are cheap and the taxes all process and overhead, you need to control the process to capture the savings. You cannot negotiate your way to a 10x cost reduction with suppliers who have profits baked in at every tier. So SpaceX became its own supplier. By building 80% of its hardware internally, engines, structures, avionics, software, and key ground systems, SpaceX collapsed the traditional aerospace stack. They outsourced raw materials and commodity parts and make everything else themselves. That's something SpaceX didn't originally set out to do when engineer noted, but was driven by suppliers' high prices. This wasn't an ideological commitment to doing everything in-house. It was the result of suppliers repeatedly quoting prices and timelines incompatible with SpaceX's cost targets. The benefits compound, when several tiers each add 15% margin, total cost multiplies through the layers. A NASA study found SpaceX developed Falcon 9 for roughly 440 million. They estimated the same work with traditional contractors would have cost 3-10 times that amount. Vertical integration also accelerates iteration. Another great line, vertical integration also accelerates iteration. When an engineer needs to change a bracket, weld, or circuit board, the manufacturing engineers in the same building, using the same CAD systems and tooling. Materials, jigs, and processes can evolve together on the scale of weeks, enabling a rapid progression from Falcon 1 to successive Falcon 9 variants, each iteration improving performance and reducing cost without waiting for suppliers to retool on multi-year cycles. But vertical integration creates a new problem. It concentrates fixed costs. If you own the factory, the machines and the staff, you're losing money every second they aren't building something. At the traditional launch cadence of 2-4 vehicles per year, in-house manufacturing is a liability not an advantage. To make the math work, you need volume. Before we get back into this, I want to tell you about the presenting sponsor of this podcast RAMP. One of the main themes in the history of SpaceX is constantly attacking and questioning your costs. RAMP helps many of the most innovative businesses in the world do exactly that. The median company running on RAMP cuts their expenses by 5%. And just like SpaceX has demonstrated a religious dedication to controlling costs, helps increase revenue and pursue opportunities you couldn't otherwise. We see that in the RAMP data too. The median company running on RAMP also grows their revenue by 16%. Many of the top founders and CEOs I know run their business on RAMP. I run my business on RAMP and you should go to ramp.com today to learn how to help your business save time and money. That is ramp.com. So that brings us to the next subheading. Build a platform. The only way to get volume is to standardize. Build a common platform that customers have to adapt to. The existing approach was bespoke vehicles per mission, custom adapters, mission specific modifications, multiple vehicle families. This optimizes each mission at the expense of manufacturing scale. SpaceX bet the opposite. That cost savings from standardization would exceed the value of customization. Yes, customers wanted custom solutions, but they wanted low prices even more. Force them to choose and they will adapt. The Falcon 9 became the industry's Model T, one rocket built in volume, same nine Merlin engines on the first stage, same vacuum Merlin on the second, same structures, same diameter, same aluminum, lithium alloy, same welding methods, same avionics, same ground systems. Even Falcon Heavy is just three Falcon 9 first stages strapped together with a shared upper stage. A scaled variant from the same core, not a new vehicle. SpaceX published a Falcon users guide which defined bolt circles, electrical connectors, and faring environments. Customers designed to SpaceX's spec instead of demanding customizations. Satellite orbits adjusted to Falcon performance curves. This flipped the negotiating power. Instead of aerospace companies serving satellite specifications, satellites adapted to SpaceX capabilities. The economics of manufacturing is what makes this work. Building 40 identical Falcon 9s annually creates automotive style learning curves that are impossible in custom aerospace, as production scales, learning improves and cost declines. How this worked in practice is that every anomaly, where pattern or manufacturing defect, fed back directly to the teams that design the parts. Finally, there's the logical conclusion of standardization, which is reusability. Reusable boosters are still the same Falcon 9 cores. You aren't just building the same model of rocket. You are literally flying the exact same hardware, because every booster was identical, every landing attempt provided perfectly comparable data. If making 40 rockets creates a manufacturing learning curve, flying the same rocket 20 times creates an operational learning curve that's even steeper. The economics are devastating for competitors. Traditional providers launching a handful of custom vehicles per year never accumulate enough data to even start this cycle. And this is so good how maxed ties us all together. You can probably see why all three tactics were necessary. First principles identified the waste. Vertical integration provided the control to eliminate it. Standardization allowed the volume to make that control profitable. And out all three, the system breaks. They work together so that each flight makes the next one cheaper. What does this sound like? A flywheel. Lower cost enable lower prices, which capture market share, which increases volume, which drives cost lower still. The incumbents understood this too late. They optimize components locally. Better engines, lighter materials, incremental gains. ASEX optimized the system for cost, accepting component level compromises for system level dominance. This flywheel relies on high volume. Competitors couldn't even imagine. There was even a market for so many rockets. And they weren't willing to take the risk of spending all the money just to find out. In a world where atoms are cheap and processes expensive, the real innovation was not a single engine or material, but the decision to redesign the entire stack around the economics of cost. But a cost target doesn't build itself. First principle strategy says what to build. It doesn't say how to build it without catastrophic mistakes along the way. Onto the subheading, the engineering. If the strategy is to rethink everything from first principles, how do you actually execute that without major consequential failures? The standard answer is to analyze exhaustively before building. So he's going to describe the standard answer. And I love how he talks about SpaceX literally inverted this. Traditional aerospace follows this path religiously. A NASA report on the commercial crew program noted that Boeing utilizes a well-established systems engineering methodology, targeted at an initial investment in engineering studies, and analysis to mature the system design prior to building and testing. Must be really fun to read these kind of reports. Plan extensively, freeze requirements early, minimize test failures. This is the measure twice cut once approach. SpaceX inverted this. Here's the problem with the traditional approach. You can't think your way to perfect solutions for problems you don't fully understand. That's another bar. Your model is always wrong in the ways you don't know yet. Complex systems have emergent behaviors that only appear when the pieces are actually bolted together. This is the paradox of first principle design. If you're questioning every inherited assumption, which you should, you're venturing into territory where analysis alone can't tell you what works. The physics might be known, but how the physics will interact with your specific materials, your specific manufacturing tolerances, your specific assembly process. That's not something you could derive from first principles. That's something you have to discover. And so what SpaceX does instead is they use reality as their validation tool. The alternative is to use reality as your primary validation tool. SpaceX focuses on rapidly iterating through a build, test, learn approach that drives modifications towards design maturity. Where Boeing invests up front in analysis, SpaceX invests up front in prototypes. The core philosophy is deceptively simple. Failures are data, not disasters. Tight feedback loops lead to a high rate of innovation and adaptation, quickly finding better solutions of what not to do. And it is a tactical advantage. This isn't new. During World War II, the P80 fighter jet went from concept to test flight in five months. In the early 1960s, the SR-71 Blackbird went from idea to roll out in four years. And it's still the fastest man plane ever built. That's nuts. Is that, could that possibly be true? In the early 1960s, the SR-71 Blackbird went from idea to roll out in four years and it's still the fastest man plane ever built. Small teams, fast iteration, real hardware. In a 2021 star-based interview, Elon explained the goal with each star-ship prototype. Push the envelope such that it blows up. That is the end of his quote. That is his whole quote. Push the envelope so it blows such that it blows up. This sounds reckless until you understand what he's actually saying. If the vehicle doesn't fail, you haven't learned where the limits are. Each failure is a precise data point about where reality diverges from your model. How can you reconcile this fail-fast approach with the care that's needed to rely but build things where human lives are on the line? The crucial distinction is between development and operations. SpaceX runs both, but with completely different risk profiles. So for the dragon, it carries crew. It can never fail. So there's large margin of safety, there's exhaustive testing, there's conservative everything. The Falcon 9, which is the operational launch vehicle, it's middle ground. It says, "Ascent can't fail, but some landing attempts are allowed to." And then Starship, which is development, failure is instrumental. And Elon has a quote about this. He says, "Starship does not have anyone on board so we can blow things up. It is really helpful." And this is a good way to think about this. This is the same company, doing two very different things, with two very different groups of people and two very different risk profiles, but they're talking to each other. And so if you go back to their very first four launches, it says, "The contrast with traditional aerospace is stark. In that world, a three failure start may have triggered years of analysis, review boards, and redesigns on paper before the next attempt." At SpaceX, each flight became the next test with fixes incorporated immediately. This pattern continued into Starship. The early integrated flights each ended in rapid, unscheduled disassemblies, which is just their name for explosions. But each came after achieving partial objectives. Such as clearing the pad, passing the max Q, reaching near orbital velocity. Then finally, the famous catch of the super heavy booster, which is the equivalent of catching a 20 story building that's falling from the edge of space. Each subsequent flight incorporated design changes based on telemetry from the previous one, where traditional aerospace might take years to go from flight anomaly to design change, SpaceX was doing it in between flights. Next, subheading, have a high production rate. Iteration only works if you can afford many attempts. This is where SpaceX's hardware rich approach becomes essential. This is what Elon says about this. A high production rate solves many ills. He has said this repeatedly, he continues. Any given technology development is how many iterations do you have and what's your time and progress between iterations? So if you have a high production rate, you can have a lot of iterations. You can try a lot of different things. If you have a small number of engines, then you have to be much more conservative because you can't risk blowing them up. SpaceX builds many cheaper prototypes, hardware rich fleets of test articles. They'd rather have 10 rough versions to blow up than one polished version they're flayed to break. This can lead to specific design decisions like using steam to steal for starship, which is cheap, easy to weld, and can be welded and attent, by the way, instead of carbon fiber, which is expensive and requires giant autoclaves. Vertical integration really helps enable this. When you own the factory, you can build fast without waiting on vendors. When you own 3D printing capability, you can produce parts on an ad hoc basis. When you can manufacture Raptor engines at high volume, losing one to a test failure doesn't set you back months. SpaceX is big into simulation as well. This moves atoms to bits where possible, letting them pre-screen designs before blowing things up. But real tests remain primary. The question being constantly asked is how quickly can it be tested in as real environment as possible? And again, Max does a great job of tying this all together down here. The pieces reinforce each other in a way that's easy to miss. First, principles engineering reduces unnecessary complexity. Fewer parts means each prototype is cheaper to build. Cheaper prototypes mean you can build more of them. More prototypes means faster iteration. Faster iteration means you can push each prototype to failure without being precious about it. More failures means more data. More data means better designs. Better design means even simpler solutions. And the cycle continues. Meanwhile, fail fast iteration extracts maximum information per prototype and per flight. You're not just testing whether something works. You're finding exactly where it breaks. That precision accelerates the next iteration. The strategy, low cost, vertical integration enables the engineering approach. The engineering approach validates the strategy faster than analysis ever could. Traditional aerospace eliminates uncertainty through planning. SpaceX eliminates uncertainty through doing. But the system doesn't run itself. Running an organization that constantly questions requirements, deletes parts, and accepts visible failures requires something that can't be built through iteration. An engineering process that treats failure as data only works if the engineers themselves believe it. A system that pushes to the edge of what's possible only to survive if the people doing the pushing can handle the intensity. The practices described here are the mechanism, but they're powered by something else entirely. And that goes to his next subheading, which is the people. And so max writes, back to my original point, the practices I've described so far aren't secret. So why can't others just copy them? The standard answer is organizational inertia, bureaucracy, risk adversion, et cetera. And yet, there's true to all of these, but it's not the whole story. The answer is that strategy doesn't exist in isolation. The same playbook in a different environment would produce different results or nothing at all. You can't copy strategy without transplanting the conditions that make them work. A fail-fast culture needs people willing to fail visibly. A first principles approach requires people willing to question experts. Skip-level truth-seeking requires people willing to deliver bad news directly to the CEO. The variable I've been circling around is people, not in the bland HR sense of our people are our greatest asset. In the structural sense, who shows up, what they believe, and what behaviors are willing to accept from each other? SpaceX didn't just hire good engineers. It built a system that attracts, retains, and amplifies a particular kind of engineer while filtering out everyone else. The variable starts with Elon. Without him, none of this exists. I don't say this as a hagiography, only in the observation about initial conditions. Someone had to fund a rocket company when the idea seemed crazy. Someone had to decide that colonized Mars was an actual engineering target. I want to call out three factors in particular that were foundational to SpaceX's culture. The first, an ambitious vision that functions as a recruiting filter. Building cities on other planets isn't just aspirational branding. It's a sorting mechanism. The mission attracts missionaries. Engineers who would never work for just another launch company will work brutal hours for a shot and making humanity multi-planetary. When the mission is that clear, prioritization becomes automatic. That's another great line. Every decision has a simple test. Second, constant forcing functions both real and manufactured. I think this part is underrated. Some were genuinely existential, like the 2008 cash crisis when SpaceX had funds for exactly one more Falcon 1 attempt. Others Elon created himself, aggressive public timelines that even he knew were ambitious. Internal do-or-die milestones that felt real even when they weren't legally binding. The forcing function prevents drift. You can't endlessly study when a deadline real or perceived is bearing down. Even an arbitrary deadline is better than no deadline because it forces decisions. Third, direct technical engagement that bypasses organizational filters. Andre Carpathi, who worked for Elon at Tesla, notes that Elon spends about 50% of his time talking directly to engineers, not to VP's summarizing engineering work. This sounds obvious, but it's unusual in the corporate world. The CEO has to trust the CTO who works through layers of managers to enact a vision. Each layer is a hop where information is lost. It's like a game of telephone. By the time the technical reality reaches the CTO, it has been polished, cabiated, and de-risked. It is a summary of a summary with the inconvenient details removed. SpaceX collapses the chain. The CEO, CTO, VP, engineer layers become a single conversation. By talking directly to the engineers, Elon removes the signal loss. They become the source of truth, not the filtered narratives that typically reach the CTO. This isn't just about speed and accuracy, it also allows SpaceX to make bolder technical bets. Elon stays aligned on what is actually possible. A non-technical manager can't tell the difference between a tactically painful path and a strategically necessary one. If your managers tell you a certain chassis design or an engine material is too difficult, and you don't have the technical depth to interrogate them, you have to defer. The decision to use steel for starship over carbon fiber is a prime example. It was highly against conventional wisdom and controversial even within the company. Ultimately, Elon had to understand all the trade-offs himself and make a call. When there's a blocker, such as a rapid reproduction, GPU supply, a regulatory delay, Elon intervenes personally. Personal phone calls to other CEOs. I've heard hilarious stories about that, by the way. Daily updates on the specific constraint until it's resolved. This is the large hammer approach as Carpathi puts it. The hammer only works because the signal is clear. If you don't know exactly where the bottleneck is, you're just swinging in the dark. But Elon alone doesn't explain SpaceX. Plenty of ambitious, technically engaged founders have failed spectacularly in the aerospace. Founders set direction, but it takes more than that to sustain a company. Start with Gwen Shotwell, currently the president of SpaceX and part of the core founding team. She's the one, quote, holding it all together as many belief. But it's a mistake to view her as merely the steady hand who keeps the lights on while the engineers dream. She is the strategic co-architect of the entire system. I wonder if Shotwell does any podcast. If anybody listening to this happens to know her, I'd love to have a conversation with her on my other show, on my new show. So back to that. She's a strategic co-architect of the entire system. In most other companies, the sales and business teams are natural enemies of engineering logic. They promise the customer whatever they want, which creates a very bespoke complexity that the first principles thinking is trying to delete. Shotwell did the opposite. She recognized that for the manufacturing and flyable to work, the market had to be forced adapt to the rocket. She made it so the world's most conservative buyers NASA and the Pentagon would accept a radical new model of standardization. She ensured that every dollar saved by engineering was converted into a dominant market position. She's the reason SpaceX didn't end up as another very impressive, very bankrupt space startup. The combination also worked because of where it happened, Southern California, where aerospace culture runs deep, not just available talent from declining programs, but delineaged back to the early aviation pioneers building flying machines in hangars. That expertise was dormant, buried under decades of bureaucracy. What Elon grafted onto it were Silicon Valley operating norms, flat hierarchy, engineer ownership, permission to walk out of unproductive meetings. From this foundation, specific cultural practices emerged, not values on a poster, actual behavioral memes that spread through the organization, memes that show up in day-to-day decisions about what to build, who gets promoted, and how to respond when rockets blow up. And real quick, before we get back into this, I need to tell you about Vanta. Vanta, Vanta, Vanta helps your company prove you're secure so more customers will use your product or service. You can think of Vanta as you're always on AI-powered security expert who scales with you the more your business grows, the more complex your security needs get, and that complexity can turn into chaos and Vanta helps tame that chaos. Vanta automates compliance, continuously monitors your controls and gives you a single source of truth for compliance and risk. So whether you're a fast growing startup like cursor or an enterprise company like Snowflake, Vanta fits easily into your existing workflows. This allows you to keep growing a company that your customers can trust. Many companies won't sign contracts unless you're certified and this is causing you to lose out on sales. That is why the average Vanta customer reports a 500 and 26% return on investment after becoming a Vanta customer. Automate your compliance security and trust with Vanta. Vanta will help you win trust, close deals, and stay secure, faster and with less effort. Go to vanta.com/founders and you will get $1,000 off that is vanta.com/founders. So Max breaks this down into five separate memes. The first one, meme number one, tip of the spear focus. Always identifying to attack the biggest limiter. Don't spread effort across secondary problems. Laser in on the single constraint that if removed would unlock everything downstream. That is true at every level. Each SpaceX site has a single dominating objective to simplify prioritization. A NASA manager who visited SpaceX observed that when a new problem appears, it looks like a flash mob in the hallway. When a system level bottleneck is identified, it gets disproportionate resources. When Starship development was bottlenecked on Raptor engine production, that became the company's focus. Not propellant loading, not heat shields, not launch infrastructure, Raptors. Elon gave it absolute focus daily updates, memos of the company, resources redirected from elsewhere. Once engine production broke through, attention shifted to the next constraint. The limiter always gets the hammer. Mememember to push through roadblocks. A roadblock isn't a reason it's a problem statement. You're either clear it or you escalate it until someone does. Admitting your block isn't shameful at SpaceX. It's expected. Hiding a blocker is what gets you in trouble. As one engineer described it, solving blockers move the needle forward on several projects. The cultural expectation is honesty about what's not working and the relentless effort to fix it. That's another good line. I gotta repeat that. The cultural expectation is honesty about what's not working and relentless effort to fix it. Memem number three, scrappiness. Cost-sensitive resourcefulness over bureaucratic process. This goes hand in hand with the low cost provider mentality. SpaceX's replacement for NASA's heritage docking system was prototype with bike shocks and catalog parts. Crude prototypes let you test ideas before committing to expensive development. The scrappy approach extends everywhere. Reused test hardware. Hacking tools together. Building ground support equipment from industrial components instead of aerospace grade systems. Small teams build end-to-end instead of handing off between specialized groups. Engineers are expected to design, build, and test what they own. Elon calls the alternative "I've re-tower engineering." Designed something, throw it over the wall, and let someone else figure out how to actually make it. At SpaceX, the person who drew the bracket is the person who welds it. Memem number four, question requirements. Every constraint, customer, regulatory, internal is treated as a hypothesis to interrogate not a fact to accept this is the embodiment of first principle thinking. Here's an example. Falcon 9's grid fins were originally designed to fold like traditional aerospace grid fins. The folding mechanism reduced drag during a cent, which seemed obviously necessary. SpaceX questioned whether it was worth the mass and complexity. Simulation showed fixed fins were acceptable, so they deleted the mechanism entirely. This is what Elon said. The best part is no part. The best process is no process. Engineers are explicitly told that requirements from quote unquote smart people are the most dangerous because nobody thinks to question them. Every requirement must have an owner, a specific person who can defend why it exists. If the owner can't explain it, or the original reason no longer applies, that requirement gets deleted. This turns into Elon's now well-known rule. If you are not adding back at least 10% of the requirements you deleted, you aren't deleting enough. And meme number five, treat everything as learning. Failures and explosions are data for the next iteration not disasters to be concealed. SpaceX published compilation videos titled "How Not to Land an Orbital Rocket." Spectacular drone ship crashes set to music. This isn't just PR. It's a genuine signal that visible failure is acceptable if you extract the lesson. Many would see the early Falcon 9 booster landings as spectacular failures. Rockets exploding on drone ships tipping over, crashing into the ocean. But over time, those iterations produced a landing success rate high enough to support reusing boosters dozens of times. That reusability is what makes Falcon 9 economically dominant. You don't get there without the explosions first. The cultural frame matters. A failed test is only bad if you didn't learn enough from it. These memes reinforce each other and they reinforce the strategy. Vision attracts people who thrive in this culture. The culture then selects for more of the same. High performers stay, others self-select out. Small elite teams maintain by default low performers actively removed rather than accumulated. This is the real moat. SpaceX's cost advantage can theoretically be matched. Their technical innovations can be studied and replicated. But the culture requires rebuilding an organization from scratch. Are you seeing the pattern yet? The entire system reinforces itself, spinning the fly will faster and becoming increasingly hard to copy. It's loops all the way down. And so that brings us to the last subheading feedback loop. So what is actually hard to copy? Strategy identified the waste. 98% of every dollar going down to process instead of atoms. Engineering found the path. Iterate fast and validate using reality instead of thinking your way to perfect solutions. Culture made it move. Question requirements. Fail visibly attack the tip of the spear. Three systems mutually reinforcing. Each turn of the fly will make the next one easier. The answer to what's hard to copy isn't any single tactic. It's that the tactics are a system. Copy one without the others and it breaks down. First, principles designed without vertical integration gives you targets you can't reach. Vertical integration without volume makes your fix cost a liability. A fail fast culture without people who can tolerate visible failures becomes theater. The output isn't just cheaper rockets. The real output is a generation trained to build hard things. Engineers who internalize these memes, question requirements, fail fast, tip of the spear are now scattered across the frontier. Space startups, defense tech, manufacturing automation, energy. The cultural memes are spreading. The lessons aren't trapped inside one company. This matters for anyone trying to build something hard. Working at frontiers creates optionality invisible from the ground. Starlink wasn't in the original vision. It emerged because SpaceX was already there launching so frequently and cheaply that a 9,000 satellite constellation became feasible. Others couldn't see that opportunity because no one else was in a position to take it. When you're at the frontier, possibilities present themselves that don't exist for anyone else. Small groups with the right structure can do extraordinary things. Not brilliant individuals. Structured teams with fast feedback loops, real forcing functions, and cultural tolerance for visible failure. The P80 and 5 months, the SR-71 in 4 years, Falcon 1 to Falcon 9 in 4 years. This has happened before. It can happen again. The lesson isn't be like Elon. Hero worship is the wrong takeaway. One person didn't build starship. The lesson is that structure matters more than the hero. Get the system right and the results follow. If I had to distill to one question, it would be how fast are your feedback loops? How fast can you get to reality? You can see this pattern in every successful frontier tech effort. The common thread is treating reality as the teacher and getting to classes often as possible. And then he describes what the book is going to be. That's the analysis. But analysis is reconstruction. Pattern matching after the fact, shaped by hindsight. It's useful. But it's not the same as watching the system get built, which is what he's doing for the book. What follows is the raw material. The SpaceX company updates over 100 dispatches from 2003 to 2013. The first five years written primarily by Elon. Technical challenges explained in real time. Near death moments, incremental victories that didn't seem incremental at the time. The culture and memes showing up in the language before anyone named them. It starts in May 2002. Elon hires Tom Mueller, a propulsion engineer building rocket engines in his garage on nights and weekends. They incorporate a company called Space Exploration Technologies. And they begin. There's a link down below to read the entire essay. Make sure you add your email so you're notified when the book is available.