Source
Founders — #415 How Elon Thinks (March 24, 2026) ·
at 30:19 ▸
When this applies
when improving any process, product, or system — in the specified order
The takeaway
Improve any system in a strict sequence — question requirements, delete, simplify, accelerate, automate — because reversing the order causes rework and wasted investment.
Why it works
Each step builds on the previous: questioning requirements prevents optimizing the wrong thing, deletion prevents simplifying something that shouldn't exist, simplification prevents accelerating waste, acceleration prevents automating the wrong process — doing them out of order wastes effort on things later discarded.
One level up
The sequence in which you apply improvement techniques matters as much as the techniques themselves; premature optimization of the wrong target is the costliest mistake.
Where it stops holding
This stops working when requirements are genuinely fixed externally (e.g. hard legal/physical constraints) and can't be questioned, or when speed to market outweighs the cost of skipping deletion/simplification.
Detail
procedure:- 1. Make your requirements less dumb (question who set the requirement and whether it's still valid)
- 2. Try very hard to delete the part or process (target deleting ~10% too much, expecting to add some back)
- 3. Simplify or optimize (only after deletion)
- 4. Accelerate cycle time (only after simplifying)
- 5. Automate (last, only after the first four are done)
rationale: I've personally made the mistake of going backwards on all five steps multiple times — automating, accelerating, and simplifying things that should have been deleted first, requiring literally tearing out hundreds of robots at Tesla.
In their words
The big mistake in the Tesla factories was I began by trying to automate every step. To fix that, we had to tear hundreds of expensive robots out of the production line.