High Performance Organizations Reading List
Everyday Astronaut&#x27;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:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=t705r8ICkRw&amp;t=13m30s" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=t705r8ICkRw&amp;t=13m30s</a><p>Here&#x27;s a rough summary:<p>1. Make requirements less dumb.<p>2. Delete part or process steps. If you&#x27;re not occasionally adding things back (he says 10%) (ideally in improved versions), you&#x27;re not removing things often enough.<p>3. Simplify, optimize, solve. Everyone&#x27;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&#x27;t be dealt with as-stated.<p>4. Accelerate process<p>5. Automate<p>Those tend to blur together at the edges. I&#x27;m sure if he formalized this and wrote it down for mass consumption it&#x27;d be presented differently, but it&#x27;s his current mental model.<p>Process testing - remove unnecessary in-process testing after production line debugging is done.  Obviously there are nuances, he&#x27;s not saying to do no in-process testing, but rather to remove testing which was intended to reveal information once that&#x27;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&#x27;s important to understand the context. The part about part&#x2F;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.