Elon's Algorithm

🧠 Free Recall ❓ Quiz 🔍 Cues 🔮 Simulation 🥷 ShadowBox 📐 Encode Cards

1. Question every requirement - Challenge the necessity of each constraint or specification
Meta-Principle: Information degrades through transmission layers. Requirements originate from someone with incomplete information, then get passed through multiple people/departments, each adding interpretation and safety margins. By the time requirements reach implementation, they often bear little resemblance to the actual underlying need.
Tactical Actions: Ask "who made this requirement and why?" Trace requirements back to their source person/customer need. Question whether the requirement addresses a real constraint or an assumed constraint. Ask "what happens if we ignore this entirely?" Challenge safety margins and buffers that may have been added reflexively.
2. Delete any part or process you can - Remove unnecessary steps, components, or processes
Meta-Principle: Complexity compounds exponentially, simplicity compounds linearly. Every additional component creates interaction effects with all existing components (n² problem). Each part has failure modes, manufacturing tolerances, supply chain dependencies, and maintenance requirements. Deletion eliminates entire trees of potential problems.
Tactical Actions: List all components/steps and ask "what if this didn't exist?" Remove anything that doesn't directly serve the core function. Eliminate redundancies and "just in case" additions. Delete so aggressively that you occasionally need to add something back - if you're not re-adding 10% of deletions, you didn't delete enough.
3. Simplify and optimize - Streamline remaining elements after deletion
Meta-Principle: Optimization without understanding creates local maxima traps. Systems naturally drift toward complexity as people add solutions to symptoms rather than causes. Only after understanding what truly needs to exist can you apply optimization energy effectively - optimizing the wrong thing makes it harder to see it shouldn't exist.
Tactical Actions: Map the remaining process/system to understand how components actually interact. Identify bottlenecks and inefficiencies in what remains. Combine steps where possible. Reduce handoffs between people/systems. Focus optimization energy on elements that directly impact the core function.
4. Accelerate cycle time - Speed up remaining processes
Meta-Principle: Feedback loops determine learning rate, learning rate determines competitive advantage. Faster cycles mean more iterations in the same timeframe. Each iteration provides information about what works and doesn't. In complex systems, this learning compounds - insights from iteration N make iteration N+1 more effective.
Tactical Actions: Measure current cycle times end-to-end. Identify the longest pole in the tent (biggest time constraint). Parallelize sequential processes where possible. Reduce batch sizes to enable continuous flow. Eliminate approval delays and review cycles that don't add essential value. Create rapid prototyping capabilities.
5. Automate - Apply automation only after previous steps are complete
Meta-Principle: Automation crystallizes current processes, making future changes exponentially harder. Automated systems become "concrete" and resist change because modification requires reprogramming rather than retraining humans. Automating bad processes locks in badness and makes fixes expensive.
Tactical Actions: Only automate processes that are stable and well-understood. Start with the most repetitive, high-volume, error-prone manual tasks. Build automation with flexibility for future changes. Maintain human override capabilities. Monitor automated processes to ensure they don't drift or optimize for the wrong metrics over time.

Unstarred

Dunk (exclude from study)

Elon's Algorithm

Review Questions

Todos

Sensemaker