The Book of Elon with Eric Jorgenson

What It Covers

David Senra and Eric Jorgenson discuss Jorgenson's book *The Book of Elon*, a curated collection of Musk's most useful ideas in his own words. They examine Musk's five-step engineering algorithm, his mission-driven decision-making across SpaceX and Tesla, how he finds and deploys exceptional engineers, and why manufacturing and product-building represent the highest-leverage work in the economy.

Key Questions Answered

• •Mission-First Company Selection: Musk selects problems based on what needs to exist, not risk-adjusted returns. He started SpaceX because no one else was working on it, and Tesla because he wanted maximum humans driving electric cars. The paradox: working on problems nobody else pursues forces genuine uniqueness, which creates more durable competitive advantage than entering crowded markets with incremental improvements. The question to ask before starting anything is what useful thing you wish existed in the world.
• •The Five-Step Algorithm (in order): Question requirements first — make them less dumb and attach a single person's name to each one. Second, delete aggressively — the best part is no part, the best process is no process. Third, simplify and optimize only what remains. Fourth, accelerate cycle time. Fifth, automate last. Musk repeatedly warns that most engineers jump to steps three through five, wasting enormous resources optimizing or automating things that should have been deleted entirely.
• •Engineering Talent as the Binding Constraint: Musk states capital is not the limiting factor — exceptional engineers are. His hiring method: ask detailed questions about a specific hard technical problem the candidate personally solved, then probe deeply. He biases toward young, unproven engineers and immediately saturates their capacity with accountability. The principle mirrors wartime skip-level promotions — identify competent people and give them more responsibility as fast as possible.
• •Tip-of-the-Spear Focus: Each SpaceX site operates with one single dominating objective to simplify all prioritization. When a new bottleneck appears, resources converge on it immediately — a NASA observer described it as a flash mob forming in the hallway. Musk physically travels to wherever the constraint exists and does not leave until it is resolved. This approach, combined with cross-company resource movement (e.g., Model 3 production expertise applied to Raptor engine manufacturing), compounds speed across the entire organization.
• •Designing Organizations for Small, Fast Failures: Musk sets deadlines he expects to miss 50% of the time — if 100% of deadlines are met, they are set too far out. He tells candidates that if they cannot describe four ways they personally broke something, they were not doing real work. The goal is to engineer the organization to generate small failures cheaply and rapidly, extract the learning, and iterate. Automating or scaling before this cycle runs produces fragility and locks in inefficiency at volume.
• •Time as the Only Non-Replaceable Currency: Musk calculates that a single half-hour meeting at Tesla can shift enterprise value by $100 million when the company generates roughly $300 million per day in revenue. He eliminated his scheduler to maintain complete control over his own time, enabling him to move immediately to the highest-priority problem. He treats equipment and money as scrappable; time is not. Serialized dependencies are avoided by running regulatory, partnership, and product work in parallel despite higher short-term cost.
• •Vertical Integration as Cost and Speed Strategy: Musk traced early rocket costs and found raw materials represented roughly 2% of total price — the rest disappeared through layers of subcontractors. By bringing manufacturing in-house, SpaceX eliminated margin stacking and dramatically shortened feedback loops between designers and production. The same logic drove Tesla's decision to cast entire front and rear underbodies as single pieces, an idea Musk developed after studying how toy cars are manufactured cheaply at scale. Control of the full stack is both a cost strategy and an iteration strategy.