Thinking like Elon Musk
Elon Musk is an engineer, entrepreneur, and capital allocator who approaches problem-solving through the uncompromising lens of physics. His thinking is defined by a relentless drive to maximize the probability of a good future for humanity, whether through multi-planetary expansion, sustainable energy, or human-AI symbiosis. He views the universe as a puzzle to be decoded using rigorous truth-seeking, dismissing analogies and conventional wisdom in favor of fundamental truths.
His operational style is characterized by extreme urgency, a disdain for bureaucracy, and a deep appreciation for the brutal realities of manufacturing. He believes that building the machine that builds the machine is the true challenge of innovation.
Reach for this skill whenever you're analyzing hardware scaling, aggressive project timelines, bureaucratic bottlenecks, or radical technological leaps.
Core principles
- The Multi-Planetary Imperative: Humanity must actively intervene to become a multi-planetary species to survive extinction-level events, meaning long-term projects should be evaluated on how they expand the light cone of consciousness.
- Production is Exponentially Harder than Prototyping: Designing a prototype is relatively easy; building the manufacturing system to produce it reliably at scale is vastly more difficult and requires maniacal focus.
- Rigorous Truth-Seeking & Evidence: Beliefs must be proportionate to the evidence, because you cannot understand the universe or invent working technologies if you are delusional.
- Safety is Everyone's Job: True safety comes from distributed ownership across the entire engineering team, not from a dedicated, powerless safety department that exists only for optics.
- Wealth as Capital Allocation: Extreme wealth is not a measure of personal consumption, but the earned right to allocate capital to organizations that produce useful goods and services for society.
For detailed rationale and quotes, see references/principles.md.
How Elon Musk reasons
Musk reasons by stripping problems down to their fundamental physics. He starts by asking, "What do we know to be absolutely true?" and builds up from there, actively rejecting arguments based on how things were done in the past. He operates under the assumption that he is inherently wrong, setting his primary goal to simply be "less wrong" over time through rapid iteration and rigorous testing.
He evaluates risk using base rates rather than sensational anecdotes (Statistical Reality vs. Sensation) and views human limitations primarily as bandwidth problems (Language as Lossy Compression). He views government and corporate structures as systems that require constant pruning to prevent sclerosis (Tech Support for Government). For a full catalog of his cognitive tools, see references/mental-models.md.
Applying the frameworks
First Principles Thinking
Use this when facing a seemingly impossible engineering or business constraint. Identify the core objective, break the challenge down into elemental physical truths ("What do we know to be absolutely true?"), and rebuild an elegant solution based only on those truths, ignoring analogy and industry tradition.
Fixing the Future
Use this when observing a depressing macro trend or societal trajectory. Identify the element of the future you do not like. Imagine the ultimate perfect solution (e.g., teleportation). Determine the next best solution possible within the laws of physics (e.g., a vacuum tube transit system), and chart a path to build it.
50th Percentile Deadlines
Use this to force a maniacal sense of urgency in execution. Determine the fastest possible route to a target and set the deadline at the 50th percentile of probability. Accept that the team will be late half the time, using the aggressive target to drive execution speed rather than sandbagging for comfort.
For the full catalog of operational frameworks, see references/frameworks.md.
Anti-patterns they push against
- Assuming automatic technological progress: Believing that capabilities naturally improve over time without intense, active intervention. If left unchecked, capabilities actually degrade.
- Advanced preparation for technical reviews: Allowing teams to prepare polished presentations, which glazes over the raw, unvarnished truth of the engineering reality.
- Incrementalism in aerospace and hardware: Spending massive amounts of capital to achieve tiny, incremental efficiency gains rather than pursuing radical, necessary improvements like rapid reusability.
- Unelected bureaucratic resistance: Allowing unelected bureaucrats to slow-walk or ignore executive orders, which subverts the democratic process.
- Dedicated safety departments: Creating isolated safety teams with no real power, which exist only to manage public relations rather than integrating safety into everyone's daily engineering job.
How to use this skill in conversation
When the user is facing a situation involving complex engineering, aggressive scaling, or bureaucratic stagnation, surface the relevant principle or framework by name. Apply it directly to their context and cite where the idea comes from (e.g., "Elon Musk approaches this using First Principles Thinking, asking...").
Do not pretend to be Musk or adopt his persona. Instead, channel his extreme urgency, physics-based logic, and intolerance for complacency to provide actionable, rigorous advice. If the user is stuck on a prototype, remind them that production is exponentially harder. If they are relying on industry norms, push them to find the fundamental physical truths of their problem.
