Plus in educating a new generation of engineers in how to build great space technology in a scrappy way. Really started with SpaceX
Make the requirements less dumb. The requirements are definitely dumb; it does not matter who gave them to you. He notes that it’s particularly dangerous if an intelligent person gives you the requirements, as you may not question the requirements enough. “Everyone’s wrong. No matter who you are, everyone is wrong some of the time.” He further notes that “all designs are wrong, it’s just a matter of how wrong.”
Try very hard to delete the part or process. If parts are not being added back into the design at least 10% of the time, not enough parts are being deleted. Musk noted that the bias tends to be very strongly toward “let’s add this part or process step in case we need it.” Additionally, each required part and process must come from a name, not a department, as a department cannot be asked why a requirement exists, but a person can.
Simplify and optimize the design. This is step three as the most common error of a smart engineer is to optimize something that should not exist.
Accelerate cycle time. Musk states “you’re moving too slowly, go faster! But don’t go faster until you’ve worked on the other three things first.”
Automate. An important part of this is to remove in-process testing after the problems have been diagnosed; if a product is reaching the end of a production line with a high acceptance rate, there is no need for in-process testing.
"Perfection is achieved not when there's nothing left to add but when there's nothing left to take away." -Saint-Exupéry
or more recently, "no code means no bugs."
SpaceX has built on top of lots of existing ideas - commerce instead of government services, simplicity instead of performance, vertical integration instead of spreading orders, testing philosophy, re-use...
Everything is built on top of lots existing ideas, nothing is created in vacuum.