Core Musk Methods
Why This Page Exists
The book ends with 69 short Musk methods. This page clusters them into loadable operating principles instead of preserving the long list order.
1. Capability and Responsibility
- Ordinary people can choose extraordinary work.
- Teach yourself aggressively.
- Assume responsibility instead of waiting for permission.
- Work on what matters enough to justify pain.
- Do not give up when the mission is important.
Use when:
The blocker is identity, courage, or ownership.
2. Utility and Creation
- Make useful things.
- Create more value than you consume.
- Build products and services, not only narratives.
- Ask whether the effort improves the product/service.
- Build what should exist, even before consensus forms.
Use when:
The project needs a purpose filter.
3. First Principles and Truth
- Reason from fundamentals.
- Separate physical laws from inherited assumptions.
- Know the theoretical limit.
- Understand component costs and the "idiot index."
- Get direct feedback from reality.
- Smash ego before it blocks correction.
Use when:
The team is copying industry behavior or defending assumptions.
4. The Algorithm
- Question requirements.
- Delete parts and processes.
- Simplify what remains.
- Accelerate cycle time.
- Automate last.
Use when:
Complexity has become the bottleneck.
5. Speed and Constraints
- Attack the bottleneck.
- Do independent work in parallel.
- Use aggressive timelines.
- Track one key metric when possible.
- Move faster through better systems, not chaos.
Use when:
The system is busy but not producing enough output.
6. Teams and Leadership
- Hire for exceptional ability.
- Keep leaders close to the real work.
- Make everyone think like a chief engineer.
- Communicate directly and simply.
- Surface bad news early.
Use when:
The organization is hiding reality behind hierarchy.
7. Failure, Risk, and Persistence
- Test the absurd.
- Treat non-catastrophic failure as learning.
- Fear of failure can create failure.
- Take pain for work that matters.
- Keep humor and play in the system.
Use when:
The team is avoiding the experiment that would reveal truth.
Quick Load Version
Be useful.
Reason from fundamentals.
Delete before optimizing.
Attack the bottleneck.
Move fast with reality feedback.
Build with exceptional people close to the work.
Persist when the mission justifies the pain.