elon-musk-thinking
Two pillars: first-principles reasoning + a ruthless engineering algorithm. The discipline is in the order — most teams optimize and automate things they should have deleted.
SKILL.mdskills/elon-musk-thinking/SKILL.md
GitHubElon Musk Method of Thinking
Two pillars: first-principles reasoning + a ruthless engineering algorithm. The discipline is in the order — most teams optimize and automate things they should have deleted.
The Algorithm (5 steps — order matters)
- Make the requirements less dumb. Question every requirement; each must carry a person's name, not a department. Even a smart person's requirements are partly dumb — so interrogate them.
- Delete the part or process. If you're not occasionally forced to add ~10% back, you didn't delete enough. "The best part is no part; the best process is no process."
- Simplify and optimize — but only after deleting. The classic error is optimizing something that shouldn't exist.
- Accelerate cycle time — speed up, but only after the first three. Never accelerate something you should have deleted.
- Automate — last. Automating before deleting and simplifying bakes the waste in permanently.
First principles, not analogy
Boil to fundamentals (physics, material costs) and build up. Use the idiot index — finished-component cost ÷ raw-material cost — to find where you're paying for inefficiency rather than physics. A high index is an opportunity.
Operating corollaries
- Technical managers must have hands-on knowledge — don't manage what you don't understand.
- Beware excess comradery: it makes people stop flagging problems. Make it safe to say "this is wrong."
- Physics is the law; expert opinion and convention are recommendations.
- Set near-impossible targets to force first-principles redesign; tolerate risk; iterate fast on prototypes (fail fast where failure is cheap and reversible).
- Weigh efforts by probability-of-success × importance; take a long time horizon.
Safety-critical caution (important for Nrupal)
The deletion bias is powerful but dangerous in safety-critical systems (his electrical/protection domain). Delete dumb requirements; never delete a protection layer that physics or regulation requires. The "add 10% back" rule exists precisely because over-deletion happens — respect it.
Pairs with first-principles-thinking (the reasoning engine) and operational-excellence-coach (delete waste, but define the process before automating it).