# The Five-Step Algorithm ## Core Definition Elon Musk's systematic framework for engineering and manufacturing optimization, executed in strict sequential order: 1. **Make Requirements Less Dumb** 2. **Delete the Part or Process Step** 3. **Optimize** 4. **Accelerate** 5. **Automate** The sequence is non-negotiable: each step depends on completing the previous one correctly. ## The Five Steps Explained ### Step 1: Make Requirements Less Dumb **Principle**: Question every requirement's validity and necessity before proceeding. - Requirements often come from smart people, making them harder to question - "The requirement is dumb" until proven otherwise - Challenge inherited constraints and assumptions - Ask: "Why does this requirement exist? Who created it? Is it still valid?" **Strategic Value**: Prevents downstream waste by addressing root assumptions first. ### Step 2: Delete the Part or Process Step **Principle**: Eliminate components or steps entirely rather than optimizing unnecessary elements. - If you're not occasionally adding things back, you're not deleting enough - Target: Remove 10% of requirements/parts (if you never add any back, you didn't delete enough) - The best part is no part; the best process is no process **Strategic Value**: Forces systematic simplification before any improvement effort. ### Step 3: Optimize **Principle**: Only optimize what remains after requirements validation and elimination. - Common mistake: optimizing something that shouldn't exist - Optimization effort should focus exclusively on validated necessities - "Don't optimize a thing that shouldn't exist" **Strategic Value**: Ensures optimization efforts create genuine value. ### Step 4: Accelerate **Principle**: Increase speed/throughput only after optimization is complete. - Acceleration amplifies whatever exists - good or bad - Accelerating an inefficient process creates faster waste - Speed comes after validation, elimination, and optimization **Strategic Value**: Prevents amplifying inefficient or unnecessary processes. ### Step 5: Automate **Principle**: Automation comes last, only after the process is validated, simplified, optimized, and accelerated. - Automating a flawed process locks in the flaws - Automation should serve validated workflows, not perpetuate poor ones - "Don't automate something that shouldn't exist" **Strategic Value**: Ensures automation amplifies excellence rather than codifying mistakes. ## The Inversion Problem Most people work this algorithm **backwards**: | Common Approach | Musk's Approach | |-----------------|-----------------| | Start with automation | End with automation | | Optimize existing processes | Delete unnecessary processes | | Accept requirements as given | Question every requirement | | Speed up what exists | Simplify before accelerating | The backwards approach optimizes, accelerates, and automates things that shouldn't exist. ## Cross-Domain Applications ### Technical Projects - Rails modernization: Remove legacy complexity rather than perpetuating it - System architecture: Question inherited patterns before implementing - AI integration: Validate which problems AI actually solves vs. marketing claims ### Strategic Planning - Career positioning: Question default path requirements - Business development: Eliminate unnecessary complexity before scaling - Market analysis: Challenge inherited industry assumptions ### Personal Systems - Household management: Delete unnecessary processes before optimizing - Knowledge work: Simplify workflows before automating - Financial strategy: Question inherited financial "requirements" ## Key Insight > "The simpler system is better" The algorithm systematically drives toward elegance through elimination rather than addition. It transforms complex problems into simple solutions by questioning what's truly necessary versus what's merely inherited. ## Cross-References - **Source Document**: [[Elon Musk Principles]] - **Related Concept**: [[Simplification Before Optimization]] - The core principle underlying steps 1-2 - **Application**: [[Development Philosophy]] - "Bugs as Missing Test Cases" reflects similar systematic thinking - **Framework**: [[Strategic Foundation Framework]] - Systematic capability building on validated foundations --- *Atomic concept extracted December 2025 from Elon Musk's engineering methodology*