Everyday Astronaut's walk and talk with Elon Musk where he attempts to explain his management process, starts at 13:30 of part 1: <a href="https://www.youtube.com/watch?v=t705r8ICkRw&t=13m30s" rel="nofollow">https://www.youtube.com/watch?v=t705r8ICkRw&t=13m30s</a><p>Here's a rough summary:<p>1. Make requirements less dumb.<p>2. Delete part or process steps. If you're not occasionally adding things back (he says 10%) (ideally in improved versions), you're not removing things often enough.<p>3. Simplify, optimize, solve. Everyone's trained to jump to this because the educational process requires you to answer a question as posed, when often the question is dumb and shouldn't be dealt with as-stated.<p>4. Accelerate process<p>5. Automate<p>Those tend to blur together at the edges. I'm sure if he formalized this and wrote it down for mass consumption it'd be presented differently, but it's his current mental model.<p>Process testing - remove unnecessary in-process testing after production line debugging is done. Obviously there are nuances, he's not saying to do no in-process testing, but rather to remove testing which was intended to reveal information once that's already been collected and addressed. He cautions about false positives from in-process testing, and notes most testing can be done end of line with acceptable results.<p>Finally, it's important to understand the context. The part about part/step deletion in particular, when things get added back 10% of the time, is not appropriate for all development processes. That would have to be adjusted a the specific product and market objective.